This project has moved and is read-only. For the latest updates, please go here.

Product key dialog shows up during installation ?



I want to install a simple single server farm SP2013 Enterprise with your script, and after following all the instructions, Unfortunately at the " - Installing SharePoint 2013 binaries......." step the Product key dialog shows up as shown on the screenshot. Why this is happening ?

Shouldn't the installation proceeds by itself and picks the PIDKey value from the XML file? Why it doesn't?

One-Single farm info:
OS: Windows 2012 R2
SQL Server 2012 SP2
SP2013 media: SP1 Slipstream (Meaning the downloading ISO from MSDN contains SharePoint with SP1 together)

<Configuration Environment="SP2013Farm" Version="3.99.51">
<Install SPVersion="2013">
    <InstallDir>C:\Program Files\Microsoft Office Servers</InstallDir>
    <DataDir>C:\Program Files\Microsoft Office Servers\SharePoint2013\Data</DataDir>
    <RemoteInstall Enable="false">
    <AutoAdminLogon Enable="true">
Could you please help out? Am I doing anything wrong?

Thank you !

file attachments


brianlala wrote Sep 22, 2015 at 9:04 PM

Can you look for your Config*.xml file? Could be in %TEMP%. Otherwise, look in your AutoSPInstaller*.xml file to determine what name you specified for the Config*.xml file. Within that file you should be able to confirm if the product key was picked up properly or not.


alex9spain wrote Sep 22, 2015 at 9:24 PM


Here is the first XML file which I built using ( I placed this file (SP2013Farm.xml) inside (D:\Temp\SP\AutoSPInstaller) along with other ps1 files. The moment I drag it and drop it into the AutoSPInstaller.bat => cmd starts and PowerShell prompt me to confirm (YES), verifies the managed accounts, installed the prerequisites, BUT, once it reaches the " - Installing SharePoint 2013 binaries......." step the Product key dialog shows up and it stuck !

<Configuration Environment="SP2013Farm" Version="3.99.51">
<Install SPVersion="2013">
    <RemoteInstall Enable="false">
    <AutoAdminLogon Enable="true">
Any thoughts Brain about my upper XML ?

brianlala wrote Sep 22, 2015 at 9:32 PM

No I mean the file "SP2013Farm.xml" - what are the contents of that file - usually gets created in your %TEMP% folder - unless it already exists in the path (which you should also check).


alex9spain wrote Sep 22, 2015 at 9:58 PM

See Brian,

Hopefully here are a better/organized details:

1) We used ( > Filled all the details properly > Review & Download > Copied all the entire XML > Stored in notepade as: SP2013Farm.xml

2) All files, binaries, scripts and everything is on the C:\Temp, Meaning:
SharePoint ISO is in C:\Temp\SP\2013\SharePoint\
SP2013Farm.xml is in C:\Temp\SP\AutoSPInstaller

3) The posted XML above previously as copy/paste from the (SP2013Farm.xml).

4) I followed all instructions accurately as they are on: (, and when we drag the (SP2013Farm.xml) into the AutoSPInstaller.bat, It works and it has installed the prerequisites.

5) The failure/stuck is only when it reaches: " - Installing SharePoint 2013 binaries......." step where the Product key dialog will prompt and stuck....

Brain, It is a single-server installation => Should the very first step in ( "Servers List:" left empty? Or, Do I need to fill the server's name ?

brianlala wrote Sep 22, 2015 at 10:05 PM

Right, so you've self-referenced the XML file you used for the entire farm build as the config file for the installation of SharePoint 2013 itself. They are two different things. Therefore when SharePoint goes to kick off the installation, it looks in your AutoSPInstaller "SP2013Farm.xml" file for a product key but the file isn't in the format expected - so you get a prompt for the product key. To get straight to resolution, try putting some other value in, for example:


And the install should proceed.


alex9spain wrote Sep 22, 2015 at 10:17 PM

Thank Brain for pointing this out.

Just to make sure that I understood you, Here what I will do:

A) I'll open (SP2013Farm.xml).
B) On the third line > I will change: <ConfigFile>SP2013PoC.xml</ConfigFile> to become: <ConfigFile>Config.xml</ConfigFile>

But, I don't have anything Config.xml !

C) Save file > drag it and drop it into the AutoSPInstaller.bat > It should install and proceed

Brain, Are these steps correct?

IvanJosipovic wrote Sep 22, 2015 at 10:19 PM

Hey Brian,

I think we should make a change to the Config File field, I think it should be blank when its auto generated and not blank when a user wants to specify a file, currently its hard to validate.


brianlala wrote Sep 22, 2015 at 10:50 PM

The Config.XML file is auto-generated and populated by AutoSPInstaller. So it does not have to pre-exist.

Agreed, Ivan (although this is the first time I can remember this having come up). Maybe even rename the element to <CustomConfigFile>.


wrote Sep 22, 2015 at 10:52 PM

armarshall wrote Oct 23, 2015 at 9:20 AM

I had the same issue as above, I just never reported it since it was easy enough to just pop open the config file and copy the key out manually.

Lucero79 wrote Mar 8, 2016 at 9:51 AM

I am having the same issue here. Seemed to work fine, and now it's not.

The config.xml file is even named config.xml. I drag it onto the .bat file and the install starts. I can see from the PS window that it's using the config.xml from the right directory. %TEMP% is clear, but maybe there's another %TEMP% location I haven't checked.

Copying and pasting the key isn't an option (is that what armarhsall is suggesting) as the installer will continue and ignore the rest of the config.xml.

Any ideas?

sqlsolver wrote Feb 7 at 8:48 PM

Experiencing this issue as well. Runs like a top through binary install until it gets to the updates (tried locating these in each of slipstream in the SP media's updates folder and placed in the updates folder parallel to the SharePoint folder, same error either way):

Setup log:
2017/02/06 14:46:34:246::[1356] Loading package metadata: D:\AutoSPInstaller\SP\2016\SharePoint\global\Wss\sts.xml
2017/02/06 14:46:34:246::[1356] Searching for patches for the current chained install in: D:\AutoSPInstaller\SP\2016\SharePoint\updates
2017/02/06 15:13:28:717::[1356] User attempting to cancel setup.  Confirming...
Canceled out as soon as the box requesting the license key came up.
 - Script halted!
 - Could not find SharePoint Server Setup log file!
Setup log was there and easily visible on the server navigating to %temp%
Install was done from UNC path, not on local server.

Had been dragging custom configuration file onto the launch file to kick off, also tried copying it to AutoSPInstallerInput and then starting the .bat as an admin.

Tried removing the name of the custom configuration file from between the ConfigFile tags as seems to be suggested above, got 'Cannot find the specified configuration file... [path]AutoSPInstaller'

wrote Nov 27 at 6:36 PM