KB2553018 and KB2493987 Sharepoint updates on SBS 2008 Servers
-
Friday, September 30, 2011 2:10 PM
Greetings,
I updated two SBS 2008 systems last night and after KB2553018 and KB2493987 were installed Sharepoint has stopped working. Curious, I checked ALL my SBS 2008 installations and found that after these updates, every system has Sharepoint problems, some more serious than others, but ALL have problems. Several can't do SBS Reporting, some have backup problems, but the worst ones the CompanyWeb and any other Sharepoint services have been rendered inoperable. These updates cannot be removed so now I have to fix them all. I'm working on my in-house system now and after 8 hours, I've made it all the way from 'HTTP 404' to 'Cannot connect to the configuration database' for CompanyWeb. (I tried all the reasonable fixes offered on these forums and blogs with little success so far.
I don't enjoy calling Microsoft for problems, I have a life and don't appreciate the time it takes to navigate their system and run through their scripted Q&A. But I might need to this time due to the fact that all 6, 100%, of my SBS 2008 systems are broken in one fashion or another, with half of them left with no Sharepoint. This update was obviously let loose on our systems without proper testing. I don't appreciate this at all.
Until this is resolved, I would recommend that you NOT install these updates to SBS 2008. And if you think you've done the updates successfully, I'd go back and check everything related to Sharepoint and SSEE and make sure they are actually working.
I'll post the details and results as they are available in this thread.
Cheers,
Ian 'Skip' Guyer - Just another IT Consultant
- Edited by Ian Guyer Friday, September 30, 2011 2:16 PM
Answers
-
Monday, October 10, 2011 4:34 AM
After agonizing hours pouring over log files and trying every reasonable suggestion I could find, I finally fixed it with a full restore from backup. This worked perfectly. You can mark it as a fix. Pathetic.
After spending hours researching problems after updates, I'm getting terribly annoyed. IE9 causes EMC to refuse to close and I get an MMC errors everytime I log out. Sharepoint has more ways to blow up than a motivated terrorist. OCS and Lync servers break with every other update. And almost every suggestion for a fix involves PowerShell and Command Prompts, and it rarely works. What, are we going full circle here. Soon I'll we'll end up back at DOS? Is that what Microsoft wants? I've got no problem with PowerShell, it's a great tool for IT shops, but I'm not an IT shop and I don't need scripts for every little thing on a 30 user system.
I'm trying to be diligent by keeping my operating systems and applications patched, but I'm spending too much time fixing errors caused by patches and not enough being an IT consultant to businesses. I feel like I'm playing whack-a-mole. I'm in the SBS world, it's difficult to justify my time to customers, they watch their pennies and don't have deep pockets. As far as some of them are concerned, I caused the problems.
Almost every post I make on the subject, someone jumps in to tell me what I did wrong. After three hard weeks I now know exactly what I did wrong - I installed updates on perfectly working systems. That's not the attitude Microsoft, or I, wants me to have, but if I'm going to be their quality control in the field on customers working systems, that's what they're going to get and deserve.
Microsoft needs to slow down, their product is getting shoddy. I'm going to STOP updates until I get my servers back in good shape (if that's even possible at this stage). Quite frankly, I'm sick and tired of it.
Ian 'Skip' Guyer - Just another IT consultant.
Ian 'Skip' Guyer
All Replies
-
Friday, September 30, 2011 8:11 PM
Open CMD (Elevated) - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
Run the following commands
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename
stsadm -o provisionservice -action start -servicetype spwebservice -servicenamethen run
psconfig -cmd upgrade -inplace b2b -wait -force
After running these commands make sure to check port 80 is binded unders SBS Sharepoint Site in IIS
Binu Kumar Small Business Server Support -
Saturday, October 01, 2011 2:32 AM
Thanks for your help. I appreciate it. Unfortunately, the stsadm won't run. I've been disconnect from the farm. Here's my update from another thread.
My in-house system: SBS 2008, nothing fancy, vanilla install, the only clever thing I've done to Sharepoint was import the Fab40, it has been working without error for almost 2 years. It has gotten worse.
I cannot connect to the configuration database. When I run SPTC to reconfigure, as it suggested, it wouldn't run unless I renamed or deleted SPCA. I opened IIS Manager and sure enough, when I went to rename SPCA, it reported that SPCA was not found. I deleted it. I ran SPTC again. Failed. Here's the first error from PSCDiagnostics Log.
09/30/2011 16:30:07 1 INF Executing the sql command SELECT @Version=Version FROM [dbo].[Versions] WHERE VersionId=@VersionId against server SBS\Microsoft##SSEE against database WSS_Content to get the versionid to make sure this is a config db
09/30/2011 16:30:07 1 INF Entering function SqlSession.ExecuteNonQuery
09/30/2011 16:30:07 1 INF Entering function Common.BuildExceptionInformation
09/30/2011 16:30:07 1 INF Entering function Common.BuildExceptionMessage
09/30/2011 16:30:07 1 INF Entering function StringResourceManager.GetResourceString
09/30/2011 16:30:07 1 INF Resource id to be retrieved is ExceptionInfo for language English (United States)
09/30/2011 16:30:07 1 INF Resource retrieved id ExceptionInfo is An exception of type {0} was thrown. Additional exception information: {1}
09/30/2011 16:30:07 1 INF Leaving function StringResourceManager.GetResourceString
09/30/2011 16:30:07 1 INF Leaving function Common.BuildExceptionMessage
09/30/2011 16:30:07 1 INF Leaving function Common.BuildExceptionInformation
09/30/2011 16:30:07 1 ERR An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Access to table dbo.Versions is blocked because the signature is not valid.
System.Data.SqlClient.SqlException: Access to table dbo.Versions is blocked because the signature is not valid.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.SharePoint.PostSetupConfiguration.SqlSession.ExecuteNonQuery(SqlCommand command)
09/30/2011 16:30:07 1 INF Leaving function SqlSession.ExecuteNonQuery
09/30/2011 16:30:07 1 INF Leaving function SqlServerHelper.GetV3WSSConfigurationDatabasesThis appears to mean (to me) that the SQL Database is corrupt -or- the security settings are wrong on the config db. What do you think?
I have a good backup, it might be better to restore the system back to before I did the updates? But I don't have that option on one other, so I'd like to fix it if possible.
Thanks for you help.
Cheers,
Ian 'Skip' Guyer
Ian 'Skip' Guyer -
Monday, October 03, 2011 5:38 AM
Ian,
Unfortunately, in my experience the Fab 40 are the issue (did you also install theGroupboard)? Agreed that SharePoint shouldn't break that easily but on SBS it kinda does.
I'd also suggest applying the SharePoint updates manually and applying via Windows Updates can also cause issues.
Next check the size of the database and logs files on SharePoint and SBs and ensure thay are not too large. The bigger they are the longer some patches take to update the database schema (if required) causing the patch to fail (especially via Windows Update).
Ensure you do an STSADM -o backup command every night to backup SharePoint to a flat file. If SharePoint site smokes you cane delete it, create new clean SharePoint site and restore flat file. If SharePoint really broken you can run up a VM and restore flat file there to stand alone server while you troubleshoot SBS.
My recommendation is always to run SharePoint on a stand alone member server in an SBS environment to make it "standard" (technically SharePoint shouldn't run on a DC or Exchange server, which SBS is).
SharePoint is fully supported on SBS (at least the version that came with SBS is) and if a patch smokes it then you should be able to call Microsoft, get an incident open and not be charged for the time to resolve. Sometime doing this can be a lot quicker than trying to do it your self.
Hope that helps.
Thanks
Robert Crane
www.ciaops.com -
Sunday, October 09, 2011 12:36 AM
Robert,
Thanks for the reply.
Good information, but it's too late for me in this case.
Is this why Sharepoint so fragile? With SBS 2003 I warned customers not to use it since restoring it, when/if possible, takes so much time and effort. I thought with SBS 2008 that had changed (Microsoft's SBS website is very proud it's included in SBS!). When I installed my first SBS 2008, I deliberately damaged it and restored it several times with no problems before I told clients it was OK to use.
To repair my system I tried every reasonable suggestion I could find here and elsewhere. I then tried a Sharepoint restore from the backup with no success. Eventually I had to do a complete system restore to get it back online.
If what you say is true about the DC and Exchange, why would Microsoft put Sharepoint in SBS? I've got several SBS 2008 clients that use Sharepoint extensively. This is not good news.
And, this is the first time I've heard the Fab40 templates could be harmful. Funny thing is I got the instructions on how to find and load them from Microsoft. This isn't very comforting.
Cheers,
Ian 'Skip' Guyer
Ian 'Skip' Guyer -
Sunday, October 09, 2011 12:45 AM
Ian,
As mentioned SharePoint isn't recommended on DC or an Exchange server by the SharePoint team. However, to get it working in a single server SBS environment there is no choice.
Like many SBS apps, they can work well or they can have problems and that to a degree is a bit random. The only guiding principal I have found is 'keep it simple'.
The issue perhaps has been of late that many SharePoint updates 'expect' SharePoint to be on a stand alone server and given the same patch must also be applied to an SBS system this is where problem may arise. Not 100% sure but I get that feeling.
The Fab 40 templates are supported like SharePoint on SBS but I am just passing on my experience. There are number of different ways to do DR on SharePoint on SBS so it is always a good idea to run through the process before needing it. I would always recommend an stsadm -o backup as well as understanding how to rebuild the farm using the database attach method.
I have plenty of people using SharePoint on SBS quite happily but in my experience there are occasions when it can go horribly wrong for unknown reasons. This can also happen with the stand alone version. My experience is to always have an stsadm -o backup data file so you can create a new clean SharePoint site and then blow the restore back quickly.
Hope that helps.
Thanks
Robert Crane
www.ciaops.com -
Sunday, October 09, 2011 12:56 AM
Robert,
Thanks for the advice. I'm going to take it.
I've had the same experience with Sharepoint, it works well until it doesn't. I was hoping that Microsoft had made it more robust with time, like Exchange has become, but that doesn't appear to be the case yet. Sharepoint is still a fragile application.
With the type of client that uses SBS (small businesses) the Fab40 are a big hit. I decided not to install any templates in SBS 2011, for the reason you mentioned; Keep it simple. And I'm a big fan of simple straight forward installations for the sake of my sanity and reputation.
This time it isn't random. I have 4 SBS 2008 installations and ALL of them had a Sharepoint failure to one degree or another. Most of my clients are SBS 2011, and several experienced errors that required PSConfig to repair.
Thanks for the info,
Ian 'Skip' Guyer
Ian 'Skip' Guyer -
Sunday, October 09, 2011 1:03 AM
Ian,
SharePoint depends on a lot of other moving parts including IIS and SQL all of which need maintenance. SharePoint is certainly robust in my experience it is the patching process which seems to have issues. That's why they have moved to the manual psconfig step with SharePoint 2010.
The issue probably lies around the size of the content. The bigger it is the more chance that it will get tripped up by an update.
Strange that you got 4 failures. I'd look for commonalities like AV or something else in the way you do installs as I have never seen this. Maybe you AV is holding up the update process and causing issues.
Also, did you check the event logs and do a reboot before applying updates? In my experience always a good idea.
Like any patching on SBS systems you need take care and be aware of how to get things back in the event of issues as SBS is a slightly different beast.
Thanks
Robert Crane
www.ciaops.com -
Sunday, October 09, 2011 1:08 AMModerator>Thanks for the advice. I'm going to take it.That's a line to remember ;-).FYI - Robert is not only a great speaker; he's also a great techie. If youhave an opportunity to attend an event that he's speaking at (like ansmbnation event, for example), don't pass on it. Do check out his website aswell; it's in his signature.-------------------------------------------------Les Connor [Ex SBS MVP 2001-2011]"Ian Guyer" wrote in messagenews:e0bd550b-4762-47f7-9373-3dd729040204@communitybridge.codeplex.com...> Robert,>> Thanks for the advice. I'm going to take it.>> I've had the same experience with Sharepoint, it works well until it> doesn't. I was hoping that Microsoft had made it more robust with time,> like Exchange has become, but that doesn't appear to be the case yet.> Sharepoint is still a fragile application.>> With the type of client that uses SBS (small businesses) the Fab40 are a> big hit. I decided not to install any templates in SBS 2011, for the> reason you mentioned; Keep it simple. And I'm a big fan of simple> straight forward installations for the sake of my sanity and reputation.>> This time it isn't random. I have 4 SBS 2008 installations and ALL of> them had a Sharepoint failure to one degree or another. Most of my> clients are SBS 2011, and several experienced errors that required> PSConfig to repair.>> Thanks for the info,>> Ian 'Skip' Guyer>>>>>>> --------------------------------------------------------------------------------> Ian 'Skip' Guyer
Ex MVP-SBS (2001-2011) -
Sunday, October 09, 2011 4:42 AM
Robert,
It is strange, but I've seen it before. OCS had an update a few years back that took out 100% of my servers AND clients. I thought this may be like that one.
"Did you check the event logs?" is a joke, right? I'm smiling.
I respect your appreciation of Sharepoint. It's a home run hitter at the plate, but it makes lots of errors in the field. Full OCS and Lync installations are (for me) easier to troubleshoot and repair, and they have far more moving parts (Sharepoint being one of them).
I'm going to take your advice and be more careful patching Sharepoint and add the stsadm backup, too.
Les,
When someone with knowledge speaks, I listen.
For the typo trolls,
I had 6 SBS 2008's, I now have 5, I wasn't counting my own with 4, and I upgraded one to SBS 2011 last weekend. And the backup issue was unrelated, but I didn't know it at the time.
Thanks All,
Ian 'Skip' Guyer
Ian 'Skip' Guyer -
Monday, October 10, 2011 12:21 AM
Les,
Thanks for the testimonial (your cheque is in the mail ;-))
Thanks
Robert Crane
www.ciaops.com -
Monday, October 10, 2011 4:34 AM
After agonizing hours pouring over log files and trying every reasonable suggestion I could find, I finally fixed it with a full restore from backup. This worked perfectly. You can mark it as a fix. Pathetic.
After spending hours researching problems after updates, I'm getting terribly annoyed. IE9 causes EMC to refuse to close and I get an MMC errors everytime I log out. Sharepoint has more ways to blow up than a motivated terrorist. OCS and Lync servers break with every other update. And almost every suggestion for a fix involves PowerShell and Command Prompts, and it rarely works. What, are we going full circle here. Soon I'll we'll end up back at DOS? Is that what Microsoft wants? I've got no problem with PowerShell, it's a great tool for IT shops, but I'm not an IT shop and I don't need scripts for every little thing on a 30 user system.
I'm trying to be diligent by keeping my operating systems and applications patched, but I'm spending too much time fixing errors caused by patches and not enough being an IT consultant to businesses. I feel like I'm playing whack-a-mole. I'm in the SBS world, it's difficult to justify my time to customers, they watch their pennies and don't have deep pockets. As far as some of them are concerned, I caused the problems.
Almost every post I make on the subject, someone jumps in to tell me what I did wrong. After three hard weeks I now know exactly what I did wrong - I installed updates on perfectly working systems. That's not the attitude Microsoft, or I, wants me to have, but if I'm going to be their quality control in the field on customers working systems, that's what they're going to get and deserve.
Microsoft needs to slow down, their product is getting shoddy. I'm going to STOP updates until I get my servers back in good shape (if that's even possible at this stage). Quite frankly, I'm sick and tired of it.
Ian 'Skip' Guyer - Just another IT consultant.
Ian 'Skip' Guyer
-
Friday, October 14, 2011 9:01 AM
Open CMD (Elevated) - C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
Run the following commands
stsadm -o provisionservice -action stop -servicetype spwebservice -servicename
stsadm -o provisionservice -action start -servicetype spwebservice -servicenamethen run
psconfig -cmd upgrade -inplace b2b -wait -force
After running these commands make sure to check port 80 is binded unders SBS Sharepoint Site in IIS
Binu Kumar Small Business Server Support
HiIve gone through the sequence above to the point of run:
psconfig -cmd upgrade -inplace b2b -wait -force
which then throws up errors:
10/14/2011 09:50:54 1 ERR Failed to upgrade SharePoint Products and Technologies.
Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
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\12\Logs\Upgrade.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\12\Logs\Upgrade.log. The number of errors and warnings is listed at the end of the upgrade log file.
at Microsoft.SharePoint.Upgrade.SPManager.RunUpgradeSession(IUpgradable root, Boolean bRecursive)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()Any ideas?
Our companyweb is still down after those two updates, thanks to Microsoft.
.png){kind=spacer}
