Microsoft SharePoint Server 2013 encountered an error during setup

(the html editor over here is a pain you know where - not even bold text is working...)

Every time I try to install SP 2013 SP1 on my WS 2012 R2 Update virtual machine the installer dies.

NOTE: I can reproduce this any time. Both the SharePoint 2013 (including SP1) .iso as well as the WS 2012 R2 (including Update) .iso are fresh copies out of the MSDN library.

The installation fails where the installer tries to install the binaries. No configuration wizard yet. I made sure all the prerequisites are there. The PreRequisitesInstaller.exe reboots the virtual machine several times (twice) and then it is all set.

PS C:\Users\bsom> add-windowsfeature net-wcf-http-activation45, net-wcf-tcp-activation45,net-wcf-pipe-activation45

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
True    No             NoChangeNeeded {}


PS C:\Users\rsom> Add-WindowsFeature Net-Framework-Features,Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,
Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-
Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-Http-Tracing,Web-Security,Web-Basic-Auth,Web-Windows-A
uth,Web-Filtering,Web-Digest-Auth,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Tools,Web-Mgmt-Conso
le,Web-Mgmt-Compat,Web-Metabase,Application-Server,AS-Web-Support,AS-TCP-Port-Sharing,AS-WAS-Support, AS-HTTP-Activation
,AS-TCP-Activation,AS-Named-Pipes,AS-Net-Framework,WAS,WAS-Process-Model,WAS-NET-Environment,WAS-Config-APIs,Web-Lgcy-Sc
ripting,Windows-Identity-Foundation,Server-Media-Foundation,Xps-Viewer

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
True    No             NoChangeNeeded {}


PS C:\Users\bsom>

UPDATE: I had a quick look at %Temp%\SharePoint Server Setup(20140513...).log

 

2014/05/13 20:30:40:858::[2344] Log level changed from: Verbose to: Standard
2014/05/13 20:30:40:858::[2344] Error: Failed to install product:  D:\global\oserver.MSI ErrorCode: 1603(0x643).
2014/05/13 20:30:40:858::[2344] Log level changed from: Standard to: Verbose
2014/05/13 20:30:40:858::[2344] Rolling back chain

Any ideas?

UPDATE: Installing office prior to the sharepoint installation had no effect (solution was suggested  here).

UPDATE: Installing all windows updates (for Windows Server and Office client applications) didn't help either... same error.

UPDATE: I made sure my windows server and sharepoint server images are exactly those you can currently find on MSDN. SHA1 hashes match.
  • Edited by Venenum Tuesday, May 13, 2014 8:06 PM
May 13th, 2014 8:30am

1. Try not to use copy which has SP1 for sharepoint

2. in Start > run > %temp% . 

the recent folder you will get some log file\folder. please share details from these logs

  • Proposed as answer by John Naguib Thursday, February 12, 2015 2:12 PM
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2014 9:04am

I'm not sure what you mean.

I have to use SP 2013 including SP1 otherwise it won't install on Server 2012 R2.
I'll have a look at %temp% once I get back to my work place.

May 13th, 2014 10:17am

At what point in the installation/configuration process is it failing?
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2014 10:43am

When it is installing the binaries. I cannot say which package exactly is failing to install. That's why I added the last successfully installed package name above.

Product: Microsoft Education -- Installation completed successfully.
Windows Installer installed the product. Product Name: Microsoft Education. Product Version: 15.0.4569.1506. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

Whatever comes after that causes a serious problem.

May 13th, 2014 12:43pm

Did anyone install SP 2013 (including SP1) on a fully patched Windows Server 2012 R2 lately? Because I really really can't. It is shockingly reproducible.
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2014 12:14pm

I've got the same exact problem. Just like you, my SharePoint With SP1 install fails on oserver.msi with error code 1603(0x643); installing on stand alone MS Server 2012 R2 using SP 2013. I was able to get past most of the obstacles by installing SQL Server 2012 before running the SP prereq's and then install, but this is the one error that I can't get past.

