Yes, it is a bit outdated, but still very useful to us. I know this application is no longer supported, but we still use it a ton because of the offline maps feature. The app runs fine when we log into it until the other user logs in for the first time, and then it can no longer be run without crashing. We even configured a new workstation (identical specs) and shipped it out to him, and he is experiencing the exact same thing. Kind of weird maybe that is the way it is supposed to be. Using ProcessExplorer, I determined that Explorer.EXE is the parent process of Streets. When it is run, it looks like Explorer refreshes the desktop because all the icons go away and come back for a split-second. And now we can't run it in our profiles either. But when the other non-privileged user ran it with a clean profile, it has never ran successfully once. When another Admin and I ran it both under our own user profiles, the application ran just fine. He is not a privileged user, so maybe that is part of the issue. But a certain user is having a heck of a time getting it to load. It works on dozens of other computers, even with the same configuration. DLL is causing the problem, but I'd love if someone knew more about this. We haven't found many clues as to why this. Event viewer shows an AppCrash and points to
0 Comments
Leave a Reply. |