Jason Medero SharePoint MVP: SharePoint Space for all things SharePoint, OCS, RMS, InfoPath, and Office

I ran into the issue that will be descirbed below about 8 months ago with a client that was having trouble upgrading their development environment with the IU Update.  For some reason whatever I tried (even rebuilding the entire farm) I kept receiving the error below when running the SPCW.

Configuration Failed

One or more configuration settings failed. Completed configuration
settings will not be rolled back. Resolve the problem and run this
configuration wizard again.

Additional exception information:
Failed to upgrade SharePoint Products and Technologies.

We didn't have the problem in production and I couldn't figure out why, being that the error messages were not very descriptive.  I thought it could possibly be that an update was applied to the SQL server that was hosting my SharePoint farms.  Or maybe it was that an update was applied to one of the web front ends in the farm and not the other.  So I began to run through all of the server to make sure that all my servers were on the same version (they were).  Long story short we just ended up migrating the data to a new farm and had no idea that it was the GroupBoard Workspace template that was installed in DEV and was not installed on PROD.

This morning I had a client that wanted me to upgrade them to the Infrastructure Update (IU) and when I ran the SPCW I again got the error message above.  I did some researching and it turned out that the client was heavily using many of the application templates that Microsoft has made available.  I was lucky enough to run into this KB article:

http://support.microsoft.com/default.aspx/kb/941678/

I followed the instructions on the second method because I could access all sites including the group workspace site.  Installed the update in my case was the X64 update for the group workspace template.  All worked without a hitch!  I wanted to post this issue because I have run into it more than once and thought it might save SharePoint folks some valuable time.

Cheers,

This entry was posted on Monday, February 23rd, 2009 at 12:44 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

I ran into the issue that will be descirbed below about 8 months ago with a client that was having trouble upgrading their development environment with the IU Update.  For some reason whatever I tried (even rebuilding the entire farm) I kept receiving the error below when running the SPCW.

Configuration Failed

One or more configuration settings failed. Completed configuration
settings will not be rolled back. Resolve the problem and run this
configuration wizard again.

Additional exception information:
Failed to upgrade SharePoint Products and Technologies.

We didn't have the problem in production and I couldn't figure out why, being that the error messages were not very descriptive.  I thought it could possibly be that an update was applied to the SQL server that was hosting my SharePoint farms.  Or maybe it was that an update was applied to one of the web front ends in the farm and not the other.  So I began to run through all of the server to make sure that all my servers were on the same version (they were).  Long story short we just ended up migrating the data to a new farm and had no idea that it was the GroupBoard Workspace template that was installed in DEV and was not installed on PROD.

This morning I had a client that wanted me to upgrade them to the Infrastructure Update (IU) and when I ran the SPCW I again got the error message above.  I did some researching and it turned out that the client was heavily using many of the application templates that Microsoft has made available.  I was lucky enough to run into this KB article:

http://support.microsoft.com/default.aspx/kb/941678/

I followed the instructions on the second method because I could access all sites including the group workspace site.  Installed the update in my case was the X64 update for the group workspace template.  All worked without a hitch!  I wanted to post this issue because I have run into it more than once and thought it might save SharePoint folks some valuable time.

Cheers,

This entry was posted on Monday, February 23rd, 2009 at 12:44 pm and is filed under Uncategorized. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.