Not able to connect ODBC DSN, getting error 1001 Authentication failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2015 10:10 PM
I am Not able to connect ODBC DSN, getting error 1001 Authentication failed, though DNS is created and tested Successfully, odbc user has SOAP role and itil role. Please suggest.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-03-2015 10:38 PM
Some thoughts:
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:
Something like this:
Driver=ServiceNow ODBC Driver 32-bit;ServiceName=ServiceNow_ODBC;UID=youruser;PWD=yourpassword;ServerDataSource=ServiceNow;CustomProperties=url=https://<yourInstanceURL>
source: http://wiki.servicenow.com/index.php?title=Configuring_the_ODBC_Driver#Using_a_Connection_String
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-05-2015 04:01 PM
Hi Sachin,
I think you have a typo in your posting. Did you meant to say:
"I am Not able to connect ODBC DSN, getting error 1001 Authentication failed, though DSN is created and tested Successfully"?
I guess you did and your connection tested OK at this point:
Testing the ODBC Driver - ServiceNow Wiki
Perhaps the failure was seen here:
Using Interactive SQL With ODBC - ServiceNow Wiki
..
CONNECT odbcuser*password@ServiceNow
..
The issue may be that you have special characters in the password.
Can you, in any case, please check the results of using customconnect which does allow the use of passwords with special characters.
ServiceNow KB: ODBC Troubleshooting Checklist (KB0538995)
..
4. Does your user name and/or password contain special characters?
In this case, customconnect should be used instead of connect:
customconnect "DSN=<System DSN>;UID=<username>;PWD=<password>"
Best Regards
Tony