9 Replies Latest reply on Mar 10, 2011 6:11 PM by Pritish

    HP MediaSmart Console crashes when choosing "Show Quarantined Files"

      [EDITED May 2, 2010 to add HomeServerConsole error log at end.]

       

      I have a trial of McAfee Total Protection Service which came with my HP MediaSmart EX495 Windows Home Server.

       

      Until recently, clicking "View Quarantined Files" in the McAfee add-in in the Home Server Console did just that. [edited, May 2, 2010: I now can't actually say for sure that this ever worked.]

       

      Now, however, that action causes the Console to crash.

       

      Just before (or simultaneously with) the console crash, the Windows Event Viewer shows an error related to ".NET Runtime 2.0 Error Reporting".

       

      Error event details are: EventType clr20r3, P1 homeserverconsole.exe, P2 6.0.0.0, P3 4acceb5f, P4 whscommon, P5 6.0.0.0, P6 4accead8, P7 334, P8 1b, P9 system.invalidoperationexception, P10 NIL.

       

      The latest Windows updates, HP updates, and McAfee updates are applied.

       

      Computer System:

      HP MediaSmart EX495

      Version 3.3.1.35433 – 2/3/2010

       

      McAfee Total Protection Service (trial):

      Product Version: V5.0.0 Patch 5

      DAT file version: 5966.0000

      DAT file creation date: 4/28/2010

      Scan engine version 5400.1158

      Buffer overflow detection version: 467

       

      HP MediaSmart Windows Home Server Add-ins:

      Add-in Central v1.0.2.31

      MediaSmart Server Drive Labeler v1.0.0.5

      Advanced Admin Console v0.5.2

      Update History AddIn v0.3.0

      Windows Home Server Toolkit 1.1 v6.0.1800.0

      McAfee Total Protection Service v4.9.2.132

       

      I can choose to "View Quarantined Files" from the McAfee program itself if I RDP into the server (right-click the McAfee icon in the server's system tray; choose “Open Console”; click “Action Menu”; choose “Product Details”; click “View Quarantined Files”)

       

      Since it's still a trial, no one at McAfee will talk to me. Maybe someone here can shed some light?

       

      I did try rebooting the server, but the problem still happens.

       

      [EDITED May 2, 2010 to add]:

      It looks like McAfee maybe isn't handling the Exception when the quarantine file doesn't exist. According to the "HomeServerConsole" logs that I found, every time the Console crashes after I click "View Quarantined Files", the following Exception is thrown:

       

      Error: Exception thrown

      System.InvalidOperationException: Cannot start process because a file name has not been provided.

      at System.Diagnostics.Process.Start() in System.dll

      at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) in System.dll

      at McAfee.HomeServer.Dianostics.ModalProcess2.Start(ProcessStartInfo psi) in TOPWHSUtility.dll [ed. sic "Dianostics"]

      at McAfee.HomeServer.Dianostics.ModalProcess2.Start(String sFilePath, String sArgs) in TOPWHSUtility.dll [ed. sic "Dianostics"]

      at McAfee.HomeServer.Console.Parts.TaskPartControl.viewQuarantinedFilesLink_LinkCl icked(Object sender, LinkLabelLinkClickedEventArgs e) in HomeServerConsoleTab.TOP.dll

      at System.Windows.Forms.LinkLabel.OnLinkClicked(LinkLabelLinkClickedEventArgs e) in System.Windows.Forms.dll

      at System.Windows.Forms.LinkLabel.OnMouseUp(MouseEventArgs e) in System.Windows.Forms.dll

      at System.Widnows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) in System.Windows.Forms.dll

      at System.Windows.Forms.Control.WndProc(Message& m) in System.Windows.Forms.dll

      at System.Windows.Forms.Label.WndProc(Message& m) in System.Windows.Forms.dll

      at System.Windows.Forms.LinkLabel.WndProc(Message& msg) in System.Windows.Forms.dll

      at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(Message& m) in System.Windows.Forms.dll

      at System.Windows.Froms.Control+ControlNativeWindow.WndProc(Message& m) in System.Windows.Forms.dll

      at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) in System.Windows.Forms.dll

      at System.Windows.Forms.UnsafeNativeMethods.DispatchMessagew(MSG& msg) in System.Windows.Forms.dll

      at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNa tiveMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) in System.Windows.Forms.dll

      at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll

      at System.Windows.Forms.Applcation+ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll

      at System.Windows.Forms.Application.Run(Form mainForm) in System.Windows.Forms.dll

      at Microsoft.HomeServer.HomeServerConsole.MainForm.Main(String[] args) in HomeServerConsole.exe

       

      Is there any way to get this info to the programmers?

       

       

      Message was edited by: nutcase1069, May 2, 2010 @ 9:08am PDT on 5/2/10 11:09:17 AM CDT