Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[NSM] Unable to log in to NSM after converting from HA to Standalone



Article ID: KB35003 KB Last Updated: 13 Sep 2019Version: 1.0

This article explains how to resolve the error message "Protocol not available 84001601,"‚Äč which is repeated in guiDaemon.0.


/usr/netscreen/GuiSvr/var/errorlog/guiDaemon.0 shows the following error continuously:

Protocol not available 84001601

Also in guiDaemon.0, you will see during startup that guiDaemon has started in HA mode (log example not available at this time).


This is observed when NSM HA is disabled and the primary server acts as a standalone server.


Check guiDaemon.0 when trying to launch the NSM client. If you observe the "Protocol not available" error repeated in guiDaemon.0, then perform the following steps:

  1. Navigate to the following directory:
cd /usr/netscreen/HaSvr/var
  1. Check for haStatus.txt and remove the file:
rm /usr/netscreen/HaSvr/var/haStatus.txt
  1. Restart the NSM services. For proper order of service restart in NSM, refer to KB11263 - Recommended starting and stopping sequences for NSM services.
  2. Log in to the NSM UI client.

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search