Error: Cannot save file "C:\Program Files (x86)\HostMon

[david.matthewson]

I'm getting a lot of these errors when HostMon (12.42) tries to write a tmp file to the working dir. Started on May 6th and despite reboots/restarts, it keeps occurring always with the same tmp file.

06/02/2020 12:56:39 Error: Cannot save file "C:\Program Files (x86)\HostMonitor\xxx-2020-02-05.hml". Cannot create file "C:\Program Files (x86)\HostMonitor\xxx-2020-02-05.tmp". Access is denied

[Company name edited to = xxx]

Any ideas where to look pls?

Env = W2016 x64 VM

[KS-Soft]

Not a good idea to store config files in %ProgramFiles% directory.
HostMonitor installation program uses %ProgramData% by default.

1) I would check permissions (by default admin should be able to write into this folder), check what account you use for HostMonitor, try to stop your antivirus..

2) Normally you adjust antivirus settings so it will not check %ProgramData%\HostMonitor\, this way antivirus will not waste system resources checking log files 100 times/sec and will not lead to problems. But I am not sure its a good idea to disable antivirus for %ProgramFiles% directory.

3) If you do not want to reinstall software and move all config files, then at least you may move HML file with tests - stop HostMonitor, move .HML file, out of %ProgramFiles% modify path to this file in hostmon.ini, start HostMonitor

Regards
Alex

[david.matthewson]

Agreed with using ProgramData and that's that this installation has. It was a clean install a few months ago accepting all the defaults.

Anyway, backed it all up, trashed it, reinstalled it and relicensed it & so we'll see what happens.

Thanks again for yr help, Alex

David

[KS-Soft]

[david.matthewson]

The box is a VM 6.7 running W2016 x64 Std edition. English lang. 2 cpu, 8Gb and all it does is act as a jump server and run HostMon.

As you say, odd.

[KS-Soft]

Sorry, we cannot reproduce the problem on Windows Server 2016 x64 Std, setup program sets C:\ProgramData\HostMonitor\ as default folder for config files..

Regards
Alex

[david.matthewson]

Thanks Alex

OK - I'll have to trash the installation and reinstall then. I'll save the config & test list, copy over and re licence.

best wishes

David

[KS-Soft]

I would try to start from item #1 - check permissions (by default admin should be able to write into this folder), check what account you use for HostMonitor, try to stop your antivirus..
You are using "incorrect" config but in most cases it should work as well.

If you want to reinstall using "correct" path to config files, please note:
- backup and restore ALL config files (*.HML, *.LST, optionally *.INI), not just .HML file with tests
- after reinstalling and restoring files please check and modify paths in INI files (e.g. find and replace C:\Program Files (x86)\HostMonitor -> C:\ProgramData\HostMonitor)

Regards
Alex

[david.matthewson]

Thanks Alex, helpful as always.

[KS-Soft]

You are welcome

Regards
Alex

[david.matthewson]

Alex

OK, fixed it. My fault as it turns out. Duh!. I'd saved the HML test list in Program Files x86 and not in Program Data and also set it to 'update when a change is made'.

Not much as perms to write to Program Files x86 and so it was failing.

Didn't reinstall but rather shut HM down, moved the HML file and altered the 'load from this location' in config.

Now all works fine.. ;}

Thanks.[/u]

[KS-Soft]

You are welcome.
I would suggest to move out log and report files as well and tell antivirus do not check HostMonitor log and report files.

Regards
Alex

[david.matthewson]

Thanks Alex - already done ;}