After SP1 Project Server services do not start

[David CB]

After applying the Project Server Servicepack 1 following the guideliness of
the "Deploy software updates for Office Project server 2007" from Microsoft,
the queue and event services do not start.
It is an architecture of three tiers (front end web server, application
server and database server) and the services are only installed on the
application server.
has anyone experienced something like this?

Thank you very much.

 

[strobel]

After applying the Project Server Servicepack 1 following the guideliness of
the "Deploy software updates for Office Project server 2007" from Microsoft,
the queue and event services do not start.

I experienced the same issue today.
In my farm, application server and web-frontend is on the same
machine. DB-Server is a seperate server.

The sharepoint and technology wizard tells something like "Cannot
start Eventing Service. Please start it manually". Same for the
Queuing service.
When I start the services (for instance eventing) manually, I find ONE
eventing-process in taskmanager (not Number of SSPs plus one; which
should be 2 in my installation) and it stopps after 30 seconds.

Thanks for any reply

 

[Bianca Roos]

I have the very same problem.

The Project Server, SQL Server and SharePoint are all installed in the same
server. I also noticed another problem with SSP admin website.

I didn't find any clue from sharepoint logs.

 

[Paul Conroy]

I can't explain why but I've come across this problem and giving the
queue/event service security account access to the Internet/setting IE proxy
on the application server resolved the problem !

Once the services were up and running I removed WWW access and the services
restarted as expected.

Weird I know, but it worked for me !

 

[Janson Shi]

I experienced the same issue yesterday. It Can't start Eventing Service
automaticly or manually. After some research, to my great surprised I found
the file name of 'c:\Program Files\Microsoft Office
Servers\12.0\Bin\Microsoft.Office.Project.Server.Eventing.exe' had been
changed to 'Microsoft.Office.Project.Server.Eâ–¡â–¡nting.exe' . I renamed the
file name back and the Eventing Service start successfully.

 

[David CB]

Thank you very much Paul!

At the beginning your answer seems to me really weird. But using a sniffer I
checked that the Queue service was trying to contact crl.microsoft.com, that
is, the certificates revocation list from Microsoft. What the service really
wants is the file
http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl
So, if you cannot give the security account access to the Internet (as it is
my case), you can publish this file in any accesible web site of the intranet
with the same name and forward the request of the service to this site.
After the queue service starts for the first time, it no longer connect to
the crl site, so it can be deleted.

Finally I have a big answer: where is that piece of info in the documentation?

 

[Bianca Roos]

Thank's a lot!
--
Bianca Roos

I can't explain why but I've come across this problem and giving the
queue/event service security account access to the Internet/setting IE proxy
on the application server resolved the problem !

Once the services were up and running I removed WWW access and the services
restarted as expected.

Weird I know, but it worked for me !

 

[Stewart Fischer]

Hi David,

I am in a similar position and it sounds like your answer will work but how
do forward the request somewhere else - are the queue jobs ccessible
somewhere?

Thanks,

Stewart.