.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

PreUpgradeCheck Failed : Pending upgrade operation detected in this farm

Posted By:      Posted Date: October 27, 2010    Points: 0   Category :SharePoint

I'm failing the stsadm -o preupgradecheck process with the following:  (preparing for MOSS 2007 to SPS 2010 upgrade).

Failed : Pending upgrade operation detected in this farm

Pending upgrade is detected on this farm. Either upgrade has not been run, or has failed after a recent update of the SharePoint software.

Run the SharePoint Products and Technologies Configuration Wizard to finish the pending upgrade. For more information about this rule, see KB article 954775 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.


View Complete Post

More Related Resource Links

preupgradecheck Failed : Pending upgrade operation detected in this farm


Hi There,

While executing stsadm command for pre-upgrade on WSS 3.0, I get an error “Failed : Pending upgrade operation detected in this farm“.
 I ran psconfig -cmd upgrade -inplace b2b -wait successfully, but still get the error above.  How do I get rid of this error?



Upgrade failed due to missing features though preupgradecheck didnt give errors

I am trying to migrate from sharepoint 2007 to 2010,I first ran preupgrade check,it gave me error realted to feature info,I migrated using database attach method,found 55 errors in log,downloaded tool called feature admin from codeplex,found some faulty features,removed them,ran preupgrade check ,received featureinfo passed,repeated again the migration process ,got 40 errors realted to missing features,if the preupgradecheck didnt give errors related to features,why am i getting upgrade failed due to missing features

Failed to change Farm Account in Sharepoint 2010 server, now Central Administration is not accessibl

Hello, I have a problem, that I no longer can access Central Administration Website, only the Sharepoint itself. I was running installation of Sharepoint 2010 Server with administrative account ImTheAdmin, who is a Domain Admin in the domain on one of the Windows 2008 R2 member servers. Besides that, I made ImTheAdmin the primary administrator of the Sharepoint. ImTheAdmin became the only user of this Sharepoint 2010 server after installation.  I installed everything on one box with default installation settings. I used builtin SQL server, not Standard or Enterprise. What then happened is: Using ImTheAdmin account, I opened Central Administration Website, and it said, that I need to change the Farm Account, for the account for Farm was the default one (I think it was network service). So I created a regular domain user MYDOMAIN\SharepointFarmAccount. The account name was too long to be as a Windows 2000 name, so it showed there without last 't', e.g. MYDOMAIN\SharepointFarmAccoun. I thought, Windows 2000 is long gone, so I didn't pay much attention, I think everywhere the account SID is important. I don't know if that is the real problem with my failure later, but it might be one of the reasons. I put MYDOMAIN\SharepointFarmAccount down in to the form of Central Administration Website, added the check mark, that it would react to password changes, and pre

FaxComExLib InteropServices.COMException (0x800710D8): Operation failed

Hi! I've developed an application that takes a PDF document and converts it to a TIFF file using GhostScript library. This process is done correctly. I then setup a fax connection using FaxComExLib.FaxServerClass to send that TIFF file through fax. My settings (developing/testing environment) are as follows: * Servers are in a domain (baker.street)  - DC containing AD | name: holmes  - Processing server | name: adler  - Fax Server | name: watson * I have a special account BAKERSTREET\Fax The application is running as a Windows Service as user BAKERSTREET\Fax. This services receives Events from a MSMQ queue that has the processing information. (again, this is done correctly). The file is transformed an then an attempt to send the fax is done. Here comes the problem: Scenario 1: * Running account: BAKERSTREET\Fax * Fax Server: \\watson * Result: InteropServices.COMException (0x800710D8): Operation failed               The fax is not sent to the fax server. Scenario 2: * Running account: BAKERSTREET\Fax * Server Fax: \\adler (localhost; this is the computer where the process runs) * Result: The fax is sent successfully to the Outbox Queue in the Fax Server. Scenario 3: * Running account: BAKERSTREET\Administrator (domain administrator account) * Fax Server: \\watson * Result: As shocking as this may

sql server 2008 version upgrade failed access to path is denied

upgrading from 2008 r2 eval to 2008 r2 enterprise. Use the maintenance option from setup. Get pretty far along in the process.  But then the following error. ( an additional note. setup warns that I am running sql server on a domain controller server. ) The link the error message points to has nothing to say. Why would my sql server upgrade fail? If I have to reinstall, will I lose my database data? thanks,   TITLE: Microsoft SQL Server 2008 R2 Setup ------------------------------ The following error has occurred: Access to the path 'C:\Program Files\Microsoft SQL Server\100\License Terms\SQLServer2008R2_License_ENT_1033.rtf' is denied. Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x60797DC7%25400xBB814387  

Failed to upgrade SQL 2K5 Express to Enterprise: Service 'MSSQL$OFFICESERVERS' could not be starte

