Attempting to add a Microsoft Office SharePoint Server 2007/2010 Farm in backup selections gives an "Access Denied" error or "Backup Exec cannot confirm the SharePoint Topology"

Article:TECH58121  |  Created: 2008-01-28  |  Updated: 2013-03-05  |  Article URL http://www.symantec.com/docs/TECH58121
Article Type
Technical Solution


Issue



Attempting to add a Microsoft Office SharePoint Server 2007 Farm in backup selections gives an Access Denied error or Backup Exec cannot confirm the SharePoint Topology

OR 

Failed SharePoint restore job with "Unable to lock the Microsoft SharePoint Portal Farm. "


Error



Access Denied

OR

None of the web server for the specified server farm could be accessed

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

OR

V-79-57344-790 - Error: Unable to lock the Microsoft SharePoint Portal Farm.  Check the option to release the lock on the SharePoint farm topology on the backup job properties for Microsoft SharePoint, and then retry the job.

OR

Connection to the restore target has been lost.  Operation canceled.


Environment



Some of the errors listed on this page also have other resolutions.  To verify this condition you MUST enable debugging on the remote servers and find the "process NOT ready!"


Cause



The error 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.
 

Solution



The Microsoft patch must be applied to all SharePoint web servers in the farm. Then, a config file named "SPSWrapper.exe.config" and "SPSWrapperV3.exe.config" must be created and placed in the directory where SPSWrapperV3.exe is located on each of the web servers as per the 'More Information' section of the article.


Creating the Config Files for SharePoint 2007 in Windows Server 2000/2003/2008:-

1. Create a new text document spswrapper.exe.config and paste the following information into it.

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

2. Save spswrapper.exe.config and place it in the "WINDOWS\Microsoft.NET\Framework\v2.0.50727" folder and the Backup Exec Remote Agent installation folder

3. For versions of .NET Framework 3.0, create a new text document spswrapperv3.exe.config 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 "WINDOWS\Microsoft.NET\Framework\v3.0 and 3.5" folders.
5. Now save a copy of both files in "C:\Program Files\Symantec\Backup Exec\RAWS".


Creating the Config Files for SharePoint 2010 in Windows Server 2008:-

1. Create a new text document spswrapper.exe.config and paste the following information into it.

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

2. Save spswrapper.exe.config and place it in the "WINDOWS\Microsoft.NET\Framework\v2.0.50727" folder and the Backup Exec Remote Agent installation folder
3. For versions of .NET Framework 3.0, create a new text document spswrapperv4.exe.config 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 spswrapperv4.exe.config and place it in the "WINDOWS\Microsoft.NET\Framework\v3.0 and 3.5" folders.
5. Now save a copy of both files in "C:\Program Files\Symantec\Backup Exec\RAWS".

 

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/SPSWrapperV4.exe to load, which will allow the SharePoint farm to be added and selected in backup selections.

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\spswrapperv4.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.


NOTE:

This fix is contained in Microsoft .NET Framework 2.0 SP1.

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


Supplemental Materials

SourceUMI
Value V-79-57344-790
Description

Unable to lock the Microsoft SharePoint Portal Farm.  Check the option to release the lock on the SharePoint farm topology on the backup job properties for Microsoft SharePoint, and then retry the job.



Legacy ID



300675


Article URL http://www.symantec.com/docs/TECH58121


Terms of use for this information are found in Legal Notices