The Kinetic Jump site navigation header requires JavaScript to be enabled and the latest version of the Macromedia Flash Player. If you are you using a browser with JavaScript disabled please enable it now. Otherwise, please update your version of the free Flash Player by downloading here.

Welcome Guest Search | Active Topics | Log In | Register

Service fails on installation Options
DJ van Wyk
#1 Posted : Wednesday, October 03, 2007 9:51:16 PM
Rank: Newbie
Groups: Member

Joined: 9/27/2007
Posts: 3
Location: South Africa
Good Morning,

I'm trying to install the Eval version on 2 developers' PC (roughly the same as mine).

After I run the installer, it hangs on "Status - Starting Service" and then eventually comes up with the following error message........

"Service 'AppLife Update Service' (KjsUpdateService) failed to start. Verify that you have sufficient privileges to start system services."

I do have the sufficient privileges to start system services and have tried everything else.

Any Suggestions?
brianh
#2 Posted : Friday, October 05, 2007 6:39:09 AM
Rank: Administration
Groups: Member, Administration

Joined: 5/24/2007
Posts: 402
Location: Minnesota
We are aware that this issue has been affecting a small group of users. Unfortunately, we are unable to reproduce this issue. We are working hard to find the cause of this problem. I will post a reply to this thread when the issue is verified to be resolved.
Brian Haas
Kinetic Jump Software
brianh
#3 Posted : Wednesday, October 10, 2007 1:57:20 PM
Rank: Administration
Groups: Member, Administration

Joined: 5/24/2007
Posts: 402
Location: Minnesota
This issue that appeared on some computers when the AppLife Update Windows Service attempted to start has been resolved.

This issue evaded us for longer than it should have mainly because we never were able to reproduce it (until we discoved what was causing it). Many thanks to those who traded emails with me as we tried to figure out what was going on.

The problem was a result of the authenticode signature of the service executable. When the framework attempts to load a digitally signed assembly, it tries to retrieve a certificate revocation list (crl) from the signing certificate authority. Well, if the current user (Local System) can not reach the certificate authority, this process takes some time before finally timing out. It takes more time than the Windows service control manager gives a service before aborting the start command and throwing a timeout of it's own, with no meaningful message.

To resolve this, we have removed our x509 digital signature from the service executable. This does not in any way degrade the security measures built into the service and how it performs its function. We are also looking at the possiblity of bootstrapping the service with an unmanaged executable that we can sign, but that has ramifications of it's own.

This issue is resolved with the release of AppLife Update 1.1. If anyone has any further issues with the service, please let us know.
Brian Haas
Kinetic Jump Software
Users browsing this topic
Guest
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.