December 21, 2017 at 2:50 am
One of the application job is failing due to
ODBC_GetThreshold: ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 2,755: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Security Services Error: Unspecified error at the GSS layer.
ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 2,763: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Security Services Error: Error writing to credentials cache. (CC_OdbcConnection::connect, file CC_OdbcConnection.cpp, line 578)
help required to fix the issue, not aware on this how to fix .
December 21, 2017 at 3:08 am
ramyours2003 - Thursday, December 21, 2017 2:50 AMOne of the application job is failing due toODBC_GetThreshold: ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 2,755: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Security Services Error: Unspecified error at the GSS layer.
ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 2,763: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Security Services Error: Error writing to credentials cache. (CC_OdbcConnection::connect, file CC_OdbcConnection.cpp, line 578)help required to fix the issue, not aware on this how to fix .
My advise would be to open a support ticket with IBM's support team to help you troubleshoot.
But has this been working ever? If so when? What has changed since when it was working and now? Service packs, driver updates, credential changes etc
December 21, 2017 at 3:21 am
we are not sure when we reran the job it is getting successful. is anything to do from database side?
iam not aware on this ..
December 21, 2017 at 3:29 am
ramyours2003 - Thursday, December 21, 2017 3:21 AMwe are not sure when we reran the job it is getting successful. is anything to do from database side?iam not aware on this ..
Unsure, that's a IBM DataDirect / DataStage error, your best off speaking to IBM about the cause and how to prevent it.
You could take a look at your logs and any monitoring software you have for the time the job failed, maybe you never know something obvious may appear on the actual cause.
December 21, 2017 at 5:37 am
This was removed by the editor as SPAM
December 21, 2017 at 7:05 am
subramaniam.chandrasekar - Thursday, December 21, 2017 5:37 AMramyours2003 - Thursday, December 21, 2017 2:50 AMOne of the application job is failing due toODBC_GetThreshold: ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 2,755: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Security Services Error: Unspecified error at the GSS layer.
ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 2,763: Msg = [IBM(DataDirect OEM)][ODBC SQL Server Wire Protocol driver]Security Services Error: Error writing to credentials cache. (CC_OdbcConnection::connect, file CC_OdbcConnection.cpp, line 578)help required to fix the issue, not aware on this how to fix .
If you could refer to this link, that would be good.
https://knowledgebase.progress.com/articles/Article/000037130
Seems Kerberos was not configured on your machine. I suspect from my end, any latest windows server update has been happened recently ?
Strange if it would be a Kerberos error as the OP mentioned when they re-ran the job the job was successful, so unless in the time it took the failure to the success the right SPN's where configured guessing this may not be the case. Although not ruling it out completely.
Ram, if by any chance did the server or instance restart just before the failure? Are your service accounts setup to automatically register and deregister SPN's, if so the above may have been true if AD replication hadn't synced the updated SPN's between all of the domain controllers.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply