Backup Exec 12.5: V-79-57344-33932 - Unable to attach to a resource Windows 2003 server

We have a Windows 2008 STD server with Exhange 2007. When I try to restore some emails, I get the error:

[i]-- The job failed with the following error: Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.
[/i]

I attached the result of the Debug Monitor as well.

What we did already:
-Try different credentials
-Complete LMhost file
-Install SP3
-Restart all backup exec services

Who can help me with this?


I do a restore with the system logon account, which is Exchange Administrator
BKUPEXEC: [04/20/10 18:35:22] [0000]     UIVirtualObjectView(JobHistoryView) Queried 121 items: 0 to 120
BKUPEXEC: [04/20/10 18:35:02] [5813]     Cluster" key does not appear to be present in the registry
BKUPEXEC: [04/20/10 18:35:02] [5813]     ailed to open Microsoft cluster ()
BKUPEXEC: [04/20/10 18:35:02] [5813]     CS cluster keys do not appear to be present in the registry
BKUPEXEC: [04/20/10 18:35:02] [5813]     ailed to open VCS cluster ()
BESERVER: [04/20/10 18:35:02] [5837]      "Cluster" key does not appear to be present in the registry
BESERVER: [04/20/10 18:35:02] [5837]      Failed to open Microsoft cluster ()
BESERVER: [04/20/10 18:35:02] [5837]      VCS cluster keys do not appear to be present in the registry
BESERVER: [04/20/10 18:35:02] [5837]      Failed to open VCS cluster ()
BENGINE:  [04/20/10 18:35:03] [5466]      "Cluster" key does not appear to be present in the registry
BENGINE:  [04/20/10 18:35:03] [5466]      Failed to open Microsoft cluster ()
BENGINE:  [04/20/10 18:35:03] [5466]      VCS cluster keys do not appear to be present in the registry
BENGINE:  [04/20/10 18:35:03] [5466]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:32] [0000]     BECryptoInit: BECrypto non-FIPS mode successfully enabled.
BENGINE:  [04/20/10 18:35:32] [0000]     BECryptoInit: BECrypto non-FIPS mode successfully enabled.
BEREMOTE: [04/20/10 18:35:33] [0000]     BECryptoInit: BECrypto non-FIPS mode successfully enabled.
BENGINE:  [04/20/10 18:35:33] [0000]     BECryptoInit: BECrypto non-FIPS mode successfully enabled.
BEREMOTE: [04/20/10 18:35:03] [1231]      "Cluster" key does not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open Microsoft cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      "Cluster" key does not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open Microsoft cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      "Cluster" key does not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open Microsoft cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      "Cluster" key does not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open Microsoft cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BEREMOTE: [04/20/10 18:35:03] [1231]      VCS cluster keys do not appear to be present in the registry
BEREMOTE: [04/20/10 18:35:03] [1231]      Failed to open VCS cluster ()
BKUPEXEC: [04/20/10 18:35:33] [0000]     UIVirtualObjectView(JobHistoryView) Queried 122 items: 0 to 121
BKUPEXEC: [04/20/10 18:35:42] [0000]     UIVirtualObjectView(JobHistoryView) Queried 122 items: 0 to 121

Open in new window

mbdeskAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rodney BarnhardtServer AdministratorCommented:
You mentioned you use a the system account. Is that a domain account, with a mailbox, and other permissions, or the local system account? I believe BE requires the use of an account with an active, unhidden mailbox on the Exchange server. This prevents bogus restores.
Also, you don't mention if you are using GRT. If so, you may want to look at the following requirements.
http://seer.entsupport.symantec.com/docs/288777.htm 
 
mbdeskAuthor Commented:
Thanks for your help.

The system account is a domain account and it has an unhidden mailbox.
I'm using GRT and I have done everything which is mentioned in your link.

I see something strange when I look into  "resource credentials" tab of the restore job. When I do a credential test on the job, the test results says: "Resource not found". I've put a printscreen as attachment.
Schermafbeelding-2010-04-20-om-2.png
mbdeskAuthor Commented:
The problem was due to the fact that we did make a recovery storage group, which was not needed.
Thanks anyway for your support.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.