John Ellis
asked on
Scribe: Allowing for SQL Authentication
Hello:
In a test installation of Scribe 7.9, I'm using a SQL-Authenticated ODBC to try to connect to Scribe's "internal" database.
Upon clicking the "Test Connection" button in the InternalDB.exe tool, the connection fails.
In fact, when this connection fails, it locks out that ODBC's SQL login account. For some reason, this InternalDB.exe tool is only successfully testing with a Windows-Authenticated ODBC connection.
We'd prefer to use SQL Authentication.
Has anyone else experienced this issue, before?
Thanks! Much appreciated!
John
In a test installation of Scribe 7.9, I'm using a SQL-Authenticated ODBC to try to connect to Scribe's "internal" database.
Upon clicking the "Test Connection" button in the InternalDB.exe tool, the connection fails.
In fact, when this connection fails, it locks out that ODBC's SQL login account. For some reason, this InternalDB.exe tool is only successfully testing with a Windows-Authenticated ODBC connection.
We'd prefer to use SQL Authentication.
Has anyone else experienced this issue, before?
Thanks! Much appreciated!
John
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Can you make your own test by creating a odbc to see that it works.
What version of SQL Server, and what edition?
Is it on Another server or is all contained on one machine, thinking firewall here.
Check under SSCM (SQL Server Configuration Manager) that the right network protocol are enabled.
Regards Marten
What version of SQL Server, and what edition?
Is it on Another server or is all contained on one machine, thinking firewall here.
Check under SSCM (SQL Server Configuration Manager) that the right network protocol are enabled.
Regards Marten
ASKER
I had a colleague of mine, also, review the server. For some reason, the SCRIBE app refuses to talk to the new SQL server instance from that server. We don't know why. We even tried uninstalling and reinstalling, and the app still will not talk to the new instance.
Thanks, for chiming in! I appreciate it!
John