What's crazy is that I had a successful installation one time so I know there's a way, but either something has changed since then or I'm just not getting the right sequence combination of steps to do it again. IDK...

Very frustrating as most of the solutions I've seen point to a bad iso file which is not correct. This I know because I downloaded it many times now and it always fails on oserver.msi. 

I found a workaround by using a program called Orca to modify the msi file but I'm not sure what the repercussions of that are. Anyone know...?

June 16th, 2014 10:28pm

I just did a Server 2012 R2 and SP 2013 w/ SP1 install the other night on Hyper-V running on 8.1 Pro without issues. ISO was from MSDN.

Have you run a crc (or md5, forget what is used) to validate the ISO matches what MSDN says it should be?

Free Windows Admin Tool Kit Click here and download it now
June 16th, 2014 10:44pm

I have installed SharePoint 2013 SP1 (both Foundation and Standard) in a Windows 2012 R2 environment many times and haven't encountered this issue before.

What's the setup - is this a virtual or physical server?  Are you installing from a mounted ISO or have you extracted the files to a local drive?  Do the prerequisites install without issue?

June 17th, 2014 5:36am

Assuming these issues are in a virtual environment, double check to make sure you are using at least two (2) processors and that you have the minimum amount of RAM.

Shannon

Free Windows Admin Tool Kit Click here and download it now
January 27th, 2015 1:41pm

Hello

I have the same problem.
I'm trying to install SharePoint 2013 on Windows Server 2012 R2
RAM: 12288
PROCCESORS: 4
The log of the installation process says:

Problem signature:
  Problem Event Name:    OfficeClassicSetup
  SETUP EXE VERSION:    15.0.4454.1000
  SETUP DLL NAME:    SVRSETUP.DLL
  SETUP DLL VERSION:    15.0.4569.1503
  ERROR CODE:    1603
  MSI HRESULT:    Unspecified
  ERROR DETAILS:    FC73469E
  FIRST ERROR CODE:    1603
  OS Version:    6.3.9600.2.0.0.272.7
  Locale ID:    3082

Looking at C: \ Users \ [Username]\ AppData \ Local \ Temp \ SharePoint Server Setup (20150212104557D30) .log I encounter this error:

Error: Failed to install product: D: \ Global \ oserver.MSI ErrorCode: 1603 (0x643).

I begin to despair.

  • Proposed as answer by Aranako Thursday, February 12, 2015 4:48 PM
February 12th, 2015 10:09am

Recently i faced same issue. My OS was Win Server 2012 R2 - I was installing Sharepoint 2013.

Same type of errors i meet. Then i figured out that i am not using the right Installation Media. 

then i used SP13 with SP1. that worked for me.

#YI do not forget to mark as answer if it helps you.

Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 10:22am

I pass the situation using this metod, but I think isn't a solution:

  1. Download the ORCA tool from the Windows SDK (ORCA allows you to modify MSI files)
  2. In Explorer, locate the global\oserver.msi file in your SharePoint 2013 install tree.
  3. Right-click the MSI and specify 'Edit with Orca'
  4. Select the InstallExecuteSequence table.
  5. Locate the ArpWrite action, right-click, Drop Row
  6. File->Save
  7. Rerun SP2013 Setup as usual.

At the end, I don't know the cause.

February 12th, 2015 1:39pm

Recently i faced same issue. My OS was Win Server 2012 R2 - I was installing Sharepoint 2013.

Same type of errors i meet. Then i figured out that i am not using the right Installation Media. 

then i used SP13 with SP1. that worked for me.

#YI do not forget to mark as answer if it helps you.

As I said, SP13 including SP1 - I checked SHA1 hashes.. all fine.
The "side effects" of my .msi editing was windows updates couldn't correctly update the existing SharePoint farm as it didn't even show up under "installed programs".

It's a hyper-v VM with 20GB RAM for the SharePoint VM. That should be plenty.

Free Windows Admin Tool Kit Click here and download it now
April 4th, 2015 9:04am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics