Tried a number of times, and on different machines. All have .NET 3.5 SP1.
Service refuses to start, so have had to rollback to 5.5.3 on all machines. This is REALLY frustrating.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 3/19/2010
Time: 8:31:55 PM
User: N/A
Computer: SJP11APP19VM
Description:
The VisualCron service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .

Could you send us the server_startup.txt log file or post it here?

---

server startup date/time stamp ends at 4:44pm today (when I installed 5.5.5)

We had one similar issue with another customer but we are not sure of the reason. The problem was about permissions.

He changed the user that runs the VisualCron service from SYSTEM to a local admin account and it started OK.

Please let us know if that works for you.

Also, please tell us more about operating system. Service packs and if you are running 32 or 64 bit Windows.

---

that worked, changing account! A bit strange, as worked fine with SYSTEM on 5.4.9.

Machine is 32 bit Windows server 2003 R2 SP1

If you hang on we will try to rebuild and maybe you can test that version instead on the other server (using SYSTEM)?

---

ok, no problem

Many thanks Hendrik

Please test this version with SYSTEM.

---

still no joy. install took a long time, and service won't start with local system, does with another account.

Please re-download 5.5.5. from website and use SYSTEM account. Please get back to us with result.

---

Hendrik,

This version of 5.5.5 has worked fine as SYSTEM.

Thank you!

Thanks for the feedback. I don't know about the original reason but we changed a code signing certificate, from Thawte to GlobalSign. It seems like the signature validation takes longer with GlobalSign. The longer validation is described here:

http://support.microsoft.com/kb/936707 

We applied a fix to skip signature verification at startup which could cause this delay and timeout.

Since we could not reproduce this problem at our servers we are curious of your feedback regarding this. We don't know if this is a cache problem at your servers or you are missing the GlobalSign root certificate or if you have any other ideas about this. Any information would be great regarding this. Thank you.

---

I'm quite sure because of some sort of firewall preventing access to the .crl file

Try installing the 5.5.8 beta

http://www.visualcron.co....aspx?g=posts&t=1185 

---

That solved my problem with starting the service. Thanks.