Troubleshooting Windows Services

Cannot Install or Start a Windows Service

IS2000 can run as a stand-alone Windows application, or as a Windows Service, which is always running and not requiring a user be logged in.

The IS2000 application, when run as a stand-alone program, requires the application to be running at all times and is dependent upon the user that is logged in for security and permissions. However, a Windows Service runs in a more secure environment on Windows and is even more tightly locked down on newer versions of Windows, such as Windows Server 2008 or Windows Vista where several new security features have been implemented in recent service packs.

Service User

Associated with each service installed on Windows is a default user. As an example, by default on Windows Vista a service runs as “Local System”. Related to this user, is certain inherited permissions to be aware of.

  • On Windows XP, the “Local System” service is somewhat restricted in what it can do, whereas on Windows Vista it is very restrictive.
  • Do not set up the IS2000 server that is not available to the user. As an example, if you are setting up the IS2000 application as a network client, make sure that the network IS2000 server is available to all users. If you are running on Vista that means the server would need to be installed not only by the Administrator, but installed with elevated privileges.

Administrative Access

Several Windows features can be an issue when installing a Windows Service. The biggest is not running as Administrator when you install or start a Windows Service. If you are going to use Windows Services, you must be logged in as Administrator. Along with this, there are a couple of other items that may come into play:

  • If you are running inside an active directories domain, group and user policies may prevent you from starting or installing a service. Check your domain server group and user policies, even if you are an Administrator.
  • If you are not running within an active directories domain, but are using group and user policies, make sure they allow services to be installed and started by the Administrator.
  • If you are running on Windows Vista, you must right click on the icon for the IS2000 Configuration Options user interface and select “Run as Administrator” to gain elevated privileges in order to install or start a Windows Service. Once done, you can then go to the Windows Services by clicking on the Windows Start menu, Control Panel, Administrative Tools, Services to manage the services.

Firewall, Network Devices and Port Access

If you are running IS2000 as a service, the user or the application will need to be granted access rights to outbound and inbound traffic for the specific service or port. Generally if the Windows firewall is running the operator will be prompted to grant or deny permissions.

Several different applications can actually cause a problem here, not just software firewalls.

  • Windows Firewall in Windows XP, Server 2003, Server 2008 and Vista all block the installation of a service if the installation is not run as Administrator. On Windows Vista even if you are logged in as Administrator, you have to go one step further. You need to actually right-click on the Configuration icon and select “Run as Administrator”. This will run with elevated privileges, above those of the user “Administrator” and will allow a service to be installed and started.
  • Windows Firewall in Windows XP, Server 2003, Server 2008 and Vista all block port access and the starting of a service if it does any network access. If you are logged in as Administrator and running with elevated privileges, you will be asked to allow this to start. In some cases, depending on your various security policy settings, you may just be denied.
  • Various Windows “Internet security suites”, such as those from Symantec or Norton or MacAfee as part of their Internet anti-virus suite, will block any port access. You may need to add the IS2000 services program as an exception to their “allowed application” lists.
  • Various third party firewalls may also block access to the network port, both inbound and outbound and either the network port will have to be opened or the application added to their application exception list.
  • If your network traffic will be going through various network devices, you may be blocked from any outside port access for those protocols needing it. Check with your network administrator.
  • One other item, if you have any anti-spam or anti-adware applications installed, we have found some that will also watch network port traffic, mimicking a firewall. These likewise may end up disrupting or blocking network traffic for specific ports used.

Service has already been installed

Once the service has been installed and needs to be uninstalled to access the GUI (Graphical User Interface), if the service has not been uninstalled successfully at that time when attempting to install the service again an error message stating the service was not installed successfully may be given.  To uninstall the service complete the steps outlined below:

Step 1: Uninstall the old version (if applicable)

  • Go to “Programs” -> “Administrative Tools” -> “Services”.
  • Find the exact name of the service by performing a double mouse click on the service.  From the General Tab locate the service name, in the example provided here the service name is IS2000.
  • Now bring up a console window so that you can make use of the utility sc or service control command that comes with most new versions of windows. If using Windows Vista ensure you have executed the command prompt with administrative privileges.  To bring up the command prompt click on the Windows “start” -> “run”, then type “cmd” and hit enter.
  • Use the following syntax to remove the existing service named, IS2000.
  • C:\ sc delete IS2000


Windows Services for IS2000 will provide you with an active way to communicate with the IS2000 server. As long as Windows is up, thick / thin clients can use the application with the appropriate network configuration.


  • Make sure you test outside of a Windows Service before running as a Service.
  • Keep in mind what is user specific about your service and what is global. This will also head off problems in advance. Windows Services