PC-Dmis will not open

[kevinq]

I have 2 operators, both operators have separate logins to the same computer. Operator #1, logs into system opens PC-Dmis, opens programs without any issues. Operator #1 logs out of the system. Operator #2, logs into system no problem, attempts to open PC-Dmis, immediate crash. Operator #2 had no issues the day before. An upgrade was completed a few weeks ago to 2019 R2 SP1. In an attempt to remedy the issue I have tried to reinstall/repair PC-Dmis, as well as completed the upgrade to 2019 R2 SP2. No changes for either operator.

No changes were applied to the computer since the upgrade to 2019 R2 SP1. Probe files are stored on the C drive. Programs are on a shared network, but due to the mix of products programs are run on dedicated machines, so there is never one program open in two different locations. I don’t believe either of these have anything to do with the issue at hand, but thought I would add the information for clarity.

I think there may be a corrupt user file or two for operator #2, but need some help from the masses to what files would need to be deleted.

[Sora5]

I'm not 100% on this, but I don't think you can have multiple operator logged in and be able to both have PCDMIS open. PCDMIS uses certain system resources that if the initial user that first open PCDMIS isn't logged out, then the second user cannot open PCDMIS.

At least, I've never been able to log in with a second user unless the first user Logs Out.

[kevinq]

User's are not logged in simultaneously. Each logs out of the system before the next logs into the system.

[AndersI]

The first thing to check is that the two operators have exactly the same access rights to the file folders and Registry folders that PC-DMIS is using. Appendix B in the ReadMe.PDF in the PC-DMIS installation folder (subfolder /en) explains most of those places.

If that doesn't lead anywhere, you could try running Settings Editor and do a Reset User when logged in as operator #2

[kevinq]

Reseting User did the trick. I will have to remember this for the future! Thank You!

[Peter Fuller]

Sounds like they answered the video driver question wrong and said "Don't ask me again".

[AndersI]

But that doesn't give a crash, just a silent stop.

[Rondog]

Sounds like they answered the video driver question wrong and said "Don't ask me again".

Why is this still something a user can do? Don't allow the check option 'Do not ask again' if not asking the question means you must find and delete a file. Bleh!

I have seen this problem described in this thread at another company (at least it sounds like it). The customer eventually fixed it but I am not sure what they did (they were a bit evasive about describing what they did). What I saw was that you could start up PC-DMIS and create a new program but trying to open an existing program crashed the software 100% of the time. This includes trying to open a program you just created moments prior. I had a look at this problem for maybe 30 minutes or so and couldn't understand why this was happening. It was really odd... It was only 2019 R2 that did this by the way.