Attempts to view SharePoint topology in SharePoint Server 2010 using the NetBackup GUI fail.

  • Modified Date:
  • Article ID:000095057


Unable to view the SharePoint topology in SharePoint Server 2010 -  backups also fail with status code 2 (none of the requested files were backed up) reported in the Activity Monitor.

Error Message

This is extract from within the Netbackup/logs/beds directory which shows a failure to enumerate - which in turn leads to the failure to display any objects:

Extract from SPSWrapper00.log
[2c3c] 01/04/13 13:03:30
[2c3c] 01/04/13 13:03:30 * VERITAS Backup Exec SharePoint Portal Server v3 Agent Debug Log *
[2c3c] 01/04/13 13:03:30 * Date-Time: Fri Jan 04 13:03:30 2013 *
[2c3c] 01/04/13 13:03:30
[2c3c] 01/04/13 13:03:30 Security initialized for multithread.
[2c3c] 01/04/13 13:03:30 Starting up exchange buffers and semaphores:
[2c3c] 01/04/13 13:03:30 Attempting to initialize semaphore: BE_SpsProcessReady141518D66312
[2c3c] 01/04/13 13:03:30 Attempting to initialize semaphore: BE_SpsRequestReady141518D66312
[2c3c] 01/04/13 13:03:30 Attempting to initialize semaphore: BE_SpsReplyReady141518D66312
[2c3c] 01/04/13 13:03:30 Attempting to initialize semaphore: BE_SpsReplyEmptied141518D66312
[2c3c] 01/04/13 13:03:30 Attempting to map file BE_SpsReqRep141518D66312
[2c3c] 01/04/13 13:03:30 We've mapped the view of the file....

...nothing else being reported


The wrappers used in the bpspsserver process have a timeout of 30 seconds - as a result, processes may exit before handshaking with .NET Framework has completed.  When this occurs, NetBackup is prevented from fully enumerating the SharePoint environment and will fail to populate the SharePoint icons in the Netbackup GUI Client.


The formal resolution for this issue (Etrack 3055770) is included in the following release:

  • NetBackup agent for SharePoint 7.5 Maintenance Release 6 (

NetBackup is now available - please access the Related Article below for more information.

Note: If you are running and up you still need to follow the steps below to create the registry key to extend the timeout value.

Please contact Symantec technical support, referencing this document Etrack 3055770 ( or Etrack 3152305 ( to receive an Emergency Engineering Binary (EEB) bundle containing a workaround for this issue and instructions for overriding the default timeout value.

Warning: Incorrect use of the Windows registry editor can have disastrous results on a server operating system. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

The following key(s) need to be created in the Netbackup Registry Hive after EEB installation.

To be applied to the SharePoint Frontend and any Index Application Servers;

Create a new Key called “Timeout“ under

Create a REG_DWORD value gettopology  under Timeout and assign it a decimal value to the number of Seconds for timeout.

For example, setting a value "200" - will allow just over 3 mins for the SPSwrapper to wait for a return from the .Net Framework.
Default behavior is 30 seconds.

Applies To

Sharepoint Server 2010 SP1
Microsoft Windows Server 2003 R2
Netbackup Enterprise Server 7.5.x.x

Other O/S and SharePoint versions may be affected as well.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)