I'm using Mercury 4.01b on a dial-up connection and schedule the connection via MercuryX Task Scheduler. This is running on a Windows XP platform.
My problem is that MercuryX Task Scheduler will not recognise the end of a command's execution.
The command run 'before starting' and 'after stopping' is 'rasdial' with appropriate switches. The checkbox "Wait until this process terminates before starting Mercury service processes" is checked.
Everything worked well until, for no apparent reason, the scheduler would make the connection via rasdial but would stay suspended 'waiting for the process to terminate'. Rasdial would terminate after the successful connection, but this was not recognised by the Task Scheduler and as a result, Mercury never transacts any mail and the connection is never cleared down.
To get around the problem, a batch file was created and used as the command to run 'before starting'. The batch file contained the rasdial command to establishing the dial-up connection. Everything worked again - Mercury would see the batch file terminate and it would then transact the mail. At the end of the run the 'rasdial /disconnect' command cleared the dial-up connection.
Now again, for no apparent reason, Mercury will not recognise the end of the batch file and so will not transact any mail which in turn leaves the line permanently connected. Reverting back to the original configuration does not help. In fact configuring Mercury to start "Notepad.exe" results in notepad starting but when terminated, Mercury fails to recognise the termination and so waits indefinitely. Bottom line is Mercury will not see the end of the command execution, irrespective of which command is used.
Can anyone shed any light on the matter - currently I'm working around the problem again by de-selecting "Wait until this process terminates before starting Mercury service processes" and using a 30 second delay before and after executing commands, but this is a poor solution.
Looking forward to some assistance . . Mervyn.
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">I'm using Mercury 4.01b on a dial-up connection and schedule the connection via MercuryX Task Scheduler.&nbsp; This is running on a Windows XP platform.</SPAN></FONT> </DIV>
<DIV align=left>&nbsp;</DIV>
<DIV align=left>My problem is that MercuryX Task Scheduler&nbsp;will not recognise&nbsp;the end of a command's execution.</DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">
</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">The command run 'before starting' and 'after stopping' is 'rasdial' with appropriate switches.&nbsp; The checkbox "Wait until this process terminates before starting Mercury service processes" is checked.</SPAN></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">
</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">Everything worked well until, for no apparent reason, the scheduler would make the connection via rasdial but would stay suspended 'waiting for the process to terminate'.&nbsp; Rasdial would terminate after the successful connection, but this was not recognised by the Task Scheduler and as a result, Mercury never transacts any mail and the connection is never cleared down.</SPAN></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">
</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">To get around the problem, a batch file was created and used as the command to run 'before starting'.&nbsp; The batch file contained the rasdial command to establishing the dial-up connection.&nbsp; Everything worked again - Mercury would see the batch file terminate and it would then transact the mail. At the end of the run the 'rasdial /disconnect' command cleared the dial-up connection.</SPAN></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">
</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">Now again, for no apparent reason, Mercury will not recognise the end of the batch file and so will not transact any mail which in turn leaves the line permanently connected.&nbsp; Reverting back to the original configuration does not help.&nbsp; In fact configuring Mercury to start "Notepad.exe" results in notepad starting but when terminated, Mercury fails to recognise the termination and so waits indefinitely.&nbsp; Bottom line is Mercury will not see the end of the command execution, irrespective of which command is used.</SPAN></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">
</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">Can anyone shed any light on the matter - currently I'm working around the problem again by de-selecting "Wait until this process terminates before starting Mercury service processes" and using a 30 second delay before and after executing commands, but this is a poor solution.</SPAN></FONT> </DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">
</SPAN></FONT></DIV>
<DIV align=left><FONT face=Arial size=2><SPAN style="FONT-SIZE: 10pt">Looking forward to some assistance . . Mervyn.</SPAN></FONT></DIV>