Jump to content

Problem connecting Persistent Variables to SQL Instance


Ben Vlaeminck

Recommended Posts

My local SQL server is a Standard server, v 2014, instance = MSSQLSERVER.

I'm getting errors (in IpPbxSrv) like this:

quote

30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () ---------> PersistentVariable.Retrieve
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () ---------> PersistentVariable.OpenDatabase
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () ---------> PersistentVariable.CalcConnectString
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () g_sPersistentVariableServerName: cs-swyx\MSSQLSERVER
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () g_sPersistentVariableDatabaseName: 
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () g_sPersistentVariableConnectString: 
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () sServerName: cs-swyx\MSSQLSERVER
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () sDatabaseName: IpPbxExtensions
30 19:52:55.558 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () ConnectString: Provider=sqloledb;Data Source=cs-swyx\MSSQLSERVER;Initial Catalog=IpPbxExtensions;Integrated Security=SSPI
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () ConnectStringExpress: Provider=sqloledb;Data Source=cs-swyx\MSSQLSERVER\SQLEXPRESS;Initial Catalog=IpPbxExtensions;Integrated Security=SSPI
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () <--------- PersistentVariable.CalcConnectString
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () Using none local SQL Express connect string.
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () Opening database...
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () Error opening database! (-2147467259)
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () [DBNETLIB][ConnectionOpen (ParseConnectParams()).]Invalid connection.
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () bReturn = False
30 19:52:55.559 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () <--------- PersistentVariable.OpenDatabase
30 19:52:55.560 0017a4 Info SrvScript  05F93660 00000015 SPBXScript::OutputTrace                 () bReturn: False

unquote

 

In the Run GSE Action box I only changed ServerName from default ("") to "cs-swyx\MSSQLSERVER"

with the default value (""), it produced similar error, but mentioned cs-swyx\SQLEXPRESS..

 

please advise for correct connection settings

thanks

Ben

Link to comment
Share on other sites


  • 3 weeks later...

Hi Ben,

 

as server name you only need to give the name of the machine the SQL server is running on, noting else. So if you configure "cs-swyx" it should work. If that is also the name of the Swyx Server you don't need to configure anything.

 

If this doesn't work please post another trace snippet.

 

The persistent variables (v1.2.1) probes which SQL server variant is installed on the local machine and creates either a connect into the full blown sql server, or into the express variant. This probing only works if the SQL server is installed locally. If you connect to an external server you have to set the connect string completely by yourself.

 

 

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and have taken note of our Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.