Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Event Registration failure Exch2003

Status
Not open for further replies.

Paula1980

Technical User
Oct 1, 2003
14
US

Did any of you know how to fix this issue?

Error Commiting Transaction : -2141913011 Event Registration failure: The specified event sink (ProgID: %1) is not allowed to run in-proc.

Thanks Paula
 
That just looks like an HResult code, a failure facility 0x5 code 0x4d. What process did ProgID: %1 match up to? What was happening when this error was thrown? Anything that would give a clue in the application log?

Generally, an event sink failed to register. It's likely a transport event sink. In IIS, it can run in porocess or out of process, but requires specific permissions to do so. Beyond that, there's not enough information in your post to determine what the problem was.



 
This is eveything I have:
removed MyArrivalSink {C65A87A1-17EC-43E7-932B-B03DE456148E}
New Event Binding created:
Event: onsyncsave
Sink: HCLEvents.HCLEv.1
FullBindingUrl: file://./backofficestorage/ADMIN/BIG6.COM/MBX/SystemMailbox{790C98E6-DE58-4559-B6C1-79AED5E327EC}/StoreEvents/GlobalEvents/my_event

Error Commiting Transaction : -2141913011 Event Registration failure: The specified event sink (ProgID: %1) is not allowed to run in-proc.

assigning priority (28010 of 32767)
registered MyArrivalSink
 
That's a store event sink. There used to be a problem in Exchange 2000 where onsyncsave would fail with access denied if the sender and receiver were on the same store. Does that sound like your scenario?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top