Mark Minasi's Reader Forum - Mysterious issues in the event log

Mark Minasi's Reader Forum

Username:	Password:
Save Password
Forgot your Password?

All Forums

HALP! Questions on Windows and Windows Server

Small Business Server

Mysterious issues in the event log

New Topic

Reply to Topic

Printer Friendly

Author

Topic

apinzari
Welcome Newcomer

Canada
3 Posts
Status: offline

Posted - 09/08/2011 : 5:02:51 PM

Hello everybody!

I am new to this forum, but definitely not new to Mark's books. Unfortunately they do not cover SBS a whole lot and recently I've inherited an organization with a SBS 2008 server that is acting up and showing a lot of issues that you would normally not see on a production SBS server.

It is a small siszed business with less than 20 users. They have a single Dell PowerEdge server running SBS 2008 SP 2. It hosts the AD and Exchange, as well as user documents.

The event log is showing the following reoccuring alerts and errors:

Log Name: Directory Service
Source: Microsoft-Windows-ActiveDirectory_DomainService
Date: 7/9/2011 6:04:48 PM
Event ID: 1153
Task Category: DS Schema
Level: Warning
Keywords: Classic
User: ANONYMOUS LOGON
Computer: WIN-Z3F7AVZBURH
Description:
Internal event: The following schema class has a superclass that is not valid.

Class identifier:
415106026
Class name:
msExchNotesConnector (different Events show different Class Names)
Superclass identifier:
196659

Inheritance was ignored.

--------------------------------------------------------------------

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 8/30/2011 12:08:48 PM
Event ID: 10009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SANDB2008.s****d2.local
Description:
DCOM was unable to communicate with the computer D9N6N5H1-ERIN.s****d2.local using any of the configured protocols.

I realize for this one it may be something with that particular workstation, but still, perhaps a server specific issue?

-------------------------------------------------------------------

There are also a ton of MSExchange Topology errors (which I'm assuming are related to schema errors that are indicated by the alerts mentioned earlier). Some examples are:

Process STORE.EXE (PID=18172). Exchange Active Directory Provider failed to obtain DNS records for domain s****d2.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).

Process STORE.EXE (PID=18172). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC).

A route to Mailbox server CN=server002,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=s****d2,DC=local could not be found for store CN=Mailbox Store (server002),CN=First Storage Group,CN=InformationStore,CN=server002,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=s****d2,DC=local in routing tables with timestamp 8/27/2011 8:59:28 PM. Recipients will not be routed to this store.

If anyone can assist me with dealing with these issues, as all online references point to cases where there are more than 1 DC (which is not the case here). I suspect a 2003 -> 2008 migration was performed, but performed very poorly (i.e. The "First Storage Group" container reminiscent from Exchange 2003) ... I was just wondering, what would be the next step as far as fixing this system would be (clean reinstall is excluded) and would very much appreciate the assistance of this community.

Sincerely,

Adrian

Edited by - apinzari on 09/14/2011 1:40:49 PM

wkasdo
Administrator

Netherlands
7403 Posts
Status: offline

Posted - 09/09/2011 : 02:47:04 AM

Hi Adrian,

Welcome...

> Internal event: The following schema class has a superclass that is not valid.

This event is normal at the moment that the schema is extended. Is it really being generated, still?

> DCOM was unable to communicate with the computer D9N6N5H1-ERIN.sealbedard2.local using any of the configured protocols.

Could be a DNS setup error.

> Process STORE.EXE (PID=18172). Exchange Active Directory Provider failed to obtain DNS records for domain sealbedard2.local.

Could be a DNS setup error.

Maybe the Exchange guys can shed some light on this.

Make it as simple as you can, but not simpler -- Albert Einstein

wobble_wobble
Honorable But Hopeless Addict

Ireland
4516 Posts
Status: offline

Posted - 09/13/2011 : 01:29:33 AM

I've answered the other Exchange question, but can we pull it all back into here as SBS is somewhat different to a standalone Exchange Server.

With regard to deleting the items from AD about Ex2003, please do not.

Before you go any further, please tell us some of the following;

What migration method was used to migrate from SBS 2003 to SBS 2008?
Was it followed and completed?
Was it successful?
Have you had any odd issues with Exchange and Outlook, Out of Office, GAL, Synching?

Joe

After everything that has happened during the month of Jan 07, I do believe that pigs fly backwards!

http://whatismyv6.com/

Jazzy
Administrator

Netherlands
1926 Posts
Status: offline

Posted - 09/13/2011 : 02:20:43 AM

I agree with Joe, there's no point in having this discussion in two different place. I will repeat my comments from the other thread:

You should've remove the Recipient Update Services during the upgrade steps, after removal of the Exchange 2003 server. The Administrative Group should not be removed, just leave it there.

The error might indicate a problem with your routing group connector between the E2003 and E2010 routing groups.

I suggest you go over the migration steps again and be very carefull at each step. What guidance did you use anyway?

Jetze Mellema

Exchange specialist
Former MVP (2005-2012)
My blog: http://jetzemellema.blogspot.com (Dutch)
My company: http://www.imara-ict.nl/

Jazzy
Administrator

Netherlands
1926 Posts
Status: offline

Posted - 09/13/2011 : 02:30:04 AM

More specific, there is an excellent guide to migrate from SBS 2003 to SBS 2008 but obviously this hasn't been used. Have a look here: http://www.microsoft.com/download/en/details.aspx?id=4023

Make sure to read the section titled "Tasks to complete prior to uninstalling Exchange Server 2003" Some of the tasks you can run anyway, like the removal of the Recipient Update Services objects from Active Directory. Other taks you can't, like dragging the PF hierarchie to the new administrative group, need to investigate that.

Jetze Mellema

Exchange specialist
Former MVP (2005-2012)
My blog: http://jetzemellema.blogspot.com (Dutch)
My company: http://www.imara-ict.nl/

apinzari
Welcome Newcomer

Canada
3 Posts
Status: offline

Posted - 09/13/2011 : 5:37:24 PM

Thank you for your assistance everybody!

As far as how the migration was performed and how diligently were the Microsoft guides followed - unfortunately I cannot vouch for that. It was done long before I took over the responsibilities of my former counterpart.

- No issues are reported so far. But, there are a few reasons why I took into investigating these issues:

1) The company experienced some mail server downtime and in the abundence of DCOM and MSExchange Routing errors it is hard to determine what are "ghost" issues which do not affect performance and functionality at all and which ones are signs of a degrading Exchange server
2) Having a clean event log (or at least as clean as possible) is something I think is vital on the long run when upgrades come around and just in everyday operations.

So there will be no harm in re-running some Exchange 2003 - > 2007 migration procedures now that E2K7 is installed?

Also, as far as DNS issues causing the DCOM entries - the only thing that I've found was that the DHCP server on the SBS box was not set to update client A/PTR records. It is no longer the case now, so we'll see if the DCOM errors dissapear as clients renew their leases.

Thank you again!

Edited by - apinzari on 09/13/2011 5:46:56 PM

peterlwj
Here To Stay