Installing Jenkins on Windows Server 2012 Standard fails

[Drew Mace]

I'm trying to install Jenkins on a Windows Server 2012 Standard edition box but hit a snag - I am getting an error: Service 'Jenkins' (Jenkins) failed to start.  Verify that you have sufficient privileges to start system services.  I ran the installer as administrator (elevated privs).  Anyone have any ideas what i could try?

[Clemens]

I dont know if you have tried to start your Service with your command line ?
Do you ?
Enter your cmd (with Admin) and try : "net start Jenkins"
Maybe he will get it this way.

Greetings

[MDKF]

Check for the cause in jenkins.err.log in the directory where jenkins.war is located.

[Dirk Kuypers]

Hi,

you could also try this:

<?xml version="1.0" encoding="utf-8"?>

<configuration>

  <runtime>

    <generatePublisherEvidence enabled="false"/>

  </runtime>

</configuration>

as

jenkins-slave.exe.config

or

jenkins.exe.config

if you are behind a proxy that does not let you contact external servers to verify program signatures.

BR

Dirk

[bearrito]

I would elevate the service that Jenkins is running under to a local admin. You can then reduce the amount of privileges by trial and error to the appropriate level for your organization.

This isn't a Windows 2012 issue as it occurs on 2008.

On Sunday, November 25, 2012 9:26:07 PM UTC-5, Drew Mace wrote:

[jes Struck]

i would Also make sure you sufficient file permissions the user the service is running as must have r-w full recursive

[Drew Mace]

Well first I want to say thank you to all that replied.

I finally figured out the issue.  Windows Server 2012 has the .Net Framework 4 installed by default.  Jenkins needs the 3.5 Framework.  Once I installed the 3.5 framework, things installed perfectly.  Hope this helps other users in the future.

On Sunday, November 25, 2012 9:26:07 PM UTC-5, Drew Mace wrote:

[bearrito]

Haha. Didn't think about that. Would be great if the installer would check for that.

[Steven Scott]

I have not used that OS, but as rule with Windows 7+, I run the Command prompt as Administrator, and even File Explorer as administrator, then do the install.  If I can when running the actual installer, I try to right click and run it as Administrator as well.  Not running the command prompt as administrator usually causes the failures.