Discussion:
Service Broker External Activator
(too old to reply)
simon
2011-10-27 09:31:22 UTC
Permalink
I installed Service Broker External Activator service from this
location:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8824

X64 Package (SSBEAS.msi) - 2620 KB

Instalation was successfully.

When I try to start the service I get the following error message:
"Windows could not start the Service Broker External Activator service
on Local Computer.
Error 1067: The process terminated unexpectedly."

Any idea what it could be?
I have windows7 64bit OS.

Thanks,
Simon
simon
2011-10-27 15:08:32 UTC
Permalink
I found out the problem. It was in EAService.config file.
It works now.

I have 2 questions here:

1. How can I put some value from message in NotificationQueue into
CmdLineArgs of external activator? In fact I would like to know which
message triggered event notification to external activator?.

2. Why message remains in TargetQueue after notification service take
the message from targetQueue and put it into notificationQueue?

Thank you,

br,
Simon
r***@gmail.com
2015-08-25 13:05:05 UTC
Permalink
Can you please share how you resolve this issues please.

thanks
Sesha.

Jeroen Mostert
2011-10-27 17:59:26 UTC
Permalink
Post by simon
I installed Service Broker External Activator service from this
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8824
X64 Package (SSBEAS.msi) - 2620 KB
Instalation was successfully.
"Windows could not start the Service Broker External Activator service
on Local Computer.
Error 1067: The process terminated unexpectedly."
Look in the event log.
--
J.
Jeroen Mostert
2011-10-27 18:00:59 UTC
Permalink
Post by Jeroen Mostert
Post by simon
I installed Service Broker External Activator service from this
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8824
X64 Package (SSBEAS.msi) - 2620 KB
Instalation was successfully.
"Windows could not start the Service Broker External Activator service
on Local Computer.
Error 1067: The process terminated unexpectedly."
Look in the event log.
Ahh, never mind, I saw your other post. Over-eagerness prompted by an overly
insufficient problem statement.
--
J.
Loading...