Unable to start service process. SSP ProjectQueueService and pjevt

D

David Kitchen

Here's the log file output:

<code>
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdb Medium [SERVICE] pjevtsvc: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdk Medium [SERVICE] pjevtsvc: ProcessWatcher restarting service for
f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdn Medium [SERVICE] pjevtsvc: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
90dq Medium [SERVICE] pjevtsvc: WindowsIdentity: DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zcy Medium [SERVICE] pjevtsvc: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd1 Medium [SERVICE] ProjectQueueService: Unable to start ExecProcess for
SSP: f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: ProjectQueueService
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdb Medium [SERVICE] ProjectQueueService: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdk Medium [SERVICE] ProjectQueueService: ProcessWatcher restarting
service for f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdn Medium [SERVICE] ProjectQueueService: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
90dq Medium [SERVICE] ProjectQueueService: WindowsIdentity:
DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zcy Medium [SERVICE] ProjectQueueService: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd1 Medium [SERVICE] pjevtsvc: Unable to start ExecProcess for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: pjevtsvc
</code>

We've tried adding the service account to the local admins, granting log on
locally and using stsadm to update the farm with the service account.

We have located another post on the net that hinted that if the servers are
not attached to the internet that these can fail if the server is unable to
automatically download a certificate update from Microsoft. These servers are
not and cannot be connected to the internet, we are also sceptical of this
proposed solution as it's only mentioned once and not much information is
given.

The above errors appear every 2 minutes after any attempt to provision a
Project workspace is made.

Thanks in advance for thoughts on this.
 
D

David Kitchen

I'll answer my own question :)

Problem:

The Queue and Event services not starting and error messages similar to
these in the WSS log files:

03/11/2008 09:18:44.16
Microsoft.Office.Project.Server (0x0684)
0x07F0 Project Server
Project Server – General
7882
Critical
Unable to start service process. SSP: f753cc72-eb71-4896-8050-d07929546afd
Service: ProjectQueueService

03/11/2008 09:18:44.16
Microsoft.Office.Project.Server (0x0640)
0x07EC Project Server
Project Server – General
7882
Critical
Unable to start service process. SSP: f753cc72-eb71-4896-8050-d07929546afd
Service: pjevtsvc

Note that the GUID’s above are random and will not tally to anything you may
witness.

Description:

The server does not have internet access or the service account used (to
perform the install or run the service) does not have internet access.

The machine needs internet access as the .Net packages that are trying to be
loaded by the service are cryptographically signed with Microsoft
Certificates.

The first time that the .Net packages are loaded .Net wants to verify that
it can trust that the code comes from Microsoft by verifying the certificate
that it was signed with. The certificate does contain that information, but a
second phase of verifying a certificate is to check that the certificate has
not been revoked.

To verify that the certificate used to sign the .Net package hasn’t been
revoked, .Net will attempt to download the Certificate Revocation Lists from
both of these URL’s:
http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl
http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl

If the .Net application cannot reach those end destinations then the .Net
package assumes that an attempt to block verification has occurred and that
the .Net packages signed by the certificates are not to be trusted.

End result, the .Net packages that are the Queue service and the Events
service will not be loaded fully even though the Services.msc snap-in will
report that they are running.

Resolution (preferred):

Allow the server and the services accounts to access the crl.microsoft.com
domain.

Resolution 2:

Turn off CRL checking by creating a turnoffCRL.reg file with this as the
content:

Windows Registry Editor Version 5.00
[HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
"State"=dword:00023e00

Merge that into the registry.

Note that this would be considered to be comprising the integrity of the
..Net signed packages stuff as we would have prevented any compromised
certificates from being disabled automatically.

Resolution 3:

Manually add the CRLs from the above Urls to the server manually (assumes
you’ve downloaded them locally first):
certutil -addstore CA CodeSignPCA.crl
certutil -addstore CA CodeSignPCA2.crl

Resolution Workaround (don’t try this unless you’ve exhausted everything
else):

We haven’t tried this yet, but it is our hunch that if you cannot allow the
server access to the internet that it may be possible to fool .Net into using
locally hosted .crl files. This could only work if the restrictions that
prevent the service account and server reaching the internet still permit a
loop-back request to itself (calling web pages from the local server).

The way to do this is to add this to your HOSTS file on the servers:
127.0.0.1 crl.microsoft.com

And then to place the CRL files (downloaded from the Microsoft website using
the Urls above) into a folder that matches the web location of:
/pki/crl/products/

This might work (providing there are no other files that we don’t yet know
about needing to be downloaded) as Microsoft have failed to perform this
request over SSL and so no proof that we are the end website is required.

Note that this would be considered to be comprising the integrity of the
..Net signed packages stuff as we would have prevented any compromised
certificates from being disabled automatically. Though if you fetch the
latest .crl files manually then you would merely be delaying this effect.

References:

http://www.microsoft.com/communitie...&mid=d059d7c7-1624-4c86-903f-26d249caa784&p=1

http://www.ureader.com/msg/11199009.aspx

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125768

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

http://blogs.msdn.com/chaitanya_med...low-after-an-iisreset-or-apppool-restart.aspx

http://sharepointtips.blogspot.com/2008/01/il-queue-services-e-levent-services-di.html

http://ebilal.spaces.live.com/blog/cns!1EB5037F50572440!825.entry

David Kitchen said:
Here's the log file output:

<code>
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdb Medium [SERVICE] pjevtsvc: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdk Medium [SERVICE] pjevtsvc: ProcessWatcher restarting service for
f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdn Medium [SERVICE] pjevtsvc: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
90dq Medium [SERVICE] pjevtsvc: WindowsIdentity: DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zcy Medium [SERVICE] pjevtsvc: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd1 Medium [SERVICE] ProjectQueueService: Unable to start ExecProcess for
SSP: f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: ProjectQueueService
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdb Medium [SERVICE] ProjectQueueService: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdk Medium [SERVICE] ProjectQueueService: ProcessWatcher restarting
service for f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdn Medium [SERVICE] ProjectQueueService: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
90dq Medium [SERVICE] ProjectQueueService: WindowsIdentity:
DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zcy Medium [SERVICE] ProjectQueueService: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd1 Medium [SERVICE] pjevtsvc: Unable to start ExecProcess for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: pjevtsvc
</code>

We've tried adding the service account to the local admins, granting log on
locally and using stsadm to update the farm with the service account.

We have located another post on the net that hinted that if the servers are
not attached to the internet that these can fail if the server is unable to
automatically download a certificate update from Microsoft. These servers are
not and cannot be connected to the internet, we are also sceptical of this
proposed solution as it's only mentioned once and not much information is
given.

The above errors appear every 2 minutes after any attempt to provision a
Project workspace is made.

Thanks in advance for thoughts on this.
Click to expand...
 
D

David Kitchen

And it didn't even turn out to be that.

It turned out to be permissions.

The SSP user wasn't able to connect to SQL, when we replaced the SSP user
with the ServerFarm user it all worked fine.

So now we're hunting for what is the problem with the SSP user and whether a
group policy is affecting that user in any way.

Permissions though... if all else fails try the ServerFarm admin user as the
SSP user just to prove whether or not it comes down to permissions. At least
that will give you a direction to follow.

David Kitchen said:
I'll answer my own question :)

Problem:

The Queue and Event services not starting and error messages similar to
these in the WSS log files:

03/11/2008 09:18:44.16
Microsoft.Office.Project.Server (0x0684)
0x07F0 Project Server
Project Server – General
7882
Critical
Unable to start service process. SSP: f753cc72-eb71-4896-8050-d07929546afd
Service: ProjectQueueService

03/11/2008 09:18:44.16
Microsoft.Office.Project.Server (0x0640)
0x07EC Project Server
Project Server – General
7882
Critical
Unable to start service process. SSP: f753cc72-eb71-4896-8050-d07929546afd
Service: pjevtsvc

Note that the GUID’s above are random and will not tally to anything you may
witness.

Description:

The server does not have internet access or the service account used (to
perform the install or run the service) does not have internet access.

The machine needs internet access as the .Net packages that are trying to be
loaded by the service are cryptographically signed with Microsoft
Certificates.

The first time that the .Net packages are loaded .Net wants to verify that
it can trust that the code comes from Microsoft by verifying the certificate
that it was signed with. The certificate does contain that information, but a
second phase of verifying a certificate is to check that the certificate has
not been revoked.

To verify that the certificate used to sign the .Net package hasn’t been
revoked, .Net will attempt to download the Certificate Revocation Lists from
both of these URL’s:
http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl
http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl

If the .Net application cannot reach those end destinations then the .Net
package assumes that an attempt to block verification has occurred and that
the .Net packages signed by the certificates are not to be trusted.

End result, the .Net packages that are the Queue service and the Events
service will not be loaded fully even though the Services.msc snap-in will
report that they are running.

Resolution (preferred):

Allow the server and the services accounts to access the crl.microsoft.com
domain.

Resolution 2:

Turn off CRL checking by creating a turnoffCRL.reg file with this as the
content:

Windows Registry Editor Version 5.00
[HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
"State"=dword:00023e00

Merge that into the registry.

Note that this would be considered to be comprising the integrity of the
.Net signed packages stuff as we would have prevented any compromised
certificates from being disabled automatically.

Resolution 3:

Manually add the CRLs from the above Urls to the server manually (assumes
you’ve downloaded them locally first):
certutil -addstore CA CodeSignPCA.crl
certutil -addstore CA CodeSignPCA2.crl

Resolution Workaround (don’t try this unless you’ve exhausted everything
else):

We haven’t tried this yet, but it is our hunch that if you cannot allow the
server access to the internet that it may be possible to fool .Net into using
locally hosted .crl files. This could only work if the restrictions that
prevent the service account and server reaching the internet still permit a
loop-back request to itself (calling web pages from the local server).

The way to do this is to add this to your HOSTS file on the servers:
127.0.0.1 crl.microsoft.com

And then to place the CRL files (downloaded from the Microsoft website using
the Urls above) into a folder that matches the web location of:
/pki/crl/products/

This might work (providing there are no other files that we don’t yet know
about needing to be downloaded) as Microsoft have failed to perform this
request over SSL and so no proof that we are the end website is required.

Note that this would be considered to be comprising the integrity of the
.Net signed packages stuff as we would have prevented any compromised
certificates from being disabled automatically. Though if you fetch the
latest .crl files manually then you would merely be delaying this effect.

References:

http://www.microsoft.com/communitie...&mid=d059d7c7-1624-4c86-903f-26d249caa784&p=1

http://www.ureader.com/msg/11199009.aspx

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125768

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

http://blogs.msdn.com/chaitanya_med...low-after-an-iisreset-or-apppool-restart.aspx

http://sharepointtips.blogspot.com/2008/01/il-queue-services-e-levent-services-di.html

http://ebilal.spaces.live.com/blog/cns!1EB5037F50572440!825.entry

David Kitchen said:
Here's the log file output:

<code>
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdb Medium [SERVICE] pjevtsvc: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdk Medium [SERVICE] pjevtsvc: ProcessWatcher restarting service for
f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdn Medium [SERVICE] pjevtsvc: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
90dq Medium [SERVICE] pjevtsvc: WindowsIdentity: DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zcy Medium [SERVICE] pjevtsvc: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd1 Medium [SERVICE] ProjectQueueService: Unable to start ExecProcess for
SSP: f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: ProjectQueueService
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdb Medium [SERVICE] ProjectQueueService: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdk Medium [SERVICE] ProjectQueueService: ProcessWatcher restarting
service for f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdn Medium [SERVICE] ProjectQueueService: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
90dq Medium [SERVICE] ProjectQueueService: WindowsIdentity:
DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zcy Medium [SERVICE] ProjectQueueService: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd1 Medium [SERVICE] pjevtsvc: Unable to start ExecProcess for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: pjevtsvc
</code>

We've tried adding the service account to the local admins, granting log on
locally and using stsadm to update the farm with the service account.

We have located another post on the net that hinted that if the servers are
not attached to the internet that these can fail if the server is unable to
automatically download a certificate update from Microsoft. These servers are
not and cannot be connected to the internet, we are also sceptical of this
proposed solution as it's only mentioned once and not much information is
given.

The above errors appear every 2 minutes after any attempt to provision a
Project workspace is made.

Thanks in advance for thoughts on this.
Click to expand...
Click to expand...
 
S

Scanners

Hi David

Just read your article as I have been trying to build Project Server 2007 on
Windows 2008 but have ran into the same problems namily how do you get the
Project Events and Queue services to run.

I get the services started but they come up with errors in the event log.

Due to the nature of the system I am working on connection to the internet
is not an option. I have tryed all the suggestions you list but with no Joy.

There has got to be a way of installing Project without connecting to the
Internet.

Any other idea's

Scanners

David Kitchen said:
I'll answer my own question :)

Problem:

The Queue and Event services not starting and error messages similar to
these in the WSS log files:

03/11/2008 09:18:44.16
Microsoft.Office.Project.Server (0x0684)
0x07F0 Project Server
Project Server – General
7882
Critical
Unable to start service process. SSP: f753cc72-eb71-4896-8050-d07929546afd
Service: ProjectQueueService

03/11/2008 09:18:44.16
Microsoft.Office.Project.Server (0x0640)
0x07EC Project Server
Project Server – General
7882
Critical
Unable to start service process. SSP: f753cc72-eb71-4896-8050-d07929546afd
Service: pjevtsvc

Note that the GUID’s above are random and will not tally to anything you may
witness.

Description:

The server does not have internet access or the service account used (to
perform the install or run the service) does not have internet access.

The machine needs internet access as the .Net packages that are trying to be
loaded by the service are cryptographically signed with Microsoft
Certificates.

The first time that the .Net packages are loaded .Net wants to verify that
it can trust that the code comes from Microsoft by verifying the certificate
that it was signed with. The certificate does contain that information, but a
second phase of verifying a certificate is to check that the certificate has
not been revoked.

To verify that the certificate used to sign the .Net package hasn’t been
revoked, .Net will attempt to download the Certificate Revocation Lists from
both of these URL’s:
http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl
http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl

If the .Net application cannot reach those end destinations then the .Net
package assumes that an attempt to block verification has occurred and that
the .Net packages signed by the certificates are not to be trusted.

End result, the .Net packages that are the Queue service and the Events
service will not be loaded fully even though the Services.msc snap-in will
report that they are running.

Resolution (preferred):

Allow the server and the services accounts to access the crl.microsoft.com
domain.

Resolution 2:

Turn off CRL checking by creating a turnoffCRL.reg file with this as the
content:

Windows Registry Editor Version 5.00
[HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing
"State"=dword:00023e00

Merge that into the registry.

Note that this would be considered to be comprising the integrity of the
.Net signed packages stuff as we would have prevented any compromised
certificates from being disabled automatically.

Resolution 3:

Manually add the CRLs from the above Urls to the server manually (assumes
you’ve downloaded them locally first):
certutil -addstore CA CodeSignPCA.crl
certutil -addstore CA CodeSignPCA2.crl

Resolution Workaround (don’t try this unless you’ve exhausted everything
else):

We haven’t tried this yet, but it is our hunch that if you cannot allow the
server access to the internet that it may be possible to fool .Net into using
locally hosted .crl files. This could only work if the restrictions that
prevent the service account and server reaching the internet still permit a
loop-back request to itself (calling web pages from the local server).

The way to do this is to add this to your HOSTS file on the servers:
127.0.0.1 crl.microsoft.com

And then to place the CRL files (downloaded from the Microsoft website using
the Urls above) into a folder that matches the web location of:
/pki/crl/products/

This might work (providing there are no other files that we don’t yet know
about needing to be downloaded) as Microsoft have failed to perform this
request over SSL and so no proof that we are the end website is required.

Note that this would be considered to be comprising the integrity of the
.Net signed packages stuff as we would have prevented any compromised
certificates from being disabled automatically. Though if you fetch the
latest .crl files manually then you would merely be delaying this effect.

References:

http://www.microsoft.com/communitie...&mid=d059d7c7-1624-4c86-903f-26d249caa784&p=1

http://www.ureader.com/msg/11199009.aspx

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125768

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

http://blogs.msdn.com/chaitanya_med...low-after-an-iisreset-or-apppool-restart.aspx

http://sharepointtips.blogspot.com/2008/01/il-queue-services-e-levent-services-di.html

http://ebilal.spaces.live.com/blog/cns!1EB5037F50572440!825.entry

David Kitchen said:
Here's the log file output:

<code>
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdb Medium [SERVICE] pjevtsvc: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdk Medium [SERVICE] pjevtsvc: ProcessWatcher restarting service for
f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zdn Medium [SERVICE] pjevtsvc: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
90dq Medium [SERVICE] pjevtsvc: WindowsIdentity: DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zcy Medium [SERVICE] pjevtsvc: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd1 Medium [SERVICE] ProjectQueueService: Unable to start ExecProcess for
SSP: f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: ProjectQueueService
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdb Medium [SERVICE] ProjectQueueService: ProcessWatcher signaled
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdk Medium [SERVICE] ProjectQueueService: ProcessWatcher restarting
service for f753cc72-eb71-4896-8050-d07929546afd PID: -1
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zdn Medium [SERVICE] ProjectQueueService: Getting list of Sites for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
90dq Medium [SERVICE] ProjectQueueService: WindowsIdentity:
DBG\svca_epm_serverfarm
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0684) 0x07F0 Project Server Project Server - General
8zcy Medium [SERVICE] ProjectQueueService: SSPGuid:
f753cc72-eb71-4896-8050-d07929546afd SSPIdentity: DBG\svca_epm_ssp
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd1 Medium [SERVICE] pjevtsvc: Unable to start ExecProcess for SSP:
f753cc72-eb71-4896-8050-d07929546afd
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
8zd2 Medium [SERVICE] The service cannot be started, either because it is
disabled or because it has no enabled devices associated with it
03/11/2008 09:18:44.16 Microsoft.Office.Project.Server
(0x0640) 0x07EC Project Server Project Server - General
7882 Critical Unable to start service process. SSP:
f753cc72-eb71-4896-8050-d07929546afd Service: pjevtsvc
</code>

We've tried adding the service account to the local admins, granting log on
locally and using stsadm to update the farm with the service account.

We have located another post on the net that hinted that if the servers are
not attached to the internet that these can fail if the server is unable to
automatically download a certificate update from Microsoft. These servers are
not and cannot be connected to the internet, we are also sceptical of this
proposed solution as it's only mentioned once and not much information is
given.

The above errors appear every 2 minutes after any attempt to provision a
Project workspace is made.

Thanks in advance for thoughts on this.
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MOSS/PROJECT - Project Queue Service 1
Unable to start service process 2
Project Queue and Event Services cannot be started 1
Unable to start server process - ProjectQueueService / pjevtsvc 5
Problem with two project's service 2
Project Server 2007 Service Error - pjevtsvc and ProjectQueueServi 14
MSP 2007 Unable to publish on server 1
Error 7882 after reset Project Server Queue and Events Services 0

Top