Backup Exec Pvl Service Error
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec Device and Media Service (PVLSVR.EXE) will not start after a fail over occurs on Backup Exec 2012 cluster installation. Article:000086150 Publish: Article URL:http://www.veritas.com/docs/000086150 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec Device and Media Service (PVLSVR.EXE) will not start after a fail over occurs on Backup Exec 2012 cluster installation. The Device and media server service terminates and will not start. The Backup Exec cluster resource may not come back online in the Windows Cluster manager. Error Message Application Log Name: ApplicationSource: Application ErrorEvent ID: 1000Task Category: (100) Description:Faulting application name: pvlsvr.exe, version: 14.0.1798.104, time stamp: 0x4f8d9bc5Faulting module name: pvlsvr.exe, version: 14.0.1798.104, time stamp: 0x4f8d9bc5Exception code: 0xc0000005Fault offset: 0x00000000000bb782Faulting process id: 0x1700Faulting application start time: 0x01cd80ae75e7717dFaulting application path: C:\Program Files\Symantec\Backup Exec\pvlsvr.exeFaulting module path: C:\Program Files\Symantec\Backup Exec\pvlsvr.exeReport Id: bcee243b-eca1-11e1-8e4a-00155d588110 Cause Issue occurs on fail back when the disk storage device had been configured before the first fail over. Solut
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet PVLSVR.exe service crashes on Central Admin Server(CASO) in Backup Exec 2012 https://www.veritas.com/support/en_US/article.TECH195477 Article:000018761 Publish: Article URL:http://www.veritas.com/docs/000018761 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article https://www.veritas.com/support/en_US/article.000018761 Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem I may be seen that the PVLSVR.exe service crashes on the Central Admin Server(CASO) during service startup in Backup Exec 2012 with SP2 installed. Error Message Errors seen in the event logs: Application Event Logs:======================================================Type : ErrorTime : 11:36:06 AMEvent : 58053Source : Backup ExecDescription:Backup Exec Alert: Storage Error(Server: "ServerName") The drive hardware is offline.Please confirm that the drive hardware is powered on and properly cabled. Type : ErrorDate : 9/17/2013Time : 11:36:03 AMEvent : 33152Source : Backup ExecCategory : (1)User : N/AComputer : Domain.ServerName.comDescription:Adamm Mover Error: GetDriveInfo Failure!Error = ERROR_INVALID_HANDLEDrive = "Tape drive 0001"{A8E56AC1-B8F6-4BAC-B5D0-150AAD535C23}Media = ""{00000000-0000-0000-0000-000000000000}Read Mode: SingleBlock(0), ScsiPass(0)Write Mode: SingleBlock(0), ScsiPass(0) Type : ErrorDate : 9/17/2013Time : 11:36:03 AMEvent : 33152Source : Backup ExecCategory : (1)User : N/AComputer : Domain.ServerName.comDescription:Adamm Mover Error: GetDriveInfo Failure!Error = ERROR_INVALID_H
Join Now Hey guys. I have a server that is running Backup Exec on it. Recently, it is starting to hang up in the middle of the night https://community.spiceworks.com/topic/127148-backup-exec-12-5-jobs-failing-and-locking-up-server and requires a hard boot (i.e, power button) to get it back up. I checked the event logs and the job monitor in BE, and I noticed the job is failing. I am not a https://www.experts-exchange.com/questions/21792256/After-reinstalling-Backup-Exec-10d-can-not-view-resources-local-or-otherwise.html BE expert by any means, so that is why I came here! I see the following errors... In BE under Job Monitor, the Daily Incremental backup has failed two nights in a row now and backup exec this is the description it gives: CriticalServer-StdPolicy-Daily Backup Job name: CriticalServer-StdPolicy-Daily Backup Job type: Backup Job status : Failed Job log: C:\Program Files\Symantec\Backup Exec\Data\BEX_SERVERNAME_01034.xml Server name: (SERVERNAME) Selection list name : CriticalServer Device name: BTD2 Target name : DailyPool Media set name: IncrementalSet All Media Used B2D000027 B2D000291 B2D000292 B2D000293 B2D000028 B2D000029 Error category: Job Errors Error: e0008821 - Job was recovered as a result of Backup Exec RPC service starting. backup exec pvl No user action is required. For additional information regarding this error refer to link V-79-57344-34849 Under event viewer, I am seeing the following Event ID flooding the App event log: EventID: 57345 Database Exception Context:BENEDB::GetSession Error:-536837662: :: -2147467259: :: DB Error Set 0: native=0x1 source= hr=0x1 GetErrorInfo() failed. EventID: 33152 Adamm Database Event: Database Connection Lost! Error = E_PVL_DB_LOST_CONNECTION Server = "(SERVERNAME)" Active Node = "" Instance = "BkupExec" Database = "BEDB" Connection String = "DRIVER=SQL Server;SERVER=(SERVERNAME)\BkupExec;DATABASE=BEDB;App=BEWS PVL" EventID: 33152 Adamm Database Event: Open Database Connection Failed! Error = ERROR_DATABASE_DOES_NOT_EXIST Server = "(SERVERNAME)" Active Node = "" Instance = "BkupExec" Database = "BEDB" Connection String = "DRIVER=SQL Server;SERVER=(SERVERNAME)\BkupExec;DATABASE=BEDB;App=BEWS PVL" The Backup Exec Device and Media Service could not connect to the specified database. Ensure that the specified database is running, and then try starting the service again. If this is a remote database, also ensure that the firewall is properly configured. All we are doing is running a Daily Incremental backup that targets a media pool for 3 SCSI disks. A Full Backup is run every Friday targetting the 3rd one of those disks. We also run another app on this server and every night for the past week at the same time as these events are generated, the serv
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > After reinstalling Backup Exec 10d, can not view resources (local or otherwise). Want to Advertise Here? Solved After reinstalling Backup Exec 10d, can not view resources (local or otherwise). Posted on 2006-03-28 Storage Software Storage 1 Verified Solution 5 Comments 12,718 Views Last Modified: 2013-12-01 We had some issues with the server and were forced to reinstall Backup Exec and since then we have been unable to view any resources to be able to make selections. It will not even see the local drives or other such resources. *FULL DIAGNOSTIC BELOW* Symantec Backup Exec for Windows Servers Diagnostics Copyright 2005 Symantec Corporation. All rights reserved. Diagnostics initiated from \\DHDSERVER by DHDLLP\administrator at 10:45:55 03/28/2006 Command line: bediag "/o:C:\Program Files\VERITAS\Backup Exec\NT\Data\bediag.fax" DHDSERVER ============================================================================== ============================================================================== Backup Exec License Information on \\DHDSERVER: Eval Edition ------------------------------------------------------------------------------ ******** BEGIN adamm.log file ******** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [1148] 03/27/06 15:34:00 Adamm Log Started! ("DHDSERVER", 1000, {C9AB739A-1AA3-4119-9088-7