DYMO LabelWriter Troubleshooting
1. "No Printer Found": What should I do if the CrisisGo Gatekeeper cannot find my DYMO printer?
When using CrisisGo Gatekeeper, you might encounter errors such as 'No Printer Found' when connecting your DYMO printer to the Gatekeeper. There are several reasons why the Gatekeeper may not find your DYMO LabelWriter printer. Please follow the checklist below step-by-step for troubleshooting.
Step 1: Check the supported models
First, ensure you are using a compatible DYMO LabelWriter that is supported by CrisisGo Gatekeeper. Refer to the Gatekeeper Front Desk System Requirements to check the supported DYMO LabelWriter models.
Step 2: Ensure the DYMO LabelWriter is working properly
Ensure that you have properly set up your DYMO label printer and print a test label directly with the DYMO software before connecting it to the CrisisGo Gatekeeper. You can follow the official DYMO User Guide to finish the setup. To learn more about how to set up the printer properly, refer to How to Set Up My LabelWriter Printer.
Step 3: Diagnose the DYMO service
Then, run the Diagnose Tool provided by the DYMO Web Service and ensure it is running on port 41951. To do this, refer to the official guidance "How to Troubleshoot DYMO Web Service" and find the section titled "Diagnosing the DYMO service". If everything is working correctly, you should see a prompt stating "DYMO Connect Service is running on port 41951".
If the service is not running on port 41951 or you don't see the expected prompt as shown above, or if you encounter errors such as:
None of these ports were configured to use SSL certificate
TrustFailure (Authentication failed, see inner exception)
SecureChannelFailure (Authentication failed, see inner exception)
Could not create SSL/TLS secure channel
The SSL connection could not be established, see inner exception. Authentication failed because the remote party has closed the transport stream.
...
then you will need to troubleshoot with DYMO before using CrisisGo Gatekeeper. For guidance, please refer to the official DYMO troubleshooting resources below.
Basic troubleshooting with DYMO Web Services: How to troubleshoot DYMO Web Service
Advanced troubleshooting steps for the DYMO Web Service, specifically concerning reinstalling the required certificate: How to reinstall the Web Service Certificate
After your troubleshooting, please recheck if your DYMO Web Service is now running on the port 41951.
STOP: Before moving to the next step, ensure your DYMO printer is functioning correctly and the Diagnose tool confirms it's running on port 41951. The CrisisGo Gatekeeper needs the DYMO Connect Service on this default port to detect your printer.
Step 4: Final DYMO service check
Click the button below to verify your DYMO Web Service:
If you see text similar to the example below then you are all set and can proceed to the next step.
<Printers><LabelWriterPrinter><Name>DYMO LabelWriter 550 Turbo</Name><ModelName>DYMO LabelWriter 550 Turbo</ModelName><IsConnected>True</IsConnected><IsLocal>True</IsLocal><IsTwinTurbo>False</IsTwinTurbo></LabelWriterPrinter></Printers>
However, if you see an error page below or any other error messages, there are still issues with the DYMO services, and you will need to return to Step 1 and follow the checklist again, strictly step-by-step.
Step 5: Check CrisisGo desktop app version
STOP: Before you proceed with this step, please ensure that you have passed all the DYMO checks above.
Please ensure that you are using the latest CrisisGo Desktop App, as the Gatekeeper requires version 6.25.0 or higher. If not, please download and install the latest CrisisGo Desktop Apps here.
Finally
After all the checks above, you should be good to go. Please try again with your CrisisGo Gatekeeper. If you are still encountering issues, refer to other related DYMO troubleshooting articles or contact CrisisGo Support for assistance.
You can also go to the DYMO Official Help Center, DYMO Official Software FAQs, and DYMO Official Label Printer FAQs for more information.