Skip to content
logo Knowledgebase

How to configure Windows Firewall for Sage 100 Advanced and Premium (video)

Created on  | Last modified on 

Summary

How to configure Windows Firewall for Sage 100 Advanced and Premium

Description


Cause


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. 
CAUTION: This solution requires advanced knowledge of your computer's operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions. 
CAUTION: Sage Customer Support does not assist with issues related to third-party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions. Please get in touch with your Sage business partner, network administrator, or accountant for assistance. Please refer to our Scope of Support document for details.

  • Create Inbound Rule for Sage 100 Service
    1. Go to Start, Windows Adminitrative Tools, Windows Firewall with Advanced Options
    2. Right-click Inbound Rules and select New Rule
    3. Select Program on Rule Type screen
    4. Click Next
    5. In the Program dialog box, select 'This program path.' Click the Browse button and browse to your '\...\MAS90\Home\' folder (i.e. C:\Sage\Sage 100 Advanced\Mas90\Home\)
    6. Double-click 'pvxwin32.exe'
    7. Click Next twice
    8. On the Profile screen, select the desired Network Profile(s) to apply settings (Domain, Private, Public)
    9. Click Next
    10. Enter Name and Description for Rule (i.e. 'Sage 100 (10000)')
    11. Click Finish


  • (if applicable) Create Inbound Rule for Sage 100 Advanced C\S ODBC Driver Service
    1. Open Windows Firewall with Advanced Options
    2. Right-click Inbound Rules and select New Rule
    3. Select Program on Rule Type screen
    4. Click Next
    5. In the Program dialog box, select 'This program path.' Click the Browse button and browse to your '\...\MAS90\Home\' folder (i.e. C:\Sage\Sage 100 Advanced\Mas90\Home\)
    6. Double-click 'pvxiosvr.exe'
    7. Click Next twice
    8. On the Profile screen, select the desired Network Profile(s) to apply settings (Domain, Private, Public)
    9. Click Next
    10. Enter Name and Description for Rule (i.e. 'Sage 100 C\S ODBC Driver')
    11. Click Finish


  • Create Inbound rule for SQL Server Instance and SQL Browser Service (Premium only)
    NOTE: Apply the following Firewall settings on SQL Server
  1. Open Windows Firewall with Advanced Options
  2. Right-click Inbound Rules and select New Rule
  3. Select Program on Rule Type screen
  4. Click Next
  5. In the Program dialog box, select 'This program path.' Select Browse and navigate to Instance of SQL Server that you want to access through firewall, and then click Open. (Example: C:\Program Files\Microsoft SQL Server\MSSQL11\Instance_Name\MSSQL\Binn\Sqlserv.exe)
  6. Click Next twice
  7. On the Profile screen, select the desired Network Profile(s) to apply settings (Domain, Private, Public)
  8. Click Next
  9. Enter Name and Description for Inbound Rule (i.e. Sage 100 SQL)
  10. Select Finish
  11. Right-click Inbound Rules and select New Rule
  12. Select Port on Rule Type screen
  13. Click Next
  14. In the Protocol and Ports dialog box, select UDP.
  15. Select Specific Port Numbers and then type the port numbers: 1434
  16. Click Next twice
  17. On the Profile screen, select the desired Network Profile(s) to apply settings (Domain, Private, Public)
  18. Click Next
  19. Enter Name and Description for Rule (i.e. 'SQL Server Browser')
  20. Click Finish


DocLink: How to use PowerShell cmdlet 'Test-NetConnection' to test access to Port on Server?
DocLink: Error: "Connection failure to host: [TCP]::NODELAY;STREAM"
DocLink: Error: “The database login failed. Failed to open the connection. Details: [Database Vendor Code: 17]”

Chat with support