Issues Related to GPM.NET Service

This topic provides troubleshooting information related specifically to GPM.NET Service issues, including:

Starting GPM.NET Service Fails Because of a Logon Issue

If the following error ("There was an error in finding the GPM.Net Service. No Endpoint was found.") displays in the GPM.NET Status area of the GPM.NET Status window, the GPM.NET Service is not running. The issue might be related to the local security policy.

Resolution: Attempt to start the GPM.NET Service from the Windows Services administration dialog box. If the service does not start because of a logon issue, set the local security policy on your machine to grant permission to your user account to log on as a service, and then start the GPM.NET Service.

  1. Attempt to start the GPM.NET Service.

    1. From the Windows Start menu, type Services.msc in the search box. Click Services.msc in the Programs list.

      The Windows Services administration dialog box appears:

    2. Select Galileo Print Manager .NET Service from the list of services. Click Start the service.

    3. If the following error message appears, continue to the next step. Otherwise, contact Galileo Print Manager.net Technical Support for assistance if a different error message appears.

  2. Set up the local security policy on your machine to grant permission to your user account to log on as a service.

    1. From the Windows Start menu, type Local Security Policy in the search box. Click Local Security Policy in the Programs list.

      The Windows Local Security Policy dialog box appears:

    2. In the left pane, select Local Policies > User Rights Assignment.

    3. In the right pane, double-click Log on as a service from the list of policies.

      The Log on as a service Properties dialog box appears:

    4. Click Add User or Group.

      The Select Users, Computers, Service Accounts, or Groups dialog box appears:

    5. In the Enter the object names to select (examples) text box, type your user account name (last name, then first name). For example, Smith, John.
    6. After typing a user name, click Check Names, and then select the appropriate user account name from a list of names in the system. (The user account name must be one that is in the system.)

    7. Click OK.

      The Log on as a service Properties dialog box re-appears.

    8. Click OK.
  3. To start the GPM.NET Service, repeat steps 1a and 1b.

Only one user can access GPM.net Service Monitor at a time

When GPM.net is installed, by default the GPM.net Service Monitor (TPMServiceMonitor.exe) will be placed in the Windows start up directory C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp. This will automatically start the GPM.net Service monitor anytime Windows starts.

In a Windows server environment multiple users can be logged in to a computer at the same time. It should be understood that the GPM.net Service monitor can only be used to monitor the GPM.net Service by one Windows user on any given computer at a time.

In the event that multiple users run GPM.net Service Monitor at the same time, on the same computer, the second user to start the GPM.net service monitor will not be able to monitor the GPM.net service even though the GPM.net Service Monitor will open. In this scenario the GPM.net Service Monitor will continue to work as designed for the first user.

The second user will see the following Trace Warning “Cannot listen on pipe name ‘net.pipe://127.0.0.1/” because another pipe endpoint is already listening in that name” and the GPM.net service will not function properly.

Due to this it is suggested that if GPM.net is installed in a Windows Server environment the GPM.net Service monitor not be started by default when Windows starts. The automatic start of the GPM.net Service Monitor app can be prevented by removing the GPM.net Service monitor from C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp where it is placed during installation and then only opening the GPM.net Service Monitor as needed from the Windows start menu and then exiting GPM.net Service Monitor when a user is finished with it.

Prevent GPM.net Service Monitor from automatically starting when Windows starts:

Exit GPM.net Service Monitor: