Project Event Reciever - events not firing

[Roy G]

Hi all,
We have a problem. The event handler we have developed is working fine on a
single server but on another archtecture (3 different machines each holding
different parts of the Project Server to improve performance) the event is
not caught. We have installed our product on the machine holding the Project
Events Service.
If anyone has ever encountered such a problem they are more than invited to
share their thoughts here.
Regards,
Roy G

 

[Brian Smith \(MSFT\)]

Hi Roy,

Also posted this in response to your comment on my blog - but sharing with
the wider audience.

I haven't seen this issue. Are there any clues in the logs? (App or ULS).
It must be completely missing it as if the code fails then the specific
process firing the event will normally fail too. I saw your newsgroup
posting and if I had a better answer I would have posted it there. If this
isn't a production server you could try debugging and attach to the event
service process - but this will probably just confirm that the code isn't
getting triggered. You probably have already but check that it registered OK
and is showing up in the UI. ProjTool (from the SDK) also has a way to view
registered event handlers.

Best regards,

Brian.

 

[Roy G]

Hi Brian,
I hope this helps someone else with similar problems. The issue was solved
by restarting the machine (The "Bill Gates Solution" ).
Nevertheless the project events service was sure to be running prior to the
restart so I guess I'll never know the real reason...

Kind regards,
Roy G

 

[Brian Smith \(MSFT\)]

Interesting. When the services initially start you will see one of each
(Events and Queue) and then another of each will start for each Shared
Services Provider that has provisioned PWA sites. So normally you should
see two of each running if you open task manager. If for some reason they
cannot contact the SSP (SQL has not started yet - or is not yet accepting
requests) then you may see just one started. This can then fool you into
thinking the service is running (it will say started in the Services applet)
but actually no queue jobs will get processed or events raised. Either
restarting the service, or in some cases restarting the server will get
things moving. One suggestion I have seen is to make a dependency between
SQL Server and the Project services so that they will not try and start
before SQL is up and running.

I have seen this behavior more on low spec machines - or in virtual
environments.