Tortured by Dr. Watson.

I m running java servlets here on Windows NT workstation with service pack 6. Now I m encountering an error of Dr. Watson everytime i run the servlets which has the Database-Interaction code. The error states that it was caused due to java.exe application. For ur information, I m using jdk1.2.2 & jsdk2.1 for the development. I also tried installing Tomcat 3.3 instead of jsdk2.1, but no good. I tried to search about this. All i can find was that this error can be eliminated by using type 4 drivers. I downloaded some type 3 drivers. But well was unsuccessful in making them to run, 'coz at some or other point they also showed their affinity towards Dr. Watson. So can u plz guide me as to what should i do ? I tried to search for those type IV drivers for Access 97, but cant find it ....

You have an environment problem and is probably not directly related to the database access.
First you might try uninstalling and re-installing java.
Second you might want to search the jdbc forum where it suggests that updating MDAC might help.
There is no such thing as a type 4 driver for MS Access. By definition, since there is no MS Access 'server', there can't be a type 4 driver.

Similar Messages

Test-OutlookConnectivity WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.

Hi All,
When we do a test-outlookconnectivity -protocol:http the result is a success but then we get the following:
ClientAccessServer   ServiceEndpoint                               Scenario
Result Latency
(MS)
xxxxxxxxxxxx... xxxxxxxxxxxxxx                 Autodiscover: Web service request. Success   46.80
WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance
of an object.
Object reference not set to an instance of an object.
    + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask
So it looks like it's not completing successfully.
I can't find anything on this in particular, and don't really know how to go about solving it - We are fully up to date, Exchange 2010 Sp2 with Rollup 5-v2
Any help appreciated!

hi,
I have the same issue also on Exchange 2010 SP2 RU5v2
I ran your command and get the below
[PS] C:\Installs\report\Activesync>Test-OutlookConnectivity -Protocol:http |FL
RunspaceId                  : ebd2c626-1634-40ad-a17e-c9a713d1a62b
ServiceEndpoint             : autodiscover.domain.com
Id                          : Autodiscover
ClientAccessServer          : CAS01.domain.com
Scenario                    : Autodiscover: Web service request.
ScenarioDescription         :
PerformanceCounterName      :
Result                      : Success
Error                       :
UserName                    : Gazpromuk.intra\extest_645e41faa55f4
StartTime                   : 8/21/2013 4:08:50 PM
Latency                     : 00:00:00.1250048
EventType                   : Success
LatencyInMillisecondsString : 125.00
Identity                    :
IsValid                     : True
WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.
Object reference not set to an instance of an object.
    + CategoryInfo          : NotSpecified: (:) [Test-OutlookConnectivity], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask
Any help would be greatly appreciated, I also get random failures of OWA, EAS and web services, very frustrating
I have no errors in the app event log
thanks
Faisal Saleem Windows Systems Analyst 07595781867

Crash dr watson in layout editor

I have an intermittent problem.
When I go in layout editor, I have often crash when I click on field. (Dr Watson) After one crash, I have always crash when I go to layout editor, I am not able to work in it without having the crash. After many manipulations in the form, I am able to go there, I don't know witch manupulation uncorrupt the form. Somebody had the same problem that me? I search the work around, I think it is a bug in form 6i.
My version is 6.0.8.10.3
Thanks.

Hi Kyle:
Please find the logs attached.
Thank you,
Mim
Attachments:
drwtsn32jan14091.txt ‏186 KB
drwtsn32jan14092.txt ‏166 KB

Dr Watson Error while trying to Print report

Hi,
I generated reports using Reports 6.0, however I'm getting Dr Watson error while tring to print the same. Any solutions to get it fixed will be appreciated.
Soumya

Hi!
I am facing the same problem.
There is one more finer detail to this. When I print the report
in defualt mode it does not give the error. It is only when I
generate the report in character mode and print it. I get this
error.
I am working on this.
If Any one can help please write back.
Hi,>I generated reports using Reports 6.0, however I'm getting Dr Watson error while tring to print the same. Any solutions to
get it fixed will be appreciated.>Soumya

Dr watson error on WINNT Please help.

