Service 'Jenkins' (Jenkins) failed to start.

3,964 views
Skip to first unread message

Artem

unread,
Oct 1, 2011, 12:11:06 PM10/1/11
to Jenkins Users
Hello! I tried to install Jenkins using jenkins-1.432.msi. The
operation system is Windows Server 2008 Enterprise Service Pack 2 x64.
The installation process goes well until starting services. Then I get
the next error (from Event Viewer): "Product: Jenkins 1.432 -- Error
1920. Service 'Jenkins' (Jenkins) failed to start. Verify that you
have sufficient privileges to start system services." I run
installation under user with local admin rights. I tried to find a
solution of this problem but without results. Please, give me some
advice that I can do with this.

nellyt

unread,
Oct 9, 2011, 8:51:51 PM10/9/11
to Jenkins Users
Did you manage to solve this, I have the same problem?

On Oct 2, 4:11 am, Artem <artemy...@gmail.com> wrote:
> Hello! I tried to install Jenkins using jenkins-1.432.msi. The
> operation system is Windows Server 2008 Enterprise Service Pack 2 x64.
> The installation process goes well until starting services. Then I get
> the next error (from Event Viewer): "Product: Jenkins 1.432 -- Error
> 1920. Service 'Jenkins' (Jenkins)failedtostart.  Verify that you
> have sufficient privileges tostartsystem services." I run

Artem

unread,
Oct 10, 2011, 5:09:46 AM10/10/11
to Jenkins Users
No, unfortunately I didn't find solution yet. I'm still trying to get
answer from Jenkins support.

Jan Seidel

unread,
Oct 10, 2011, 8:00:24 AM10/10/11
to Jenkins Users
Hi Artem,

this sounds like an issue with the context the installation is running
in.
The post WinXP/W2003 era has some nasty changes at hand for
administrators/power users.
You can only install system critical stuff, or software that could put
the system at risk via the trustedInstaller context.
That service has the highest level of privileges. It is higher than
the administrators privileges and if I do recall right, even high than
the SYSTEM context.
The lack of using the TrustedInstaller or errors in the manifest file
can result in this.

It seems that Jenkins is getting installed and only the step to
register/create the service fails.
I would suggest simply to install it without the service and make the
last step manually. I would even disregard the installer and use the
archive.
You should then try to start Jenkins and install it as service from
the "manage Jenkins" section.

You could optionally try to create the service yourself with the CLI
command SC. sc create [service name] should do it. Then review the
service and make changes if necessary.
I can't tell for sure if SC still is a valid working command as I atm
only have WinXP in reach.

Take care
Jan

Albert

unread,
Mar 15, 2013, 7:15:58 PM3/15/13
to jenkins...@googlegroups.com
according to this post, the right answer is to update .NET using the following command 

Dism /online /enable-feature /all /featurename:NetFX3

Reply all
Reply to author
Forward
0 new messages