Follow

Troubleshooting DispatchLog

If DispatchLog (sometimes referred to as Realtime Services) is showing error messages or isn’t behaving normally, there could be an issue with the Application Server or Windows Firewall. Below are steps to resolve the most common issues within DispatchLog.

Check the Application Server

Because DispatchLog communicates via Net.TCP to Port 808, you should check to ensure that Net.TCP is enabled on the application server.

  1. Open Services.

  2. Ensure the Net.Tcp Adapter and Net.Tcp Port Sharing Service are started. If they’re not started, right-click their names, then click Start.

Check Net.TCP in Internet Information Serivces (IIS) Manager 

  1. Open IIS Manager.

  2. Expand your local host in the Connections pane.

  3. Expand Sites.

  4. Single-click Default Web Site.

  5. Click Bindings under Edit Site in the Actions pane.

  6. Ensure that tcp 808:* appears here. If it doesn’t, click the Add button. 

  7. Click Close.

  8. Expand Default Web Site in the Connections pane.

  9. Right-click PerspectiveRealTime.

  10. Hover your cursor over Manage Application.

  11. Click Advanced Settings.

  12. Type http,net.tcp in the Enabled Protocols section. Ensure a comma is added between http and net.

  13. Click OK.

Check the Perspective Configuration File

  1. Navigate to your PerspectiveServices directory. By default, the location is C:\inetpub\wwwroot\Perspective\PerspectiveServices.

  2. Right-click the config file.

  3. Click Edit to open the file in Notepad or click Open with… and select Notepad.

  4. Locate the <PerspectiveRealTimeURL> near the bottom of the document.

  5. If the net.tcp URL contains localhost, replace localhost with a valid server name or IP address.

  6. Click File > Save to save your changes.

  7. Close Notepad.

  8. Restart IIS.

  9. Restart Perspective and DispatchLog.

Confirm Net.TCP is Listening to the Correct Port

  1. Open Services.

  2. Confirm that the Tcp Listener Adapter status is Running and the Startup Type is Automatic.

  3. If it’s not Running and/or it doesn’t have an Automatic status, right-click Net.Tcp Listener Adapter, click Properties to change the settings.

  4. Close Services.

  5. Run Command Prompt as an administrator.

  6. Enter the prompt netstat –na | find “808” and press Enter. This will find the specific port that RealtimeServices (DispatchLog) is using.

  7. To view all ports, type netstat –a.

  8. Confirm port 808 is LISTENING.

Check Windows Firewall Rules

    1. Open Control Panel > System and Security > Windows Firewall (if viewing Control Panel in Category view) or Control Panel > Windows Firewall (if viewing Control Panel in Icon view).

    2. Click Advanced Settings.

    3. Check the Inbound Rules and Outbound Rules to ensure Windows Communication Foundation Net.TCP Listener Adapter is Enabled.

      • If Windows Communication Foundation Net.TCP Listener Adapter is Disabled, right-click it and click Enable.
      • If the rule doesn’t exist, click New Rule in the Actions pane to create it.

If you’ve follow all the above steps and DispatchLog still isn’t working correctly, contact Perspective Customer Support.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk