Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Sharepoint backups fail - The logon account that was provided does not have valid credentials

Created: 07 Feb 2014 • Updated: 07 Feb 2014 | 5 comments

I'm backuping a Sharepoint 2010 Infra with Backup Exec 2010 R3.

Backups were running well for a while, but since 3 weeks, backups fail with error:

Final error: 0xe0009b61 - The logon account that was provided does not have valid credentials. Ensure that the user name and password are correct, and then try again.
Final error category: Security Errors

Nothing has changed in our SP farm or backup server.

 

When I try to browse the SP farm in the selection list, I have an "None of the Web servers for the specified server farm could be accessed" error as mentionned here: http://www.symantec.com/business/support/index?page=content&id=TECH134986

 

I followed the previous article without success.

Followed also related articles without success:

http://www.symantec.com/business/support/index?page=content&id=TECH129044&actp=search&viewlocale=en_US&searchid=1391774393031

https://www-secure.symantec.com/connect/forums/adding-sharepoint-farm-none-web-servers-specified-server-farm-could-be-accessed-error-e000fef

I checked persmissions in SP, SQL, Windows, all is fine.
 

Operating Systems:

Comments 5 CommentsJump to latest comment

lmosla's picture

Try uninstalling and reinstalling the remote agent. Then restart the remote agent services.

vigneshwaran's picture

First restart Backup Exec agent on share point server. If it's not come under selection list. do the above steps said by lmosla

- Vicky

 

Service Informatique's picture

Thank you two for your answers.

Some more informations I didn't specify due to lack of time last friday:

The only workaround is to uninstall the remote agent on the SP web server, then reinstall. After that SP Farm is browsable again in selection list. Backup run well for a day. Next day, same error. Sometimes restarting the agent on the SP web server will do the trick for one more day, but after that reinstall is necessary.

 

I also tried to delete and recreate the SP farm in the selection list without success.

 

Service Informatique's picture

When I debug what happens when i try to browse the sp farm, i got this in beremote.log:

[8368] 02/13/14 09:52:03 [fsys\spsv3]         - process NOT ready!
[8380] 02/13/14 09:52:09 [fsys\spsv3]         - GetTopology returned be0, from server S2SPFRONT, as user S2\backupexec
[8380] 02/13/14 09:52:09 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 1352(0x548) retval = 0
[8380] 02/13/14 09:52:09 [fsys\shared]        - FS_CreateTempDLE
[8380] 02/13/14 09:52:09 [fsys\spsv3]         - This is an SPS server, but we failed to get the topology
[8380] 02/13/14 09:52:09 [fsys\spsv2]         - ERROR: Could not connect to server S2SPFRONT
[8380] 02/13/14 09:52:09 [fsys\spsv2]         - This server is NOT an SPS webserver
[8380] 02/13/14 09:52:09 [ndmp\ndmpsrvr]      - DSEnumerator failed with -536805633: La machine spécifiée n'est pas un serveur SharePoint.
[8368] 02/13/14 09:52:09 [ndmp\ndmpsrvr]      - sslClose() : Closing SSL for: 00000000DF9D5BBF
[8368] 02/13/14 09:52:09 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 1404(0x57c) retval = 0
[8368] 02/13/14 09:52:09 [ndmp\tpfmt]         - FreeFormatEnv( cur_fmt=0 )
[8368] 02/13/14 09:52:09 [ndmp\tpfmt]         - FreeFormatEnv( cur_fmt=0 )
[8368] 02/13/14 09:52:09 [ndmp\ndmpsrvr]      - sslClose() : Closing SSL for: 00000000DF9D5BBF
[8368] 02/13/14 09:52:09 [ndmp\ndmpsrvr]      -  sslClose() : certinfo = 0  ; sslConn = 0
[11200] 02/13/14 09:52:43 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Security is enabled!!!
[11200] 02/13/14 09:52:43 [ndmp\ndmpcomm]      - GetCertificateDataFolderPath: Not checking for cluster.
[11200] 02/13/14 09:52:43 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: connect to target=157.26.166.27 port=6101 failed
[11200] 02/13/14 09:52:43 [ndmp\ndmpcomm]      - NrdsAdvertiserThread: Retrying in 60 seconds

