Dr. Watson Error 1

[IRABYY]

Hi, fellows!

I've got a question for ya:

Have anybody seen the following error messages appearing on the exit from the program written in VFP 7.0 running on WinNT 5.0/2000 machines:

Msg. Box #1, tilte &quot;Program Error&quot;: &quot;<process has already exited> has generated errors and will be closed by Windows. You will need to restart the program.

An error log is being generated.&quot;

Msg. Box #2, title &quot;DrWatson Fatal Error&quot;: &quot;Dr. Watson was unable to attach to the process. It is possible that process exited before Dr. Watson could attach to it.

Windows 2000 returned error code=87
The parameter is incorrect.&quot;

This happened on the machines (WS, not FS) running under Windows 2000 ver. 5.00.2195, one machine has SP2 and another SP3 installed, both WinNT 5 Professional.

From what I read about Dr. Watson follows that this &quot;spy&quot; program is some debugging tool that's supposed to trap an error and create a log file with .WLG extension. Instead, it generates an error itself!

I cannot say that my program is perfect, but it ain't generating any errors on Win9x or WinNT 4.0 machines, only on WinNT 5/2000.

The worst thing - it's intermittent on one of the machines (the one with SP3), though persistent on another (with SP2).

Any ideas why it may happen?

BTW: The KB article Q175875 and others on Dr. Watson topic in MSDN give the description for this behavior on WinNT 4.0/5.0 server, but not on workstation.

Regards,

Ilya

 

[Mike Gagnon]

IRABYY

This link might help:

http://www.computerhope.com/software/drwatson.htm

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[IRABYY]

mgagnon (Programmer): This link might help:

http://www.computerhope.com/software/drwatson.htm

Mike Gagnon

Mike,

yes, I know I can disable Dr. Watson by cleaning out its key from the Windows registry (even programmatically). But then again - two issues would spring up for sure: 1) User Rights (it's Windows Registry, after all), 2) machine would be left without diagnostic tool - and you know how customers' System Administrators would react in both cases.

Under tcp/ip protocol, try to set the fixed unique ip address for both 2000 server and workstation.

e.g. 192.168.100.1
192.168.100.2

Regards

See

See:

Thank you for trying to help me.

Unfortunately, my program goes out to customers having wide variety of environments, from Thin Client to stand-alone-PC, from Novel 3.11 to WinNT 5 FS SPx. I have no idea where my program would end up (until &quot;Your freakin' program does not work&quot; call from customer ). How can I possibly know their TCP/IP addresses on customer's network - even if this is the case?

Worse yet, the SP3 machine mentioned in my original post is a laptop, and it was not connected to neither network, LAN or WAN (internet) when this error occured.

Nevertheless, I would appreciate if you tell me what have caused you to think about the TCP/IP protocol in connection with Dr. Watson in reference to the beforementioned errors.

Thanks!

Regards,

Ilya

 

[IRABYY]

Another development in the subject matter:
Dr. Watson error springs up when exiting the program after running a query (SQL SELECT) resulting in big cursor file.
Any ideas?

Regards,

Ilya

 

[monikai]

Hi !
May be you use another data (not VFP) via ODBC ? Kind regards from Warsaw !!!!!
Monika (monikai@yahoo.com)

 

[IRABYY]

monikai (Programmer): May be you use another data (not VFP) via ODBC?

No, my lady, it MUST be XBase table format, period.

Djenkuye bardzo anyway.

Regards,

Ilya

 

[monikai]

Hi, my dear Slav friend !
Some years ago i had similiar error (not VFP - VB3 and database INGRES), but solution was new version ODBC. And we had some problems in installation new version. We had to form system hard disk and install Win.
If you send me your e-mail - i'll send you Christmas greetings ! Kind regards from Warsaw !!!!!
Monika (monikai@yahoo.com)

 

[DSummZZZ]

Maybe verify your pathing and rights. Does the app have erase rights in the designated TEMP directory?
You should also make sure the workstations have the latest service packs. That is definitely an issue.
Dave S.

 

[IRABYY]

DSummZZZ (Programmer): Maybe verify your pathing and rights. Does the app have erase rights in the designated TEMP directory?

Dave,
you may be right: all these Dr. Watson errors happened - so far - on the machines where TEMP and TMP env. vars. were assigned to point on the &quot;Documents and Settings&quot; folder. And we know that FoxPro does not like spaces in the path. We are checking your suggestion, thank you!

Regards,

Ilya

 

[IRABYY]

DSummZZZ (Programmer): Maybe verify your pathing and rights. Does the app have erase rights in the designated TEMP directory?

Ilya: Dave,
you may be right: all these Dr. Watson errors happened - so far - on the machines where TEMP and TMP env. vars. were assigned to point on the &quot;Documents and Settings&quot; folder. And we know that FoxPro does not like spaces in the path. We are checking your suggestion, thank you!


Dave, you are the man!

After the dude changed his settings for TEMP and TMP Environment Variables from C:\Documents and Settings\Blah-Blah-Blah... to C:\WinNT\Temp directory this Dr. Watson error ceased to appear!

Thank you for the tip, bro! I marked your post with the Star (of Appreciation ())

Regards,

Ilya

 

[DSummZZZ]

Thanks, glad you got it working!
Dave S.