Thanks for the reply.

If a user needs to be able to monitor and operate a Production would they not still need access to that data base?  Also, that table is granted via %ENSROLE_OPERATOR which such a user will need?

Thanks for the explanation, I assumed it worked something like that.

Do you agree with that approach though or would you prefer something more like Robert's description?

In my mind you don't create a database based on a specific file so the DAT should be swappable and retain the database settings, other database settings work that way.

Hi, that was my understanding but I have seen resource issues caused by moving CACHE.DAT in the past and recently had an odd issue on IRIS then did the below to test it.

I just copied the IRIS.DAT from the USER database folder, which has the %DB_USER resource, to another database folder which had %DB_%DEFAULT and afterwards the other database had %DB_USER instead of %DB_%DEFAULT and so it seems the Resource does move with the DAT file.
The copy was done manually with windows file copies while IRIS was down and no config changes made.

This is all viewing the database resource via the portal in  System > Configuration > Local Databases

That removes all " characters, while these are indeed doublequote's, someone could also mean "" where there are double quotes, as in quotes inside a quoted string (str="this is a quote"".")

For that


or I find it more readable to use the ASCII value so to remove


or to replace with a single "


Good point, I guess it depends on the variables scope at that stack level, I generally just run it twice.

Either way, as you say, it is useful to know to do this to ensure "leftovers" don't interfere with later commands.

Not 100% sure of the requirement but if you write the output from the Cache code as if it was to the terminal then you can redirect the output to a file by appending >output.file but I don't think cterm is the way to do that as cterm will trap all the output itself, you would need to use csession for that.

You could just write to a file in your Cache code or run an external command/script from inside the Cache code?

Access Denied is generally either a user permissions or a resource issue.  However, from one of your screenshots it looks like you are connecting to a Cache install running an evaluation license?  These can have limitations so it is also possible you are hitting a license (user/process) limit?

Most likely the user does not have permissions.  Based on screenshots in other comments it looks like you are using the wrong password for the Marco user and that the Admin user is disabled but you have obviously been able to log into the portal and overcome the issue mentioned with selecting events?  Would also be useful to check the console log for that time as well.

If this is still happening perhaps update this query with details on the username, whether that user works in the portal, and the latest errors in event log that relates to the studio failure, look at all entries for that time, not just the login failures, in case the issue is different.