Hello, I have a standalone SharePoint Server 2007 with SQL Server 2K5 Express and today I upgrade the SQL 2K5 Express to Enterprise with the command: setup.exe SKUUPGRADE=1. At the last, the wizard give me a error dialog saying the following error.  I search the Internet for half a day but in vain. Hope you can show me some idea. Thanks. TITLE: Microsoft SQL Server 2005 Setup------------------------------ Service 'MSSQL$OFFICESERVERS' could not be started. Verify that you have sufficient privileges to start system services. The error code is (1067) The process terminated unexpectedly. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=1067&EvtType=sqlsetuplib%5cservice.cpp%40StartServices%40sqls%3a%3aService%3a%3aStart%40x42b  Hope Helpful | Xiaofeng Wang | http://www.leoworks.net

Feature Infor Failed when running preupgradecheck

I want to upgrade to sharepoint 2010 ,I ranthe preupgrade checker,it gave me Feature info failed ,how can I solve this error,and can this error stop the migration

SharePoint 2007 to 2010 Upgrade AND Farm Merge


Hello all,

I'm curious to see if anyone has done this.  Currently, my environment has 3 seperate SharePoint 2007 server farms.  I'm currently evaluating SharePoint 2010 and so far like what I see.  I'm wondering though what would be the steps I would need to go through to actually upgrade and then merge them all to one SharePoint 2010 farm?  The steps I can think of are the following:

1. Make sure all 2007 farms are on the lastest (or at least similar) version

2. Upgrade each farm to SharePoint 2010

3. Create new 2010 farm

4. Copy upgraded farms' site collections to NEW 2010 farm.

OR can I do this:

1. Make sure all 2007 farms are on the same version

2. Create a copy of each current SharePoint 2007 site collection that I want

3. Create NEW 2007 Farm

4. Copy content to new farm

5. Upgrade new farm to 2010


Any and all help would be greatly appreciated, thanks!


MOSS 2007 Restore Operation Failed: The specified component exists.


I have a production MOSS farm and selected to backup my content database to a share on my network so I can move its data to my development environment. I used the Sharepoint Central Administration GUI to do this backup and selected New Configuration since I didnt want to use the same config as my production server (i.e - my development environment has its own farm with different naming conventions for those servers), and then changed the name of the Database server and kept the same name as the current _SITE database in my DEV environment. The backup ran fine, but now on restoring from the backup I receive this message below:


Object portal1_SITE failed in event OnRestore. For more information, see the error log located in the backup directory. SPException: The specified component exists. You must specify a name that does not exist.

Below is some information from the log...


[9/19/2007 9:57:18 AM]: Verbose: Starting OnRestore event.
[9/19/2007 9:57:18 AM]: Verbose: Starting object: portal1_SITE.
[9/19/2007 9:57:18 AM]: Verbose: [portal1_SITE] SQL Server Conn

Failed upgrade from wss 3.0 to moss 2007. Cannot open database "ProjectServer-live_Published" reques


While trying to upgrade from WSS 3.0 to MOSS 2007 the process finished, but it stated that it completed with errors. Those errors seem to be causing problems within the Central Administration site. I will try outline the errors the best I can from the upgrade.log file and with the actions I've been attempting. THANK YOU in advance for any and all assistance.

[SharedResourceProviderSequence] [ERROR] [9/23/2010 11:15:03 AM]: Unable to locate SearchDatabase for the SharedResourceProvider Hyperion_SSP
[SharedResourceProviderSequence] [ERROR] [9/23/2010 11:15:03 AM]: Exception thrown was: System.ArgumentNullException: Value cannot be null.
Parameter name: No search database is associated with the search shared application, Hyperion_SSP
   at Microsoft.Office.Server.Search.Upgrade.SharedResourceProviderSequence.get_SearchDatabase()
   at Microsoft.Office.Server.Search.Upgrade.SharedResourceProviderSequence.AddNextLevelObjects()
[SharedResourceProviderSequence] [INFO] [9/23/2010 11:15:03 AM]: Re-run upgrade using stsadm -o upgrade to ensure the search database gets upgraded appropriately
[SharedResourceProviderSequence] [DEBUG] [9/23/2010 11:15:03 AM]: No search database was found, so skip upgrading it

As advised in the info section for this error I re-ran the upgrade

SQL Server 2008 Feature Upgrade Failed



I have an installation of SQL Server 2005 Express, and I'm trying to upgrade it to SQL Server 2008 Express.  During the installation, when it gets to the "Upgrade Rules" part, everything passes except for "SQL Server 2008 Feature Upgrade."  It says the specified edition upgrade is not supported, but according to the upgrade matrix it should be.  We plan on purchasing licenses for the Enterprise edition, but I would like to figure this out in the meantime.



b2b upgrade timer job failed

I recently tried upgrading to MOSS SP1 and came across 'The b2b upgrade timer job failed' error with no better explanation of what failed on the upgrade.

Server is single installation Server 2003/SQL Server 2005.

I installed the WSS 3.0 SP1 and MOSS 2007 SP1 binaries and then ran the configuration wizard. It got to step 8 of 9 (Updating the server) and failed out.

