1

TL;DR

Uninstalling SharePoint 2010 and installing SharePoint 2007 makes PSCONFIG stop running since it misses the Microsoft.SharePoint.DLL version 14. How can this be solved?


On a SharePoint 2010 server SharePoint was uninstalled. The 14-hive was manually removed and the SharePoint Web Sites and IIS was deleted. Upon installing SharePoint 2007 SP 2, everything went fine until the final step – running PSCONFIG. We got the error message from the console stating

C:\Users\SP_Setup>psconfig

Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=7
1e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' ---> System.IO.FileNotFoundException: Could not load file
or assembly 'Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

   at Microsoft.SharePoint.PostSetupConfiguration.Common.SetThreadCultureToInstalledCulture(Thread thread)
   at Microsoft.SharePoint.PostSetupConfiguration.Common.SetCurrentThreadCultureToInstalledCulture()
   at Microsoft.SharePoint.PostSetupConfiguration.PsconfigCommandLineMain.Main(String[] args)


C:\Users\SP_Setup>

enter image description here

What puzzles me is the way PSCONFIG tries to access Microsoft.SharePoint.DLL version 14 in the first FileNotFoundException. Is there a reference somewhere that we didn’t think of when we uninstalled SharePoint 2010, that couldn’t be resolved upon installing SharePoint 2007? Is there a way to fix this or should we bluntly reinstall the entire Windows Server 2008 R2?

  • Why are you going backwards? ;) – Robert Lindgren Feb 17 '15 at 8:07
  • @RobertLindgren My initial question to customer too ;-). But we need a fresh 2007 installation to test a database move using SQL Alias. And since this DB-move will take place during 11PM to 3AM one want to be sure it works... – Benny Skogberg Feb 17 '15 at 8:09
  • I think you can find something that affect to this problem in regedit ;) – BioGeneZ Feb 17 '15 at 9:40
  • Try: 1)Open "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\" 2)Remove folder 14.0 – BioGeneZ Feb 17 '15 at 10:10
  • @BioGeneZ Thanks for the tip. The 14.0 folder doesn't exist... – Benny Skogberg Feb 17 '15 at 10:15
2

This is probably not the recommended, nor the supported way to do it. The best would probably be to reinstall Windows Server 2008. However, in my case, it solved the problem and could be used as a last resort if you can’t reinstall the server. I opened the regedit and searched for ”14.0.0.0” and found these interesting posts:

Img

I updated the path from 14 to 12 the following way on all locations:

enter image description here enter image description here

Further, I changed the regedit ServerRole from SINGLESERVER to APPLICATION to be able to specify Database Server in the following location:

“HKLM_Local_Machine/Software/Microsoft/Shared Tools/Web Server Extensions/12.0/WSS/”

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.