we have about 8 workstations running MS in our network and when I start Microstation V8 2004 on one of the computers in particular, I have no access to the network through the file open dialog. I can see all the drives in Windows Explorer but not in MS.
Any idea why this could be happening?
Are all client computers running the same version of MicroStation V8 (2004)? Version 08.05.XX.XX?
Are all client computers running the same desktop operating system? Windows XP? Windows 7 x64?
What is your server operating system? Windows Server 2003? Windows Server 2008 R2?
If different user logs on to the machine that is not seeing the network drives in MicroStation, do the drives show up then (in MicroStation)?
Are all 8 computers accessing the same workspace - the same way? Local or Networked workspace?
1. We are using different versions of MS on all machines but are slowly moving towards V8i SS2. Strangely, the problem described above only occurs when V8 2004 (08.05.02.56) is started, and only on one or two machines, and only every odd day, which leads me to believe that server hiccups could be causing the problem. Our Admin says it can't be the server and I say it can't be MS so we're deadlocked right now :-)
2. All machines are running XP Professional 32bit
3. Server OS is SBS 2003
4. Good question. Believe it or not, at the moment we don't log into Windows with individual user profiles. Our computers start into Windows automatically. Interesting indeed. Our Admin will set up two new profiles on the problem computers tomorrow and then we can compare.
5. All computers access the same workspace which is located on network drive B for Bentley. I suddenly realise that using a drive called B could also be a problem as this drive letter was tradionally reserved for floppy drives. We will also try a different drive letter to see what happens
I'm wondering if it will help if we move UCF and UPF files to a local directory. Will try this as well.
Looking forward to further input.
Thanks to your questions David, we were able to find the solution. The problem was related to question 4, the login routine. Our admin uses TweakUI to log useres in automatically. On the computers in question, the auto-login somehow misses the network connection part, thus leaving our CAD-STANDARDS drive out of the network all together. Don't quite understand the exact workings but since our admin changed the login from auto to manual, all seems to be fine again.