We help IT Professionals succeed at work.

Exchange down on SBS 2011 - urgent help needed

Gerhardpet
Gerhardpet used Ask the Experts™
on
I have a SBS 2011 at a customer scheduled to reboot once a week using Level Platforms.

After the reboot today user can't connect to exchange with their outlook clients anymore. The password screen pops up and when entering the password the password screen pops right back up. I tried OWA and it works fine and emails are coming in and I can send emails too from OWA.

Here are a few error logs from application event viewwer that may be related to this problem. Please help

Log Name:      Application
Source:        MSExchange ADAccess
Date:          19/04/2012 5:05:51 AM
Event ID:      2102
Task Category: Topology
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FFISERVER.ffi.local
Description:
Process MAD.EXE (PID=2364). All Domain Controller Servers in use are not responding:
FFISERVER.ffi.local
 

Log Name:      Application
Source:        MSExchangeTransportLogSearch
Date:          19/04/2012 5:05:40 AM
Event ID:      7005
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FFISERVER.ffi.local
Description:
Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The configuration loader failed to initialize 'TransportServerConfiguration'.
   at Microsoft.Exchange.Transport.Configuration.ConfigurationLoader`2.RegisterWithAD[T](ADObjectId rootId)
   at Microsoft.Exchange.Transport.Configuration.ConfigurationLoader`2.Builder.Register[T](ADObjectId rootId)
   at Microsoft.Exchange.Transport.Configuration.ConfigurationLoader`2.Builder.Register[T]()
   at Microsoft.Exchange.Transport.Configuration.ConfigurationLoader`2.Load()
   at Microsoft.Exchange.Transport.Logging.Search.LogSearchService.BeginStart(Object state).

Log Name:      Application
Source:        MSExchangeThrottling
Date:          19/04/2012 5:05:38 AM
Event ID:      1002
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FFISERVER.ffi.local
Description:
The Microsoft Exchange Throttling Service encountered an Active Directory error while building an RPC security descriptor. This failure may indicate that no Domain Controllers are available at this time. The service will be stopped. Failure details: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
   at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
   at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()
   at Microsoft.Exchange.Data.Directory.ADSession.GetConfigurationNamingContext()
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.GetWellKnownExchangeGroupSid(Guid wkguid)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.GetExchangeServersUsgSid()
   at Microsoft.Exchange.Data.ThrottlingService.ThrottlingRpcServerImpl.GetRpcSecurityDescriptor()
   at Microsoft.Exchange.Data.ThrottlingService.ThrottlingRpcServerImpl.<>c__DisplayClass1.<TryGetRpcSecurityDescriptor>b__0()
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)


Log Name:      Application
Source:        MSExchangeRepl
Date:          19/04/2012 5:05:35 AM
Event ID:      2121
Task Category: Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FFISERVER.ffi.local
Description:
The Microsoft Exchange Replication service failed to start the TCP listener. Error: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
   at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
   at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()
   at Microsoft.Exchange.Data.Directory.ADSession.GetConfigurationNamingContext()
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.GetWellKnownExchangeGroupSid(Guid wkguid)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.GetExchangeServersUsgSid()
   at Microsoft.Exchange.Cluster.Replay.RemoteDataProvider.StartListening()


And some more
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Can you ping DC...Check if there is any errors on dc..

Commented:
put the exchange services n manual and boot again,
check eventvwr for errors regarding the DC on the SBS2011
startup the exchange services manually and verify the eventvwr

Author

Commented:
Yes I can ping it by name and get response. SBS 2011 DC is working fine...I have a pervasive database on and users can access it no problems
Kini pradeepDevelopment Manager

Commented:
Its SBs so the DC and the Exchange are on the same Server, let me know if this is not correct.
From the SBS server if you do a nltest /dsgetdc does it show the DC?

could you quickly run a Dcdiag / V and pipe the output here

Author

Commented:
Yes here it is

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   * Verifying that the local machine FFISERVER, is a Directory Server.
   Home Server = FFISERVER
   * Connecting to directory service on server FFISERVER.
   * Identified AD Forest.
   Collecting AD specific global data
   * Collecting site info.
   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ffi,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSi
teSettings),.......
   The previous call succeeded
   Iterating through the sites
   Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ffi,DC=loc
al
   Getting ISTG and options for the site
   * Identifying all servers.
   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=ffi,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),
.......
   The previous call succeeded....
   The previous call succeeded
   Iterating through the list of servers
   Getting information for the server CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Co
nfiguration,DC=ffi,DC=local
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   * Identifying all NC cross-refs.
   * Found 1 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\FFISERVER
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         Determining IP4 connectivity
         * Active Directory RPC Services Check
         ......................... FFISERVER passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\FFISERVER
      Starting test: Advertising
         The DC FFISERVER is advertising itself as a DC and having a DS.
         The DC FFISERVER is advertising as an LDAP server
         The DC FFISERVER is advertising as having a writeable directory
         The DC FFISERVER is advertising as a Key Distribution Center
         The DC FFISERVER is advertising as a time server
         The DS FFISERVER is advertising as a GC.
         ......................... FFISERVER passed test Advertising
      Test omitted by user request: CheckSecurityError
      Test omitted by user request: CutoffServers
      Starting test: FrsEvent
         * The File Replication Service Event log test
         ......................... FFISERVER passed test FrsEvent
      Starting test: DFSREvent
         The DFS Replication Event Log.
         Skip the test because the server is running FRS.
         ......................... FFISERVER passed test DFSREvent
      Starting test: SysVolCheck
         * The File Replication Service SYSVOL ready test
         File Replication Service's SYSVOL is ready
         ......................... FFISERVER passed test SysVolCheck
      Starting test: KccEvent
         * The KCC Event log test
         Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
         ......................... FFISERVER passed test KccEvent
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configurati
on,DC=ffi,DC=local
         Role Domain Owner = CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configurati
on,DC=ffi,DC=local
         Role PDC Owner = CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=ffi,DC=local
         Role Rid Owner = CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=ffi,DC=local
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites
,CN=Configuration,DC=ffi,DC=local
         ......................... FFISERVER passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         Checking machine account for DC FFISERVER on DC FFISERVER.
         * SPN found :LDAP/FFISERVER.ffi.local/ffi.local
         * SPN found :LDAP/FFISERVER.ffi.local
         * SPN found :LDAP/FFISERVER
         * SPN found :LDAP/FFISERVER.ffi.local/FFI
         * SPN found :LDAP/cf8d0660-654b-4b53-a709-1c581a29e656._msdcs.ffi.local
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/cf8d0660-654b-4b53-a709-1c581a29e656/ffi.local
         * SPN found :HOST/FFISERVER.ffi.local/ffi.local
         * SPN found :HOST/FFISERVER.ffi.local
         * SPN found :HOST/FFISERVER
         * SPN found :HOST/FFISERVER.ffi.local/FFI
         * SPN found :GC/FFISERVER.ffi.local/ffi.local
         ......................... FFISERVER passed test MachineAccount
      Starting test: NCSecDesc
         * Security Permissions check for all NC's on DC FFISERVER.
         * Security Permissions Check for
           DC=ForestDnsZones,DC=ffi,DC=local
            (NDNC,Version 3)
         * Security Permissions Check for
           DC=DomainDnsZones,DC=ffi,DC=local
            (NDNC,Version 3)
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=ffi,DC=local
            (Schema,Version 3)
         * Security Permissions Check for
           CN=Configuration,DC=ffi,DC=local
            (Configuration,Version 3)
         * Security Permissions Check for
           DC=ffi,DC=local
            (Domain,Version 3)
         ......................... FFISERVER passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         Verified share \\FFISERVER\netlogon
         Verified share \\FFISERVER\sysvol
         [FFISERVER] User credentials does not have permission to perform this operation.
         The account used for this test must have network logon privileges
         for this machine's domain.
         ......................... FFISERVER failed test NetLogons
      Starting test: ObjectsReplicated
         FFISERVER is in domain DC=ffi,DC=local
         Checking for CN=FFISERVER,OU=Domain Controllers,DC=ffi,DC=local in domain DC=ffi,DC=local on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=f
fi,DC=local in domain CN=Configuration,DC=ffi,DC=local on 1 servers
            Object is up-to-date on all servers.
         ......................... FFISERVER passed test ObjectsReplicated
      Test omitted by user request: OutboundSecureChannels
      Starting test: Replications
         * Replications Check
         [Replications Check,FFISERVER] DsReplicaGetInfo(PENDING_OPS, NULL) failed, error 0x2105
         "Replication access was denied."
         ......................... FFISERVER failed test Replications
      Starting test: RidManager
         * Available RID Pool for the Domain is 1614 to 1073741823
         * FFISERVER.ffi.local is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 1114 to 1613
         * rIDPreviousAllocationPool is 1114 to 1613
         * rIDNextRID: 1186
         ......................... FFISERVER passed test RidManager
      Starting test: Services
         * Checking Service: EventSystem
         * Checking Service: RpcSs
         * Checking Service: NTDS
            Could not open NTDS Service on FFISERVER, error 0x5 "Access is denied."
         * Checking Service: DnsCache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... FFISERVER failed test Services
      Starting test: SystemLog
         * The System Event log test
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:35:13
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:35:14
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:35:29
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:40:56
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:40:57
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:41:13
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:43:43
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.16 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:43:50
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.23 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:44:13
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.16 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:44:49
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.16 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:46:41
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:46:43
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:46:57
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:49:06
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.16 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:52:25
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:52:26
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:52:41
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:58:08
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:58:15
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   07:58:25
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:01:36
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.17 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:03:53
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:04:00
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:04:08
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:09:36
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:09:37
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:09:52
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:15:20
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:15:21
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:15:36
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:21:04
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:21:05
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.5 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:21:06
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:21:20
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:26:48
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:26:48
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.5 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:26:49
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.6 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:27:04
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.1 using any of the configured protocols.
         An error event occurred.  EventID: 0xC0002719
            Time Generated: 04/19/2012   08:32:31
            Event String:
            DCOM was unable to communicate with the computer 192.168.16.3 using any of the configured protocols.
         ......................... FFISERVER failed test SystemLog
      Test omitted by user request: Topology
      Test omitted by user request: VerifyEnterpriseReferences
      Starting test: VerifyReferences
         The system object reference (serverReference) CN=FFISERVER,OU=Domain Controllers,DC=ffi,DC=local and backlink
         on CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ffi,DC=local are correct.
         The system object reference (serverReferenceBL)
         CN=FFISERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=ffi,DC=local and
         backlink on
         CN=NTDS Settings,CN=FFISERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ffi,DC=local
         are correct.
         The system object reference (frsComputerReferenceBL)
         CN=FFISERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=ffi,DC=local and
         backlink on CN=FFISERVER,OU=Domain Controllers,DC=ffi,DC=local are correct.
         ......................... FFISERVER passed test VerifyReferences
      Test omitted by user request: VerifyReplicas

      Test omitted by user request: DNS
      Test omitted by user request: DNS

   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : ffi
      Starting test: CheckSDRefDom
         ......................... ffi passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ffi passed test CrossRefValidation

   Running enterprise tests on : ffi.local
      Test omitted by user request: DNS
      Test omitted by user request: DNS
      Starting test: LocatorCheck
         GC Name: \\FFISERVER.ffi.local
         Locator Flags: 0xe00033fd
         PDC Name: \\FFISERVER.ffi.local
         Locator Flags: 0xe00033fd
         Time Server Name: \\FFISERVER.ffi.local
         Locator Flags: 0xe00033fd
         Preferred Time Server Name: \\FFISERVER.ffi.local
         Locator Flags: 0xe00033fd
         KDC Name: \\FFISERVER.ffi.local
         Locator Flags: 0xe00033fd
         ......................... ffi.local passed test LocatorCheck
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
         provided.
         ......................... ffi.local passed test Intersite

Author

Commented:
Yes it is a SBS 2011 with exchange on the same box
Commented:
restart the netlogon service, check for errors
if no erros, check exchange/olk, if still issues, restart the exchange services

Author

Commented:
I found that these 2 services did not start which are set to Automatic but are not started

They are:
1 Microsoft Exchange RPC Client Access
2 Microsoft Exchange Address Book

After starting both services everything is back to normal.

Any idea why they would not have started?

Commented:
should be in the eventvwr,
any patches installed before the reboot?

Author

Commented:
Yes it did install some updates but I would have to check which once. It could be related. I will reboot one more time after hours to see if the problem comes back.
Kini pradeepDevelopment Manager

Commented:
Microsoft Exchange RPC Client Access is responsible for outlook connections.
Have you tried rebooting the workstation(s)
I always get my users to reboot after a server reboot.

Mark

Commented:
workstation reboot is not required for exchange, outlook will reconnect automatically
Hi.

I have had this happen a few times with SBS 2011. In most cases, setting tthe RPC Client Access Service to 'Automatic (delayed)' start has resolved the issue. It must be a timing issue where the service is attempting to start before something that is depends upon has been completed (i.e. another service starting etc) but I have not yet determined what that is.
Hi X treeme,

On all my networks, it doesn't. It prompts for a password.
But, that might be just how my customers are setup. So I am not totally disgreeing with you. But it is worth a try.

Mark
As long as Exchange is working correctly and the RPC Client Access Service is operational, a restart of Outlook is all that is required. The password prompt is because Outlook cannot connect to the server (as it is offline) and therefore thinks the password is wrong.
OK. That makes sense. I insist all my users reboot before calling the helpdesk. So I never really get calls about this. Sorry Author for going a little off topic.

Mark