Sage 100

Workstation control panel: repair the two Crystal Reports run-times.

SQL instance firewall should be a program exception, not port (if you have more than one SQL instance on the machine... otherwise port 1433 should work).

In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. 

Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]

@Kevin Moyes ?

1. I ran the repair mode for crystal reports runtime.
2. In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. (When I updated the passwords I made sure I used the SA login to update)
3. Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]  - do you mean change it to IP address when I uninstall and reinstall workstation setup?

The suggestion 3 is the only thing I haven't tried yet. Still doesn't work after suggestion 1 and 2.

Workstation control panel: repair the two Crystal Reports run-times.

SQL instance firewall should be a program exception, not port (if you have more than one SQL instance on the machine... otherwise port 1433 should work).

In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. 

Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]

For #3, I mean in the Sage SQL settings utility.

When printing, Sage passes a connection string in memory to the workstation's print engine, which then accesses SQL data using those credentials.

If you can print from Sage 100 on the server, the MAS_Reports password is fine... and you are probably dealing with a workstation connection issue.

KB
https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=224924150049613&page=1&position=1&q=the%20database%20login%20failed

@Kevin Moyes ?

1. I ran the repair mode for crystal reports runtime.
2. In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. (When I updated the passwords I made sure I used the SA login to update)
3. Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]  - do you mean change it to IP address when I uninstall and reinstall workstation setup?

The suggestion 3 is the only thing I haven't tried yet. Still doesn't work after suggestion 1 and 2.

Workstation control panel: repair the two Crystal Reports run-times.

SQL instance firewall should be a program exception, not port (if you have more than one SQL instance on the machine... otherwise port 1433 should work).

In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. 

Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]

@Kevin Moyes I checked and it pointed to the correct database server. I tried the additional steps in the article and confirmed everything is in place with the rules with the firewall. It's still failing to print and preview the reports from the workstation level. I don't know if this makes a different but because this is a viritual server should I have the IT group reboot this server? 

For #3, I mean in the Sage SQL settings utility.

When printing, Sage passes a connection string in memory to the workstation's print engine, which then accesses SQL data using those credentials.

If you can print from Sage 100 on the server, the MAS_Reports password is fine... and you are probably dealing with a workstation connection issue.

KB
https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=224924150049613&page=1&position=1&q=the%20database%20login%20failed

@Kevin Moyes ?

1. I ran the repair mode for crystal reports runtime.
2. In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. (When I updated the passwords I made sure I used the SA login to update)
3. Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]  - do you mean change it to IP address when I uninstall and reinstall workstation setup?

The suggestion 3 is the only thing I haven't tried yet. Still doesn't work after suggestion 1 and 2.

Workstation control panel: repair the two Crystal Reports run-times.

SQL instance firewall should be a program exception, not port (if you have more than one SQL instance on the machine... otherwise port 1433 should work).

In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. 

Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]

Test a SQL DSN / Excel query to make sure you have basic connectivity with the SQL instance.  If that doesn't work, it isn't a Sage problem.

@Kevin Moyes I checked and it pointed to the correct database server. I tried the additional steps in the article and confirmed everything is in place with the rules with the firewall. It's still failing to print and preview the reports from the workstation level. I don't know if this makes a different but because this is a viritual server should I have the IT group reboot this server? 

For #3, I mean in the Sage SQL settings utility.

When printing, Sage passes a connection string in memory to the workstation's print engine, which then accesses SQL data using those credentials.

If you can print from Sage 100 on the server, the MAS_Reports password is fine... and you are probably dealing with a workstation connection issue.

KB
https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=224924150049613&page=1&position=1&q=the%20database%20login%20failed

@Kevin Moyes ?

1. I ran the repair mode for crystal reports runtime.
2. In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. (When I updated the passwords I made sure I used the SA login to update)
3. Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]  - do you mean change it to IP address when I uninstall and reinstall workstation setup?

The suggestion 3 is the only thing I haven't tried yet. Still doesn't work after suggestion 1 and 2.

Workstation control panel: repair the two Crystal Reports run-times.

SQL instance firewall should be a program exception, not port (if you have more than one SQL instance on the machine... otherwise port 1433 should work).

In the Sage SQL settings, make sure you are using the full and proper instance name, not localhost\instancename, which won't work from anywhere other than the Sage server. 

Try the ipaddress\instancename if the servername\instancename doesn't work.  Any values with special characters like a dash, wrap in square brackets: [server-name]\[instance-name]

Try opening inbound traffic on the server port 1433.

@Doug Higgs I tried that with no luck.

Try opening inbound traffic on the server port 1433.