Platform : NT4.0 with SP6 installed
JDK: 1.2.2
DB: Oracle
When I try to perform a some operations on running weblogic server I
will get Dr watson error saying accessviolation. This problem occurs
when I make high processor intesive calls or repeat smaller resource
consuming calls for 4 to5 times continuously.
Can any body tell me is there any knownproblems with the environment
which I am running in. Also kindly reply to my email id
regards
suresh

For the record, the JAVACLASSPATH should only contain the boot classes (and the JDK
classes for 1.1 JVMs). Everything else, including weblogicaux.jar, should be in the
WEBLOGICCLASSPATH.
nsuresh wrote:
Hello guys,
Finally we could get it working. Problem was in the entries of
WEEBLOGICCLASSPATH amd JAVACLASSPATH. JAVACLASSPATH should have only
bootclass and weblaugicaux.jar and rest of it should be in weblogic
class path ( or other way round) and you should not mix different
things. strange solution but we got it working.
bye and thanks for all the help.
bye
suresh
Venkatesh Iyer wrote:
Suresh
Are there any messages in the weblogic.log.
To isolate the JDBC related errors, set the trace on for JDBC.log in your properties
file and execute your tests. There is a chance there you may find something useful
in your jdbc.log file.
Venkatesh
Joseph Weinstein wrote:
nsuresh wrote:
Unfortunately Even I am not able to get any further information. There is
not JNI involved in my code. We are ussing Type3 driver with Oracle. Just
the problem is when we try to run some moderately high performing call we
get Dr watrson error.
regards
sureshOracle doesn't make a type-3 driver, only a type-4 and a type-2. The type-4
(thin) driver is all Java. The type-2 driver does use native code, in the Oracle
OCI library.
Joe
Rob Woollen wrote:
It's impossible to tell from the information that you've given.
Dr. Watson's are caused by errors in native code not java.
What JDBC driver are you using?
Are you using JNI or any of your own native code?
-- Rob
nsuresh wrote:
Platform : NT4.0 with SP6 installed
JDK: 1.2.2
DB: Oracle
When I try to perform a some operations on running weblogic server I
will get Dr watson error saying accessviolation. This problem occurs
when I make high processor intesive calls or repeat smaller resource
consuming calls for 4 to5 times continuously.
Can any body tell me is there any knownproblems with the environment
which I am running in. Also kindly reply to my email id
regards
suresh
PS: Folks: BEA WebLogic is in S.F., and now has some entry-level positions for
people who want to work with Java and E-Commerce infrastructure products. Send
resumes to [email protected]
The Weblogic Application Server from BEA
JavaWorld Editor's Choice Award: Best Web Application Server
Java Developer's Journal Editor's Choice Award: Best Web Application Server
Crossroads A-List Award: Rapid Application Development Tools for Java
Intelligent Enterprise RealWare: Best Application Using a Component Architecture
http://weblogic.beasys.com/press/awards/index.htm

Dr. Watson Error on exiting weblogic server 6.1

Hi,
I sometimes get the Dr.watson error when I stop my weblogic server.
The details are given below.
I have weblogic 6.1
Windows 2000 5.00.2195 Service pack 2
Memory=392mb
The message from Dr. Watson is:-
"Dr. watson was unable to attach to the process. It is possible that process exited
before Dr. Watson could attach to it.
Windows 2000 error code=87 The parameter is incorrect."
The message from the console is:-
<Jan 15, 2002 5:08:10 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'9' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:10 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'0' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:11 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'1' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:11 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'2' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:11 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'3' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:12 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'4' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:12 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'5' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:12 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'6' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:12 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'7' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'8' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'10' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'11' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'14' for queue: 'default'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'0' for queue: '__weblogic_admin_html_queue'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'1' for queue: '__weblogic_admin_html_queue'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'0' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:13 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'1' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:14 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'2' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:14 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'3' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:14 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'4' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:14 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'5' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:14 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'6' for queue: '__weblogic_admin_rmi_queue'' stopped.>
<Jan 15, 2002 5:08:14 PM CST> <Critical> <Kernel> <Execute Thread: 'ExecuteThread:
'7' for queue: '__weblogic_admin_rmi_queue'' stopped.>
C:\bea\wlserver6.1>goto finish
C:\bea\wlserver6.1>cd config\mydomain
C:\bea\wlserver6.1\config\mydomain>ENDLOCAL
C:\bea\wlserver6.1\config\mydomain>

