Hello Mike,

Thanks for quick reply.

The application simply does not start, but generates an uninformative general error saying that application has failed to start, and that Windows will inform me if solution is found. If I promote the user to a local admnistrator, application starts normally.

This should be easy to reproduce for you locally. On the other hand, I would have to visit the user, demote him to standard user, test, make snapshots, then revert to the working setup again..... If you insist - I'll do it, but it would probably not do wonders for our visibility ;-)

I can tell you that there is nothing usefull in system or application log, other than the fact that logger.exe has failed to start. Giving read/write access to application folder or SQL Express folder did  not make any differenece. Duing the process I have only learned that configuration set is not persistant on machine, but has to be set for each user separately - which might not be the intended behaviour - certainly not in environments where more than one user work in shifts.

Best regards,
Ivo

Hi Ivo,

I can't reproduce it. But I think it's problem with access to registry keys and/or data folders.
First I recommend install the newest software version (4.0.12.6, see http://www.cometsystem.com/products/reg-SWR001#download).
If reinstall doesn't help, please check following keys and folders for access rights:
HKCU\Software\CometLoggers\Logger and subkeys (read, write)
HKLM\Software\CLSec CS Limited (read)
HKLM\Software\CometLoggers\Logger (read)
C:\ProgramData\CometLoggers\Logger and subfolders (read, write)

Please report results back. Thank you.

Mike

I have installed the latest version (it seems that it changed from 4.0.11.x to 4.0.12.x since this afternoon), but again it does not work.

The initial splash screen pops up, it reports loading Main Form on the bottom of the dialog, then loading something else (too quick to tell), and it finally ends up in dialog saying: Datalogger progam with database has stopped working.

BR,
Ivo