Win10 updated to v1909, client PC unable to access Medisoft
Posted: Fri Feb 07, 2020 3:06 pm
Starting today (2/07), 1 client workstation will not load the database after logging in to Medisoft. Program worked with no issues prior to the update (2/06 and earlier). After accepting the credentials, the program sits on the Medisoft version window and eventually (after ~1 minute) goes to 0% CPU usage. The full program window never opens.
The only significant change between today and yesterday is 1 client PC updated Windows 10 to version 1909. The 2nd (working) client PC is running Windows 10 v1903.
Office Hours Professional loads with no issues on both workstations.
We're using Network Professional version 21 SP2 (21.2.2.68), installed on a server system with 2 client systems.
Steps taken:
- Reboot workstation
- Reboot server & then both workstations
- Repair installation of Network Professional (NP)
- Try different NP login. Both logins work on working workstation, neither work on problem workstation
- Uninstall & reinstall NP
- Uninstall NP, delete Medisoft folder, reinstall
- Create a new, local admin user. Point data path to empty location on the server. Create a new set of data. Program loads successfully. Close that connection, attempt to change data path back to original database location, problem comes back.
- Turn off all anti-virus and firewall components, including built-in Windows security
The only significant change between today and yesterday is 1 client PC updated Windows 10 to version 1909. The 2nd (working) client PC is running Windows 10 v1903.
Office Hours Professional loads with no issues on both workstations.
We're using Network Professional version 21 SP2 (21.2.2.68), installed on a server system with 2 client systems.
Steps taken:
- Reboot workstation
- Reboot server & then both workstations
- Repair installation of Network Professional (NP)
- Try different NP login. Both logins work on working workstation, neither work on problem workstation
- Uninstall & reinstall NP
- Uninstall NP, delete Medisoft folder, reinstall
- Create a new, local admin user. Point data path to empty location on the server. Create a new set of data. Program loads successfully. Close that connection, attempt to change data path back to original database location, problem comes back.
- Turn off all anti-virus and firewall components, including built-in Windows security