Questions

MicroStation

Tags:
+
0 Votes
Locked

MicroStation

carolgray27
We are having some issues with our network set up in regards to MicroStation. MicroStation is opening files at a glacial pace, even taking a long time to start up and get to the MicroStation Manager window.

I would like to know if anyone is having issues with Cisco WAE, Riverbed, etc. devices and MicroStation. Any input in regards to this would be very helpful.
  • +
    0 Votes
    sherlikt

    I haven't got XM deployed all over the network yet, but can open files in other offices via our Riverbed units without any problems. In this case all of XM is in this office, local application, networked workspace, and data in remote site. No time delays other than the first opening of a remote file, subsequent openings using cached data are at local speed.

    +
    0 Votes
    rickantonio90

    We have a very similar setup and everything is working fine. We haven't completely switched to XM, however our users that are on XM say that it is faster than V8 2004.

    +
    0 Votes
    sherlikt

    Have you seen any slowdowns at all? We've noticed some hiccups when writing to your UPF across the WAN.

    +
    0 Votes
    carolgray27

    Hey Guys, Thanks for your input.

    Yes, we have had instances where they have stopped caching. We have had hiccups with Word, Excel, Outlook, MicroStation V8 and XM as well as ACAD. We are using the Cisco WAE units. I too have been trying to complete the XM setup between production and support work. The overall access has been problematic and considerably slower than local. We have also noticed increased slowness in file access

    +
    0 Votes
    loki_the_fiddler

    How have you setup Microstation?
    Have you used microstation to configure it as a network install or have your IT boffins taken a standard install and then networkized it?

    Because that just won't work.
    Microstation needs to be configured for network and then the software is still local.
    Cisco WAE I guess places the software on the network..
    uh-OH! you will then be having a lot of caching over the network too.. all the *.tmp cache files that get created merged deleted every time the dgn cache is written to disk will be on the network.. Doh!
    Not to mention all the on access virus scanning **** the core IT demi gods insist on.

    Only the microstation workspace is designed to be configured to be run from the network.

    The software is meant to run from the local drive.
    It can be configured to run off a network or Projectwise datastore but you really do have to mess around with the temp and local variables. I doubt this has been done.
    Bet you have a default network install and some IT guys figured the software could be placed on the network too.
    I bet when people switch to reference files you get microstation abourts too?
    Typical dgn caching fault if so.
    Enable dgn debuging and check the debug files.
    If you are getting sgn cache errors ..
    that's the problem..

    get the sysmantec utils and look at what files are being opened my Microstation.
    You'll see hundreds of tmp files created in the microstation temp folder which is meant to be local.
    Another thing that can cause this is excessive access scanning.
    Dgn dwg and tmp files in the microstation temp folder don't need to be scanned on read and again on write.
    I have never ever heard of a microstation virus or acad.
    Mind you convincing core IT is never easy.

    Hope it helps.
    Email me if you want more help.

    regards..
    Karsten Evans
    Microstation oldtimer

    +
    0 Votes
    OH Smeg

    So I very much doubt that you'll get any answer.

    Col

  • +
    0 Votes
    sherlikt

    I haven't got XM deployed all over the network yet, but can open files in other offices via our Riverbed units without any problems. In this case all of XM is in this office, local application, networked workspace, and data in remote site. No time delays other than the first opening of a remote file, subsequent openings using cached data are at local speed.

    +
    0 Votes
    rickantonio90

    We have a very similar setup and everything is working fine. We haven't completely switched to XM, however our users that are on XM say that it is faster than V8 2004.

    +
    0 Votes
    sherlikt

    Have you seen any slowdowns at all? We've noticed some hiccups when writing to your UPF across the WAN.

    +
    0 Votes
    carolgray27

    Hey Guys, Thanks for your input.

    Yes, we have had instances where they have stopped caching. We have had hiccups with Word, Excel, Outlook, MicroStation V8 and XM as well as ACAD. We are using the Cisco WAE units. I too have been trying to complete the XM setup between production and support work. The overall access has been problematic and considerably slower than local. We have also noticed increased slowness in file access

    +
    0 Votes
    loki_the_fiddler

    How have you setup Microstation?
    Have you used microstation to configure it as a network install or have your IT boffins taken a standard install and then networkized it?

    Because that just won't work.
    Microstation needs to be configured for network and then the software is still local.
    Cisco WAE I guess places the software on the network..
    uh-OH! you will then be having a lot of caching over the network too.. all the *.tmp cache files that get created merged deleted every time the dgn cache is written to disk will be on the network.. Doh!
    Not to mention all the on access virus scanning **** the core IT demi gods insist on.

    Only the microstation workspace is designed to be configured to be run from the network.

    The software is meant to run from the local drive.
    It can be configured to run off a network or Projectwise datastore but you really do have to mess around with the temp and local variables. I doubt this has been done.
    Bet you have a default network install and some IT guys figured the software could be placed on the network too.
    I bet when people switch to reference files you get microstation abourts too?
    Typical dgn caching fault if so.
    Enable dgn debuging and check the debug files.
    If you are getting sgn cache errors ..
    that's the problem..

    get the sysmantec utils and look at what files are being opened my Microstation.
    You'll see hundreds of tmp files created in the microstation temp folder which is meant to be local.
    Another thing that can cause this is excessive access scanning.
    Dgn dwg and tmp files in the microstation temp folder don't need to be scanned on read and again on write.
    I have never ever heard of a microstation virus or acad.
    Mind you convincing core IT is never easy.

    Hope it helps.
    Email me if you want more help.

    regards..
    Karsten Evans
    Microstation oldtimer

    +
    0 Votes
    OH Smeg

    So I very much doubt that you'll get any answer.

    Col