SCE2007 Console Crash
I'm having a problem and I feel I've done my share of research but can't come to a resolution for this issue. I have a new install of SCE 2007 on a 64bit 2003 R2 server. All service packs and updates installed. The install went well and I'm able to start System Center Essentials 2007 Console. I see the overview and it lists the few PCs I've discovered and installed so far. As soon as I click on "All Clients" about 1 second goes by and it crashes. The app log gives me: Event Type:ErrorEvent Source:.NET Runtime 2.0 Error ReportingEvent Category:NoneEvent ID:5000Date:1/22/2008Time:9:53:52 AMUser:N/AComputer:PL-SC1Description:EventType clr20r3, P1 b0jhpzqr1b3ggbemyeifskrwrqlfywdd, P2 6.0.1250.0, P3 4629da7a, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 f46, P8 7, P9 n3ctrye2kn3c34sgl4zqyrbfte4m13nb, P10 NIL. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data: I've noticed that I'm able to click on "All Servers" and I don't crash and can see all the details of the SC server. I can look through the Monitoring, Updates, Software and Reporting just fine. I can run reports (like hardware) against the PCs and everything is great. This happens on the local server's console and both client PCs I've tried it on (Vista and XP). I'm guessing it's a server side issue but I'm not sure where to go from here. Any help would be appreciated.
January 22nd, 2008 7:02pm

Just a quick update, I have uninstalled .net 2.0 and 3.0. Restarted, renamed the 2.0 folder to v2.0.50727_OLD, stopped IIS then reinstalled them both. I'm still getting the same errors.
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2008 2:02am

Hi.I'd like to suggest you Install .Net framework 2.0 SP1 and .Net framework 3.0 SP1you can download them from the following website:Download details: .NET 2.0 SP1 (x86)http://www.microsoft.com/downloads/details.aspx?FamilyID=79bc3b77-e02c-4ad3-aacf-a7633f706ba5&DisplayLang=enDownload details: .NET Framework 3.0 SP1http://www.microsoft.com/downloads/details.aspx?FamilyID=ec2ca85d-b255-4425-9e65-1e88a0bdb72a&DisplayLang=en--------------------Regards,Eric ZhangMicrosoft Online Community Support
January 24th, 2008 1:18pm

Thanks for the reply, Eric. However since posting that I had installed both of those with no luck. I even did the 3.5 install hoping it may change something. This is a new server who's first role is SCE so I'm lucky enough that I can reboot and rebuild it often. Since I posted this last message I started over. This is an HP Blade so I started from scratch with the Smart Start CD. Formatted and everything. I installed Server 2003 Standardx64 R2. Next I applied all current Windows updates. Joined the domain.Then I installed SQL 2005 x64 (reporting services included with default settings). Restart then installed SQL SP2. Installed all availibleWIndows Updates again.Restarted again and installed SCE2007 wtih all defaults. Here's an interesting thing I noticed this time around: The first client I added through the console was a Vista Business PC. It worked fine, I could see thedetails of the PC with no console issues. Next I added a server, same positive results. It's only when I add an XP workstation that causes the crash. ANY XP PC that's added will cause a crash in the console unless I shut off the Details Pane. Once that's off I can highlight any PC in the All Clients group with no issues. This has me leaning towards something being wrong with the SQL Reporting since I'm pretty sure that's the meat behind the details pane. Not sure if all of this makes it easier or harder to help with. :-\
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2008 5:38pm

HiPlease try the solutions inside this KB:Unhandled exceptions cause ASP.NET-based applications to unexpectedly quit in the .NET Framework 2.0http://support.microsoft.com/default.aspx?scid=kb;EN-US;911816--------------------Regards,Eric ZhangMicrosoft Online Community Support
January 25th, 2008 1:37pm

Still no luck. I changed that setting (using method 2) in both %WINDIR%\Microsoft.NET\Framework\v2.0.50727 and %WINDIR%\Microsoft.NET\Framework64\v2.0.50727. After the change I have restarted with continuing crashes. Thank you again for the ideas of things to try. I'll keep try.
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2008 5:14pm

Hi,I think this KB maybe helpful for you:An IIS 6.0 application pool may unexpectedly exit when a worker process shuts down or is recycledhttp://support.microsoft.com/?scid=kb%3Ben-us%3B918041&x=8&y=6--------------------Regards,Eric ZhangMicrosoft Online Community Support
January 28th, 2008 12:25pm

Still no luck, Eric. In desparation I've remade the server in a 32bit enviorment using MSVL Server 2003 StandardR2 witih SP2. Then 32bit SQL 2005. Then SQL SP2. I restart, go to WIndows Update and get all updates that are out right now. I restart and install SCE. After running through the few steps to get it up and running I add one XP box. Sure enough, exact same thing happens. That's 3 brand new server builds and 3 times the exact same thing happens (twice in x64 and once in x32). I would have hoped that by now MS would have tried to reproduce the issue since is seems pretty easy to create. I've put enough time into troubleshooting the issue at this point. I'm pretty disapointed in the product right now.
Free Windows Admin Tool Kit Click here and download it now
January 29th, 2008 7:51pm

Hi,Did you push the agents to Windows XP clients or manually install it?Also, which policy did you use? domain policy or local policy?--------------------Regards,Eric ZhangMicrosoft Online Community Support
January 30th, 2008 1:57pm

Yes I pushed all of the agents out and I used a domain policy. I had also tried a manual install but nothing changed. Thank you
Free Windows Admin Tool Kit Click here and download it now
January 30th, 2008 5:32pm

Hi, Let's collect ETL trace logs for further analysis. ETL trace collect all the background activities of the SCE & logged in to the file. It will be useful to identify the issue. Please follow the steps to get the etl trace: 1. Open the command prompt CD %program Files%\System Center Essentials 2007\tools\startTracing.cmd VER2. Click "All Clients" for it fails.3. Then stop the ETL tracing using StopTracing.cmd4. You can find the ELT logs in the following path c:\windows\temp\MOMTraceBid.etl, MOMTraceNative.etl & MOMTraceUI.etl5. Please send all 3 etl log to scedata@microsoft.com. Note:Please include the following three lines in the email body:SCE2007 Console Crashhttp://forums.microsoft.com/TechNet/AddPost.aspx?PostID=2766410&SiteID=17Eric Zhang - MSFTRegarding more information about how to send email to SCEDATA@microsoft.com, please refer to:How to send files to the Microsoft SCE team for review <http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1680389&SiteID=17>Also, please post a quick note in the current thread to inform me after sending the email.Thanks! --------------------Regards,Eric ZhangMicrosoft Online Community Support
January 31st, 2008 12:25pm

Hi Eric, the files have been sent. Hope I haven't messed with the thing too much to flaw the traces.
Free Windows Admin Tool Kit Click here and download it now
January 31st, 2008 5:17pm

Hi,Thanks for your mail.Also, I'd like to confirm which SCE version did you use? Is it a trial version?--------------------Regards,Eric ZhangMicrosoft Online Community Support
February 4th, 2008 12:10pm

Originally I downloaded the ISO form the MSVL site and installed from the ISO. I have also tried installing from the MSVL DVD from July 2007 (UHC-01245). I have never downloaded the trial version. Hope that helps.
Free Windows Admin Tool Kit Click here and download it now
February 4th, 2008 5:21pm

Hi, One thing we can try is to check the MT_DeploymentSettings table in the OperationsManager database. If it has a row where the Name_<Guid> column is All Clients, then delete the row and then try to add it back to the Computer section of the console. --------------------Regards,Eric ZhangMicrosoft Online Community Support
February 5th, 2008 12:35pm

All that did was get rid of the All Clients group. The client can still be selected in All Computers. Once selected and the details pane is turned on the console will crash. Again, I have not had this problem with Vista or 2003 server clients. ONLY XP PCs that have had the agent installed. I completed my 4th build of the system this morning and the exact same thing is happening. Another thing I noticed - when I try to put a simple software package together using a 3MB exe file I get the same crash and same error.
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2008 6:55pm

Hi, Please try following steps outlined below: 1. Open SCE console and go to administration-> management packs. 2. Find default management pack, microsoft system center essentials default user MP and essentials internal library MP and remove them one by one. 3. Then, re-importthese MPs (Microsoft.systemcenter.essentials.internal.mp, Microsoft.systemcenter.operationsmanager.defaultuser.xml, Microsoft.systemcenter.essentials.defaultuser.xml)from %programfiles%\system center esstials 2007 Also, how about click "All computers", as this group contains the Windows XP clients, did it crash? --------------------Regards,Eric ZhangMicrosoft Online Community Support
February 7th, 2008 10:35am

Hi,As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as Answered as the previous steps should be helpful for many similar scenarios.If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.In addition, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.Thanks!--------------------Regards,Eric ZhangMicrosoft Online Community Support
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2008 5:10am

Did this solve your problem,I am having the same problem.ThanksMike
April 21st, 2008 11:04pm

No none of the above helped. We ended up just going with a SSCM instead. Too bad too but with the amount of time this was taking we needed to move forward with something.
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2008 11:09pm

So there is no fix for this? We don't have the budget to simply move to SCOM.
June 3rd, 2009 3:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics