Hi, you simply got an information (0 in the log), these are system db so you can choose to not backup them (they are included in the installation) and running the task as another use won't solve the problem (that is not a problem).

Also mounting them as rw is a bad bad thing because you can end up in modifying the DB (Andi you don't want this).

You should simply ignore the message and if it's a monitoring system that warns you, set it to check for 1 or above severity (I'll go for 2 or more).

If you really really want to get rid of it and still backup every db, write a custom backup routine tanto mounts the db row, backup them, get them ro again. But this would be a waste of time because it's just an info

Hi Scott,
not an expert for zstop, but what you are looking for cannot be developed with the zstop.

With an "iris force", hardware failure (hard power off, server fault,... anything that is not a "polite" shutdown) or other similar condition where iris simply is killed, no zstop is executed. You can only be aware of an unclean shutdown at the iris restart, but that's too late for what you are looking to do.

What you can do is to have an agent that monitors the iris instance (qlist, process, messages.log) and execute action when certain conditions are met.

Moreover i haven't found anything on the "shutdown" cause, it's just a shutdown inside iris i think

Pietro

unfortunately unless you got a very very high log set in the instance and a very long journal history you can't discover that.

If you got the info you can find in the journal the global change, get the process info and search the log for them. But usually is something that you can spot in the near time or something that happens on a regular basis, something spot is really difficult to find in that way.

Hi,

never done that, always installed production under linux. Respecting the allocation size it will be good to match the same size so if you are using only 8k, it should be better to have 8k also on fs so 1 unit for db should also be 1 unit for fs and it won't be split in 2 fs operation. 8k should be fine because you can accept that if you are using a mixed db allocation size for 8k and 16k it will always be beneficial also for 16k chunks.

On this argument always remember to align the partition and the fs dropping the first bytes as per ms best practice so that also the disk (if on a raid) could match the writes

https://support.microsoft.com/en-us/topic/recommendations-and-guidelines...

Hi,
the most straightforward thing to do is to use the upload manager that will take care of everythings.
But if you want to go via code, as Davide said, you should use ##class(User.SSUser).%New() to create the user.
Keep in mind that the user at first login MUST change the password. To avoid that, you have to have 2 row in the password table, so you should change the password one time via class and then the user should be able to login with the specified credentials.
So the main suggestion is to go with upload manager and, may be, ldap as a backend for password auth.

Hi,
the error is quite generic and it basically says that you can't login but you don't know why.

Check that the superserver port is the same used in studio,

Check the license on the instance.

If the everything is fine, fire up the management portal, go to
system administration -> security -> auditing -> enable auditing
and check that the auditing is enabled. After that go to
system administration -> security -> auditing ->  configure system events
and check that
%System/%Login/LoginFailure
is enabled. If not click on "change status".

Try to login again with studio and check the audit database
system administration -> security -> auditing -> view audit database
and see what error comes up

Pietro