I want to share some troubleshooting tips I've discovered for issues with the Welch Allyn / Mortara Diagnostic Cardiology Suite after spending several days digging into them. Specifically, I've encountered three main problems: startup crashes, server connectivity issues, and a login crash related to the PGDBInterface. Here's a rundown of each issue along with solutions that worked for me.
1. **Startup Crashes**: When you try to start the CorScribeAppServer service or run the ExamMgrUI.exe, the application crashes. This is due to a bug where it looks for misspelled DLL files. You can fix this by creating dummy files with the incorrect names. Run specific commands in the Command Prompt with Admin rights to create these files in the SysWOW64 directory.
2. **Server Not Available**: Even if the firewall is configured correctly, the client may display "Server not available" because certain config files might default to 'localhost.' You'll need to use PowerShell to update those settings. Make sure you replace 'localhost' and '127.0.0.1' with the actual server's IP.
3. **Login Crashes**: Finally, if you can access the login but get a WCF FaultException, this indicates a database connection issue. Ensure that the DBConnectionString points to the local loopback (127.0.0.1) instead of a network IP. You'll have to modify the server's config file and restart the necessary services.
I have checked everything with the original vendor, but it turns out some software like SentinelOne can interfere with these legacy systems, creating additional hurdles. I just wanted to share so others can avoid the confusion I had!
3 Answers
Thanks for putting this together! I never used this software but your detailed write-up is a lifesaver. Without folks like you sharing their experiences, it would be so hard to troubleshoot these older systems.
It is pretty concerning that the software is looking for those particular DLLs with misspellings. How can something like that even be in production? At least you traced the problems back to SentinelOne—definitely something to keep in mind for legacy systems!
Yeah, right? It just feels risky relying on software that has such obvious typos. Glad you verified the digital signatures and hashes though; that's a smart move!
As a former Healthcare IT staff, I feel this write-up is really well done but probably comes from a misconfiguration. Just a couple of questions: has this setup worked before, or is it a new project? If issues like this happen, I’d generally advise reaching out to the vendor first, and always document everything.
Thanks for the insights! To answer your questions: Yes, it worked previously before we had a leak; now just trying to set it properly. I reached out to the vendor after running into problems but it seemed to go nowhere quickly, so I started tinkering!
I appreciate that! I was really hoping to contribute once I figured things out myself, so it feels great knowing it's helpful.