Cache Security Error

114 views
Skip to first unread message

Viraj

unread,
Aug 9, 2011, 9:38:18 AM8/9/11
to InterSystems: Ensemble in Healthcare
Hi,
We have built an application which uses asp.net / c# with .NET
Framework 3.5 as a front end and Cache Database as a backed.

We are using Cache's managed provider for data access. The application
follows 3 tier architecture where database access and CRUD operations
are performed on data tier. All the compiled code will produce .dll
files (assemblies)

At the time of development, we used asp.net development server (which
runs under administrator account automatically and has full rights).
our application was having no issues to communicate with cache and
perform database operations.

Now, we have tried to deploy it on IIS 6.1 and 7.0 (WS 2003 and Vista
respectively). When we run the application or try to perform database
operations using any of our front end's page, we receive a strange
error called 'Cache Security Error'.

I have searched the Cache documentation and internet as well was not
able to find any help on this issue.

However, i built another test application without any tiers and used
the same way to communicate with cache and interestingly it is working
find on both IIS and Asp.Net Application Web Server.

Can anybody guide me on this ?

Thanks in advance.

Viraj

unread,
Aug 9, 2011, 9:47:55 AM8/9/11
to InterSystems: Ensemble in Healthcare
UPDATE :
I have found out something about this error on intersystems'
documentation : http://docs.intersystems.com/documentation/cache/20091/pdfs/GCRN.pdf
=====
-417: This error is raised when login fails. Usually this is due to
username and password checking
failure. It can also occur if the username is not privileged.
SQLCODE = -417 Cache Security Error
=====

In my connectionstring, i am passing the default username _SYSTEM and
its password to connect to cache namespace. I have not changed
anything for the _SYSTEM user of Cache. Do i need to configure/change
some parameters in order to solve the issue ?
Reply all
Reply to author
Forward
0 new messages