I talked with Sun today about this issue and they stated that the error I received is the result of a bug. Sun Bug ID: 6650667
Synopsis: Cannot repack the changelog after trimming. libdb: DB_ENV->log_put: record larger than maximum file
We can see the the following lines in your error log:
[05/Jan/2010:00:05:03 -0500] - DEBUG - conn=-1 op=-1 msgId=-1 - libdb: DB_ENV->log_put: record larger than maximum file size (15956384 > 10485760)
[05/Jan/2010:00:05:03 -0500] - Repacking backend 'changelog', LDAP entries error Invalid argument (22).
[05/Jan/2010:00:05:03 -0500] - Repacking backend 'changelog' ended.
There is no fix, and a workaround is listed as follows:
Work Around:
Increase nsslapd-db-logfile-size in dse.ldif (In entry "cn=config,cn=ldbm database,cn=plugins,cn=config" )
This attribute is not present by default in the file.
Its default value is 10485760.
Which would make it the default as stated in the bug workaround.
Make the change as directed above, perform the repack again and let me know the results.

Work stoppage because of scratch disk error. The torture continues! Please help!

Hi, everyone:
I would greatly appreciate help.
In December, I began receiving the error message Could not initialize Photoshop because the scratch disks are full. I deleted all the large files from my hard drive, and the problem went away.
Now, I am working on a large Photoshop file (i.e., 585,155kb). I am working at 300 ppi for print reproduction, using multiple layers. I am opening each new image to be added to the master document in a separate Photoshop window. I set the resolution of each at 300 ppi, then crop and transfer to its new layer in the master file (using drag and drop). After I crop and transfer, I close the open window of the file I just cropped and transferred. No other programs are running. This seems to be fairly standard stuff.
All was fine (although very slow) until two nights ago. When cropping, I received the error Could not complete your request because the scratch disks are full.
Once again, I researched scratch disk error messages, and I came to the conclusion I had no choice but to increase my RAM. So, I upgraded from 512MB to 2 GIG. (I successfully opened my PC and installed the RAM myself, confirming it on the Properties window. A major success, as the RAM was costly, and difficult to find, so I saved some money and time by installing it myself!)
With great enthusiasm and excitement, I opened the master Photoshop file again and the next image to be set to 300 ppi, cropped, and transferred over to a layer. But, when I tried to crop, I received the SAME sickening message, Could not complete your request because the scratch disks are full.
How can this be? I have four times the RAM I had before, which was costly, and I expected Photoshop to work swift and smooth with this new, more efficient increase in RAM. I am simply bewildered.
I tried changing my Scratch Disks to C: rather than Startup, but then I received the error message You currently have Adobe Photoshops primary Scratch and Windows primary paging file on the same volume, which can result in reduced performance. It is recommended that you set Adobe Photoshops primary Scratch volume to be on a different volume, preferably on a different physical drive.
More scratch disk torture.
None of this makes any sense, and, while Photoshop error messages are upsetting, they dont explain what you should do. I am not a programmer, and I am totally stumped.
I know that someone somewhere upgraded their RAM and still received a Scratch disk error too, so I hope someone can advise me on what I need to do next. I cannot continue my work and just spent a lot of money on RAM.
Thank you!

