Error: "Connection failure to host: [TCP]server:port number:NODELAY;STREAM"

Summary

Error: “Connection failure to host: TCP : : NODELAY : STREAM” occurs when accessing and processing in any application module or task window in Sage 100.

Cause

∙ Firewall rules are not properly set for the Sage 100 program; How to configure Firewall for Sage 100 Advanced and Premium

∙ The service may be corrupt or another application is using the same port number as Sage 100 ERP.

∙ The root cause is often due to a problem with the network environment. The suggested resolutions are potential workarounds.

Resolution

 CAUTION: This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions. 

It is also possible to get “NODELAY;STREAM” error if Sage 100 Application Server Configuration – Server tab – has the “CmdAsUser” checkbox. If this is selected, uncheck this checkbox and select Apply to save the settings and then Exit.

Warning: changing settings may require stopping and starting the Application Server service which would disconnect Sage 100 users.

To resolve these issues, try the following potential resolutions or workarounds. Note: The issue may be due to network/environmental problems, Sage 100 Customer Support cannot guarantee resolution. Sage 100 Customer Support is not responsible for troubleshooting network or environmental issues!

If error occurs with all tasks and the port number in error is random port number from 49152 – 65535, then program process Inbound Rules needs to be created on the Windows Server under Windows Firewall Advanced Security.

∙ Set Inbound Rules

    1. Open Administrative Tools, Windows Firewall with Advanced Security console
    1. In the left pane of the console, select Inbound Rules
    1. Right-click select New Rule
    1. Select Program click Next
    1. Select “This program path:” and browse to \..\mas90\home\pvxwin32.exe (i.e. C:\Sage\MAS90\Home\pvxwin32.exe) on server
    1. Select Next until get to ‘Specify the name and Description of this Rule” screen
    1. Enter name for Inbound Rule
    1. Select Finish

If using the Client/Server ODBC Driver in Sage 100 Advanced, follow the steps below:

  1. In the left pane of the console, select Inbound Rules
  1. Right-click select New Rule
  1. Select Program click Next
  1. Select “This program path:” and browse to \..\mas90\Home\pvxiosvr.exe (i.e. C:\Sage\MAS90\Home\Pvxiosvr.exe) on server
  1. Select Next until get to ‘Specify the name and Description of this Rule” screen
  1. Enter name for Inbound Rule
  1. Select Finish

To remove corruption from the Sage 100 service, disable and reinstall the service. Then create new files:

∙ To uninstall the Sage 100 ERP service:

    1. From the Windows desktop on the Sage 100 server, click the Start button. On the Programs menu, point to Sage Software, and then click Uninstall Application Server Service.
    1. In the Service field, select the service, and then select the port of the service.
    1. Click the Remove button.
    1. Click Yes to confirm.

∙ To reinstall the Application Server Service:

    1. From the Windows desktop on the Sage 100 server, click the Start button. On the Programs menu, point to Sage Software, and then click Application Server Service Setup.
    1. Select the path to the Sage 100 folder
    1. Click OK to add the service.

∙ Note: The service is added based on the settings on the Server tab of Application Server Configuration.

To refresh the Application Server Configuration files in case they were corrupted:

  1. Stop the Application Server and close the Application Server Configuration application.
  1. On Server go to the Task Manager and kill all PVXWIN32.exe’s.
  1. On the Sage 100 server, rename the following files:

∙ ..\MAS90\MAS_System\SY_Console.m4t

∙ ..\MAS90\MAS_System\SY_Workstation.m4t

∙ ..\MAS90\Home\Lib\_Appserv\Locate.pvk

∙ ..\MAS90\Home\Lib\_Appserv\Sessions.pvk

  1. Go to All Programs and find the Application Server Configuration and Open it, once it has created the files you can close it.
  1. Restart the Application for Sage 100 ERP Advanced or Premium

∙ From the Windows Desktop at the Sage 100 ERP server, click Start

∙ On the Programs menu, point to the Sage Software or Sage program folder

∙ Select click Application Server Configuration

∙ Click the Server tab. Clear the KeepAlives check box

∙ Click the Clients tab. On the Re-Connect list, select None

∙ Note: New Locate.pvk and Sessions.pvk files are created when the Application is restarted. If Sage 100 is normally run as a Service, start the Application first and follow the steps above, then make sure at least one user can log in. Then have that user log out and stop the Application, then Start the Service and allow users to log in.)

∙ Note: If there is on-going network corruption, then these refreshed files may become corrupted again.

If problem continues, consider changing the port number:

  1. At the Sage 100 ERP server, set the service to Manually Start.
  1. From the Windows Desktop on the Sage 100 server, click Start. On the Programs menu, point to Sage Software or Sage program folder, then click Application Server Configuration.
  1. Click the Server tab. In the Sockets field, change the socket number to any unused number between 9,000 and 10,000. (If using a firewall, make sure the port is not blocked.)
  1. Click the Start button
  1. If the service starts and runs as an application on the new port number, remove the previous service, and create a new one with the new port number.

∙ Remove the original service using Uninstall Application Server Service.

∙ Create a new service using Application Server Service Setup

If the message is occurring only for specific users:

  1. Have all users exit Sage 100.
  1. Log on to Sage 100 as Administrator.
  1. From Administrative Tools, select User Maintenance.
  1. Select the first user, and click the Preferences tab.
  1. Select the Spawn Tasks from Application Server check box, and click Accept.
  1. Proceed for remaining users.
  1. Click Done.

If Sage 100 Advanced or Premium is running as a Service, try running Sage 100 as an Application instead:

  1. Stop the Sage 100 service (in Windows, Control Panel, Administrative Tools, Services)
  1. On the Sage 100 server from the Windows Task bar, click Start, Program Files, Sage, Application Server Configuration.
  1. Click Start