I have a DGNLIB that was ported over from V8i to CE that will not let me edit if located on a Network drive. If I copy the .DGNLIB back to my Profile and change the name from UM-menu.dgnlib to Personal.dgnlib all of my customized menu items are editable (BOLD).
Once I take this file and copy it back to my network drive (that I have full permissions on) and rename it back to it's original name and delete my Personal.dgnlib all menu items are grayed out and not editable.
Any ideas? (dgnlib file is attached).
File location Not editable: P:\CAD\Bentley\UMConnectConfiguration\Organization\Dgnlib\Gui\UM-menu.dgnlib
File location fully editable: C:\Users\mitil\AppData\Local\Bentley\MicroStation\10.0.0\prefs\Personal.dgnlib
2843.UM-Menu.dgnlib
Off network named UM-menu.dgnlib:
Same file on local C: drive named Personal.dgnlib:
Do you also have the network location as part of the MS_GUIDGNLISTLIST ?
Yes, If I didn't I wouldn't even be seeing the customization...
Mark Itil
University of Michigan
CAD Manager and UofM Site administrator
Thank you for covering the installer part, Marc! The screen can be accessed when clicking [Configure] button which locates upper right hand corner as soon as the installer pops up.
As Marc mentioned, your UNC path does not need to have three slashes. I have confirmed the setting if you did not use the Custom Configuration option during the installation. Here enclosed an image for reference.
Regards,
Hyung
Here is my modified Configurationsetup removing the 3rd backslash. When I open the UM-Menu.dgnlib the menu modifications are still gray. I'm lost as to how your getting this to work.
I GOT IT! Here is the problem. We are configuring Microstation with UNC paths. HOWEVER. We do have a network drive mapped to the location in our group. When I go to edit the DGNLIB file I am opening it from a mapped network drive and is NOT editable.
When I open the file from a direct UNC path it is indeed editable.
I assume this is still something that should be addressed and fixed. Now that I know I can edit the file in it's network location by mapping a UNC path I can continue to function. Please verify and file a Defect if you would. Thanks to everyone!!!
Mark Itil said:When I go to edit the DGNLIB file I am opening it from a mapped network drive
What are the steps that lead you to the mapped drive in place of the UNC path?
If you open the file from P:/ when MS_GUIDGNLIBLIST is expecting the DGNLIB to be on the UNC path it's not going to allow editing. The file has to be in a location included by MS_GUIDGNLIBLIST to be editable. I can reproduce this, I think this is expected behaviour.
I mapped a Z:/ drive to the network file location, opening the file from that location reproduces what you see. This is not a defect, there should only be one configured path to a file. If the mapped path was added to MS_GUIDGNLIBLIST the file might be editable but would probably show duplicated tabs on the ribbons (at best; asking the UI to read the same file via different paths might have other undesirable results).
Marc
So now that I understand the issue I have created some workarounds. The problem is that I am configuring Microstation and our Custom interface to be used by multiple groups that don't map the same network drives.
Our group does map network drives. I am opening the file from the P: drive (I was) but the configuration is setup as UNC path. Since the GUI is configured as UNC it should find the configurations and whether I open it by clicking on the P: drive path or map a UNC path to open the file shouldn't matter since the system knows where the file is.
I don't know either if this is a defect or just a W.A.D. Now that I understand why it was going read only I know how to handle it.