Version error while restoring a backup from a client system.

Toutes les réponses

• mardi 15 mai 2012 17:04

   

   
  

  1

  Hi,

  After installing Feb 2012 CU, did you run the SharePoint product configuration wizard and did it go through successfully? Please run it once more in your dev environment just to make sure.

  If that also does not upgrade your version #, please try to reinstall the Feb 2012 CU and see whether you get nothing is there to update message?

  I would start with just the product configuration wizard though.

  ---

  Thanks, Soumya | MCITP, SharePoint 2010

  • Proposé comme réponse GoingForward mardi 15 mai 2012 18:15
  • Non proposé comme réponse Steven AndrewsEditor mardi 22 mai 2012 10:53
  •  
  • Réponse
  • Citation

   
• mardi 15 mai 2012 17:40

   

   
  

  0

  Hello Soumya B

  Thanks. Running the configuration wizard actually updated the version number of the config db to

  Configuration database version: 14.0.6117.5002

  However, the main problem consists in that I am unable to restore a site that comes from a 14.0.5130.5002 (Dec 2010 Cumulative) System on my dev machine. The error is the same:

  Restore-SPSite : Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '14.0.0.5130' or later.

  • Réponse
  • Citation

   
• mardi 15 mai 2012 17:41

   

   
  

  0

  I faced the same issue recently. Unfortunately I do not think you have a choice in not installing patches. You would have to update your dev environment to the corresponding version as your production environment is already set. 

  As sowmya mentioned you would have to restart the server once you have installed the updates and then run the sharepoint products configuration wizard. If this completes successfully you should see the updated version in CA. 

  If it fails there are three things you can try:

  1. Re run the wizard. 

  2. Re run from Powershell : http://sanganakauthority.blogspot.com/2011/05/i-have-started-with-sharepoint.html

  3. Follow these steps

  close all the screens & then open services.msc on that server.
   
  Stop SharePoint 2010 Timer
   
  Open the folder "C:\ProgramData\Microsoft\SharePoint\Config\" in which we shall see a folder with a GUID.
   
  Open the folder with the latest date.
   
  Delete all the .XML files
   
  Then, open the cache.ini file in the same folder & change the value in it to 1 & save the file.
   
  After which, restart the Windows SharePoint Services Timer from services.msc
   
  Open the command prompt & run : psconfig -cmd upgrade -inplace b2b -wait -force
   
  The above command will update the server. 

  Hope this helps!

  • Réponse
  • Citation

   
• mardi 15 mai 2012 17:44

   

   
  

  0

  Hi

  So you are suggesting, along with other steps to clear SharePoint configuration cache.

  ---

  Thanks, Soumya | MCITP, SharePoint 2010

  • Réponse
  • Citation

   
• mardi 15 mai 2012 17:47

   

   
  

  0

  Soumya. 

  Yes. The third solution was suggested directly by Microsoft. 

  • Marqué comme réponse SPlex mardi 15 mai 2012 17:49
  • Non marqué comme réponse SPlex mardi 15 mai 2012 17:49
  •  
  • Réponse
  • Citation

   
• mardi 15 mai 2012 17:52

   

   
  

  0

  Hello GoingForward

  Thank you for your reply.

  You are suggesting that I have to update my dev machine, so it corresponds with the live environment. However, the versions are the other way around: The dev machine is a very recent version (february 2012 cumulative) while the live environment is relatively old (december 2010 cumulative!). However, since backups should be compatible with newer versions (which this is), I do not understand why I cannot load the backup into my dev machine. That's the problem I am facing.

  Cheers!

  • Réponse
  • Citation

   
• mardi 15 mai 2012 18:00

   

   
  

  0

  SPlex

  " The dev machine is a very recent version (february 2012 cumulative) while the live environment is relatively old (december 2010 cumulative!)."

  I am not going to comment on the compatibility aspect as I don't want to misguide you but what you could try is this: 

  1. Update your live environment (Preferably off Business hours or at your earliest convenience if you can afford to, during business hours) to the latest feb 2012 CU and then create your backup. You can now use this backup to restore to your dev environment.

  2. If you cannot afford to update your live environment any time soon, you would have to bring your dev environment down and match it to the live environment's version. In this case, you could use the backup that you already have.  

  • Réponse
  • Citation

   
• mardi 15 mai 2012 18:03

   

   
  

  0

  Hey GoingForward

  I have already suspected those two possibilities to be the only options I have. I am however, reluctant to both. It alienates me that Microsoft obviously made the backups not truly compatible with newer versions, but that, at one point, an old backup is rendered useless. Disappointing but not very surprising.

  Anyway, thank you for your help. I will see what I can do.

  • Réponse
  • Citation

   
• mardi 15 mai 2012 18:14

   

   
  

  0

  Well, I thought it was compatible as well! But tough luck I guess.

  In my case the production environment had a higher version than the dev environment and I tried the same thing you did and got the same result/error as yours. 

  I looked around the net and it looked like everyone suggested the same. So I just updated my dev environment and then backed up and it worked.

   

  
  

  • Marqué comme réponse Rock Wang– MSFT samedi 26 mai 2012 08:08
  •  
  • Réponse
  • Citation