Is this the SQL version? I ask because the Knowledge Base (it's your friend) has the following:

Description

"The data login failed to open the connection. Details: Database Vendor Code 17" when opening Sage 100 ERP Premium client.

Cause


The Database Server field in Sage 100 ERP Settings Utility contain the wrong server name.


Resolution


For version 4.5

In Windows, select Start, All Programs, Sage, Sage ERP MAS 200 SQL, Sage ERP MAS 200 SQL Settings Utility.
Select EDIT.
Select the Database Server field.
Enter the SQL Server name. (NOTE: it may be necessary to enter SERVERNAME\INSTANCE NAME if SQL is installed on a Separate Server)
Select Apply.
Enter SQL Database Login Credentials.
Select OK.
Select OK on Test Connection Results screen.
Select Close.

For Version 2013

In Windows, select Start, All Programs, Sage, Sage 100 ERP 2013 , Sage 100 Premium ERP 2013 SQL Settings Utility.
Select EDIT.
Select the Database Server field
Enter the SQL Server name (NOTE: it may be necessary to enter SERVERNAME\INSTANCE NAME if SQL is installed on a Separate Server)
Select Apply
Enter SQL Database Login Credentials
Select OK
Select OK on Test Connection Results screen
Select Close

If error continues add a Firewall Inbound Rule for the SQL Server service:

Open port in Windows firewall for TCP Access

Open Administrative Tools, Windows Firewall with Advanced Security console
In the left pane of the console, select Inbound Rules
Right-click select New Rule
Select Port and click Next
In the Protocol and Ports dialog box, select TCP.
Select Specific Port Numbers and then type the port numbers: 1433, 1434
Select Next until get to 'Specify the name and Description of this Rule" screen
Enter name for Inbound Rule (for instance SQL - TCP)
Select Finish

Open port in Windows firewall for UDP Access

Open Administrative Tools, Windows Firewall with Advanced Security console
In the left pane of the console, select Inbound Rules
Right-click select New Rule
Select Port and click Next
In the Protocol and Ports dialog box, select UDP.
Select Specific Port Numbers and then type the port numbers: 1434
Select Next until get to 'Specify the name and Description of this Rule" screen
Enter name for Inbound Rule (for instance SQL - UDP)
Select Finish

Open access to SQL Server when using dynamic ports

Open Administrative Tools, Windows Firewall with Advanced Security console
In the left pane of the console, select Inbound Rules
Right-click select New Rule
Select Program and click Next
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)
Select Next until get to 'Specify the name and Description of this Rule" screen
Enter name for Inbound Rule (for instance SQL - Dynamic)
Select Finish

Yes, it is the SQL version. We are in the process of upgrading from 2013 to 2016 and I am testing everything before the switch over. I did find that in the knowledge base already, but does not seem to help me. I did add the ports to the firewall even though I already have 2013 running and working. I do not see the Sage 100 ERP Settings Utility installed on this computer.

The Sage SQL settings utility needs to be run from the new server. Make sure the MAS_Reports ID is functional.

Are you using the CS-ODBC service? Is that set up on the new server?

Can you print from the v2016 server, and the problem is just the workstation?

The SQL utility does appear to be setup correctly on the server and test connection works.

I do see the Client Server ODBC service running on the server.

Printing on the server the crystal report does load and is working on the server. Just an issue on the workstation.

Reinstall / repair the workstation software. Be sure to use the autorun.exe (to ensure prerequisites are installed) and to Run as Adminstrator. The first time the workstation is run, be sure to Run as Admin then too, so the PU1 files are installed properly.

I had uninstalled and reinstalled using the Run As Admin before, but did not use the Autorun.exe. So I just tried the autorun.exe with Run as admin and did a reinstall, but still having the same issue.

Yes, unfortunately I can not exactly remember what the solution was.  Since many have answered my questions here I am kicking myself for not posting the solution back then.  We were not only upgrading from 2013 to 2016 but also putting in on a new server so some of the problems and solutions for them have all become a jumble in my head.

Here are a couple things that had to be done to get some things working but for what exactly I don't remember.  The settings in the "Application Server Configuration" needed to be done again(since we were on a new server) and was initially forgotten about.  We have a couple apps that needed to be setup here too.   Also since I was running both servers at the same time, for testing purposes, they needed to be on different ports.  So there is a  port  setting in the Application Server Configuration and needed to change the port # in the Sota.ini file.  

One issue we did have was that the VI import jobs that were migrated from 2013 to 2016 did not migrate 100%.  They looked almost perfect but if you looked at the queries for them the field names were a little different and it could not be edited and fixed to work.  I ended up recreating it exactly as it was before and they worked only after recreating.

Sorry could'nt be more specific.