Did this article resolve your question/issue?



Pro2SQL - Unable to open Pro2 Admin tool due to ODBC error "Cannot create SSPI context"


TitlePro2SQL - Unable to open Pro2 Admin tool due to ODBC error "Cannot create SSPI context"
URL Namepro2sql-unable-to-open-pro2-admin-tool-due-to-odbc-error-cannot-create-sspi-context
Article Number000114916
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: Windows
Other: Pro2, ODBC
Question/Problem Description
Pro2SQL - unable to connect to SQL due to ODBC error "Cannot create SSPI context"
Checked ODBC DSN (32-bit) and found that even a Test Connect failed.
Using Windows NT authentication on the DSN.
There were updates and changes to the environment carried out recently before failure.
Steps to Reproduce
Clarifying Information
Replication itself seems to be working, based on check the ReplQueue table (was decreasing) and the Pro2 logs.
Using Windows NT authentication on the DSN.
Error MessageS1000: [Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context
Failed to connect to the MSS database. (6142)
Defect/Enhancement Number
The exact cause is not known at this time.

Suspect that Windows Authentication is being used and the Windows password has expired and needs to be reset.
Attempt logging into the same system with the same Windows login to see if a message is returned that the password has expired.
If this is the case, perform the necessary steps to update the Windows password.
Last Modified Date8/24/2017 2:32 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.