Good Afternoon,I am trying to configure CONNECT so that I can keep the Workspaces on the local drive but to direct the child Worksets to a network drive. That way the standards (and any resource files) are local but the drawings can be accessed by all on the network.
The custom location of the WorkSpaces are here: C:\!msCONNECTconf\WorkSpaces (See Custom Folder in screenshot Workspaces.png)
I can create the WorkSpace for the Local Drive (See screenshot CONNECT_Open 2.png)
Afterwards I can create the WorkSpace for the Y:Drive / network drive and create a WorkSet and even a dgn within it, and everything appears normal in the current session of CONNECT, but once I Close CONNECT and try starting CONNECT, it will crash.This what I have for the "Local C.cfg" file:
_USTN_WORKSPACEROOT = $(_USTN_WORKSPACESROOT)$(_USTN_WORKSPACENAME)/_USTN_WORKSPACESTANDARDS = $(_USTN_WORKSPACEROOT)Standards/_USTN_WORKSETSROOT = C:/PIN/_USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSROOT)/
MS_MACRO > $(_USTN_WORKSPACESTANDARDS)Macros/MS_VBASEARCHDIRECTORIES > $(_USTN_WORKSPACESTANDARDS)Macros/_USTN_WORKSPACEDESCR = Workspace used to direct to proper drive
And this is what I have for the "Network Y.cfg" file:
_USTN_WORKSPACEROOT = $(_USTN_WORKSPACESROOT)$(_USTN_WORKSPACENAME)/_USTN_WORKSPACESTANDARDS = $(_USTN_WORKSPACEROOT)Standards/_USTN_WORKSETSROOT = Y:/pin/_USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSROOT)/
MS_MACRO > $(_USTN_WORKSPACESTANDARDS)Macros/MS_VBASEARCHDIRECTORIES > $(_USTN_WORKSPACESTANDARDS)Macros/_USTN_WORKSPACEDESCR = Workspace directs to Y drive
Is there some trick I am not aware of when creating a configuration in this way?Thanks for your Help and your time,
you also have a forward slash at the end of the _USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETSROOT)/ line. In the previous variable definition, it is already pointed to a folder, so the forward slash on the DGNWSROOT should not be needed.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Good Afternoon Tim,
The company's Standards are kept at the Organizational level which would be everyone's PC. So the two Workspace configurations have very little in them except direction on where their child Worksets are located. Workspace "Local C" has its Workset location under the "Pin" folder on the "Local Drive / C". Workspace "Network Y" has its Workset location under the "Pin" folder on the "Network Drive / Y".
Thank you for your time,
crash with no exception log created ?
Nope
not sure what you are missing.
I can get the scenario to work.
If you look at the screenshot you can see I have a local workspace, and a networked workset.
I made a copy of one of my local workspaces and renamed it "test workspace" along with a copied config file (which was also renamed to match). I then edited the config file and only added the _USTN_WORKSETSROOT = Z:\Temp\Tim_H/ line. I then copied an existing workset out to my "temp" folder on my Z drive along with the config file and DGNWS.
I started MicroStation and selected the workspace, which in turn showed me the workset. I selected the workset, and then a DGN file to open. It opened, and then I created the screenshot of "about configuration" to show it working.
I just created a workset from the UI with it located out on my network with no issues.
Is it possible that you have a syntax issue or possibly misnamed something ?
Or maybe something wrong with the WorkSpace Dialog box where you set the location of the various files?
I created a new folder on my network and it was empty. I then started Connect Edition. At the start dialog I selected my local workspace. I then selected create workset. In the dialog that opened, I keyed in my new workset name, gave it a description and then selected the browse button for the root folder and picked the empty folder out on my network. Doing this filled in the rest of the options (design files, standards files and standards subfolders). I selected ok and it created the workset. Now since the DGN folder was empty, I had to create a new DGN file. I did this, and then entered the file.
It works for me - I am not able to reproduce the issue. Either doing it manually or thru the dialog.
So Let me get this Straight:
1. You didn't create a second WorkSpace that directs to the Network Drive?
2. You created a second WorkSet within your Original WorkSpace which directs this empty dgn folder on the Network Drive?
Because if the above is true that is not what my problem is.
I looking to create TWO WorkSpaces
One with WorkSets on the Local Drive
One with WorkSets on the Network Drive.
I used the same method that you used to place the Workset on the network and it did work for me. It is possible that something is not working correctly with your install of MicroStation but MicroStation is capable of doing what you are trying to accomplish. You can try running a repair of your MicroStation installation. I would also suggest that you try creating the workspace and workset from a different computer. That will determine if something is wrong with the installation of MicroStation on your computer.
You said, “The company's Standards are kept at the Organizational level which would be everyone's PC”. Most companies prefer to keep their Organizational level standards on the network. If you need to make a change to the standards (add a level to a level library or make a change to a text style), if the standards are local, you need to make the change to every computer running MicroStation. If the standards are on the network, you make the change on the network and everyone gets the change. It is much easier to maintain. You can also make the folders read-only if you wish.
I did create a second workspace to look at the network worksets. As a matter of fact I have 4 different workspaces. One of which is pointing to my network for its worksets - which is what the screenshots show. It is loading my workset *,cfg file off of the network location.
Answer Verified By: Grot