Hello,
We have several workstations (Aui) which are not enabled anymore to start. We need remove the pvssconf.inst.lck file
in order to start WinCCOA
What were the reasons of the presence of this file and what are also the circumstances that it wasn't removed.
Note : we are working on 3.12P31. We have also seen disconnections on the LAN with the servers.
regards
Emmanuel
Pssconf.inst.lck file
- schneebergera
- Posts:89
- Joined: Sun Apr 03, 2016 5:52 pm
Re: Pssconf.inst.lck file
Hello,
During the default WinCC OA installation the pvssInst.conf will be created.
[C:\\ProgramData\\Siemens\\WinCC_OA]
If you uninstall and install WinCC_OA again on the same machine (even several versions) there it could happen that the file is locked - not writable.
There are several reasons why the file could be "corrupt". Did you perform an upgrade, re-installation, fresh installation? It also could be that any project wasn't stop regularly before.
After that a backup of file will be created (lock-file) - pvssInst.conf.lck
Did you receive an error message (windows-popup)?
suggestion...
within version 3.14 there was a known issue that the "Installation User" causes a problem (already fixed).
This information is used when generating the pvssInst.conf during setup. It is read from the registry from
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\RegisteredOwner.
--> Please check registry on your machine.
Either set the "InstallationUser" (pvssInst.conf) of all projects after installation to something like:
InstallationUser = Windows User
or
InstallationUser = ""
or you should change the registry entry to some user.
with best regards,
Andreas
During the default WinCC OA installation the pvssInst.conf will be created.
[C:\\ProgramData\\Siemens\\WinCC_OA]
If you uninstall and install WinCC_OA again on the same machine (even several versions) there it could happen that the file is locked - not writable.
There are several reasons why the file could be "corrupt". Did you perform an upgrade, re-installation, fresh installation? It also could be that any project wasn't stop regularly before.
After that a backup of file will be created (lock-file) - pvssInst.conf.lck
Did you receive an error message (windows-popup)?
suggestion...
within version 3.14 there was a known issue that the "Installation User" causes a problem (already fixed).
This information is used when generating the pvssInst.conf during setup. It is read from the registry from
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\RegisteredOwner.
--> Please check registry on your machine.
Either set the "InstallationUser" (pvssInst.conf) of all projects after installation to something like:
InstallationUser = Windows User
or
InstallationUser = ""
or you should change the registry entry to some user.
with best regards,
Andreas