Error: “Please start the Integration Engine” when selecting Load Sage CRM Data in Sage 100

Resolution

1. On the Sage 100 server, check the Services list in Windows for the Sage 100 ERP Integration Engine (followed by port ID) and start the appropriate service if it is not running (if it is not installed or missing see related resource “How to manually install CRM Integration Engine”)
2. On the SQL server, check the Services list in Windows for the SQL Server service matching the SQL instance where the CRM database is installed and restart the service if appropriate
3. Set an “inbound rule” and “outbound rule” for Ports 1433 and 1434 on both the workstation and SQL Server
4. In Sage 100, select Customer Relationship Management, Main, CRM Server Options and correct any incorrect information:
5. • •  Integration Server Name: Type the name of the server where the Sage 100 ERP Integration Engine is located
     •  Integration Server Port ID: Type the TCP/IP port where the Sage 100 ERP Integration Engine is running
     • Sage 100 ERP User Logon: Enter the Sage 100 ERP user logon that the Sage 100 ERP Integration Engine will use to communicate with Sage 100 ERP or select the lookup button to list all user logons. The user must have access to the Sales Order, Accounts Receivable, and Customer Relationship Management modules. Enter a logon not used by any other users. It must be used by the Sage 100 ERP Integration Engine only to synchronize data with the SageCRM system
     • SageCRM SQL Server Name: Type the name of the SQL Server where the SageCRM system is installed
       • • • if using a named instance in SQL then the Sage CRM SQL Server Name field must include the Named Instance as well as the SQL Server Name (i.e. SERVER\MYINSTANCE) .
           • Microsoft SQL Server Express installs will need SQLEXPRESS or CRMSQLEXPRESS (depending on the SQL instance that was created) added to the server name
             • • For example: SERVER\CRMSQLEXPRESS
               • NOTE: When Sage CRM is integrated with Sage 100, “Microsoft SQL Server Express is not supported in a production environment” per the Sage 100 Installation Guide section on Installing Sage CRM.
   • SageCRM SQL Database name: Type the name of the SageCRM SQL database to integrate with this Sage 100 company
   • SQL Server Uses Integrated Logon: Select this check box if the SageCRM SQL Server uses integrated Windows Authentication. If the SQL Server uses a separate administrator logon (for example: sa), clear this check box and then type the logon and password at the SQL Server Administrator Logon and Password fields
   • SQL Server Administrator Logon: Type the user logon that is used for administrative access to the SageCRM SQL Server. This field is available only if the SQL Server Uses Integrated Logon check box is cleared
   • Password: Type the password for the SageCRM SQL Server administrator logon. This field is available only if the SQL Server Uses Integrated Logon check box is cleared
   • SageCRM Web Portal Address: the URL linked to the SageCRM software installation. The URL entered at this field is used only when selecting the Launch CRM icon in Sage 100 ERP.
6. Run the Sage 100 ERP Integration Engine as an application (see Related Resource “How to run the Sage 100 ERP Integration Engine as an application”) rather than a service and check that screen for more detailed errors when you select Load Sage CRM Data

• • • • If the Sage 100 Integration Engine application window shows “SA login failed” then confirm the SA user password in SQL Server Management Studio for that SQL instance
      • If the SA user password has special characters then Sage 100 Integration Engine communication may fail – you may need to change the SA user password (see CRM related KB article “You may need to recreate views manually after changing sa user password” in Related Resources).
      • if the error refers to login but not SA login then it may be the Sage 100 ERP User Login being selected in CRM Server Options. Correct any user account issues in User Maintenance in Sage 100 (Library Master, Main, User Maintenance) or select a new Sage 100 ERP user logon
      • If the Sage 100 Integration Engine application window displays “SQL server does not exist or access denied”, confirm that the settings are correct in CRM Server Options (if named instance, then the instance name is included on the SQL Server field). If all correct, there may be a firewall issue including if hosted SQL/CRM then it could be Google Cloud firewall, etc. that is blocking CRM SQL port (default 1433 as mentioned above, SQL Configuration manager will list the TCP port information for the instance)