With Version 4.10 RC2, it hangs too, but there's no 'Send Report To MS" Window ...
Here's the Inbuilt Log File created :
code:
Opening Log File : _Connect-ExecLog.Log
CONNECT THE LONG VERSION.KIX ! 2002/06/17 17:49:46
-------------------------------------------------------------------------------
Scanning For One Potential Device ...
Using Device U:
Opening File _Connect-ResourceNames.Kix
Adding : \\Server1\Site
Adding : \\Server2\Site
Adding : \\Server3\Site
Adding : \\Server4\Site
Closing File _Connect-ResourceNames.Kix
Resource Name(s) Added : 4
Rejected Line(s) : 5 (Did'nt Begin With '\\')
===============================================================================
Connecting To \\Server1\Site ...
Operator Is : SuperAdminWhoMakesScriptsHanging
U: Connected To \\Server1\Site
*********************************************
Calling Internal Procedure : JobToDo
Returning From Internal Proc. : JobToDo
*********************************************
DisConnecting From \\Server1\Site ...
U: Correctly DisConnected From \\Server1\Site
===============================================================================
Connecting To \\Server2\Site ...
Operator Is : SuperAdminWhoMakesScriptsHanging
U: Connected To \\Server2\Site
*********************************************
So it seems to have executed the "use" command for the second server and hangs when or just before executing internal Proc. "JobToDo".
Am I right when I guess you were suggesting me to do something else to track for misexecuted code ?