The SPSWrapper.log was created, but almost empy:

[16b0] 02/13/14 09:21:11 *************************************************************************
[16b0] 02/13/14 09:21:11 * VERITAS Backup Exec SharePoint Portal Server v3 Agent Debug Log       *
[16b0] 02/13/14 09:21:11 *    Date-Time:        Thu Feb 13 09:21:11 2014                         *
[16b0] 02/13/14 09:21:11 *************************************************************************
[16b0] 02/13/14 09:21:11   Security initialized for multithread.

 

The more revelant information I found about this is this thread:https://www-secure.symantec.com/connect/forums/adding-sharepoint-farm-none-web-servers-specified-server-farm-could-be-accessed-error-e000fef

As I also have "- NDMPEngine::SetupNDMPConnection(): Using proxy authentication as requested", I tried to uncheck proxy configuration in Internet Explorer, for my domain admin account and backupexec account on the SP web server...

and now I can browse without error and backups run again... ?

I tried to enable proxy and restart agent to check that the proxy configuration is really in cause, but it's still working. I'm a little bit confused!

 

If I look at beremote.log I see that the SPS procees is now ok:

7224] 02/13/14 10:05:03 [ndmp\ndmpsrvr]      - LogonuserError: 0
[6556] 02/13/14 10:05:03 [fsys\spsv3]         - NDMPEngine::SetupNDMPConnection(): Using proxy authentication as requested
[7224] 02/13/14 10:05:03 [fsys\spsv3]         - process ready?
[7224] 02/13/14 10:06:00 [ndmp\ndmpsrvr]      - sslClose() : Closing SSL for: 00000000DF9BE9FF
[6556] 02/13/14 10:06:00 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 1276(0x4fc) retval = 0
[7224] 02/13/14 10:06:00 [BESocket]           - @@@@@@@MyCloseSocket called with sockfd = 1140(0x474) retval = 0
[7224] 02/13/14 10:06:00 [ndmp\tpfmt]         - FreeFormatEnv( cur_fmt=0 )
[7224] 02/13/14 10:06:00 [ndmp\tpfmt]         - FreeFormatEnv( cur_fmt=0 )
[7224] 02/13/14 10:06:00 [ndmp\ndmpsrvr]      - sslClose() : Closing SSL for: 00000000DF9BE9FF
[7224] 02/13/14 10:06:00 [ndmp\ndmpsrvr]      -  sslClose() : certinfo = 0  ; sslConn = 0
[6556] 02/13/14 10:06:00 [fsys\spsv3]         - checking for SPS evidence on S2SPFRONT, in S2LMOSS1
[6556] 02/13/14 10:06:00 [fsys\spsv3]         - checking for SPS evidenc: key opened
[6556] 02/13/14 10:06:00 [fsys\spsv3]         - checking for SPS evidenc: ret = 0
[6556] 02/13/14 10:06:00 [fsys\spsv3]         - checking for SPS evidenc: WOW key opened
[6556] 02/13/14 10:06:00 [fsys\spsv3]         - checking for SPS evidenc: ret = 0
[6556] 02/13/14 10:06:00 [beutil]             - Input Error (       0) for Type: (43)
[6556] 02/13/14 10:06:00 [fsys\shared]        - FS_ResolveDevName: [Prod Farm (S2SPFRONT)]

 

And the SPWrapper.log is created

 

So the only thing i'm sure about is that the SPWrapper process wasn't ready before but is ready now. Maybe it's just a coincidence?!







Service Informatique's picture

After some days running well, the same problem happens again.

I read again the post http://www.symantec.com/docs/TECH75063 and discovered that I checked for the wrong checkbox the first time I read it!

Unchecking 'Check for publisher's certificate revocation' corrected the problem.

I checked it again, restarted the remote agent, browse in the selection list and it fails.

One more time I unchecked it an it's working.

 

I'll keep an eye on it for some days before confirm.