• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1921
  • Last Modified:

Backup Issues in SBS2011

I have an SBS 2011 that stopped backing u due to a VSS issue. This includes refusing to do Acronis backups.
I've seen this a few times and usually the fix is:
1.Open an Administrative command prompt.
2.Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3.Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures


In this case however the manual update fails:
I have filtered out all Errors and Warnings from the update logs.
------------------------
Begin tracelogging forSharePoint 2010 Products Configuration Wizard.  Version 14.0.6009.1000
10/10/2011      17:23:22      8      WRN      Found registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS\ComponentsToRegister, but the SubKeyCount is zero
10/10/2011      17:23:25      8      WRN      Failed to add the service connection point for this farm
10/10/2011      17:23:25      8      WRN      Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.

10/10/2011      17:23:34      8      ERR      Task upgrade has failed with an unknown exception
10/10/2011      17:23:34      8      ERR      Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 4.0.21.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. ---> System.NullReferenceException: Object reference not set to an instance of an object.
10/10/2011      17:23:34      8      ERR      An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Action 4.0.21.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed.
10/10/2011      17:23:34      8      ERR      Task upgrade has failed
10/10/2011      17:23:34      1      ERR      Task upgrade SharePoint Products failed, so stopping execution of the engine
10/10/2011      17:23:34      1      ERR      Failed to upgrade SharePoint Products.
10/10/2011      17:23:34      1      ERR      One or more configuration tasks has failed or some tasks were not run
10/10/2011      17:23:34      1      ERR      One or more configuration tasks has failed to execute
10/10/2011      17:23:34      1      ERR      Configuration of SharePoint Products failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_10_10_2011_17_21_29_264_638499507.log, fix the problem, and run this configuration wizard again.
10/10/2011      17:23:34      1      ERR      Post setup configuration was not run successfully when using the command line task driver module

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Action 4.0.21.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 4.0.21.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. ---> System.NullReferenceException: Object reference not set to an instance of an object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 4.0.21.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. ---> System.NullReferenceException: Object reference not set to an instance of an object.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Action 4.0.21.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. ---> System.NullReferenceException: Object reference not set to an instance of an object.
------------------------------------

Does anyone know how I can fix this please?
Any suggestions would be appreciated.
Regards
Olaf
0
Olaf De Ceuster
Asked:
Olaf De Ceuster
  • 17
  • 15
1 Solution
 
jaw34Commented:
We had a very similar issue, only that we use BackupAssist as we have a virtual server environment.

We also experienced a failure the first time it was run, however we simply re-ran it again and it succeeded on the second attempt.

We did it a time when there were very few users logged on.

I hope it works for you. Try it a few times in succession, just to be sure!!!
0
 
