|
My ItemAdded event recevier is not firing when the Word Automation Services adds a file to a Sharepoint document library. If I manually debug the ItemAdded event receiver, it is getting triggered. I don't know why it is not getting triggered when the file is added from Word Automation Services. Please help. |
||||
|
|
|
I am not sure about this, but I know that there have been problems with starting workflows automatically, if a file is added by the "system account". See this article: http://blogs.technet.com/b/victorbutuza/archive/2009/03/14/workflows-do-not-start.aspx As a said, I don't know if it is the same with event handlers -but I could be the reason. |
|||
|
|
|
i ran into the same problem, wondering why my breakpoint was not hit. Then i realized that the event handler is not running under the default W3WP process. So attaching your debugger to the right worker process (or all ) will give you (again) all debugging facilities. |
|||
|
|
|
Maybe you should handle ItemFileConverted event? |
|||
|
|
|
Is it possible that the Word Automation Service runs under the wrong application pool and has no permission? |
|||
|
|
I have been having this problem 3 days and finally found reason why and the solution. The reason the debugging was not working was that the debugger should attached to the app pool that the Word automation service is running. Usually it's named with GUID and you will see the an app pool has many app run under. After I attach my debugger to that app pool my break point is reached. I hope it helps somebody... |
|||
|
