Error in Agent Log: Script not running

[KarenS]

Hi,<br><br>I have a problem with an agent running on a public folder in Exchange 5.5. The error message I recieve is &quot;Could not find a connection point for the event that has been triggered.&quot; It is shown in the event log as Event ID 20 being reported by MSExchangeES. I have tried stopping and restarting the event service to no effect. The script ran ok before - I moved a lot of messages into the folder (the script is set up to run each time a new item is added) and I believe it may have run out of resources at that time - but moving a single message does not seem to help it.<br><br>I cannot find anything on Technet or the Microsift site in the Event Id or the error. In fact any good refernce material on the Event Service in Exchange would be very useful.<br><br>Thanks

 

[algin]

Hey there, I have the same problem, and was wondering if you've ever found a solution for that problem?

Thanks!

Al

 

[KarenS]

I have had it a few times and I recreated the agent and then it started working - strange. I think the first time I had to actually delete the folder (wait for replication) and then recreate the folder and the agent. I have had it since on a test server which does not replicate so maybe you need to just remove the agent and wait for that to replicate before adding it back.

I never found any doco on it though. Good Luck.

 

[algin]

Hi Karen: Last night I found a reference to the error at

http://www.cdolive.com.

&quot;One of the used Scripting Agent script events is misspelled in your Microsoft Exchange Server Scripting and Routing script.&quot;

Also, in the application log on the Exchange server, I found random entries of:

&quot;Script Failed with a run time or syntax error on the last event. Since the Script was not modfied since the last failure, the script will not be run again until the error is fixed. Please refer to agent log for more information about the failure.&quot;

The only thing I cannot figure out is how there could be a syntax error that spontaneously occurs to a working script/agent?

But, thanks! Let me try deleting the folders/agents and see if it works.

Al