Hi, everyone: Thank you for your help with my problem. I appreciate everyones time and feedback, as well as the openness to help and explain (and further explain) what I do not fully understand. I learned a lot more, as Photoshop always introduces new things to learn and figure out. (One has to be part programmer to make PS work!) I appreciated the clear instructions and simple analogies too (for example, the head vs. suitcase was great).
Good news: The Scratch disk error has subsided for now!
I believe (although I am not certain) that the problem was something very simple after all, and I am embarassed. Only time will tell if this was really the culprit, for, if the Scratch disk error reappears later, it may be something else all together that is lurking in the background.
For now, it seems to have been a problem that Peter K.s advice helped me discover...
Peter's advice was to check the crop settings in the option bar for the common mistake of specifying pixels/cm rather than pixels/inch. My setting was correct (pixels/inch). However, I inadvertently used my pixel width number as inches in the Width setting, causing a MUCH bigger file than intended. When I changed the number, the Scratch disk error disappeared, putting me back in business! Thanks, Peter, for pointing me the direction that eventually revealed the problem.
Could it be this simple?
I kept working most of the night to test drive, free of the Scratch disk error for now! I hope the good fortune continues.
The lesson for others may be to check simple settings carefully first, before diving into the deep end of Photoshop.
Meanwhile, the new RAM is speeding up Photoshop considerably, so I feel like it was a good investment and will probably help safeguard against further Scratch disk errors, which I have had in the past. Also, Ive taken everyones advice to consider a dedicated, separate HD for Photoshop Scratch disk use. Ill plan that as a future/next investment. However, technical notes say an external HD isnt a good idea, but I dont have capacity for an internal HD, so it will have to be an external one. I would appreciate any words of wisdom here. Also, I still have to research SATA-II drives too (which are new to me) and ascertain if I can utilize one on my system. It may simply be too old for this technology, if it is new?
If interested, I also tried several things:
(1) Checking the space available on my HD again The pie chart indicated it was approximately half full (there was 46% free space, or 34.38 GB free space). I'll look for more to remove, but it seems reasonable to have 46 percent available, I think.
(2) Checking the need to DEFRAG The Analyzer said a DEFRAG was not needed, and, indeed, the color chart that plotted the files showed only a thin red line or two (red indicates fragmentation).
(3) Searching for more TEMP files to delete. I found 750 MB in TEMP files to delete, so, while not a lot, there were some still there. Previously I followed these directions to safely delete temporary Internet files: Ctrl Panel > Internet Options > General > Delete Files > Delete all offline content. But, when I navigated to C:\Windows\Temp, sure enough, I found more. Directly opening C:\Windows\Temp seems to be more effective. (I have done it that way in the past too, but lately I was trying to follow the "safe" way I had stumbled across recently.)
(4) Checking my Photoshop Memory Allocation, which was already set at 85% (which may be too high, so I may back it down later, but I did not change it for now). I remembered adjusting it some time ago, but I had forgotten by how much!
I also read the links that everyone recommended, as well as numerous other documents I found across the Web. Some introduced still more to learn/understand, of course.
Thank you once again. Ill resurrect or repost if the Scratch disk error haunts me again later, but, for now, a happy ending.

Event 4999 - Watson report about to be sent for process id: 27244 on Mailbox Server every five minutes

On one of my DAG enabled Exchange 2013 mailbox servers, I get this error in event viewer every five minutes:
Log Name: Application
Source: MSExchange Common
Date: 6/25/2014 10:49:46 AM
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: mailboxserver
Description:
Watson report about to be sent for process id: 27244, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.E.RpcClientAccess.Service, unknown, M.E.R.S.U.DatabaseInfo..ctor, System.NullReferenceException, aba8, unknown.
ErrorReportingEnabled: True
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Common" />
<EventID Qualifiers="16388">4999</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-06-25T17:49:46.000000000Z" />
<EventRecordID>687360</EventRecordID>
<Channel>Application</Channel>
<Computer>mailboxserver</Computer>
<Security />
</System>
<EventData>
<Data>27244</Data>
<Data>E12IIS</Data>
<Data>c-RTL-AMD64</Data>
<Data>15.00.0913.022</Data>
<Data>M.E.RpcClientAccess.Service</Data>
<Data>unknown</Data>
<Data>M.E.R.S.U.DatabaseInfo..ctor</Data>
<Data>System.NullReferenceException</Data>
<Data>aba8</Data>
<Data>unknown</Data>
<Data>True</Data>
<Data>False</Data>
<Data>Microsoft.Exchange.RpcClientAccess.Service</Data>
<Data>
</Data>
</EventData>
</Event>
Everything is working ok, but I'm concerning that I"m seeing this.
ST

