How do I fix the "server not responding" error in Legacy?

🔹 Article Title:

“SERVER_NOT_RESPONDING” error occurring in Legacy

🔸 Applicable Device Information:

• Device Type: Pharmacy.
• Software/Firmware Version (if applicable): Legacy.

🔹 Problem Description:

(Brief overview of the issue, when it typically occurs, and any context needed.)

• An error message will generate on the screen saying “SERVER_NOT_RESPONDING.
• Loss of access to the virtual logbook.

🔸 Common Symptoms:

(List of observable signs or behaviors when the issue occurs.)

• “SERVER_NOT_RESPONDING” error message will come up on the screen.

🔹 Common Causes:

(List likely root causes based on previous incidents or manufacturer guidelines.)

• Bug within the legacy system that causes this to happen.

🔸 Common Resolutions / Troubleshooting Steps:

(Step-by-step instructions or resolutions. Include preventative actions if applicable.)

1. Have the client log out and then back in.
2. If it is still occurring, do manual powercycle on the machine and login again.

🔹 Escalation Criteria:

(When to escalate the issue to Development or Implementation team.)

• Issue persists after all troubleshooting steps have been attempted.
• Customer workflow is at a standstill.

🔸 Related Documentation or References:

(Links or titles of user manuals, service bulletins, or SOPs.)

🔹 Last Updated By:

• Name/Role: Amber Schauer, Clinical Support Specialist
• Date: 05/14/2025
• Version: 1.0