Link to home
Start Free TrialLog in
Avatar of mystikal1000
mystikal1000

asked on

Application 1000 errors

Has anyone encountered errors like this in Event Viewer.  How can I determine if this is an Application problem or an Windows 2003 error?


Event Type:      Error
Event Source:      Application Error
Event Category:      None
Event ID:      1000
Date:            02/05/2008
Time:            9:15:22 AM
User:            N/A
Computer:      Server1
Description:
Faulting application pre.exe, version 2.0.0.0, faulting module pre.exe, version 2.0.0.0, fault address 0x0018ed2b.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6c 70 6d   ure  pre
0018: 2e 65 78 65 20 32 2e 30   .exe 2.0
0020: 2e 30 2e 30 20 69 6e 20   .0.0 in
0028: 6c 70 6d 2e 65 78 65 20   pre.exe
0030: 32 2e 30 2e 30 2e 30 20   2.0.0.0
0038: 61 74 20 6f 66 66 73 65   at offse
0040: 74 20 30 30 31 38 65 64   t 0018ed
0048: 32 62 0d 0a               2b..    
Avatar of santhoshu
santhoshu
Flag of India image

Find out which folder is pre.exe residing and also find out which application is using that folder.
You will have to contact that application vendor to get this fixed.  Event ID 1000 is a generic one.
ASKER CERTIFIED SOLUTION
Avatar of Member_2_49692
Member_2_49692

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mystikal1000
mystikal1000

ASKER

Sorry I should of told you this pre.exe is ingrown home application on the windows 2003 servers, its not malware...
then your going to need to look at that application using a debugging tool to see what it is doing.  If that is an application that was create in house your programmers are going to have to use debuggers and look at its memory usage it is crashing itself.

Something like ollydbg or microsofts debugger will be needed
Yes.  As I mentioned in my first comment, this is something the developers of the pre.exe should look and resolve.
santhoshu,

wasn't trying to copy your answer had the questioner told me PRE.EXE was an in house app I would have simply agreed with you in the first place. I thought it was a malware because of the very generic name and a malware that is known to carry that name.
no problem braincassin.  you are right.  I was just cursing myself of not seeing it from the malware view (as the author didn't inform us that it is a in house applicaiton).  Your thoughts were in the right direction.
:)
Sorry I should of mentioned the apps is homegrown...

Thanks.