Amit,
I don't see the same type of 4999 error every five minutes anymore. It only get the 4999 error about 3 times a day. I get one with the same ID and other completely different process ID. The error is below:
Log Name: Application
Source: MSExchange Common
Date: 7/2/2014 6:01:36 AM
Event ID: 4999
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: computer
Description:
Watson report about to be sent for process id: 13152, with parameters: E12, c-RTL-AMD64, 15.00.0913.022, w3wp#MSExchangeOWAAppPool, M.E.Data.ApplicationLogic, M.E.D.S.GccUtils.GetClientIPEndpointsFromHttpRequest, System.NullReferenceException, 868, 15.00.0913.017.
ErrorReportingEnabled: True
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Common" />
<EventID Qualifiers="16388">4999</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-02T13:01:36.000000000Z" />
<EventRecordID>825358</EventRecordID>
<Channel>Application</Channel>
<Computer>computer</Computer>
<Security />
</System>
<EventData>
<Data>13152</Data>
<Data>E12</Data>
<Data>c-RTL-AMD64</Data>
<Data>15.00.0913.022</Data>
<Data>w3wp#MSExchangeOWAAppPool</Data>
<Data>M.E.Data.ApplicationLogic</Data>
<Data>M.E.D.S.GccUtils.GetClientIPEndpointsFromHttpRequest</Data>
<Data>System.NullReferenceException</Data>
<Data>868</Data>
<Data>15.00.0913.017</Data>
<Data>True</Data>
<Data>False</Data>
<Data>w3wp#MSExchangeOWAAppPool</Data>
<Data>
</Data>
</EventData>
</Event>
Going to keep an eye on it, but its not causing any issues.
ST

Dr. Watson error trying to generate report

I am running Sun Java System Web Server 6.1 SP5 on Windows Server 2003 with SP1 which has been locked down using the Bastion Host server role from the Windows Server 2003 Security Guide. When I try to generate a report on the web site statistics through the Server Manager (web admin console) I get the pop-up screen which says:
Starting analysis
Attempting to run:
D:/Sun/WEBSER~1/WEBSER~1.1/extras/flexanlg/flexanlg -F -n acol-prod2.acol.ca -i D:/Sun/WEBSER~1/WEBSER~1.1/HTTPS-~2/logs/access -o c:\stat.txt -c hnrfeuok -t s5m5h10 -l c+5h5 -p ctl
This may take a bit.
But the report does not get generated and I get the following error in the Event Viewer Application Log:
Event Type:     Information
Event Source:     DrWatson
Event Category:     None
Event ID:     4097
Date:          2/20/2006
Time:          9:17:06 AM
User:          N/A
Computer:     WEB100
Description:
The application, D:\Sun\WebServer\WebServer6.1\bin\https\httpadmin\bin\lganalyz.exe, generated an application error The error occurred on 02/20/2006 @ 09:17:06.313 The exception generated was c0000005 at address 77BD03BA (msvcrt!popen).
I thought this might be a permissions problem, so I tried running the Administrator Server service as the local admin account instead of Local System Account. I get the same result either way.
Any ideas on what might be causing the problem?
Thanks,
Chris

Just a little further info. I installed Windows 2003 with SP1 and the latest updates available through Windows Updates and Sun Java System Web Server SP5 on a new server. I did not do any of the security configuration lockdown as I had done on the other server. I am still getting the Dr. Watson error when trying to generate a report, but I am also getting the following error:
Event Type:     Error
Event Source:     Application Error
Event Category:     (100)
Event ID:     1000
Date:          2/23/2006
Time:          1:42:16 PM
User:          N/A
Computer:     WEB100-TEST
Description:
Faulting application lganalyz.exe, version 0.0.0.0, faulting module msvcrt.dll, version 7.0.3790.1830, fault address 0x000303ba.
Hope this helps!
~Chris

Why does labview generate Dr. Watson error "C0000005 access violation"

