none
Office Sharepoint SP1 Upgrade

    Question

  • I have just tried to install the Service Pack 1 for the Office Servers, and it has errored and taken the complete sites down.

     

    The error in the log is;

     

     

    12/13/2007 20:59:18  18  ERR                    The B2B upgrader timer job failed.
    12/13/2007 20:59:18  18  INF                    Entering function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                      Resource id to be retrieved is UpgradeTaskFailConfigSyncDisplayLabel for language English (United States)
    12/13/2007 20:59:18  18  INF                      Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Failed to upgrade SharePoint Products and Technologies.
    12/13/2007 20:59:18  18  INF                    Leaving function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                    Entering function Common.BuildExceptionMessage
    12/13/2007 20:59:18  18  INF                      Entering function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                        Resource id to be retrieved is ExceptionInfo for language English (United States)
    12/13/2007 20:59:18  18  INF                        Resource retrieved id ExceptionInfo is An exception of type {0} was thrown.  Additional exception information: {1}
    12/13/2007 20:59:18  18  INF                      Leaving function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                    Leaving function Common.BuildExceptionMessage
    12/13/2007 20:59:18  18  ERR                    Task upgrade has failed with a PostSetupConfigurationTaskException An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to upgrade SharePoint Products and Technologies.
    12/13/2007 20:59:18  18  INF                    Entering function Common.BuildExceptionInformation
    12/13/2007 20:59:18  18  INF                      Entering function Common.BuildExceptionMessage
    12/13/2007 20:59:18  18  INF                        Entering function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                          Resource id to be retrieved is ExceptionInfo for language English (United States)
    12/13/2007 20:59:18  18  INF                          Resource retrieved id ExceptionInfo is An exception of type {0} was thrown.  Additional exception information: {1}
    12/13/2007 20:59:18  18  INF                        Leaving function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                      Leaving function Common.BuildExceptionMessage
    12/13/2007 20:59:18  18  INF                    Leaving function Common.BuildExceptionInformation
    12/13/2007 20:59:18  18  ERR                    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to upgrade SharePoint Products and Technologies.
    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

     

     

     

     

     

     

    Can anyone suggest away of retriving the system?

     

     

    Thursday, December 13, 2007 9:03 PM

Answers

  • Senario:
    I had experienced the same identified issue as stated above after installing sp2, over the slipstream MOSS install, and running the SharePoint Products and Technologies Configuration Wizard:

     The B2B upgrader timer job failed.
    12/13/2007 20:59:18  18  INF                    Entering function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                      Resource id to be retrieved is UpgradeTaskFailConfigSyncDisplayLabel for language English (United States)
    12/13/2007 20:59:18  18  INF                      Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Failed to upgrade SharePoint Products and Technologies.
    12/13/2007 20:59:18  18  INF                    Leaving function

    When this occured the configuration of the service pack wasn't complete.


    Farm Configuration:
      - Two FEW servers (64b Windows 2008)
      - One index\Query\SSP (64b Windows 2008)
      - One SQL (64b Windows 2008 SQL 2008)


    Troubleshooting:
    I was have the issues on the index\query\ssp server with the above mentioned timer job issue.  After going further in my logs I realized what the issue was.  I didn't intend on using IIS on the SSP so I never installed the service (Windows 2008).  When I installed MOSS under advanced installation the admin is promped with three options for install, Single Server Install, Web Front End ONLY or install all services.  While the SharePoint Products and Technologies Configuration Wizard is running it is upgrading services, jobs, files which included the web.config content IF it was a front end web server.  Because it was installed with all services, it had this service activated in the farm when it joined despite that it didn't have IIS running on it.

    Solution:
    I central admin, I deactived the web front end service.  After doing that I re-ran the SharePoint Products and Technologies Configuration Wizard and everything went perfect.


    HaloX
    • Marked as answer by Mike Walsh FIN Saturday, November 13, 2010 5:46 PM
    Friday, October 2, 2009 1:57 PM

All replies

  • Any fixes yet?  I am having the same issue.

     

    Friday, December 14, 2007 8:35 PM
  • Me too......

     

    Please... SharePoint team... I'm gonna be fired!!!!!!!

    Saturday, December 15, 2007 2:57 AM
  • Don't make the mistake I made and rely on Microsoft on this....I would rebuild another server and restore your stsadm backups then move web server custom files over to the new server.

     

    IMAGE....IMAGE....IMAGE!!!!

     

    I hate to say this, Sharepoint is a great product but it makes us look bad when we suggest to use it and then it goes so wrong.  My boss thinks I am an idiot for suggesting to use it now....MICROSOFT WISE UP!  You are putting your flagship product in jeopardy by releasing a questionable service pack then having poor support on the other end.  I DON'T WANT TO SPEAK TO SOMEONE IN INDIA ANYMORE!  Hell we all know it isn't cheaper anymore....

     

     

     

    Saturday, December 15, 2007 3:07 AM
  • Hi

    I am having the same problem. Any solutions ?

    Madhur
    Saturday, December 15, 2007 8:39 AM
  •  

    Has anyone called MS yet?  I have not had the best luck with SP support in the past especailly since I am running my dev in VM.   Glad to know I have good company but it is a shame it is happening at all.

     

    Just for the record.   My install is a 4 server farm running MOSS 07 (no upgrade) on VM.  I also have checked the version in my content db in the siteversions table and it appears everything except the base wss_content dabase has been upgraded.

     

    Luckly this is 1 of dev farms that I have but I wish I would have taken some snaps before I tried.  After seeing this thread, I am concerned with trying it on my next farm.

     

    Can anyone else provide details of their install so we can look for similiar points????

    Saturday, December 15, 2007 4:34 PM
  • Has everyone followed steps like *removing the orphaned objects from database*, I missed this step since I didnt understand this one.
    Also, there is one step of checking and removing the previous upgrade timr jobs from the jobs list.

    See here,
    http://technet2.microsoft.com/Office/en-us/library/f484f5f2-35bb-4d70-bf56-dd1c4c287c721033.mspx?mfr=true

    Madhur
    Saturday, December 15, 2007 4:45 PM
  • Did this help you?  Since I cant get into Central Admin, I am not sure how to check for previous timer jobs.  As for the database, my siteversions table appears to have the correct version so I think I am past orphans.

     

     

     

    Saturday, December 15, 2007 11:08 PM
  •  

    The best part of your situation is that since you upgraded, you cannot restore your stsadm backups over the config and admincontent databases.  They need to warn folks in the upgrade KB paper about this!  How great it is that they tell you to backup your system when you have no ability to recover from a fubar!
    Sunday, December 16, 2007 1:23 AM
  • I am not closer to a solution, than it sounds like the rest of you are.  Will have to try and get hold of SP support next week to try and sort out. Otherwise, I think it will be then end to the Sharepoint and Project Server project we have been working on and we will have to look for solutions else where, probably move to CAs project server solution instead.

     

     

     

    Sunday, December 16, 2007 9:56 PM
  • Even I faced a similar error while upgrading on a MOSS image. During my first attempt I had installed the Office 2007 client SP1 and then started the WSS 3.0 SP1 installation.  After completion, I ran the config wizard, only to be faced with the above issue where in it used to say that the "SharePoint_Config" database is an invalid configuration database. Later on I realized that the Config wizard should be run only after the MOSS SP1 installation. During my second attempt, I stopped the World Wide Publishing Services and started with WSS 3.0 SP1 installation followed by MOSS SP1. Yet the Config wizard failed at the last task - Task No.9. I checked the Upgrade.log to find the error "[SPXmlConfigurationManager] Unable to load the assembly Microsoft.GroupBoard........". Then I downloaded the Microsoft GroupBoard Workspace installation and ran the exe on my image. After this installation I ran the config wizard and it was successful. The version was updated to 12.0.0.6219 ! and the existing sites were also running fine.

     

    Thanks

    Prasad

    Monday, December 17, 2007 8:49 AM
  •  

    Hmmm.   Interesting Point.   I have MOSS 07 and only installed the WSS SP1.  I guess I can try to install the MOSS SP1 on top and see what happens.  Cant be any worse than it is now.

     

    Monday, December 17, 2007 2:12 PM
  • John,

    During the application of the WSS 3.0 SP1 and the Office Server 2007 SP1 to our test servers, I came across the same error.  After doing some investigating and scanning the logs, it turned out that the GroupBoard had been installed and was causing the problem.  The GroupBoard came out near the same time as the fabulous 40 templates and was installed at about the same time, but it never seemed to work properly. After uninstalling it, I re-ran the configuration wizard and that problem went away (I did have some others that were of a different nature – all now resolved).  I really found what I was looking for in the Upgrade.log by looking for the first errors in the SP upgrade that I ran.  It showed me right away what the issue was. 

    Your problem may not be the GroupBoard, but it could be some other installed feature or a customized MOSS related installation package causing the problem. The Upgrade.log is the best place to start for tracking down the problem.

     

    Thanks,
    Harry Irvine

     

    Monday, December 17, 2007 4:27 PM
  • I went back and applied the sp for MOSS before running the config wizard.  I still got some errors and I check th update.log like HIrvine mentioned above.  I found it was having problems with one of my sites and luckly CA was still barely responding(CSS messed up) and I deleted that site.  My configuration wizards are now  running successful.  MY css is still messed up in CA but making progress.

     

    Monday, December 17, 2007 11:24 PM
  • The specified SPContentDatabase Name=SharePoint_AdminContent_e824c47e-3958-452a-ae12-ac6cc041cd7a Parent=SPDatabaseServiceInstance Name=[HOST] has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

     

    How do I get any newer?!?? if I click on WSS or MOSS SP1 I get the message they have already been installed on the WFE.

     

    P.S. I have Project Server installed. Does this have something to do with it.

     

    I'm quite scared to run this against my production instance. Any ideas how to do a test run without risking damage.

     

    Monday, December 17, 2007 11:31 PM
  • Same Problem here.


    Would be glad if somebody from Microsoft would tell us how to fix this problem.


    Happily I put the update first on test server! :-)

     

     

    Tuesday, December 18, 2007 2:50 PM
  • I think my problem was also that I installed WSS and immediately ran the psconfig utility.

     

    I rolled back the databases, and was able to run the command psconfig -cmd upgrade b2b. This restored my Central Admin website to a functional state with SP1 installed. the Content database was attached but had several errors related to Ghost features that I can't find (I've been worried about that for quite some time - SharePoint tends to leave remnants of features if you're not careful)

     

    [SPWebTemplateSequence] [ERROR] [9/19/2007 9:28:47 AM]: Template STS#0: SPWeb Id=6e15012b-b46f-409e-a3b6-b93d811e22d4 could not be accessed in SPSite Id=d0100dff-4e2d-4158-bbae-5fcd705258e2 due to exception. Skipping this SPWeb for template upgrade. Exception: Microsoft.SharePoint.SPException: Unable to connect to database.  Check database connection information and make sure the database server is running. --->

     

    [SPManager] [ERROR] [12/17/2007 9:53:00 AM]: CanUpgrade [SPContentDatabase Name=SharePoint_AdminContent_e824c47e-3958-452a-ae12-ac6cc041cd7a Parent=SPDatabaseServiceInstance Name=DBHOST] failed.
    [SPManager] [ERROR] [12/17/2007 9:53:00 AM]: The specified SPContentDatabase Name=SharePoint_AdminContent_e824c47e-3958-452a-ae12-ac6cc041cd7a Parent=SPDatabaseServiceInstance Name=DBHOST has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.
    [SPManager] [ERROR] [12/17/2007 9:53:00 AM]:    at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()
       at Microsoft.SharePoint.Upgrade.SPManager.CanUpgrade(Object o)

     

    I read somewhere

    [Ammended:

    http://technet2.microsoft.com/Office/en-us/library/f484f5f2-35bb-4d70-bf56-dd1c4c287c721033.mspx?mfr=true

     

    "After you upgrade your server farm, you must attach the content databases back to the server farm. You can only attach one content database to the server farm at a time, because when you attach the databases to the upgraded server farm the content database is upgraded automatically."

     

    If you want to streamline the upgrade process even further, you can configure additional computers as Office SharePoint Server 2007 Service Pack 1 Web servers in a single-computer server farm, we recommend 4 to 5 Web servers. Then, to perform a parallel upgrade of the content databases, use these Web servers to upgrade the content databases while they are detached from the original server farm.

     

    After you detach the upgraded content databases from the temporary Web server, and attach them back to the original server farm, the content databases are ready for service. At this point, you should remove any content databases from the previous version and then back up the server farm.

    12/20/2007]

     

    that you can attach the databases one at a time and the upgrade happens automatically when you attach the database. I remember this worked when moving from wss2 to MOSS. I rolled my Content database to before the upgrade and tried to attach it again and I now get the error:

     

    "DB on DBHOST contains user-defined schema.  Databases must be empty before they can be used.  Delete all of the tables, stored procedures and other objects or use a different database."

     

    Tuesday, December 18, 2007 8:12 PM
  • "Otherwise, I think it will be then end to the Sharepoint and Project Server project we have been working on and we will have to look for solutions else where, probably move to CAs project server solution instead."

     

    Agreed. This may prove to be the final nail in the coffin to a product that already proved uncustomizable for our needs. I've been afraid of this for quite some time because of the way SharePoint leaves lingering elements of poorly-written features (GroupBoard for example). If problems of that nature are having anything to do with the fact that an entire farm drops to its knees to an unrecoverable state, then the cost of a enterprise sharepoint deployment really outweighs the benefit.

     

     

     

    Tuesday, December 18, 2007 8:17 PM
  •  

    Guys,  dont throw the baby out with the bath water.  Agreed this service pack is a bit buggy.  Depending if you are using wss or Moss.  Free (wss) is pretty good for the capabilities. Dont know much about group board, but it is free ...right.

     

     

    We have done some really cool stuff of Moss including our public site which went live 2 months ago. 

     

    Back and test are key.  How bad do you need sp1 right now?  Just something to think about!!!

     

    Good Luck.

    Wednesday, December 19, 2007 2:53 AM
  • It's not just the service pack that's buggy. Sharepoint itself is too buggy to be fit for purpose beyond a small knock-up server with no business-critical data - that is, unless your company is big enough to have a team of developers dedicated to beating Sharepoint into submission, so it actually can do everything it should be able to do out of the box without any dependency on custom code - and do it without falling over on a regular basis.

     

    For example I have a list on the production server which generates nested SQL errors when displaying/editing some items - but not all items. The list has under 200 items in it, and there's only 6 custom columns in the list. I've rebuilt the list twice, in one case recreating it completely from scratch - and cannot get rid of the problem. On another server, it just works. Exactly the same setup, exactly the same data.

     

    I know many companies that are Microsoft shops all the way, but won't use Sharepoint for anything remotely business-critical because it's nowhere near robust enough and they get far better performance from a SQL server and custom web front end than they'd ever get with Sharepoint and BDC doing the same job.

     

    The problems people are running into with the service packs, only serve to undermine market confidence in the product because it was a flakey beast already.

     

     

    Wednesday, December 19, 2007 1:12 PM
  • Do you ever get the feeling this Service Pack was released to the public for stress testing? And we'll shortly see an update that fixes all the problems we used our man hours to discover Smile lol

     

    BTW My attempt to recover from this manually failed. the PSCONFIG utility found itself in a deadlock situation waiting for the central admin database to be unprovisioned (already not provisioned) before  I could even disconnect from the farm, and the central admin database was waiting for the farm database to get a schema upgrade before it could be provisioned so that I could unprovision it.

     

    When I tried to reconnect I got even more errors.

     

    Also running each step manually corrupted entries in the farm database that I had to remove manually (Modifying databases leaves you in an unsupported state)

     

    UpdatedConcurrencyException: The object SPWebConfigFileChanges Name=WebConfigChanges - 1939b6f7-aff2-4d9a-9c1c-fedbff56cc5d Parent=SPWebApplication Name=SharePoint - [HOST]

     

    http://blog.thekid.me.uk/archive/2007/03/23/corrupt-webconfigmodifications-in-sharepoint.aspx

     

    SELECT    Id, ClassId, ParentId, Name, Status, Version, Properties

    FROM        Objects

    WHERE    (Name LIKE '%WebConfig%')

     

    I ended up creating a new farm. We'll see where we go from there.

     

     

    Wednesday, December 19, 2007 4:14 PM
  • Chris.

     

    You're right. SharePoint does some really neat things.

     

    Our problem has been we don't have the staff to support the many extensibility points that are required to touch because the original product is cumbersome to our users.

     

    We've done pretty well with it out of the box. The users though, feel like they are settling for a poorer experience than they are used to. I freely admit that is more the deployment staff's fault (just me) than it is the product.

     

    We've had to make some tough decisions because of the sheer grandness of the product. We don't need SP1 right now, but being mired down in a Service Pack Upgrade when we DO need it scares me to death after this first experience with SP1.

    Wednesday, December 19, 2007 4:23 PM
  • I tried applying the WSS3 SP1 on two of my test servers, which are in totally different farms. One worked fine no errors. The other server fails with the following error in the log,

     

    The B2B upgrader timer job failed.

    12/20/2007 10:02:14 11 INF Entering function StringResourceManager.GetResourceString

    12/20/2007 10:02:14 11 INF Resource id to be retrieved is UpgradeTaskFailConfigSyncDisplayLabel for language English (United States)

    12/20/2007 10:02:14 11 INF Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Failed to upgrade SharePoint Products and Technologies.

    12/20/2007 10:02:14 11 INF Leaving function StringResourceManager.GetResourceString

    12/20/2007 10:02:14 11 INF Entering function Common.BuildExceptionMessage

     

    Our Sharepoint server has been so unstable with a weekly crash/reboot. I was hoping for the SP1 solve most of the problems if not all. Now, I am not sure if I want to try this in the production.

    Thursday, December 20, 2007 3:27 PM
  • Well I have solved my problem, I had to remove all the sharepoint templates, that I had installed from the Top 40 Templates.

     

    This mean removing two templates.  Once I had done I re ran the configuration it works fine.

     

    John

     

     

    Thursday, December 20, 2007 5:12 PM
  • Interesting.  I upgraded a second farm (single server) with the 40 on it and it was fine.  Someone mentioned weekly reboots above.  Why, what symptoms are you seeing?  We were seeing some errors with vss writer/bad memory error but it was fixed with and OS hotfix.  We also get IIS not to respond and were rebooting.  Since then, we found a utility from Mindsharp that identifed it as a timer bug and the have a wsp that adds a custom stsadm command to reset the timer across the farm.

     

    Just some FYI.

     

    Thursday, December 20, 2007 6:23 PM
  • http://tech.groups.yahoo.com/group/sharepointdiscussions/message/22668

     

    Here is one of the threads that you are talking about on mindsharp's SharePoint discussion.

     

    Chris, just to clarify, fixes to this problem were not included in SP1, correct?

     

    Thursday, December 20, 2007 6:31 PM
  •  

    I was also able to fix my problem. Unfortunately I was unable to access the forum to post my solution.

     

    Here is a link to my post on the yahoo sharepoint discussion board hosted by mindsharp.

     

    http://tech.groups.yahoo.com/group/sharepointdiscussions/message/24295

     

    Thursday, December 20, 2007 6:41 PM
  • I was also fixed my problem !!  ( upgrade to SP1 , stage 8 )

     

    The problem was fixed when I Stopped these two services from Central Addministration (Operation>Services) :

    1. Office Server Search

    2.WSS Help Search

     

    and after that run the psconfig command : psconfig -cmd upgrade -inplace b2b -force

    after that I ran SharePoint Pruducts and technologies and in completed successfully !!!

     

    Hope could help you !

    Sunday, December 30, 2007 12:20 PM
  • Error: Failed to upgrade SharePoint Products and Technologies

    If you add a new Web server to an existing server farm that does not have any Web applications, and you update the Web server and then run the SharePoint Products and Technologies Configuration Wizard, you might receive the following error message:

    An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products and Technologies.

    This error occurs when the SharePoint Products and Technologies Configuration Wizard cannot locate or modify the Web.config file.

    To resolve the issue, you must manually copy the Web.config file from %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\Config to %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\Template\Layouts. After the Web.config file is in the Layouts folder, you can run the SharePoint Products and Technologies Configuration Wizard again.

     

    this wont resolve my problem

    worst case i could do this but  I dont want ot reintall and unistall sharepoint , . any other way to solve th problem.

     

    thanks

    gmail001

     

     

     

     

     

    Monday, December 31, 2007 5:58 PM
  •  

    did u solve this problem  yet.

    thanks

    gmail001

    Monday, December 31, 2007 5:59 PM
  •  

    I did fix my initial problem in not being able to upgrade my development farm. After some struggling I was successful.

     

    So I figured since the farm is now in SP1, I should be able to disconnect production content DB's and migrate them over. (Erroneous assumption???? it seems to follow that I was able to do this in migrating the development database, first by detaching the content databases, performing the upgrade, and then attaching them agan)

     

    On the production farm I created a new content database, and added a pristine team site. I then detached (removed) the content database from the farm.

     

    On the development farm I used stsadm -o addcontentdb  to try to add the production content to the development SP1 binaries. I get this error:

     

    MossBYUI_SP1TestDB on [host]\[instance] contains user-defined schema.  Databases
     must be empty before they can be used.  Delete all of the tables, stored proced
    ures and other objects or use a different database.

     

    What's going on?

    Monday, January 7, 2008 9:43 PM
  • I saw similar errors in our lab and posted our fix here: http://blogs.mgtechgroup.com/grant/archive/2008/01/07/Upgrade-to-WSS-SP1-MOSS-SP1-failed.aspx

     

    Please post comments, success, etc. there.

    Monday, January 7, 2008 10:25 PM
  •  

    I agree with the initial posts.  This all is just unacceptable.  I appreciate the hard work that all you folks put in for the work arounds and what not, but it seems everyones situation is slightly different. 

     

    Where the hell is MS.  I should be able to click on a setup and have a base install upgraded.  Whats going on MS?? 

     

    Bah!

    Wednesday, January 23, 2008 8:43 PM
  • I stick to my long running theory. MS gets the concept of open community. Pass it out to the community, and it will come back to you with LESS COST. We got the software, we get to test it, and now they're working on the fixes according to our specs.

     

    I guess there is some teeth to the arguments about TCO of community over proprietary. Unfortunately it is the MS developers that are reaping that benefit of community KNOWLEDGE until it comes back out to us in the form of SP2. Hang in there. I'll bet it is on it's way 5th quarter '0-something

    Thursday, January 24, 2008 6:08 AM

  • Uninstall the Microsoft GroupBoard Workspace from Control Panel/Add or Remove Programs. Then when you run the configuration wizard this error will not surface. You may face PostConfigurationTaskSetUp errors. Delete sites which have been created from the Fantastic 40 Application Templates. You can probably take the backup of the entire web application before deleting it. These 2 steps will ensure that the configuration wizard runs successfully. You can download the Microsoft GroupBoard Workspace from the internet and install it again. Hope this helps!

    Thanks
    Prasad
    Thursday, January 24, 2008 12:44 PM
  • Two Questions: 1) What if I'm using one of the fab 40 websites in my farm for a production site?

    2) If the answer is "delete it" are we supposed to commit ourselves to the idea that SharePoint is *either* extensible *or* upgradeable?

     

     

     

    Thursday, January 24, 2008 3:32 PM
  • I have also had major problems trying to apply Sharepoint SP1. I successfully ran the

    wssv3sp1-kb936988-x64-fullfile-en-us.exe, but failed when running

    officeserver2007sp1-kb936984-x64-fullfile-en-us.exe. The error message shown was "the installation of this package failed" I have only had a quick look through the log files so far, but they haven't been much help either.

     

    I found this from Microsoft which appears to be the same as my issue, but I have 4gb free on my system drive so this really shouldn't be an issue.

     

    http://support.microsoft.com/kb/943589

     

    If anyone has any ideas let me know. It should be alot easier than this and after it failed it completely broke my company intranet and I had to perform a restore of the webserver......not good enough

    Tuesday, February 5, 2008 1:29 AM
  • dave17,
    I have ran into the exact same error on my site.  Did you find a fix for this?  I too, have plenty of free space so that doesn't really relate.  Please let me know.  Thank you.
    Tuesday, February 12, 2008 4:02 PM
  • I meet the same problem. Any suggestions will be welcomed.

     

    Wednesday, February 13, 2008 12:57 PM
  • I was also fixed my problem !!  ( upgrade to SP1 , stage 8 )

     

    The problem was fixed when I Stopped One Service Only from Central Addministration (Operation>Services) :

    1.WSS Help Search

     

    No need to run psconfig by hand, simply re-run the Sharepoint Products and Technology Wizard.

     

    Hope this helps - Gus.



     

    Thursday, February 28, 2008 12:29 AM
  • I had the same #%&! failure of the Config Wizard when I ran it on my first app server - the one hosting Central Admin.  The message I found in the trace log: "The B2B upgrader timer job failed"

     

    I tried the command above - "psconfig -cmd upgrade -inplace b2b -force" on this server and the 4-step config ended successfully.  I then was able to rerun the Configuration Wizard SUCCESSFULLY on my first app server and then on my 2nd App server and my web server.  Apparently it worked cuz so far everything appears to be in good order. 

    THANK YOU!

     

    Sunday, March 9, 2008 2:37 AM
  • Thanks, Gus!!!

     

    This completely fixed my issue!

     

     Gus Cortes wrote:

    I was also fixed my problem !!  ( upgrade to SP1 , stage 8 )

     

    The problem was fixed when I Stopped One Service Only from Central Addministration (Operation>Services) :

    1.WSS Help Search

     

    No need to run psconfig by hand, simply re-run the Sharepoint Products and Technology Wizard.

     

    Hope this helps - Gus.



     

    Wednesday, April 2, 2008 10:59 AM
  • Error: Failed to upgrade SharePoint Products and Technologies

     

    Hi,

         Similar type of error i m facing with while running Sharepoint products and Technology configuration wizard for WSS upgradation. It gets failed at 8th of 9 creating a log file by name "PSCDiagnostics_4_21_2008_17_21_55_502_1441193062.log" at the location "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS". The log file state so many thing but under ERR "The B2B upgrader timer job failed." . Please help me out by providing practical solution ...

     

    Tuesday, April 22, 2008 10:11 AM
  •  

    Same problem with me too...

    please me out

    Friday, May 9, 2008 12:31 PM
  • Something that helped me was this KB article:

     

    How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint Services 3.0 or SharePoint Server 2007

    http://support.microsoft.com/kb/944267

     

    My particular error was "InstallAspNet [WebSiteID] failed" after installing KB950279 - a post-SP1 hotfix. Reinstalling ASP.NET and creating the suggested registry key (just in case) fixed the problem.

     

     

     

    Tuesday, May 20, 2008 10:56 AM
  • Hi,
       Well I had suffered from the same issue and had to format my server, bcz it crashed badly .
       But after that when I re-installed the server and MOSS on it, then I followed following steps:
    1. Goto Computer Management > Services.
    2. Here find Service "World Wide Web Publishing Service" Service Name: W3SVC
    3. Stop this service manually
    4. And then run the Installer exe of MOSS SP1.
    Note: I did above steps for following server environment
    1. Windows 2003 server R2 with MOSS installed.
    2. I havent upgraded/migrated the SharePoint version means from SharePoint 2003 to MOSS.
    3. Kind of MOSS server installed is with "Advance Setup" and Not "Basic" one.
    4. I first Installed SP 1 for WSS 3.0 and then SP 1 for MOSS
    Please refer to the documentation available online for installtion of SP for MOSS
    Wednesday, May 21, 2008 7:34 AM
  • Deleted
    Sunday, July 27, 2008 11:34 AM
  • Gus,

    This worked for me as well!!  My problems started when I installed KB941422 in preparation for DPM 2007.  Sure got my heart pounding when I couldn't access any of my sites.

    Thanks
    dan
    Saturday, November 1, 2008 10:30 PM
  • "Sharepoint is a great product"

    Are you kidding... SharePoint is an _absolute_ piece of garbage. I have never had a worse experience with an MS product. I love the .Net framework and the C# language, but SharePoint is a completely bug-ridden, bloated piece of garbage.
    Friday, April 3, 2009 7:43 PM
  • Well. I still have the same error in the upgrade.log.

    I test all solutions proposed upper but error continues. In my case I have seen versions table in content database and there are some site collections in version 6.0.2.5530 (windows sharepoint services 2.0). Could it be that service pack 1 is trying to upgrade this old sites? The migration process finished one year ago but these sites aren't migrated.

    CatDef table is WSS 2.0 or SPS 2003 table. It is not in current Sharepoint Content Databases (3.0, 2007).

    I need your help, thanks.

    Edited Later:

    Could i remove upgrade definition files from ..\12\config\upgrade folder? Are those files necessary for apply service pack 1 for MOSS/WSS or only for migrating WSS2.0/SPS2003 TO WSS3.0/MOSS 2007?
    • Proposed as answer by Dave Joye Friday, October 2, 2009 1:44 PM
    • Unproposed as answer by Mike Walsh FIN Saturday, November 13, 2010 5:45 PM
    Thursday, May 14, 2009 10:32 AM
  • Senario:
    I had experienced the same identified issue as stated above after installing sp2, over the slipstream MOSS install, and running the SharePoint Products and Technologies Configuration Wizard:

     The B2B upgrader timer job failed.
    12/13/2007 20:59:18  18  INF                    Entering function StringResourceManager.GetResourceString
    12/13/2007 20:59:18  18  INF                      Resource id to be retrieved is UpgradeTaskFailConfigSyncDisplayLabel for language English (United States)
    12/13/2007 20:59:18  18  INF                      Resource retrieved id UpgradeTaskFailConfigSyncDisplayLabel is Failed to upgrade SharePoint Products and Technologies.
    12/13/2007 20:59:18  18  INF                    Leaving function

    When this occured the configuration of the service pack wasn't complete.


    Farm Configuration:
      - Two FEW servers (64b Windows 2008)
      - One index\Query\SSP (64b Windows 2008)
      - One SQL (64b Windows 2008 SQL 2008)


    Troubleshooting:
    I was have the issues on the index\query\ssp server with the above mentioned timer job issue.  After going further in my logs I realized what the issue was.  I didn't intend on using IIS on the SSP so I never installed the service (Windows 2008).  When I installed MOSS under advanced installation the admin is promped with three options for install, Single Server Install, Web Front End ONLY or install all services.  While the SharePoint Products and Technologies Configuration Wizard is running it is upgrading services, jobs, files which included the web.config content IF it was a front end web server.  Because it was installed with all services, it had this service activated in the farm when it joined despite that it didn't have IIS running on it.

    Solution:
    I central admin, I deactived the web front end service.  After doing that I re-ran the SharePoint Products and Technologies Configuration Wizard and everything went perfect.


    HaloX
    • Marked as answer by Mike Walsh FIN Saturday, November 13, 2010 5:46 PM
    Friday, October 2, 2009 1:57 PM
  • Thanks HaloX, worked for me...

    custom sharepoint development
    Thursday, January 7, 2010 7:46 AM
  • THANKS, THANKS....... The problem was fixed . The problem was fixed when I Stopped these two services

     

    Saludos desde Chile...

    Escenario: SP1 --> SP2

    Saturday, November 13, 2010 4:19 PM