
Every couple seconds I am seeing:
Log Name: Application
Source: Windows Error Reporting
Date: 1/10/2012 8:08:40 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxx
Description:
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: swjobengineworker2.exe
P2: 2.2.4.138
P3: 4ecf8688
P4: mscorlib
P5: 2.0.0.0
P6: 4e154c6c
P7: 11eb
P8: 112
P9: System.ObjectDisposedException
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_swjobengineworke_57a8255e70278ced004f71e9b4f72e96ab081_1e8a2768
Analysis symbol:
Rechecking for solution: 0
Report Id: f0ea7f70-3c09-11e1-bbe8-005056810029
Report Status: 4
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-01-11T04:08:40.000000000Z" />
<EventRecordID>7215</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxxxxxx</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>CLR20r3</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>swjobengineworker2.exe</Data>
<Data>2.2.4.138</Data>
<Data>4ecf8688</Data>
<Data>mscorlib</Data>
<Data>2.0.0.0</Data>
<Data>4e154c6c</Data>
<Data>11eb</Data>
<Data>112</Data>
<Data>System.ObjectDisposedException</Data>
<Data>
</Data>
<Data>
</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_swjobengineworke_57a8255e70278ced004f71e9b4f72e96ab081_1e8a2768</Data>
<Data>
</Data>
<Data>0</Data>
<Data>f0ea7f70-3c09-11e1-bbe8-005056810029</Data>
<Data>4</Data>
</EventData>
</Event>
and it is leaving a bunch of cscripts open
Who should I show this to?
I did a reboot of the server and the app crashes stopped (but so did the app discovery). Maybe it was because I told it to inherit the credentials from the parent server, but the parent servers were SNMP, so it wouldn't be able to find the windows credentials(?). I'll try the discovery again tomorrow.
I scanned for the "Windows Server 2003-2008 Services and Counters" against 230 servers and everything was "ok", but then I scanned 10 ESX servers and had the app crashes.
Hello,
looks like some issue with App discovery to me. I'll try to reproduce it right away.
Just for clarification, which beta build are you running? It is Beta 5?
Beta 5. I am still trying to get a pattern. I got it again when I tried it against 230 windows servers and these monitors:
Active Directory 2003-2008 Services and Counters
Citrix XenApp 5.0 Core WMI counters
Citrix XenApp 5.0 ICA Session WMI counters
Citrix XenApp 5.0 Presentation Server WMI counters
Citrix XenApp 5.0 Services
Errors in Application Event Log
SQL Server 2005-2008 Performance (SQL)
SQL Server 2005-2008 Performance (WMI)
Windows Server 2003-2008 Services and Counters
Windows Update Monitoring
This time I used an existing scan credential but when I scanned the Windows Server 2003-2008 service and counters, I had just created the credential.
I am just trying to throw out all the different thing I can think of that might be causing it.
netlogix, I'll be following up with you offline. We'll need you to collect a SolarWinds Diagnostic so we can get a better understanding of what's causing the application faults.
They told me that they found the issue. It has something to do with powershell and windows scripts. So don't use them in discoveries with Beta 5, but that it should be addressed in the next build.
Thank you for the update, netlogix. Most appreciated.
DH
I am not getting it in RC1 - Yea!