Has anyone else seen problems like this? Is there a way to find what failed. I checked all the logs already and could not find any more descriptive errors.

Solution Deployment failed in Server Farm - Some of the files failed to copy during deployment of th


Hi guys,

I created a solution package in my development environment that works well. When I try to deploy it in a test environment that is a farm with two web front end(card0023 / card0024) servers and a application server(where I have the central administration / card0027) I got the error bellow:

Deployment Status: Error
Deployed To: None
Last Operation Result: Some of the files failed to copy during deployment of the solution.
Last Operation Details: CARD0023: http://card0027:11000/ : The solution was succesfully deployed.
    CARD0027: http://card0027:11000/ : The solution was succesfully deployed.
   CARD0023: http://card0027:11000/ : The solution was succesfully deployed.
   CARD0024: http://card0027:11000/ : The solution was succesfully deployed.
   CARD0027: http://card0027:11000/ : SharePoint - 11000 : Error: The web.config is missing from this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\11000\web.config. 
Someone can help me?


André Rentes

SPWebApplication, This operation can be performed only on a computer that is joined to a server farm



We are trying to migrate a console program (C#) from Moss 2007 to SP 2010.

One of the functions in the program has to loop thru several web apps/site colls/sites/lists to trim permissions and uses this sentence to get a reference to the web app:

- SPWebApplication webApplication = SPWebApplication.Lookup(serverUri);

In MOSS 2007 it works but in SP 2010 we see this error message:

"This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the

Error When Joining Reporting Server to Farm: "Task configdb has failed with an unknown exception" an


This is apparently a very common error message, as I see numerous posts about it on these forums.  Unfortunately, none of the solutions have worked for me.  So I'm hoping somebody knows what is happening in my case.

CURRENT FARM (all in same domain):

Server Web3, Windows Server 2003 R2 (x86) <- WFE, WSS 3.0, SP2
Server Web4, Windows Server 2003 R2 (x86) <- WFE, WSS 3.0, SP2 (also Central Admin host)
Server SQL2, Windows Server 2003 R2 (x64) <- Database server for WSS installation (SQL 2008)
Server SQL5, Windows Server 2008 R2 (x64) <- New reporting server (SQL 2008), WSS 3.0 SP2 - unjoined from farm

- Reporting server database is configured in Sharepoint integrated mode.
- All WSS servers are at SP2.  I have double, triple, and quadruple checked this.  Build on all three servers is 12.0.6425.1000 (as retrieved from Add/Remove Programs and Programs and Features, respectively.)
- No additional hotfixes were applied after SP2.

When trying to join my new server (SQL5) to the existing farm using the configuration wizard, I get the following error...

10/11/2010 19:21:16  8  ERR                      Task configdb has failed with an unknown exception

The operation failed because an unexpected error occurred. (Result Code: 0x81071003)


Hi all,  I have a SINGLE web service that I call through two different programs.  I input the same values into the service and call a sevice method.  One call fails every time, one call works every time.  I have installed Fiddler2 and copied the requests and responses from each.  They are identical except for the [VsDebuggerCausalityData] header value and the [Authorization:] value (data below)  what is this error? What can I do to address it? Why does it work for one app, but not the other when the requests are the same.  I guess since the Authorization is different it could be a security problem. But I'm not so sure because I'm not getting a security type error.  The first trace is the working example (look at the response) the second is the failing call.  I have changed the Authorization values.

POST http://kerryportal/global/DMS/CRM/_vti_bin/Lists.asmx HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.4952)
VsDebuggerCausalityData: uIDPo+bNI0fMARFBsgZwKLhVCEUBAAAA2xBAL4gjpUWSP4dBtR8U/4q2nB9UKJVFvuCo3qZaaXUACQAA
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://schemas.microsoft.com/

Adding an SP 2010 server to an existing farm. "Failed to connect to the configuration database." dur


I have an existing sp 2010 enterprise server hosting websites and central administration.  I have a seperate sql 2008 r2 server holding the databases.  My goal is to setup another sp 2010 enterprise server to provide redundancy for the websites and central admin.  I believe I am able to accomplish this by adding another web front end to the farm.  On the second server, I install sp 2010, run the config wizard and connect to the config database located on the sql server, however, I am interrupted at step 3 when I am notified of the following:

Failed to connect to the configuration database.
An exception of type System.InvalidOperationException was thrown.  Additional exception information: There was an error encrypting or decrypting credentials. Either a credential update is currently being performed, or you must update the farm account credentials on this server before you can perform this task.
System.InvalidOperationException: There was an error encrypting or decrypting credentials. Either a credential update is currently being performed, or you must update the farm account credentials on this server before you can perform this task.
   at Microsoft.SharePoint.Administration.SPEncryptedString.CheckCredentialLock()
   at Microsoft.SharePoint.Administration.SPManagedAccount.Deploy(SPApplicat

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend