SBS2003 | Windows Server 2008 - Exchange 2007
|
From: Ace Fekay [MCT] on 20 Oct 2009 23:29 "cctanaka" <cctanaka.40dznb(a)DoNotSpam.com> wrote in message news:cctanaka.40dznb(a)DoNotSpam.com... > > I have promoted second server as a Global Catalog. Event viewer logs are > OK. > I think I still need to configure DNS Server and DHCP. Is that right? > > Thank you again. > > > -- > cctanaka Good to hear! Install DNS. Allow the zone to auto-populate. Do not create any zones manually, or you will introduce a duplicate-zone problem that is complex to clean up. Refresh the DNS console until the zones show up. Once they do, change the 1st DNS entry in the new server to itself, and the second entry to the SBS server IP. In the SBS, add the new server as a second entry. I hope that helps. Ace
From: cctanaka on 21 Oct 2009 15:27 Hi, I have not seen Event viewer of SBS 2008 Server, only the second server. This last one is OK, but the main server registered several errors after restarting. Beside, Exchange stop working again. In the SBS Server there are errors in Application, I think the main are: ---------------------------------------------------- Level Date and time Source Event Identification Task Category Error 21/10/2009 08:01:56 MSExchange ADAccess 2114 Topology Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1964). Failed to discover Topology; error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad LDAP message)). -------------------------------------------------- -------------------------------------------------- Level Date and time Source Event Identification Task Category Error 21/10/2009 08:02:32 MSExchange ADAccess 2501 General Process MSEXCHANGEADTOPOLOGY (PID=1964). Fail of site monitor verifying the actual site name - Call=HrSearch Error code=80040a01. -------------------------------------------------- -------------------------------------------------- Level Date and time Source Event Identification Task Category Error 21/10/2009 08:03:36 MSExchangeIS 1121 General Error 0x96f when connecting with Microsoft Active Directory. -------------------------------------------------- I have run the Exchange Best Practice Analyzer and it seems OK. Now I have unpromoted second server again and rebooted the main server, so Exchange is working again. -- cctanaka ------------------------------------------------------------------------ cctanaka's Profile: http://forums.techarena.in/members/144719.htm View this thread: http://forums.techarena.in/small-business-server/1256973.htm http://forums.techarena.in
From: Ace Fekay [MCT] on 21 Oct 2009 20:24 "cctanaka" <cctanaka.40favb(a)DoNotSpam.com> wrote in message news:cctanaka.40favb(a)DoNotSpam.com... > > Hi, > > I have not seen Event viewer of SBS 2008 Server, only the second > server. This last one is OK, but the main server registered several > errors after restarting. Beside, Exchange stop working again. > In the SBS Server there are errors in Application, I think the main > are: > ---------------------------------------------------- > Level Date and time Source Event Identification Task Category > Error 21/10/2009 08:01:56 MSExchange ADAccess 2114 Topology Process > MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1964). Failed to discover Topology; > error 0x80040952 (LDAP_LOCAL_ERROR (Client-side internal error or bad > LDAP message)). > -------------------------------------------------- > > -------------------------------------------------- > Level Date and time Source Event Identification Task Category > Error 21/10/2009 08:02:32 MSExchange ADAccess 2501 General Process > MSEXCHANGEADTOPOLOGY (PID=1964). Fail of site monitor verifying the > actual site name - Call=HrSearch Error code=80040a01. > -------------------------------------------------- > > > -------------------------------------------------- > Level Date and time Source Event Identification Task Category > Error 21/10/2009 08:03:36 MSExchangeIS 1121 General Error 0x96f when > connecting with Microsoft Active Directory. > -------------------------------------------------- > > > I have run the Exchange Best Practice Analyzer and it seems OK. > Now I have unpromoted second server again and rebooted the main server, > so Exchange is working again. > > > -- > cctanaka Sorry to hear you are still having problems after promoting a new DC/GC. ANytime there are AD Access or DSAccess errors with Exchange, it is saying that it cannot contact AD. Keep in mind, ALL of Exchange's configuration information is not stored in Exchange, rather it is stored in AD. If it cannot contact AD, Exchange simply will not start. Apparently Exchange is discovering the new DC/GC, however it appears since Exchange is sitting on a DC/GC, may be part of the issue. I know SBS is customized to make this work, however, there are some issues that may still persist when it discovers another GC. When you discovered the errors, did you try to restart all of the Exchange services? Only as an FYI (don't make any changes), take a look at the following article (it applies to SBS 2008): Services for Exchange Server 2007 or Exchange Server 2010 cannot start automatically after you install Exchange Server 2007 and Exchange Server 2010 on a global catalog server: http://support.microsoft.com/kb/9408453 I just posted that article as an FYI, but don't make any changes yet. What I would like you to do is promote that other server one more time, but this time do not select it to be a GC. Ace
From: cctanaka on 23 Oct 2009 13:35 Hi Ace, I have promoted the second server with DCPROMO, but now I have not checked -Global Catalog, -DNS Server, RODC. After rebooted both machines, Exchange is still working. There are 3 warnings in Event Log, Application: - Event 6005, Winlogon - Event 2106, MSExchange ADAccess. Process MSExchangeADTOPOLOGYSERVICE.EXE (PID=1080). The Active Directory for Exchange failed to get DNS registers for forest ... - Event 2105, MSExchange ADAccess. Process MSExchangeADTOPOLOGYSERVICE.EXE (PID=1080). The Active Directory for Exchange failed to get DNS registers for domain mpr.local. The priority and DNS Weight of domain controllers in this domain are set to default value 0 (priority) and 100 (weight). Looking at help, I saw that Global Catalog could not be correctly registered in DNS Server (I think it is). Besides, help says to use Exchange tools to correct this problem. Any idea? Thank you. -- cctanaka ------------------------------------------------------------------------ cctanaka's Profile: http://forums.techarena.in/members/144719.htm View this thread: http://forums.techarena.in/small-business-server/1256973.htm http://forums.techarena.in
From: Ace Fekay [MCT] on 23 Oct 2009 18:29
"cctanaka" <cctanaka.40iunb(a)DoNotSpam.com> wrote in message news:cctanaka.40iunb(a)DoNotSpam.com... > > Hi Ace, > > I have promoted the second server with DCPROMO, but now I have not > checked -Global Catalog, -DNS Server, RODC. > > After rebooted both machines, Exchange is still working. There are 3 > warnings in Event Log, Application: > - Event 6005, Winlogon > - Event 2106, MSExchange ADAccess. Process > MSExchangeADTOPOLOGYSERVICE.EXE (PID=1080). The Active Directory for > Exchange failed to get DNS registers for forest ... > - Event 2105, MSExchange ADAccess. Process > MSExchangeADTOPOLOGYSERVICE.EXE (PID=1080). The Active Directory for > Exchange failed to get DNS registers for domain mpr.local. The priority > and DNS Weight of domain controllers in this domain are set to default > value 0 (priority) and 100 (weight). > > Looking at help, I saw that Global Catalog could not be correctly > registered in DNS Server (I think it is). > Besides, help says to use Exchange tools to correct this problem. > > Any idea? > Thank you. > > > -- > cctanaka > ------------------------------------------------------------------------ This is a DNS issue. Look at EventID 2106 and 2105 errors. It says it can't find something in DNS. So it points back to a DNS issue. Please provide us an updated ipconfig /all from both servers, please. Also, are all firewall instances on the new server disabled? Is the firewall on the SBS active? Ace |