My computers were automatically updated to version 1803 recently, of course without my prior approval. It was a terrible nightmare, thanks to M$. My system ran into chaos. The client computers' CMS failed to start because they could not connect to the server. In fact no computers appeared at the windows explorer page any more. That meant we could not find one another and share files or use others' sharing printers attached to print files. My clinic procedures almost came to a halt. Fortunately one of the client computer had been updated but not yet rebooted. It's still running the old version and thus our work could be carried on temporarily.
More fortunately was that a friendly old client attended me at that damn right time. He is an IT professional and he helped me to solve this emergency.
First of all, after the update. the computers were no longer publicizing their presence in the network. To recover this, two services' startup type need to be set to: automatic (delayed start) for all computers:
1. Function Discovery Provider Host
2. Function Discovery Resource Publication
Open a CMD and type services.msc to get the list of services to edit and enable.
After that the network group was retrieved to a seemingly normal state but the client CMS still could not connect to the server. Eventually we found out that now the Win 10 had become so stupid that we could ping by IP but not by name. Since CMS connects to the server by its host name, it failure is certain. The solution we used was fixing the server name to its IP address.
Open a CMD at the server. Type ipconfig to check its IP. Open a CMD with administrative right at each client computer. change directory to
C:\Windows\System32\drivers\etc, type notepad hosts, edit it by inserting a line:
the host computer’s IP(eg 192.168.1.138) its name(eg master)
and save. Fix the IP address to static as such at the router's control panel. it worked. The system could be run again.
The same worked for network printer by fixing the host's name to its IP.
The HKMA CMS 3.0 is an open-source clinic management system developed by Hong Kong Medical Association. It is cross-platform and comprehensive. I have been using it since 2010. My version is 3.02, WinXP. I have encountered several issues, big and small. Luckily the IT professional from Mobigator, the developer, helped me tackle them all. Since the system is free and you might be operating it on your own, my experience might be a useful reference to you. So I wrote this blog to share with you.
introduction
-
After the automatic update of my Java RE to version 1.6.0_32, the CMS client can no longer connect to the local server. Even the Apache Tomc...
-
I found some error in the databases one day and I tried to fix it by restoring to the previous day's backup. "Failure to restore th...
-
Sometimes you may need to edit the databases. A graphical editor would help. Navicat is the most famous but it is expensive. I found a very...
-
To run HKMA CMS 3.0 smoothly, you need a robust computer. Mine is Sandy bridge quadcore i5 2500, 4 GB ram (only 3.2 GB usable under 32 bit W...
-
One morning, I tried to edit a client but the system failed to save the changes, namely "submission failed". So were all other edi...
-
Talking about free office suite, as an alternative to the costly M$ Office, many people think of Open Office. But it is quite slow to start ...
-
Windows firewall prevents foreign intrusions. However, if you want your client computers be able to connect and access the server, you need ...
-
If the Java runtime autoupdate is not turned off, it will urge you to update from time to time. If you allow it, you may not be able to conn...
-
On designing the drug label, I drew a line separating the header and the content. However when the labels were printed in sequence, the line...
-
The field "Alias" is not only for recording the alternate name of an object, but also rendering you more convenient to search it. ...