RE: SBS2008 Console Stops Responding

Tech-Archive recommends: Speed Up your PC by fixing your registry

I agree,

I never truly thought it was a problem with Trend because the console worked
until I installed the rollup. As soon as I uninstalled the rollup the problem
was corrected. But I did read something about the Trend reporting something
that the rollup didn't like. That is why I posted the entire FATAL log. Hope
Robbin or someone can help!

Thanks
Nick

"Vasilios" wrote:

Nick,

I don't think its an issue with Trend Micro installed. This is a duplicate
key being registered. I was having this problem with no other A/V program
installed. I simply uninstalled the rollup and the problem went away. I
will be installed Trend Micro Worry-Free Business Security Advanced to see if
that affects it though.

--
Vasilios Kalaitzidis
Throttle Worx


"Nick" wrote:

Thank you for your detailed reply. I did some research on the net for this. I
found a site that talked about a similar situation. We are using Trend WFBS
5.1. I honestly don't know if this is part of the problem.

I only have one AV software on the server and only installed it once. Here
is part of the log file for one of the crashes.

[11072] 090227.171954.5574: Admin: !!!!FATAL: Console shutting down due to
unhandled exception: An item with the same key has already been added.
[11072] 090227.171954.5574: Exception:
---------------------------------------
An exception of type 'Type: System.ArgumentException, mscorlib,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has
occurred.
Timestamp: 02/27/2009 17:19:54
Message: An item with the same key has already been added.
Stack:
Server stack trace:
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue
value, Boolean add)
at System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value)
at
Microsoft.WindowsServerSolutions.AntiVirus.Infrastructure.AntivirusProductCollection.Add(AntivirusProduct avProduct)
at
Microsoft.WindowsServerSolutions.AntiVirus.ServerSideClientReporting.SecurityCenterAVProductCollection.Add(AntivirusProduct avProduct)
at
Microsoft.WindowsServerSolutions.AntiVirus.ServerSideClientReporting.SSCRSecurityCenterFromDataStore.ProcessSecurityCenterAntivirus(String
clientIdentity, SecurityCenterAVProductCollection avCollection)
at
Microsoft.WindowsServerSolutions.AntiVirus.ServerSideClientReporting.SSCRSecurityCenterFromDataStore.QueryAVProducts(String clientIdentity)
at
Microsoft.WindowsServerSolutions.AntiVirus.Infrastructure.AntimalwareClient.QueryAntimalwareProducts()
at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,
Object[]& outArgs)
at
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message
reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed,
MessageData& msgData)
at
Microsoft.WindowsServerSolutions.AntiVirus.Infrastructure.QueryAVClientDelegate.EndInvoke(IAsyncResult result)
at
Microsoft.WindowsServerSolutions.AntiVirus.Infrastructure.AntimalwareReport.EndAVClientQuery(IAsyncResult asyncResult)
at
System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(IMessage msg)
at
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
at
System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at
System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object
state)



""Robbin Meng [MSFT]"" wrote:



Hi Nick,


Thanks for your feedback. I fully understand your situation and will try my best to be of any help on this issue.

I have been working on this issue these days and performed some further research. Actually, we have found several similar SBS console crash cases.
However, please be assured this is not a common issue nor "bug" for SBS 2008 rollup 1 update.


Based on research and discussion, there are generally two scenarios based on the error message logged in "console.log" file. The "console.log" file by
default is located under C:\Program Files\Windows Small Business Server\Logs.

1. If the error message "FATAL: Console shutting down due to unhandled exception: Exception has been thrown by the target of an invocation." is logged;

For this situation, we need to use LDP query to search AD database to check dNSHostName for the duplicate machine name. Usually, we can remove
the duplicated dNSHostName to fix this issue.


2. If the error message "FATAL: Console shutting down due to unhandled exception: An item with the same key has already been added." is logged;

If so, it is related to multiple antivirus programs installed on the server(and not properly cleaned up upon uninstall). Duplicated AV entries are left in
database and we may have to use wbemtest to remove the invalid instance in its WMI securitycenter for the same AV name/version.

For this situation, as you did, we can temporarily uninstall SBS rollup 1 as a work round.


Therefore, in order to narrow down the root causes for this issue to reinstall Rollup 1 update, please let me check the problematic console.log before we
perform further steps.

Information Need
==============
Please send the console.log under C:\Program Files\Windows Small Business Server\Logs to me for further research at : v-robmen@xxxxxxxxxxxxx .

Hope this helps and thanks for your time and efforts.


Best regards,
Robbin Meng(MSFT)



.

Relevant Pages

  • RE: SBS2008 Console Stops Responding
    ... System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink) ... please be assured this is not a common issue nor "bug" for SBS 2008 rollup 1 update. ... we need to use LDP query to search AD database to check dNSHostName for the duplicate machine name. ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 SP4 Update Rollup "Sticking"
    ... Thanks again Robert. ... I didn't manually run spuninst.exe to initiate the uninstalls of the Rollup. ... I used the entry in "Add/Remove Programs", which I assume does that anyway. ... If the uninstall can be run with a "verbose" option, I will try that and see ...
    (microsoft.public.windowsupdate)
  • RE: SBS2008 Console Stops Responding
    ... please be assured this is not a common issue nor "bug" for SBS 2008 rollup 1 update. ... we need to use LDP query to search AD database to check dNSHostName for the duplicate machine name. ... For this situation, as you did, we can temporarily uninstall SBS rollup 1 as a work round. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2008 Console Stops Responding
    ... I don't think its an issue with Trend Micro installed. ... I was having this problem with no other A/V program ... please be assured this is not a common issue nor "bug" for SBS 2008 rollup 1 update. ... we need to use LDP query to search AD database to check dNSHostName for the duplicate machine name. ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA is bust...
    ... Can't uninstal Rollup 5. ... During uninstall the installer displays a dialog looking for EXCHANGESERVER.msi ... Delete owa virtual directory from exchange 07 command shell (replace ...
    (microsoft.public.windows.server.sbs)