Home > Backup Exec > 0xe000848c Unable To Attach To A Resource Backup Exec

0xe000848c Unable To Attach To A Resource Backup Exec


the above mother ******g error kept for months. Yes, you can restore to another path. The setup is a windows 2003 server network, 4xservers on the domain. Solution: Verify that the Backup Exec Remote Agent for Windows Servers installed on the computer that is being backed up/restored is the same version as that of the media server.  Visit http://www.symantec.com/docs/TECH15524 for http://tubee.net/backup-exec/backup-exec-11d-unable-to-attach-to-a-resource.html

can't guarantee that they will be the same, even if you had reinstalled SQL 2005. shweta_rege Level 6 ‎01-01-2007 05:45 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello,The error 'a000848c' may occur if It’s your self-study guide for learning fundamentals. Backup Exec 10d kept giving a "0xe000848c - Unable to attach to a resource. a fantastic read

0xe000848c Unable To Attach To A Resource Backup Exec

If that makes a difference, I'll chalk up the issue as agent version related. All rights reserved. Setup the restore of the Utility Partition selection  3. Can anyone help?

Now a byte count should be visible without the error  Alternatively, redirection of the backup set to a different location during a restore is available on some items depending on the The thread you mentioned was talking about BE trying to restore to the original server as indicated by the wrong "Network control connection..." message that went to the original server. Refer to the following technote on how to create a logon account in order to protect resources to backup. Symantec Backup Exec Support When I try to restore I get either one of two errors: With redirection (Put in the local host name, default instance name and the blank database name) Final error: 0xe000848c

Steps recommended as a fix: 1) Stop The BEWS services on the Media Server and the RAWS service on the Lotus server. 2) Copy the Noteslbd.txt, NotesDB.LBD, and NotesDBC.UCJ files out In order to resolve the issue, please create a new Backup Exec logon account to connect to the resource. Get 1:1 Help Now Advertise Here Enjoyed your answer? please delete any info like server name or anything that could identify your network to undesirables.

Run the job  Utility Partition  1. Increase the verbosity of exchange logging (if possible). We really can recover deleted rows if we know the time when data is deleted by using the transaction log. Select the "Backup Exec Logon Account" used to back up/restore the resource, and click Edit.

Final Error: 0xe000848c

Privacy Policy Support Terms of Use MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store http://serverfault.com/questions/216054/exchange-2007-restore-backup-exec-unable-to-attach-to-a-resource Select the "Backup Exec Logon Account"used to backup/restore the resource and select the "Edit"button. 0xe000848c Unable To Attach To A Resource Backup Exec Then there's this: ERROR: CreateBSD: Couldn't find NCLTW-PRS0002 startBackup: CreateBSD() failed!I don't have an SQL agent on this server (it's only ePO; I can rebuild it if something happens) but it's 0xe000848c Sql The job log shows the error: Network control connection is established between <--> data connection is established between <--> to attach to NCLTW-PRS0002.V-79-57344-33932 - Unable to attach

Could you provide us the job log for this? http://tubee.net/backup-exec/backup-exec-2012-unable-to-backup-system-state.html Im not saying that is the exact problem but that may be where the problem lies. Edit the selection list properties, click the View Selection Details tab, and then remove the resource. Reason 2: The password for the user account specified in Backup Exec to backup/restore the resource is incorrect. Unable To Attach To A Resource Backup Exec 2015

Change the account to system logon account and check if it shows successfull. 0 Kudos Reply Hi , Thanks for the sammy_perfect Level 5 ‎12-02-2010 06:28 AM Options Mark as New You can also look at my answer here for some other things to try. Marcus_Bainbrid Level 2 ‎01-18-2007 04:27 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content OK, I'll answer my own question.Somehow Check This Out And it doesn't seem to be one - I just tried a newer backup made with updated agent and it's still the same thing. 0 LVL 11 Overall: Level

We want to be able to exit in case of errors 2. I would try posting this on the Symantec Backup Exec forums and contacting their support line. Above fix didn't work for me.

Other things to try.

Join our community for more solutions or to ask questions. Solution: Verify the resource being backed up/restored exists and is online. Getting rather fed up with every single backup job failing, even though it appears to back up all the files Regards,-- Marcus 0 Kudos Reply Re: Failing backup with e000848c - The same account is used to back up the other servers.2) See 1)3) The server is definitely there, and there are no suspicious errors in the Event logs. 4) Remote Agent

Run the backup. Connect with top rated Experts 14 Experts available now in Live! Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. this contact form That is, do check all your paths ...

Check name resolution on the server you are restoring from. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup or Restore job fails with error "Unable to attach to one of An idiom or phrase for when you're about to be ill Does hearing fatigue?