Event Type:Warning Event Source:PlugPlayManager BE 7.01 Windows XP 64 bit OS

[rkramer40]

I am running Windows XP 64 bit version.  The error listed below is repeated every 2 minutes.  It can be stopped only by restarting the vproSvc service…. Then re-appears after the completion of the next backup.  Any thoughts.

Storage Volumes are on an E200I HP Raid contoller (latest firmeware) (2) 80 gig (raid1)  (2) 160gig (raid1) Sata drives.  Additional devices…  (1) 35 GIG Iomega REV drive  and (1) 500 gig usb attached hard drive.

Event Log

Event Type:        Warning

Event Source:    PlugPlayManager

Event Category:                None

Event ID:              257

Date:                     8/25/2007

Time:                     6:18:30 AM

User:                     N/A

Computer:          ML350VMHOST

Description:

Timed out sending notification of target device change to window of "C:\Program Files (x86)\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe"

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

[David_F]

You may want to consider the following suggestions in your troubleshooting of this issue:

(1) Complete uninstall and reinstall of the 7.01 or later build BESR product. Please see the following attachment to obtain the uninstall batch file needed to remove artifact files that may remain after an Add & Remove uninstall of the product.

Is there an uninstall.bat file for BESR 7.0?
http://support.veritas.com/docs/292055

(2) Verify under the new install that backup storage devices seen in TOOLS> “Manage Backup Destination” are those for the current backup jobs and not those for backup destinations from the previous install(s); especially external storage devices like USB or firewire. Backup locations that were physically removed but still exist in the “Manage Backup Destination,” though the backup jobs are edited to backup to a new storage drive(s) could result in this error.

(3) Be sure that backups do not coincide with other backup products (e.g. Backup Exec) that may be attempting to create an image of the same drive BESR is attempting to backup.

(4) If relational databases are running on this system (SQL or Exchange) be sure to configure any maintenance jobs to run and complete prior or after the recovery point image creation job is scheduled to launch.

[cs_master]

we have the same problem, but with a different OS. We are running Windows 2003 Server Enterprise x64 SP1 with Microsoft cluster and we have this error message on both nodes, 10 messages every 5 minutes.
This cluster is a micosoft sql 2005 cluster

We have installed Symantec BESR 7.0.3.24709 with management control 7.0.3.24784

Since this installation, there are many other problems:

• to start a windows explorer requires about 20 seconds
• to start symantec BESR requires about 20 seconds, and the performance is very slow
  
• logout from windows, the process VProTray.exe will not end
  

we have this problem only on this cluster, is there any fix available to solve this problem?

[VODA-LP]

We've got a customer with a WS2003 x64 server, running BESR 8.5.5.33937.  Hours after the backup starts (maybe after the verify operation?) we start seeing Event 257 show up repeatedly three times in succession, every two minutes.  So at 6:50:14 AM there will be three of these errors.  Then at 6:52:14AM there will be three more.  And so on, until the server becomes completely unresponsive, even to a console Ctrl-Alt-Del and needs to be power cycled.

This originally started sometime into our usage of BESR 7.01.  We had it co-existing with Backup Exec 11d on the same server for probably a year or more, running fine.  Backups ran at different times, no problems.  Not sure the circumstances surrounding when this error first started appearing.

We've removed the antivirus software (NOD32 3.x, also tried NOD32 4.x), removed BE11d, and tried a host of other things yet it persists.  Completely removed BESR 7.01 and installed BESR 8.5.5.  Same thing.

As a workaround, I'm considering scripting a restart of the vprosvc (Backup Exec System Recovery) service at the END of the backup job, as I see above someone mentioned restarting the BESR service gets rid of the error.

There is also an MS article and hotfix that describes the error message, but the details surrounding their example don't fit.  I'm considering this hotfix as another option, but don't want to "shotgun" the server with multiple attempts at solving.  The MS article is at: support.microsoft.com/kb/924390

I've got BESR running on multiple servers, different customers, and it's a killer product.  Love it.  But in this one case, it's murder.  Any ideas/suggestions?  A workaround like scripting a restart of the service is not an acceptable solution.

[VODA-LP]

BTW, some details on the server and infrastructure:

• WS2003 x64 SP2
• All Windows updates current
• Is a domain controller, DNS, WINS, DHCP (about 75 computers/users on network)
• Is Exchange 2007 server
• BESR runs at night, little to no users accessing network
• No other backup or maintenance jobs scheduled during the time of the backups
• Doesn't always freeze up, doesn't always exhibit the event above
• Details of PlugPlayManager Event 257: 

  Timed out sending notification of target device change to window of "C:\Program Files (x86)\Symantec\Backup Exec System Recovery\Agent\VProSvc.exe"

• Symantec BESR updates up to date
• Antivirus exclusions on Symantec BESR destination folders
• Server is HP ProLiant ML370 G5, with all HP firmware, BIOS, drivers up-to-date except NIC drivers as the latest ones were causing both HP ML370s onsite to never pass the "Preparing Network Connections" part of the OS startup, so we're 1-2 versions behind on them.
• Backup destination is external 1TB SATA drive in USB enclosure, so USB interface (have to connect this to the rear USB ports, as nothing requiring more power than a mouse or keyboard seems to work in the front of HP's servers)
• After removing BESR 7.01, also deleted all backups created by BESR 7.01 and installed 8.5.5, did manual backup; no issues on that backup.
• No offsite configured at this time
• Not backing up any other servers

[criley]

VODA-LP,

Just wondered if you had any updates on this issue? Have you tried the MS hotfix yet?

[VODA-LP]

Just started seeing this behavior on a second server at the same site, interesting similarity.

• This second server is WS2003 x32, so that's different.
• Has been working fine for the last 1.5 months, which is the last time I saw this error (PlugPlayManager) on that server.
• This server is running BESR 8.0.4.30166.
• What changed before the last BESR 8.0 snapshot is I installed Backup Exec 12.5 to the server, allowed it to install Symantec drivers.
• BESR is backing up to an external USB drive, like the first server.
• Haven't setup any jobs yet in BEWS 12.5, but services are running.
• Also is an HP ProLiant ML370 G5, all HP firmware BIOS, drivers up-to-date except NIC drivers as the latest ones were causing both HP ML370s onsite to never pass the "Preparing Network Connections" part of the OS startup, so we're 1-2 versions behind on them.

[VODA-LP]

Chris, thanks for replying.

I have not yet patched it; wanted to ensure we had a full server backup before doing so, ironically.

I will need to escalate these issues to Symantec phone support; what's the best number to call for Canada?

[criley]

Details for contacting support are here:

http://www.symantec.com/business/support/contact_techsupp_static.jsp

[VODA-LP]

Thanks!

[bob_geysen]

We are seeing the same problem on several machines w2k3 x86  besr 8.5 

Server freezes.

Is there a fix for this???

regards

Bob