Olaf De CeusterAuthor Commented:
I have already  tried 7 x times.
Even after a fresh restart.
:(
0
 
jaw34Commented:
Were they in succession, that is, while the PSConfig.exe window was still open and straight after the first failure? Was it 7 times, one after the other?
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Olaf De CeusterAuthor Commented:
No diffrent days.
I'll do a couple one after the other.

Olaf
0
 
jaw34Commented:
Try at least 3 or 4 times, to be totally sure. Seems ridiculous, but it worked for us!
0
 
Olaf De CeusterAuthor Commented:
5 times, only me logged on.
See attached.
sharepoint.PNG
0
 
jaw34Commented:
I have been going over my notes on this issue, and I had a link bookmarked that I never bothered trying.

See if this helps: http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/e883a0fc-2e0b-41f6-96c9-465d7fd1b48d/

There must be a solution!
0
 
jaw34Commented:
Any progress on this issue? Did you manage to try the steps in the link I posted?

Regards.
0
 
jaw34Commented:
Here is a link to a blog that discusses clearing the cache.ini file: http://lindachapman.blogspot.com/2011/07/sharepoint-2010-how-to-clear-cacheini.html
0
 
jaw34Commented:
Here is another link that also discusses clearing the cache.ini file: http://latenightsp.wordpress.com/2011/03/16/sharepoint-config-cache/

Hopefully this will enable you to proceed with the inplace upgrade of Sharepoint, to get your backups working again.

Regards.
0
 
Olaf De CeusterAuthor Commented:
Hi Jaw,
Flushed the cache. Tried the in place Upgrade. Same result.
Olaf
Capture.PNG
0
 
Olaf De CeusterAuthor Commented:
This SBS is an upgrade from my previous SBS2008.
Companyweb had a few sub sites called http://companyweb/IT. They are now present on the sbs2011. How can I delete them?
Can't be deleted from Sharepoint Central admin?
I am assuming these are the sites stopping e upgrade from succeeding.
I tried a manual delete. See attached.
Olaf
 Sharepoint
0
 
jaw34Commented:
I doubt that this would be causing the upgrade to fail.

I am assuming that the SharePoint Foundation 2010 Service Pack 1 has been installed onto this server. Is this correct?

If so, as mentioned in the following article: http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx you should determine if you need to complete the update process with PSCONFIG.

From the article:
•Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
•Once the shell opens, type the following command followed by enter:
(get-spserver $env:computername).NeedsUpgrade
If the result is True, then the update process with PSCONFIG is required.

If not, then it looks like there are other issues going on. What bothers me is that the errors you are getting are identical to the errors that we experienced. These were simply resolved by running the command twice, one immediately after the other.
0
 
Olaf De CeusterAuthor Commented:
This is given me the shhhhhhts.
See attached.
Capture.PNG
0
 
jaw34Commented:
OK. Take a deep breath.

Has SharePoint Foundation 2010 Service Pack 1been installed onto this server?
0
 
Olaf De CeusterAuthor Commented:
It has.
Capture.PNG
0
 
jaw34Commented:
What are the results when you follow the "Check upgrade status" link in the Central Administration console?
0
 
Olaf De CeusterAuthor Commented:
0
 
jaw34Commented:
Looks like at one point it succeeded!!!

What are the errors you are getting in the server application log when you say it "stopped backing up due to a VSS issue"?

Is it something like the following:
Log Name:      Application
Source:        Microsoft-Windows-Backup
Event ID:      521
Level:         Error
User:          SYSTEM
Description:
The backup operation that started at '?2011?-?07?-?06T02:12:07.198000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Could you provide further details about the backups that are failing?
0
 
Olaf De CeusterAuthor Commented:
0
 
Olaf De CeusterAuthor Commented:
0
 
Olaf De CeusterAuthor Commented:
0
 
Olaf De CeusterAuthor Commented:
0
 
jaw34Commented:
The backup operation that failed looks like it has occurred ~15 mins prior to the succeeded message in Central Administration > Upgrade status.

Were these the most recent errors in the application event log?

I found an article that may be helpful: http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/7d6fd770-945c-4120-8607-f61813ba4fcd/

The SBS "diva", Susan Bradley has a fair bit of input in this article. I haven't had time to read the article in depth, but will get around to studying it shortly.

Going by the Upgrade status, and the False result from the SharePoint Management Shell command line, I think we can assume at this point that Sharepoint Foundation has been upgraded. Although, I don't know what impact running the PSCONFIG command has on SharePoint if it has already been upgraded???

0
 
jaw34Commented:
Olaf,

Have you tried any backups since my last post?

I have studied the link in my last post and this is chiefly concerned about post installation errors. Our server application log is full of the VSS "Warnings" Event ID 8230, and as Microsoft points out here, they can be safely ignored.

Could you please have a look at the server application log and list the most recent errors, over the last 24 hours?

Hopefully, the Event ID 70 errors have cleared. If not, then you will need to check whether an upgrade is required. I know we've already done this, but let's just keep at it:
•Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
•Once the shell opens, type the following command followed by enter:
(get-spserver $env:computername).NeedsUpgrade
Post back with the results.

(You may be interested to know that I was checking our server, since I last posted, and an upgrade was required. Probably due to a whole list of patches that were installed last week. The upgrade went smoothly the first time.)
0
 
Olaf De CeusterAuthor Commented:
Hi Jaw,

Much appreciated.
I have about 10 x sbs2011 running out there and mine is he only one with isues.
I am thinking it might be a hardware issue. (This is a Dell...say no more).
Might have to start again.
Olaf
5.PNG
0
 
Olaf De CeusterAuthor Commented:
0
 
jaw34Commented:
If it is any comfort, others (although very few it would seem) have had persistent issues with the SharePoint SP1 upgrade command.

Would you be willing to work through the following article http://www.msprojectnow.com/DesktopModules/SunBlog/Handlers/Print.aspx?entryid=294 ???

There appears to some similarities with the errors in your original post.
0
 
Olaf De CeusterAuthor Commented:
Been there done that.
Even compared web config files with other servers. All seems OK.
Even read an article saying to copy web config to other dir before update...no go either.
It would be interesting to find out if there is any consistency in hardware regarding failed update?
Olaf
0
 
jaw34Commented:
Olaf,

Have you made any progress on this issue?

For your interest, here is a link to a technet article: http://social.technet.microsoft.com/Forums/en-AU/smallbusinessserver/thread/94a8bb64-e0ea-493f-8e29-01347b1fc6c7

Susan Bradley has offered to set up a case for others faced with the same issue. You might like to take her up on her offer!!
0
 
Olaf De CeusterAuthor Commented:
Just posted this on Technet.
Will see what happens.
Thanks for trying.
Olaf
0
 
Olaf De CeusterAuthor Commented:
Still no resolve but thanks for your time.
Olaf
0
 
lintentechCommented:
Getting similar problems and gone through loads of documents and got nowhere.  Hoping someone can shed some light on this please.

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>PSConfig.exe -cmd upgrade -inplace b2b -wait -force
SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) Microsoft Corporation 2010. All rights reserved.

