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,
Once you choose to create a Workspace and are in the dialog box to direct where the Worksets live and make these edits:
Once I hit Ok it crashs
if that pin folder is where your worksets exist (9204,18883, etc...) then there should be a *.cfg and *.dgnws file of the same name listed here. I do not see these in the screenshot. This is where you are telling MicroStation to look.
Afternoon Tim,
The screenshot is of where Workspace "Local C" is directing it's Workset folder location. The Workspace "Network Y" is directing to another Drive altogether. Once I fill out the dialog box to create the "Network Y" Workspace and Click on "Ok" is locks-up and Crashes.
Peace,
where are the CFG and DGNWS files for the worksets ?
Workspace CGF is here: C:\!msCONNECTconf\WorkSpaces
Workset DGNWS and CGF is here: C:\PIN
the CFG and DGNWS files for the Y drive worksets, need to be in the Y:\PIN folder along with the rest of the data. I would suggest putting/moving them there.
With the "Local C" WorkSpace The CFG and DGNWS of the WorkSets are exactly where you would expect them to be C:\pin\ <right-here>. When everything is on the same drive everything goes fine
When I TRY to Create a WorkSet "Network Y" (that is on the C: drive) that directs it's WorkSets to a network drive location Y:\pin\ <right-here>. I press Ok it CRASHES at the dialog box, where you create Worksets.
When I TRY to Create a WorkSpace "NetWork Y"....
I understand what you are "trying" to do.
As a test, try to set one up manually on the network. From the screen shots all it looks like is needed, is placing a CFG and a DGNWS file out there. Copy an existing one and rename it to one of the workset folders you have out there.
Once this is done, load that network workspace configuration and see if the manually created workset shows, and if it does, are you able to open a file and see all the needed configurations.
This is just a test.....
IF you manually put a WorkSet folder and WorkSet cfg and dgnws on the Network Drive location and the WorkSpace is set to look for the WorkSet on the Network Drive. You do this while out of CONNECT. You restart CONNECT it will Crash.