I am running Labview 5.1.1 in Windows 2000 Professional on a machine with the following configuration
*----> System Information <----*
Computer Name: ANDANTE
User Name: Administrator
Number of Processors: 2
Processor Type: x86 Family 6 Model 8 Stepping 3
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 4
Current Type: Multiprocessor Free
I have all of a sudden begun to experience labview crashes. The crash occurs systematically after tens of minutes; not just a few minutes, but not more than an hour or so. I am running a vi but not actively interacting with the machine (no other applications running, not even moving the mouse around). The problem happens even when running a vi that I have run successfully for extended periods of time (overnight) only 3 months ago. I have tried it with two different vis, one that I have recently made a lot of modifications to and another that has not been touched for months (since before the crashes began), and it happens with both vis. They do much different things (communicate with different GPIB or PCI boards, write to different kinds of files in different locations, etc.), so the problem seems to be vi-independent.
When the crash occurs, I see a dialog appear with the error
labview.exe has generated errors and will be closed by windows. You will need to restart the program. An error log has been created.
The Dr. Watson error log is generated and the error is
Application exception occurred:
App: (pid=1160)
When: 4/25/2004 @ 01:57:56.640
Exception number: c0000005 (access violation)
I always get the same Dr. Watson error information -- i.e., it is very reproducible. I don't really know how to interpret the rest of the Dr. Watson log, but I include the report on the first thread, which is the one with the "FAULT" in it, at the end of this email.
Looking around on the web, it may be that a temporary virus infection could have created the problem. In the period since the machines was last successfully used, I have seen two files be infected by the W32.Welchia.B.Worm virus, the files were svchost.exe and WksPatch[1].exe. These files have been quarantined and no other infected files have been found since this error began to appear.
Any ideas? I've seen on the web that reinstalling Windows 2000 and/or upgrading to Labview 7.0 might solve the problem, but it would be nice to get some confirmation before taking the time/spending the money.
Here is the state dump for the thread with the FAULT in it, as provided by Dr. Watson:
State Dump for Thread Id 0x574
eax=00000062 ebx=00000000 ecx=00000000 edx=00000004 esi=00000000 edi=05692214
eip=00748236 esp=0012fb28 ebp=0012fb28 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246
function: StrLen
00748230 55 push ebp
00748231 8bec mov ebp,esp
00748233 8b4d08 mov ecx,[ebp+0x8] ss:00ba9a0e=????????
FAULT ->00748236 8a11 mov dl,[ecx] ds:00000000=??
00748238 8d4101 lea eax,[ecx+0x1] ds:00a79ee6=????????
0074823b 84d2 test dl,dl
0074823d 7407 jz GetCDReg+0x6f6 (00750c46)
0074823f 8a10 mov dl,[eax] ds:00000062=??
00748241 40 inc eax
00748242 84d2 test dl,dl
00748244 75f9 jnz CfgRemove+0x44f (0074ae3f)
00748246 2bc1 sub eax,ecx
00748248 48 dec eax
00748249 5d pop ebp
0074824a c3 ret
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0012FB28 00737A74 00000000 00000000 05692214 00000400 !StrLen
0012FC40 00736A45 050753E4 05692214 0012FC6C 00736724 !SetKeyboardHandlerProc
0012FC50 00736724 05692214 0012FCB4 05692214 BDBC0000 !SetKeyboardHandlerProc
0012FC6C 00736627 05692214 0569232C 00000400 00000000 !SetKeyboardHandlerProc
0012FC98 0074B470 0012FCB4 BDBD0001 00000000 0569E8E0 !SetKeyboardHandlerProc
0012FCD0 0074ACD0 00000000 0074AC10 0569FFA4 010A2418 !CfgRemove
0012FCE8 007808D5 00000000 00000000 00000001 00000000 !CfgRemove
0012FD08 007ACEB6 00000000 00000000 77E18F95 00000000 !ChkOccurrences
0012FD9C 006033DE 00000001 00000000 77E2ADC1 007A5C80 !WMainLoop
0012FF24 007B2186 00400000 00000000 00000001 00000001 !WMain
0012FFC0 7C581AF6 005C0057 0061006C 7FFDF000 C0000005 !inp
0012FFF0 00000000 007B2030 00000000 000000C8 00000100 kernel32!OpenEventA
*----> Raw Stack Dump <----*
0012fb28 40 fc 12 00 74 7a 73 00 - 00 00 00 00 00 00 00 00 @...tzs.........
0012fb38 14 22 69 05 00 04 00 00 - 16 4d 65 74 68 6f 64 20 ."i......Method
0012fb48 4e 6f 74 20 49 6d 70 6c - 65 6d 65 6e 74 65 64 00 Not Implemented.
0012fb58 55 1f f8 77 18 25 f8 77 - 2f a8 fd 74 c4 01 00 00 U..w.%.w/..t....
0012fb68 05 a5 fd 74 d0 26 ce 01 - 00 00 06 01 10 04 00 00 ...t.&..........
0012fb78 00 00 00 00 00 00 00 00 - 2e fb 69 05 42 e9 69 05 ..........i.B.i.
0012fb88 c1 2f 7b 00 00 00 00 00 - 12 04 00 00 11 04 00 00 ./{.............
0012fb98 30 fb 69 05 12 04 12 00 - bb 35 7b 00 00 00 06 01 0.i......5{.....
0012fba8 11 04 00 00 00 00 00 00 - 00 00 00 00 2e fb 69 05 ..............i.
0012fbb8 35 34 7b 00 4c 34 7b 00 - 48 00 06 01 f8 fb 12 00 54{.L4{.H.......
0012fbc8 10 04 00 00 ec 53 07 05 - 11 04 00 00 08 fc 00 00 .....S..........
0012fbd8 ee c8 77 00 30 fb 69 05 - 11 04 00 00 00 00 00 00 ..w.0.i.........
0012fbe8 00 04 00 00 01 00 00 00 - ec 53 07 05 00 04 00 00 .........S......
0012fbf8 00 38 83 00 1c fc 12 00 - 23 ca 77 00 00 38 83 00 .8......#.w..8..
0012fc08 40 ff 69 05 01 00 00 00 - 00 00 00 00 2d 00 00 00 @.i.........-...
0012fc18 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
0012fc28 00 00 00 00 00 00 00 00 - 00 00 00 00 01 00 00 00 ................
0012fc38 50 fc 12 00 1a 6a 73 00 - 50 fc 12 00 45 6a 73 00 P....js.P...Ejs.
0012fc48 e4 53 07 05 14 22 69 05 - 6c fc 12 00 24 67 73 00 .S..."i.l...$gs.
0012fc58 14 22 69 05 b4 fc 12 00 - 14 22 69 05 00 00 bc bd ."i......"i.....

For questions like these, you are better off contacting NI directly. Goto www.ni.com/ask for directions. It has been my experience that Dr. Watson error logs are only useful as supplementary information. It is best for support and for the forum if you can provide a clear description on how to cause the error consistently.

Read Image File - Dr. Watson Error

Greetings,
Sorry for posting Developer4.5 problem here. I am reading an
image (JPG) file from Forms Builtin Read_Image_File. Whenever it
try to load image file to image item it gives Dr. Watson Error.
I am working on Forms4.5.9.7.0 on Windows NT with service pack
3.0. Thanks for any help.
Regards
Ajay Khandelwal
null

The problem was with the version. There was bug in the
Forms4.5.9.7.0 version. I changed the JPEG to JFIF format and
its running perfectly. The newer versions support the JPEG
format also. Thanks for bearing me.
Ajay Khandelwal
ajay khandelwal (guest) wrote:
: Greetings,
: Sorry for posting Developer4.5 problem here. I am reading
an
: image (JPG) file from Forms Builtin Read_Image_File. Whenever
it
: try to load image file to image item it gives Dr. Watson Error.
: I am working on Forms4.5.9.7.0 on Windows NT with service pack
: 3.0. Thanks for any help.
: Regards
: Ajay Khandelwal
null

[svn:bz-trunk] 17010: Bug: Watson #2652870 - use a property file to drive the custom configuration tokens as opposed to setting it in the command line

Revision: 17010
Revision: 17010
Author:   [email protected]
Date:     2010-07-22 02:52:41 -0700 (Thu, 22 Jul 2010)
Log Message:
Bug: Watson #2652870 - use a property file to drive the custom configuration tokens as opposed to setting it in the command line
QA: Yes
Doc: Yes - in custom tokens section, talk about the new token.file option
Checkintests: Pass
Details: Changed TokenReplacer to look for a token.file JVM option. If it's specified (eg. -Dtoken.file=/User/matamel/Desktop/token.properties), then TokenReplacer looks for a properties file where token name and values are specified. This allows someone to specify a file for custom tokens. Custom tokens can still be specified as straight JVM option and in case where a token is defined both as a JVM option and in a token properties file, JVM option takes precedence.
Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/config/TokenReplacer.java

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Dr Watson Postmortem Debugger message after installing Adobe Reader 9

After I installed 'Adobe Reader 9' I was greeted with a 'Dr Watson Postmortem debugger' message so then I uninstalled Adobe and haven't had the dr.watson message since. What can I do as lots of sites require Adobe Reader such as 'youtube'. Can anyone help me?

Reader Forum http://www.adobeforums.com/webx?13@@.3bbf42f7

Having problem with Dr Watson error

I am running a web form in forms6i. If I write any messages in post-query trigger at block level, I am getting a Dr Watson Application error and simply exits the form. If I remove the messages, form is running fine.Is there any fix for this error?
Please help me out.
Thanks,
Sunitha.

tomk wrote:Post the error.
Here this is the error
ccache gcc -c -I./../../mzscheme/gc -I./../../wxxt/src/AIAI-include -I./../../wxxt/src -I./../../mred/wxme/ -I./../../mzscheme/ -I./../../mzscheme/include/ -I/usr/include -I/usr/include/freetype2 -DOPERATOR_NEW_ARRAY -DUSE_GL -DWX_USE_XRENDER -DWX_USE_XFT -DWX_USE_LIBPNG -DWX_USE_LIBJPEG -Dwx_xt -I./XWidgets -o XWidgets/xwMenu.o ./XWidgets/xwMenu.c
./XWidgets/xwMenu.c:709:31: error: X11/bitmaps/gray: No such file or directory
./XWidgets/xwMenu.c: In function 'CreateGCs':
./XWidgets/xwMenu.c:711: error: 'gray_bits' undeclared (first use in this function)
./XWidgets/xwMenu.c:711: error: (Each undeclared identifier is reported only once
./XWidgets/xwMenu.c:711: error: for each function it appears in.)
./XWidgets/xwMenu.c:711: error: 'gray_width' undeclared (first use in this function)
./XWidgets/xwMenu.c:711: error: 'gray_height' undeclared (first use in this function)
make[5]: *** [XWidgets/xwMenu.o] Error 1
make[5]: Leaving directory `/var/abs/local/src/plt-301/src/wxxt/src'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/var/abs/local/src/plt-301/src/wxxt/src/x'
make[3]: *** [wx_xt] Error 2
make[3]: Leaving directory `/var/abs/local/src/plt-301/src/mred'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/abs/local/src/plt-301/src/mred'
make[1]: *** [mr] Error 2
make[1]: Leaving directory `/var/abs/local/src/plt-301/src'
make: *** [all] Error 2
==> ERROR: Build Failed. Aborting...

Watson Errors RPCClientAccess freezing up CAS

I am occasionally getting errors that are freezing up the CAS, preventing mail transmission until I restart services. Most of the errors I get are similar to the one below, they ALL have to do with RPC. Using Exchange 2010 SP3 (where did all
the 2010 forums go? couldn't find, so am posting to the 2013 forums, sorry). I turned on windows error reporting settings in the registry to dump the error log, but absolutely nothing shows up so that is no help. The information I find mostly
points to installing rollups (most of the rollups are older than what I have installed). I don't have any really definitive information here and it is getting frustrating. At least this time I got the exact same error at the exact same time on
both of my CAS servers instead of getting it on one CAS server, and this time it showed up BEFORE all the systems froze, instead of after everything came back, so at least I could start checking/restarting services, etc. Any ideas here? Thank you.
Watson report about to be sent for process id: 11556, with parameters: E12, c-RTL-AMD64, 14.03.0123.004, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.EmptyFolderSegmentedOperation.InternalDispose, System.NullReferenceException, ad2a, 14.03.0123.003.
ErrorReportingEnabled: False

yes, restarting the services usually works, but sometimes these hang. as far as installing patches, if you look at errors of this nature, a multitude of patches (sp and ru) are supposed to correct this. we just installed sp3 in our environement
which was VERY intrusive and time consuming as we had to take one system out of the DAG since we have journaling turned on and the journaling db is not in the DAG (there was supposed to be a workaround for this and I was on the phone with Microsoft until the
wee hours of the morning trying to get the workaround to work, and it didn't). Needless to say, since we just installed a service pack (one that was tried and true, wanted to make sure what we installed had been road tested extensively), that is not
really an option right now. And as I said, there are multiple updates that are supposed to correct this issue. I am looking for an alternative to installing a patch and then finding it isn't going to solve the problem. The patches that are
supposed to correct this go all the way back to RTM versions.

Tortured by Dr. Watson.

Similar Messages

Maybe you are looking for