Performing configuration task 1 of 4
Initializing SharePoint Products upgrade...

Waiting to get a lock to upgrade the farm.

Successfully initialized SharePoint Products upgrade.

Performing configuration task 2 of 4
Initiating the upgrade sequence...

Successfully initiated the upgrade sequence.

Performing configuration task 3 of 4
Upgrading SharePoint Products...

100.00%

Failed to upgrade SharePoint Products.

An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
rver Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.

Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed.  Configuration must be performed be
fore you use SharePoint Products.  For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\1
4\LOGS\PSCDiagnostics_1_20_2013_23_53_35_708_63478246.log and the application event log.


-----

Begin trace logging for SharePoint 2010 Products Configuration Wizard.  Version 14.0.6009.1000

01/20/2013 23:54:05  9  WRN            Failed to add the service connection point for this farm
01/20/2013 23:54:05  9  WRN            Unable to create a Service Connection Point in the current Active Directory domain. Verify that the SharePoint container exists in the current domain and that you have rights to write to it.
Microsoft.SharePoint.SPException: The object LDAP://CN=Microsoft SharePoint Products,CN=System,DC=johnmhayes,DC=local doesn't exist in the directory.
   at Microsoft.SharePoint.Administration.SPServiceConnectionPoint.Ensure(String serviceBindingInformation)
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()

01/20/2013 23:54:33  9  ERR            Task upgrade has failed with an unknown exception
01/20/2013 23:54:33  9  ERR            Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
tion
01/20/2013 23:54:33  9  ERR            An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

01/20/2013 23:54:33  9  ERR              Task upgrade has failed
01/20/2013 23:54:33  9  INF              friendlyMessage for task upgrade is An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
01/20/2013 23:54:33  9  INF              debugMessage for task upgrade is An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

01/20/2013 23:54:33  1  ERR          Task upgrade SharePoint Products failed, so stopping execution of the engine

01/20/2013 23:54:33  1  ERR          Failed to upgrade SharePoint Products.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.  Additional exception information: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20130120-235348-70.log.  The number of errors and warnings is listed at the end of the upgrade log file.
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
   at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

01/20/2013 23:54:33  1  ERR          One or more configuration tasks has failed or some tasks were not run

01/20/2013 23:54:33  1  ERR        One or more configuration tasks has failed to execute

01/20/2013 23:54:33  1  ERR          Configuration of SharePoint Products failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\PSCDiagnostics_1_20_2013_23_53_35_708_63478246.log, fix the problem, and run this configuration wizard again.

01/20/2013 23:54:33  1  ERR      Post setup configuration was not run successfully when using the command line task driver module
0

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 17
  • 15
Tackle projects and never again get stuck behind a technical roadblock.
Join Now