[SN][ODBC ServiceNow driver][OpenAccess SDK SQL Engine]Cannot connect to the instance. [dataSource=2288219503944] [user=odbc_user]You are not authorized to perform this operation. Please verify your credentials and try again.[1001]

[Tracy Li Gao]

The user odbc_user can login my PDI, and have given the role odbc.

I tried to install ServiceNow-ODBC-64-bit_1.0.15.exe, when PDI has been started about 2 mins, clicks "Test Connect" in ODBC 64 bit, it shows connected successful.

Then several mins later, would get error when clicking "Test Connect" in ODBC:

[SN][ODBC ServiceNow driver][OpenAccess SDK SQL Engine]Cannot
connect to the instance. (dataSource=2366386112856)
[user—odbc user]You are not authorized to perform this operation.
Please verify your credentials and try again.[1001]

Run command "connect odbc_user*password@servicenow;", get the output as attached.

Why connect successful at first 1-2 mins, then failed later? How to resolve the issue?

Please help to provide your suggestions next.

[Mahak2]

Hello,

Please refer to this KB Article:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0538995

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0538954

https://community.servicenow.com/community?id=community_question&sys_id=df605b29dbdcdbc01dcaf3231f96191b

Please mark my response as Helpful and Correct in case it solves your query.

Thanks

[Tracy Li Gao]

Thank you for the feedback.

I had checked the KB Articles, but not helpful.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0538995

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0538954

I checked the link below today.

https://community.servicenow.com/community?id=community_question&sys_id=df605b29dbdcdbc01dcaf3231f96191b

I installed ServiceNow-ODBC_1.0.15 64bit

OS: Windows 10 Enterprise 64bit

SQL Server: sql_server_2008_r2_standard x64

I see the "SQL Server Reporting Services" installed in folder "Program Files" which indicate it's 64 bit.

When testing the connection with the ODBC driver (via ODBC Administrator UI), it's failed with the same error. So I think the issue is different.

Thank you for helping anyway.

[Mahak2]

Hello Tracy,

Can you please check these points:

a) make sure that the user that you're using to connect is not locked out. This can be validated in the user record.

b) try updating the password to something really simple

c) be aware that ACLs are enforced. The records available for the user will be those permitted by the ACLs

d) try specifying a connection string with the user and password instead of defining a DSN:

Also please refer to the below :

https://community.servicenow.com/community?id=community_question&sys_id=ca86c725db1cdbc01dcaf3231f96193b

https://community.servicenow.com/community?id=community_question&sys_id=246f36a9db58dbc01dcaf3231f961926

Please mark my response as Helpful and Correct in case it solves your query.

Thanks

[Tracy Li Gao]

Hi Mahak,

Thank you for the 4 checking points provided.

I have checked one by one, please refer to attachments attached.

The customconnect report the same error.

I find one thing for same days, this morning again, the connection is successful when the PDI is hibernated, the error appears when the PDI become ready for "Start Building" in several minutes automatically. 

I feel the error is related with certain background configuration become active when the PDI is ready for "Start Building".

I do not find there is a way to keep PDI hibernated manually.