Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Firewall Security Manager (FSM) > Error: "Could not access FSM Orion Web Services on port number <>."

Error: "Could not access FSM Orion Web Services on port number <>."

Created by Interspire Import, last modified by Karen Valdellon on Jul 03, 2017

Views: 32 Votes: 0 Revisions: 12

Overview

This article provides possible causes and solutions to the following FSM error:

Could not access FSM Orion Web Services on port number <>.

Environment

All FSM versions

Cause

The following are possible causes for this error:

  • The FSM Web Service is not running.
  • The FSM Web Service is not running on the specified web service port.
  • The specified web service port is blocked.
  • The installer could not determine if FSM Orion Web Services is installed, or could not determine the port.
  • There are permission issues in c:\windows\TEMP.

Resolution

 

  • The Firewall Security Manager Web Service is not running.
    Solution: 
    1. Go to Control Panel > Services.
    2. Start FSMWebService.
       
  • The Firewall Security Manager Web Service is not running on the specified port.
    Solution: The designated port for FSMWebService is 17784. This port is assigned at FSM installation. Uninstall and re-install Firewall Security Manager to resolve this issue.
     
  • The specified web service port is blocked.
    Solution: If the Firewall Security Manager Web Service is running on a remote computer, confirm that there are no network blocks on port 17784.
     
  • The installer could not determine if FSM Orion Web Services is installed, or could not determine the FSM Orion Web Services port.
    Solution: Uninstall and re-install Firewall Security Manager, and then install the Orion Firewall Security Manager Module.
     
  • Permission issues in c:\windows\TEMP
    Solution: Modify the rights to the c:\windows\temp folder with the account that IIS uses for the Application Pool.
Last modified
22:06, 2 Jul 2017

Tags

Classifications

Public