I had Doors 9.6 working on all four computers before upgrading to Windows 10. I upgraded to Windows 10 and now two computers fully function and two get the following error: The specified user certificate could not be found. Doors will now exit.
This issue does not affect RPE in anyway, so it is only Doors that will not function on the two computers. I tried loading from scratch three times, to no avail. ManOfKnight - Tue Mar 28 12:11:50 EDT 2017 |
Re: Doors 9.6 User Certificate Could Not Be Found I don't think it has something to do with certification. Can you compare the registry keys for any difference? There must some difference, right? |
Re: Doors 9.6 User Certificate Could Not Be Found These are sysprepped images that were EXACTLY the same. The DOORS were loaded the same way. Why would two work and two not work? Everything else on the system functions correctly, just not DOORS on two of them. |
Re: Doors 9.6 User Certificate Could Not Be Found ManOfKnight - Tue Apr 04 18:25:23 EDT 2017 These are sysprepped images that were EXACTLY the same. The DOORS were loaded the same way. Why would two work and two not work? Everything else on the system functions correctly, just not DOORS on two of them. Since DOORS works fine in other machines, there must be some problem with either installation or network etc. And seems like the issue you are having can be resolved by reinstalling... Could you try once again reinstall DOORS client? Please make sure all of previous DOORS data is removed and run installation as admin. |
Re: Doors 9.6 User Certificate Could Not Be Found I have uninstalled it numerous times. They are built off the same image. Normally a login box appears when you launch DOORS, these are just erroring instead. Could they be hitting the database and the computer name or something be off and it isn't recognizing the system? I am grasping at straws.
Where in the registry is DOORS hidden? Should I completely uninstall everything? Installation Manager, RPE, everything? RPE works fine. |
Re: Doors 9.6 User Certificate Could Not Be Found OK. So I have narrowed it down to the client_authentication.kdb file. If I rename that, the error changes. NOW for the issue. Even using the backed up version of the client_authentication.kdb file from the Windows 7 backup, it still doesn't work. Nothing has changed, only the fact that it used a sysprepped image of Windows 10. Two systems work fine without bringing in their old kdb files, two systems do not connect at all and receive the error in my first post. All systems functioned before imaging to Windows 10. |