UC Reporter -Post 11.5 Upgrade Cannot Connect to SQL Server.

[Cedric_Jackson]

After upgrading from 11.4 to 11.5, I cannot reconnect back to my SQL Server.  Here is the output from my Setup UC Reporter log.

2/7/2019 9:33:40 AM - Info: Parameters:
2/7/2019 9:33:40 AM - Info: Service user: CATL0AS1511\Prognosis_PROD
2/7/2019 9:33:40 AM - Info: Service password: ****
2/7/2019 9:33:40 AM - Info: Database user (sql authenticated): Prognosis_PROD
2/7/2019 9:33:40 AM - Info: Database password: ****
2/7/2019 9:33:40 AM - Info: Database instance: CATL0DB710/prognosis
2/7/2019 9:33:40 AM - Info: Server port: 5999
2/7/2019 9:33:40 AM - Info: Logging port: 5998
2/7/2019 9:33:40 AM - Info: Paper size: Letter
2/7/2019 9:33:40 AM - Info:
2/7/2019 9:33:40 AM - Info: Validating service creation
2/7/2019 9:33:43 AM - Info: ..... Services ok
2/7/2019 9:33:43 AM - Info: Validating prerequisites
2/7/2019 9:33:43 AM - Info: Found that the DCOM Identity for Microsoft Word 97 - 2003 Document is the same as the service user.
2/7/2019 9:33:43 AM - Info: ..... Prerequisites ok
2/7/2019 9:33:43 AM - Info: Validating registry access
2/7/2019 9:33:43 AM - Info: ..... Registry ok
2/7/2019 9:33:43 AM - Info: Validating config files
2/7/2019 9:33:43 AM - Info: ..... Configuration files ok
2/7/2019 9:33:43 AM - Info: Validating database connection and permissions
2/7/2019 9:34:13 AM - Error: Cannot connect to SQL server instance with provided credentials.
One of the reasons of failure could be that SQL Browser is not running or the TCP/IP protocol is not enabled on the SQL Server. Details:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.)
2/7/2019 9:34:13 AM - Error: Validation failed, stopping setup

[GeraldC1 · Accepted solution]

There is a command line utility that should help to validate the SQL connection parameters with some trial and error and with some dialog with your SQL team if necessary:

1. Open an Administrator command prompt and set the path to “C:\Prognosis\Reporter\Bin” 
2. Run the command (using the details your attempting in the Setup): 

irOsql -U SQL_user -P YOURPASSWORD -S sqlserver.something.something\instance,SQL-TCP-port  -Q "Use IPTM_Device; select * from pbx"

(SQL-TCP-port is 1433 by default or could be a custom port set by your SQL team)

(YOURPASSWORD is the password of the SQL_user )

in your case start with something like (based on the your log):

irOsql -U Prognosis_PROD -P YOURPASSWORD -S CATL0DB710\prognosis,  -Q "Use IPTM_Device; select * from pbx"

HTH

[Cedric_Jackson · Accepted solution]

Actually after resetting the service startup account to match the account used to setup UCReporter, I ran this command

SetupUCReporter -i=DatabaseServername\DatabaseInstance A=DOMAIN\Username  -P=XXXXXXXX  -s=Letter