10-26-2010 07:05 AM
Hi.
The service vprosvc.exe hangs sometimes. It is impossible to restart it. When I try to kill the process vprosvc.exe I get the error message "access denied". I tried pskill.exe with another admin account but I get the same error.
The best would be to restart the server, I know. As it is a production server with Exchange on it, it's not very practical...
Anyone with an idea how to kill the process?
Best regards.
G
Solved! Go to Solution.
01-27-2011 02:34 AM
The installations have been upgraded to the latest version.
10-26-2010 10:12 AM
Event Type: Warning
Event Source: PlugPlayManager
Event Category: None
Event ID: 257
Date: 26.10.2010
Time: 18:32:38
User: N/A
Timed out sending notification of target device change to window of "C:\Program Files\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe"
Here was the underlying process blocking vprosvc.exe: PlugPlayManager
That's what I found in the event log after rebooting the server.
10-26-2010 12:07 PM
Try to logon as local system and kill the process or use taskkill /IM vprosvc.exe /F.
11-11-2010 12:13 AM
Any updates ?
12-09-2010 07:41 AM
I wanted to wait to see if the process would froze again. It happened today. The last time I solved it by restarting the server outside office hours.
How can I logon as local system?
The taskkill /IM vprosvc.exe /F returns the same as the task manager kill process: Access is denied.
Regards.
G
12-09-2010 09:07 PM
You might schedule the taskkill using an AT. This should run the command in the context of Local system.
12-10-2010 12:43 AM
I tried with the sheduled task... no luck:
0x1: An incorrect function was called or an unknown function was called.
I made sure I had the correct syntax.
I tried with psexec... no luck:
PsExec.exe -s taskkill /IM vprosvc.exe /F
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
ERROR: The process "VProSvc.exe" with PID 1684 could not be terminated.
Reason: Access is denied.
taskkill exited on SRVEX01 with error code 1.
Regards.
G
12-10-2010 03:07 AM
Then you have to reboot I think.
12-15-2010 12:18 PM
Any news here ?
12-17-2010 12:45 AM
The server was rebooted and things got back to normal.
I am planning an update of the BESR 2010 installation during the next maintenance window. I'll see if the problem was triggerd by BESR or a Windows component.
Regards.
G
01-13-2011 12:44 AM
So would you please mark this post as solved ?
01-17-2011 01:12 AM
Having to reboot a server to solve a problem is not what I call a solution.
01-17-2011 03:15 AM
So have you upgraded to BESR 2010 SP2 in between ?
01-27-2011 02:34 AM
The installations have been upgraded to the latest version.
02-02-2011 05:52 AM
The issue still comes up ?
02-09-2011 03:44 AM
Time will tell us...
03-17-2011 04:33 AM
Has the issue come up again ?
03-21-2011 06:05 AM
Nope, everything is running smoothly since the update to SP2.
03-21-2011 12:41 PM
Has time told you enough to mark this post as solve ? ;)
03-23-2011 02:54 AM
Boom, it's solved.