This just started today. A user launches Power InRoads and the Splash Screen appears for a few seconds an then closes and the program never loads. Most of our users use the InRoads tools so much that we only install Power InRoads, but since the Power Platforms are based upon MicroStation, I believe this post belongs here. Besides, most of the InRoads code appears to load after the session opens.
I'm assuming Shortcut is using a -WC switch to load a customised workspace, does the same problem happen without it?
Have you tried running a debug using the shortcut?
is it just one user ? or anyone who attempts to start Power InRoads ?
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
We integrate our workspace into the process so no special shortcut is needed. They never get to the main dialog box to select a file. We use ProjectWise but this user only uses it occasionally. I have suggested a re-install of it as well and asked them to see if they can create an MSDEBUG.TXT file.
I have been asked is there any other log file or diagnostic approach we can take that will report the processes that are loading and any errors that occur.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
So far, it seems to be a single user. I'm having them see if it is local to the PC or only that user on that PC.
You can check the Event Viewer. Event Viewer > Windows Logs > Application. It may be slow loading up. Once it does look for Stop sign icons and check if they are about MicroStation. Sometimes the System log in that same area may have pertinent info (but not usually for an application crash)
For user specific problems like this, i usually double-check the UCF to make sure something hasn't written garbage to it. Rename the user's upf file to let a new one generate. If that doesn't do it, i'll disable our custom configuration completely and run stock to see what happens.
If you suspect the projectwise integration is causing a problem, even if not opening from projectwise, you can check the pwc.log file for error messages.