Compiled scripts generate errors

petersa2 · Post by **petersa2** » Thu Mar 27, 2003 3:44 pm

I am using MS 7.1.18 to compile execs to run on win2k pc's. They are being called from batch files, run from startup, or called from the registry. Periodically, I will get an error on startup that the exec has generated errors and will be closed by windows. I then have to start the script manually, sometimes with multiple attempts, after which it runs fine. Is there any way to prevent this?

support · Post by **support** » Fri Mar 28, 2003 1:43 pm

Hi,

Please use the LogFile parameter to enable a log so that we can see where the error occurs.

armsys · Post by **armsys** » Sat Mar 29, 2003 2:11 am

Hi Petersa2,

Thanks for posting your technical issue here. Nonetheless, would you be very kind enough to offer us a fair chance to assist you by posting exactly the details of "error"? Look forward to hearing from you soon.

Happy scripting.

petersa2 · Post by **petersa2** » Mon Mar 31, 2003 10:40 pm

The exe errors out without running. If I use the /LogFile option, nothing is written. Dr Watson reports the error as "RtlTraceDatabaseEnumerate". I have emailed the DrWatson log to support.

rwstorer · Post by **rwstorer** » Tue Apr 22, 2003 8:13 pm

I have emailed the particulars to support. Since the particulars may include proprietary information I will not include them here. Sorry.

Ray

Guest · Post by **Guest** » Thu May 22, 2003 7:01 am

rwstorer wrote:I have emailed the particulars to support. Since the particulars may include proprietary information I will not include them here. Sorry.

Ray

Hy,

Is there any HELP for this Dr. Watson Problem or not???
I have the same Problem as you!!!

petersa2 · Post by **petersa2** » Thu May 22, 2003 8:31 pm

I am still having this problem, and have heard nothing from support.

Chaoticz · Post by **Chaoticz** » Wed Jun 11, 2003 4:08 pm

Is there any progress on this bug?

Here are some conditions under where this problem has surfaced:
1) Running multiple executables at the same time
2) Passing multiple parameters to the executables
3) Calling GetDate> , EditIniFile> or WriteLn>
4) Once it happens once it is more likely to happen again.
5) Windows 2000 Professional/SP3

------- Here is the information from event log ----------
Application popup: cprac.exe - Application Error : The instruction at "0x64afdfe8" referenced memory at "0x64afdfe8". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program
--------

Here is one of the script that crashes.

Let>TEMP_DIR=c:\hya\temp\
Let>SK_DELAY=200
Let>WW_TIMEOUT=10
Let>hya_ini=c:\hya\hya.ini
Let>running_ini=c:\hya\running.ini

gosub>date_format
Let>log_file=c:\hya\hya.%date_var%.txt

// Select Main Window
WaitWindowOpen>HYA -*
Wait>1
SetFocus>HYA -*
Wait>1

// Open Window
Press Alt
Wait>1
Send>tp
Wait>1
Release Alt
WaitWindowOpen>Change*
Wait>1

// Enter in text to select the appropriate practice.
Send>practice
Wait>1
Press Enter
Wait>1
GetDate>date_var
GetTime>time_var
WriteLn>log_file,result,%date_var% %time_var% - Changed Practice to %practice%

SRT>unknown_error
GetDate>date_var
GetTime>time_var
WriteLn>log_file,result,%date_var% %time_var% - Unknown Window Displayed...
PushButton>HYA,OK
Wait>3
MouseMove>828,568
Wait>2.41
LClick
goto>end_script
End>unknown_error

SRT>date_format
GetDate>date_var
MidStr>date_var,4,2,day_var
MidStr>date_var,1,2,month_var
MidStr>date_var,7,4,year_var
Let>date_var=%month_var%%day_var%%year_var%
End>date_format

EditIniFile>running_ini,CPRAC,running,no

Label>end_script