AI Assistant
Notifications
Clear all

Carlson - file lock

2 Posts
2 Users
0 Reactions
811 Views
jbstahl
(@jbstahl)
Posts: 1342
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Carlson 2015 Intellicad 64

I'm getting the following error when entering deed descriptions:

[INDENT=1]Loading Carlson Software program files...
Loading Quick Keys...
Carlson 2015, build 150126
Copyright (c) 1989-2014 Carlson Software.
[hl]Command: PDD[/hl]
Pick point or point number:
Exit/Curve/: 100
Varas/Meters/Poles/Chains/: 42.35
Labeling entities
[hl]Waiting 1.5 seconds to obtain file lock...
Waiting 5 seconds to obtain file lock...[/hl]
Error 1: Could not open file: C:UsersJBDocumentsProjDataCarlsonCarlson SettingsProject SettingsKTM1201-Base.crd
It might be read-only or in use by another application.
Error: unable to open file C:UsersJBDocumentsProjDataCarlsonCarlson SettingsProject SettingsKTM1201-Base.crd
Undo/Exit/Curve/Bearing (Qdd.mmss): e
Opened file: C:UsersJBDocumentsProjDataCarlsonCarlson SettingsProject SettingsKTM1201-Base.pdd
Writing deed: 1315465E
Closure error distance> 42.3500 Error Bearing> N
Closure Precision> 1 in 1.0 Total Distance Traversed> 42.350
Command:[/INDENT]
[INDENT=1] [/INDENT]
Anybody have any ideas what the issue is? First time its' happened. Full reboot didn't help.

JBS


 
Posted : July 15, 2015 12:26 pm
RoadBurner
(@roadburner)
Posts: 362
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Not sure if it's related, but I've had .crd files give me trouble caused by file permissions after an IT guy changed my windows user name. I had to take ownership of the files in explorer.


 
Posted : July 15, 2015 6:51 pm