Error Starting The Service Backup Exec Dlo
Contents |
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 backup exec dlo administration service won't start Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal symantec backup exec dlo Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas
Symantec Dlo Administration Service Not Starting
PartnerNet The Backup Exec DLO Administration Service on Local Computer started and then stopped. Some services stop automatically if they have no work to do for example, the
Backup Exec Desktop Laptop Option
Performance Logs and Alerts service. Article:000032688 Publish: Article URL:http://www.veritas.com/docs/000032688 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 Article Languages Subscribe uninstall backup exec desktop and laptop option to this Article Manage your Subscriptions Problem The Backup Exec DLO Administration Service does not start, after changing the Backup Exec Server Name and even after updating the Configuration for New Media Server Name under BEUtility. Error Message "The Backup Exec DLO Administration Service service on Local Computer started and stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts Service" Figure 1: The following error is listed in the Application Event log: (Figure 2) Event Type: Error Event Source: DLOAdminSvcu Event Category: None Event ID: 50040 Figure 2 Cause The new Backup Exec server name is not updated in the registry. Solution Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It
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
Backup Exec Desktop And Laptop Option Has Been Detected
ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor netbackup dlo Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA veritas dlo Site: Veritas Veritas PartnerNet DLO Administration service fails to start and gives error "service did not respond to the start or stop control command within the specific https://www.veritas.com/support/en_US/article.TECH50086 timeout period." Article:000020046 Publish: Article URL:http://www.veritas.com/docs/000020046 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 Article Languages Subscribe to https://www.veritas.com/support/en_US/article.000020046 this Article Manage your Subscriptions Problem DLO (Desktop and Laptop Option) Administration service fails to start and gives error "service did not respond to the start or stop control command within the specific timeout period." Error Message Event Viewer Application log on DLO server shows following error events: Log Name: ApplicationSource: DLOAdminSvcuEvent ID: 50030Level: ErrorDescription:The description for Event ID 50030 from source DLOAdminSvcu cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.If the event originated on another computer, the display information had to be saved with the event.The following information was included with the event: 735shadow\Server\consolesvc\consolesvc.cpp0x80004005: ADODBError-_com_error: foundationerror=80004005, comerr=80004005, nativeerror=916, conn=Provider=SQLOLEDB;Data Source=Servername\DEDUPE;Initial Catalog=master;Integrated Security=SSPI;Connect Timeout=120, query=EXEC sp_detach_db N'dedupedb', msg=Unspecified error, src=Microsoft OLE DB Provider for SQL Server, desc=The server principal "Domain\User" is not able to access the database "dedupedb" under the current security context
for 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 https://www.experts-exchange.com/questions/27185293/Backup-Exec-Logon-Failure-When-Starting-Services.html 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 > Backup Exec Logon Failure When Starting Services Want to Advertise Here? Solved Backup Exec Logon Failure When Starting Services Posted on 2011-07-07 Windows Server 2003 Storage Software 1 Verified Solution 3 Comments 1,362 Views Last Modified: 2012-05-11 Hello, A backup exec couple months ago people working in an office that I started managing changed their administration password on their Windows 2003 server. Because their original IT guys set up backup exec to use the administrator account it obviously stopped working. I created a new Domain admin account called backups and set all services to that. Everything worked fine. Today I logged on the server to a dialog that the server backup exec dlo had crashed (not sure what caused it). When logged in I could no longer start Backup Exec and I could see that the MSSQL service wasn't working because of a logon failure. I didn't realize that I hadn't changed the service logon password for the SQL database. However, before I realized this I reset the password for backups. So I set the SQL server to use this account when starting the service and the MSSQL server is now loading fine. However, backupexec will still not load. I get the default dialog that services are stopped so I click on "Service Credentials" and input the new password for the backups account. However, the issue remains the same. I attached the messages that show up in the dialog as it is restarting, the error that is being returned is a logon failure. Does anyone know why this is happening? Thank you. Processing services Stop services on server: OCTOPUS01 Stopping Backup Exec DLO Maintenance Service on OCTOPUS01. The service Backup Exec DLO Maintenance Service on OCTOPUS01 is already stopped. Stopping Backup Exec DLO Administration Service on OCTOPUS01. The service Backup Exec DLO Administration Service on OCTOPUS01 is already stopped. Stopping Backup Exec Agent