I have a user who has our proprietary workspace set on their machine. We have it all over the company and it works successfully. Currently does for most as if it didn't we would hear about it from many users.
MicroStation is updated to the most recent version (17). I was able to open MicroStation and manually select the workspace from the list, and sometimes opens with the workspace or crashes with a test file. When using that same file or, especially working files, it says it does not see the workspace and opens in the standard window without the additional tools.Note, this user is remote and has a less than stellar internet connection so maybe it could have to do with their internet speed.
If you need more clarification questions (other than proprietary info of course) I am all ears.Thank you.
(Apologies if this has been asked before but I could not find a suitable previous thread and have not used this forum at much length.
This is really hard to answer without being able to see the workspace. Are they on your network or on a different network? If they are on a different network does you workspace use any UNC network connections they can't make, or reference network drive letters that they don't have a matching drive letter for?
Run a debug on your computer and their computer and compare them to see where they differ.
Instructions on running a debug are here:
How to Quickly Generate a Debug File - MicroStation Wiki - MicroStation - Bentley Communities
They are working remotely connected via VPN. The workspace is hosted on our server as to update any changes to the workspace for everyone who uses it. I am considering copying the workspace locally to his machine and pointing the configuration file to the local directory as opposed to the network.
As far as UNC I am not sure what that is. I don't use the program very extensively myself, just basic IT support of installing and updates, which usually fixes issues. I will try the debug steps and see if there is something there.
a unc is a way to access network resources without needing to use a mapped network drive. They're in the form \\servername\sharename.
Copying the workspace locally would be a good test. We moved all our users to local workspaces as much as possible over Covid office shutdowns.
How did you go running a debug. That should at least show you what is being found and what isn't.
Will be running it this afternoon. We will see what happens then.