Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

IP Change

Created: 10 Jun 2013 • Updated: 11 Jun 2013 | 3 comments
This issue has been solved. See solution.

Hello,

We moved our primary and secondary media servers to a DMZ today.  This required assigning new IP addresses to the media servers.  Now, the services will not start on either server.  I went into the BEUtility to the Update Configuration to Reflect New Media Server Name and entered the information into the dialog box.  We still get an error when starting the services.  The Backup Exec Device & Media Service fails to start and returns error code 0x2000e2d3 (536928979).  I tried starting the service with BEUtility and it returned and error 1056 - An instance of the service is already running.  Also even though I updated the server configuration, a "?" still appears next to the media server in BEUtility with the status as unknown.  Any help is greatly appreciated.  Thanks!

William

Operating Systems:

Comments 3 CommentsJump to latest comment

Sush...'s picture

You may also want to refer to following technotes

http://www.symantec.com/docs/TECH77113 : Backup Exec Device & Media Service terminated with service-specific error 536928979 (0x2000E2D3)

    http://www.symantec.com/docs/TECH59527 : The Backup Exec Device and Media Service terminated with service-specific error 536928979

http://www.symantec.com/docs/TECH163556 : After an install or upgrade of Backup Exec 2010, Backup Exec device and media service fails to start with error 536928979

http://www.symantec.com/docs/TECH126275 : Backup Exec Device and Media Service fails to start with error "The Backup Exec Device & Media Service terminated with service-specific error 536928979"

Thanks,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

sdcadmin's picture

Thanks for the links.  We had to use the fully qualified name for the log on account in order to start the service instead of the user name.  Why this changed I don't know moving to a DMZ required the change.  I guess this would fall under #3 of VJ's link.

Thanks!