Marketing_Insists
asked on
help with a short mdmp file
I'm not a programmer, but I'm in charge of a application server that is showing these errors in a mdmp file. The application crashes have been blamed on hardware, but the below suggests otherwise.
My first guess is that OMRrefr.exe is crashing when it does something with mscorwks while releasing memory?
Help a sys admin avoid the heat. Thanks!
FAULTING_IP:
kernel32!CreateActCtxW+210
77e55e02 5e pop esi
EXCEPTION_RECORD: ffffffff -- (.exr ffffffffffffffff)
ExceptionAddress: 77e55e02 (kernel32!CreateActCtxW+0x
ExceptionCode: e0434f4d (CLR exception)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 80131509
BUGCHECK_STR: CLR_EXCEPTION
DEFAULT_BUCKET_ID: APPLICATION_FAULT
PROCESS_NAME: OMRrefr.exe
ERROR_CODE: (NTSTATUS) 0xe0434f4d - <Unable to get error code text>
MANAGED_STACK: !dumpstack -EE
Failed to load data access DLL, 0x80004005
LAST_CONTROL_TRANSFER: from 79f97065 to 77e55e02
STACK_TEXT:
00b2f608 79f97065 e0434f4d 00000001 00000001 kernel32!CreateActCtxW+0x2
00b2f668 7a0945a4 0108fcc8 00000000 00000000 mscorwks!HndDestroyHandleT
00b2f72c 794aba4f 01045fcc 00000001 010465d4 mscorwks!RecordPool::Repla
WARNING: Stack unwind information not available. Following frames may be wrong.
00b2f768 794b4771 01045fcc 00b2f7d4 7a2ed514 mscorlib_ni+0x3eba4f
00b2f790 79f3cb53 00000001 00b2f818 79f3caeb mscorlib_ni+0x3f4771
00b2f7a4 00000000 00b2f890 00000001 00b2f808 mscorwks!TiggerStorage::Wr
STACK_COMMAND: ~3s; .ecxr ; kb
FAULTING_THREAD: 000001b8
FOLLOWUP_IP:
mscorwks!HndDestroyHandleT
79f97065 ?? ???
ASKER
I've not been able to see the errors from the web interface. Then again, the error's only show up in the logs a few times a day.
When I log in to the machine locally, I see numerous errors listed about OMRrefr.exe in a error application list box ready to be sent to MS for "further analysis".
In the application event log, I see:
.NET Runtime 2.0 Error
EventType clr20r3, P1 OMRrefr.exe, P2 1.0.0.1,
P3 4362dacf, P4 mscorlib, P5 2.0.0.0, P6 4333ab80,
P7 4055, P8 a3, P9 system.invalidoperationexc
P10 NIL.
and
OMRrefr.exe,
An error has occurred while establishing a connection
to the server. When connecting to SQL Server 2005,
this failure may be caused by the fact that under the
default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server)
This suggests trouble with connecting to a SQL DB, but I do not see a single error on either machines suggesting a network interruption.
I have a perl base service whose interpretor is kept on another share, it would show errors if it were unavailable, so I do not believe it is a connectivity issue.
When I log in to the machine locally, I see numerous errors listed about OMRrefr.exe in a error application list box ready to be sent to MS for "further analysis".
In the application event log, I see:
.NET Runtime 2.0 Error
EventType clr20r3, P1 OMRrefr.exe, P2 1.0.0.1,
P3 4362dacf, P4 mscorlib, P5 2.0.0.0, P6 4333ab80,
P7 4055, P8 a3, P9 system.invalidoperationexc
P10 NIL.
and
OMRrefr.exe,
An error has occurred while establishing a connection
to the server. When connecting to SQL Server 2005,
this failure may be caused by the fact that under the
default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server)
This suggests trouble with connecting to a SQL DB, but I do not see a single error on either machines suggesting a network interruption.
I have a perl base service whose interpretor is kept on another share, it would show errors if it were unavailable, so I do not believe it is a connectivity issue.
Is this a Windows 2003 server?
Bob
Bob
ASKER
yes
I couldn't find a reference for OMRrefr.exe, so I was thinking that it could be either for Windows 2003 Server or SQL Server 2005 (which I don't have either).
If you are getting these exceptions in a log, but the application is not experiencing any problems, then it might be a self-healing problem, and this is just a report of the initial problem.
That is difficult to tell, though, without really understanding the environment.
Bob
If you are getting these exceptions in a log, but the application is not experiencing any problems, then it might be a self-healing problem, and this is just a report of the initial problem.
That is difficult to tell, though, without really understanding the environment.
Bob
ASKER
Understood.
Do you think I can rule the problem as hardware vs code issue? e.g., more likely a memory issue than a connectivity issue?
Do you think I can rule the problem as hardware vs code issue? e.g., more likely a memory issue than a connectivity issue?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Bob