Hello, I was running into this issue with AS4.2 after I ended PVI Manager’s task in Task Manager. I needed to end the task in order to install something. After that, whenever I tried to open a project in AS4.2, I was getting the error window “Unable to start PVI Manager (Error 12064). Please check registry!”. I started PVI Manager manually and opened the project but was unable to connect to a panel using ethernet. I looked at online settings and the IP address of the panel matched the destination IP address of my connection method. I switched the ethernet cable I was using and still could not find the panel. After that I restarted my computer and tried to connect to the panel again, running into the same issue upon starting AS4.2. I eventually decided to try uninstalling and reinstalling AS4.2, which has worked for a few issues before. After reinstalling the software the issue remained. Has anyone run into this issue before?
Hi,
haven’t seen this error before, but the PVI error code 12064 says that there’s a problem with the Windows service:
12064 No access privilegs to start windows service “B&R PVI Manager”
“B&R PVI Manager” is installed as a windows service on that system but it is currently not running. The current user privilegs do not allow to start the service automatically. You have to start this service manually.
If PVI is installed as Windows service, and the service isn’t running / can’t be started for whatever reason, even starting PVI Monitor manually won’t start the Windows service (this could explain the behavior that no online connection is established).
So I propose to check the Windows service settings (services.msc) if the PVI manager service is running/manual or stopped/disabled, and try to start the service manually.
If service starts, try again to get an online connection. If the connection works, set the Service in the Windows service control panel to “start manual”.
If there’s no technical reason for using PVI as service, it would be also a possibility to reinstall PVI and deactivate the setting “use as service”… if doing so, PVI acts as a “normal Windows process” that is started when needed, but is not running as a service.
I think there’s even a command line parameter to (de)register PVI as service, but unfortunately I can’t remember…
EDIT: found the PviMan.exe parameters
Best regards.
It looks like it was disabled. I remember now what I downloaded last week. One of the projects I opened required a higher version of PVI Manager than I had. I believe having the newer version was causing a conflict. I am looking into removing the older version as a service and putting the newer version in its place. I will post here if it works.
Ok, it looks like that worked. Thank you for the help!
1 Like