Database Write Protection

[jelvers]

I am not sure whether the following is a bug or my procedural mistake.

I have IMA up running, then click <Stop> and click <Close> and shut down the computer. Now, sometimes it happens that when I try to open IM after booting my W10 system again I get the message "Database locked or write-protected". When I then close IMatch, start IMA, I can see that it is still running! When I then click <Stop> again, IMatch can be opened as expected.

I cannot always repeat this behaviour so I guess it is due me rather than a "bug". But what does cause it?

Regards, Juergen

[Mario]

Did you enable the option to automatically start the IMatch WebService when the system starts?
This is the default for "remote" or headless machines where IMWS must run when Windows runs so it can accept connections.

If this option is off, I don't see why Windows should device to start IMatch WebServices.

You can check in the Windows Service Manager if IMatchWebServices are configured to start automatically.
See the IMWS help for details if you have never used Windows Service Manager.

[jelvers]

Did you enable the option to automatically start the IMatch WebService when the system starts? ...... If this option is off, I don't see why Windows should device to start IMatch WebServices.

It was enabled. So that was the reason. Everything ok now. Many thanks!

Regards, Juergen

[Mario]

Cool. This setting is indispensable for using IMWS on remote servers. but should be of when you switch between IMWS and IMatch on the same computer.