Hi all.  II have an error which seems very basic but generic, yet the suggested solution just seems to be way toounusual for such a vanilla setup I have here. 

I have a backup job for Exchange 2010.  BE 2010 R3 media server is on the 2008 R2 system that is a Hyper-V host. The (sole) Exchange 2010 SP1 server is on a VM on this host.  The backup job is created to back up the Information Store (there is only one mbx database).  When I run the job, I get this error:

Job ended: Tuesday, November 15, 2011 at 8:39:59 AM
Completed status: Failed
Final error: 0xe0000391 - Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-913

 If I click on the link within the job log for the article V-79-57344-913 , it brings me to a page that talks about communications issues with Powershell with a fix that involves editing the registry on the Exchange machine to add a DWORD value.  For such a basic, vanilla server/BE setup that I have here I am skeptical of why this would be the final solution.  For such a generic error to have such a specifc fix makes me doubt it's vaildity especially when it might stand to reason that this error could happen to many people.  I would go ahead with it, except than if I Google for the very same article # I  get different versions of this same article and the solution is entirely different 0 no PowerShell registry edit, just some regular troubleshooting of account credentials. 

So rather than rely on these articles I would rather ask here if anybody can suggest anything or even just to say yes, the powershell registry edit is the only fix, or something else suggested is most welcome as well. I will look into the credentials related issues now. 

Thank you.