Forum Discussion
SharePoint 2013 install fails with error 1603 everytime...it cannot be done
- Nov 13, 2019
Finally solved this problem. It appears the MSI - oserver.msi was having an issue with compatibility (i assume windows). I downloaded another copy of SharePoint SP1 from MSDN and copied the oserver.MSI package into my initial installation (extracted ISO). I tried just the new copy of the install from MSDN that failed, and the old one also failed on it's own. BUT, the install worked when i replaced this whole "global" directory.
New MSI was created on 2.10.2012 and the one i had was newer - created on 25.01.2014.
For some reason the installation did not like this newer version of the oserver.MSI
So i added the registry entry for Installer logging - but nothing new is logged?
I do see some older logs there and one of them says for my troublesome MSI - oserver.msi is incompatible
Then i tried to set the compatibility and only option is - Compatible with previous Windows versions - none to be selected. What? But then installation fails anyways with the same error.
I saw this article but not sure if this is the right way forward and how safe can it be: https://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/how-to-change-the-compatibility-setting-of-msi/3e803835-9655-48cd-a945-08ecc0327b21
Finally solved this problem. It appears the MSI - oserver.msi was having an issue with compatibility (i assume windows). I downloaded another copy of SharePoint SP1 from MSDN and copied the oserver.MSI package into my initial installation (extracted ISO). I tried just the new copy of the install from MSDN that failed, and the old one also failed on it's own. BUT, the install worked when i replaced this whole "global" directory.
New MSI was created on 2.10.2012 and the one i had was newer - created on 25.01.2014.
For some reason the installation did not like this newer version of the oserver.MSI
- aselimagicSep 22, 2020Copper ContributorDownload direct from MSDN. Then just compare the versions of oserver.MSI
As you can see above - older MSI was created on 2.10.2012 and the one I had was newer - created on 25.01.2014. If you have the new one, try replacing it with the older msi version. - Sep 04, 2020MSDN is a pay-for service. You need to purchase a subscription. Mix and matching MSIs isn't a good idea. SP 2013 w/ SP1 ISO works on Win Svr 2012 R2 without issues.
- sharkawyDevoSep 03, 2020Copper Contributorcould u please send me link for msdn source u downloaded cause i get same issue
- SteveKnutsonNov 13, 2019MVP
aselimagic I'll add a link to this on my blog. Glad you got to the bottom of the issue. Well done.
- aselimagicNov 13, 2019Copper ContributorThank you to both Trevor Seward SteveKnutson - each of you helped in a way to get to the logs of the MSI and also to check the AppFabric install. It seems the AppFabric was not culprit this time around.