Since it isn't on by default, you should also make sure to enable the %System/%Security/Protect event in "System Administration > Security > Auditing > Configure System Events. You'll be looking for either a Protect event or a LoginFailure event (enabled by default) when you look at the audit log.
To help... - If not already enabled; enable security auditing via the system management portal's "System Administration > Security > Auditing > View Audit Database", and look at this audit log after generating the error.
It will shed some more light on the user in question, or service, or whatever - may be causing this issue.
When you say 'localhost' are you implying that you are using the private Web Server contained within Cache?
Is this the only application being run from the web server vs localhost?
If not then are the other applications still accessible via the external web server.
Some things to check right off the bat.
enabling audting and seeing which user is getting the error will help
Use the CSP Gateway Management pages HTTP trace capability to see if the request is even making it into Cache. It would seem so from the error, but better to confirm everything.
Make sure that the user that the CSP Gateway associated with the Web Server uses to communicate to Cache has access to your database. This would be different from the person logging into your application. This can be found in the CSP Gateway Management for the server.
To leave a comment or answer to post please log in
Ensure that user, which you are using to access the database has apropriate permissions to connect and access data.
Hi Eduard,
Thank you for the help ! My system is now running :)
Since it isn't on by default, you should also make sure to enable the %System/%Security/Protect event in "System Administration > Security > Auditing > Configure System Events. You'll be looking for either a Protect event or a LoginFailure event (enabled by default) when you look at the audit log.
Hi Steve,
Thank you for the help ! My system is now running :)
Hi Steve,
Thank you for the help ! My system is now running :)
Hi Rich,
Thank you for the help ! My system is now running :)
Ahncel, now please mark an answer as "accepted".
Here are the instructions:
https://community.intersystems.com/post/january-10th-dc-release-mark-ans...
In this case, several DC members posted a "comment" rather than an "answer", and the DC software currently only allows "answers" to be accepted.
Hi Ahncel,
To help... - If not already enabled; enable security auditing via the system management portal's "System Administration > Security > Auditing > View Audit Database", and look at this audit log after generating the error.
It will shed some more light on the user in question, or service, or whatever - may be causing this issue.
Steve
Some questions first.
Some things to check right off the bat.
Social networks
InterSystems resources
To leave a comment or answer to post please log in
Please log in
To leave a post please log in