Seriously guys !!!
I was making a new Line style .rsc file and put it in my MS_SYMBRSRC path ... no problems still works like the old days
THEN, I close down OpenRoads Designer and went to rename my resource .rsc file ... then I got this !!!
What the heck is Connect Client doing with MY files .. I have to go to the Task Manager and kill this before I can rename the file !!!! REALLY
Hi Chris,
That folder holds some xmls that the software uses to initialize commands. If you still have the folder that showed this message, you could bit by bit remove content to narrow it down to what exactly is causing the message. From there, we could investigate further.
Holly
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
After deleting all the contents of C:\Users\you user name\AppData\Local\Bentley\OpenRoadsDesigner\10.0.0. and then re-trying to rename my .rsc file I received the same message ... However, all my user pref's where also deleted ... so I went and made a new set of user pref's and ORD made a new folder C:\Users\you user name\AppData\Local\Bentley\OpenRoadsDesigner\10.0.0_1 (version number changed at the end) ... very interesting !!
NOW, the problem has gone away ...... very interesting ... and frustrating .... the proverbial 'needle in a haystack' ..... I'd be interested in any theories !!
Still get the same message:
OpenRoads Designer Connect edition update 2 ver. 10.02.00.60
Connection Client ver. 10.0.10.19
Chris,
Try this, and let me know your results. First, remove the contents located here: C:\Users\you user name\AppData\Local\Bentley\OpenRoadsDesigner\10.0.0. Then, open a dgn in a Bentley delivered workspace. Create the rsc file and locate it to your desktop. Then, do you still get the message? What version of ORD and Connection Client do you have installed?
Hi Holly
Thanks for your reply.
No we are not working with ProjectWise and it is also not a Connected Project.
But the problem still persists ....... I have attached the log file as requested.
Bentley.Connect.Client.exe.log