· Nov 20, 2017

Cache ODBC - Access Denied


I'm working on integrating a Cache database into an existing .NET project of mine.  I'm trying to execute certain queries utilizing the Cache ODBC driver.  The first error I ran into was "[S1000] [Cache ODBC][State : S1000][Native Code 417] Access Denied".  The part that's throwing me for a loop though is that the application ran ~200 successful queries before I started getting that.  After some of those Access Denied errors, they turned into "[Cache ODBC][State : S1T00][Native Code 450] Request timed out due to user timeout".  This was all with the regular (2.5?) driver.

I then started using the 3.5 driver.  But, the same scenario played out again.  The only difference being the State: from S1000 to HY000.  These then also turned into "Request timed out due to user timeout" with a state of HYT00 instead of S1T00.

Has anyone seen this before?  The fact that it doesn't start happening until after many successful queries have occurred has left me stuck.  Are there any initial steps I should take to try to troubleshoot this?

Discussion (8)2
Log in or sign up to continue

Turn on Auditing (Portal -> System Admin -> Security -> Auditing -> Enable Auditing, configure system events to audit login failures ).

It can give you a clue on why you are getting Access Denied.

It could be an issue of licensing : check the system dashboard for Licensing use (maybe you have too many connections open).

If all this does not help, you can also turn on ODBC logging in the ODBC DSN.

Kyle, thanks to you and Danny for your responses.  One extra piece of information is that I'm a third-party vendor in this scenario.  As a result, I don't believe I have access to the Portal to turn on Auditing.  I did enable ODBC logging, but that didn't reveal any additional information.

In the meantime, I decided to switch back to the ADO .NET driver.  We were able to work through an unrelated issue there, so we're thinking we might just use that and back-burner ODBC.

Follow Danny's advice above (or below, no idea where this comment will land) and if it turns out to not be straightforward, feel free to contact Support (, 617-621-0700).  One of us would be happy to log in with you and help you troubleshoot this. 

For what it's worth, enabling Auditing (after you change the System events for Protect and LoginFailure to be enabled) should tell you what the problem is pretty clearly.