Exact Error Message
Access Denied

OR

An error was encountered while attempting to browse the contents of Server Farm.
Although the specified server is a SharePoint resource,Backup Exec cannot confirm the topology.
Review your sharepoint credentials and ensure services are running on the Web servers

Details:

When attempting to add a Microsoft Office SharePoint Server 2007 (MOSS) or Windows Sharepoint Services 3.0 Farm to backup selections under the 'Microsoft SharePoint Server Farms' icon by adding the web server name, an Access Denied error is returned after about 30 seconds.  This may occur because one of the Remote Agent processes that Backup Exec relies on to connect to MOSS,  SPSWrapperV3.exe, does not start.  In order to determine whether this issue is being encountered, the SharePoint server Backup Exec Remote Agent debug must be reviewed. See Related Documents for information on creating debug logs for the Backup Exec SharePoint Agent.  The excerpt below from the Remote Agent (beremote.exe) debug shows initiating the SPSWrapperV3 process with the 'process ready?' entry.  In the case where the SPSWrapperV3 process does not start, 30 seconds later the debug log shows 'process not ready!':


[4276] 11/28/07 16:47:15 process ready?
[4276] 11/28/07 16:47:45 process NOT ready!

The SPSWrapperV3 process is allowed 30 seconds to start up by the Remote Agent.  If this time elapses before the SPSWrapperV3 process starts, the Remote Agent debug will show 'process NOT ready!', and the Access Denied error will be received.  This condition can be caused by the fact that the SPSWrapperV3.exe managed application is digitally signed, and something in the environment is preventing the signature from being verified.
Error from the selection list:
Fig. 1




Solution
The Microsoft Knowledge Base (KB) article 936707 entitled "FIX: A .NET Framework 2.0 managed application that has an Authenticode signature takes longer than usual to start" provides a resolution to the problem by allowing the disabling of signature verification for a specific managed application. Currently this KB article is available from  
http://support.microsoft.com/?kbid=936707
The Microsoft patch must be applied to all SharePoint web servers in the farm. Then, a config file named "SPSWrapperV3.exe.config" must be created and placed in the directory where SPSWrapperV3.exe is located on each of the web servers per the 'More Information' section of the article.  

Creating the Config Files in Windows Server 2000/2003/2008:
1. Create a new text document and paste the following information into it.

<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>

2. Save the file as spswrapper.exe.config and place it in the "WINDOWS\Microsoft.NET\Framework\v2.0.50727" folder and the Backup Exec Remote Agent installation folder "C:\Program Files\Symantec\Backup Exec\RAWS".
3. For versions of .NET Framework 3.0,  create a new text document and paste the following information into it.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>

4. Save the file as spswrapperv3.exe.config and place it in the "C:\Program Files\Symantec\Backup Exec\RAWS " and "WINDOWS\Microsoft.NET\Framework\v2.0.50727" folders.
Once the .NET Framework fix is applied and the .config files created it should take significantly less time for the SPSWrapper.exe or SPSWrapperV3.exe to load, which will allow the SharePoint farm to be added and selected in backup selections.
Note:  The Fix referenced in the Acknowledgements section is also contained in Microsoft .NET Framework 2.0 SP1.

For Windows Server 2008, Microsoft has confirmed the patch has been applied to the operating system through .NET 2.0 Service Pack 1 and only the APPLICATION.EXE.CONFIG file is needed to resolve the issue.
The creation of this file must be saved with a .exe.config extension. Any other extensions like .doc, .rtf, or .txt will cause the file to be ignored by SPSWrapper.exe.

If the selection list is still not available and the above error is still observed, confirm no other file extensions have been appended to the SPSWrapper.exe.confiig file by following the steps below.

To remove the additional extensions from the file, remove the "Hide extensions for known file types" option by following the steps below.
1. Open Control Panel
2. Select Appearance and Personalization.
3. Select Folder Options.
4. Select the View tab.
5. To show file extensions, uncheck the "Hide extensions for known file types" checkbox.
6. Click OK button.
7. Check the file name and file extensions of the spswrapper.exe.config and spswrapperv3.exe.config

C:\Program Files\Symantec\Backup Exec\RAWS" folder and "WINDOWS\Microsoft.NET\Framework\v2.0.50727" folder.

If any other file extensions are appended to the file name, rename the file to remove the extension and restart the Backup Exec Remote Agent for Windows Servers service.

Related Documents:

275281: How to enable debug logging in Backup Exec 10.x or higher for the Agent for SharePoint Portal Server
 http://support.veritas.com/docs/275281

Acknowledgements
Microsoft KB 936707

---