Exchange Server Forums

Outlook Web Access could not connect to Microsoft Exchange

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> Outlook Web Access could not connect to Microsoft Exchange

Page: [1]

Message

<< Older Topic Newer Topic >>

Outlook Web Access could not connect to Microsoft Exchange - 28.Apr.2011 6:00:21 PM

BrianRoden

Posts: 10
Joined: 19.Jul.2007
Status: offline

We've been having some issues with ActiveSync connectivity sometimes dropping (usually at night or on the weekends, almost never when I'm in the office, which means I'm doing a lot of remote work). Usually a restart of the CAS/Hub Transport server gets it going again. But often after that reboot, we'll have issues with OWA not working. Generally an iisreset on the mailbox server, and restarting the Exchange processes on the CAS/Hub Transport gets it back. But I haven't been able to get OWA back since last night, even though our iPhones and Android phones are getting mail fine with ActiveSync

Could it have something to do with the First Administrative Group held over from Exchange 2003? We had to install a 2003 server when our division was sold to another corporation in 2007, to import our existing mailboxes from their system, then migrate them to our new Exchange 2007 system. The server name of the old Exchange 2003 server was still in some AD entries until recently, when we deleted it with ADSIEdit and were finally able to apply service packs. Now that I think about it, these errors started showing up after that edit and applying those updates. How do I change the mailbox administrative group to Exchange Administrative Group (FYDIBOHF23SPDLT)?

Request
Url: https://mailgateway.domain.net:443/owa/forms/premium/StartPage.aspx
User host address: 172.16.60.135
User: Brian Roden
EX Address: /o=Leisure Arts/ou=First Administrative Group/cn=Recipients/cn=Brian Roden
SMTP Address: Brian_Roden@domain.com
OWA version: 8.3.137.0
Mailbox server: lei-exchg1.domain.net

Exception
Exception type: Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException
Exception message: Event Manager was not created.

Call stack

Microsoft.Exchange.Data.Storage.EventPump..ctor(EventPumpManager eventPumpManager, String server, Guid mdbGuid)
Microsoft.Exchange.Data.Storage.EventPumpManager.GetEventPump(StoreSession session)
Microsoft.Exchange.Data.Storage.EventPumpManager.RegisterEventSink(StoreSession session, EventSink eventSink)
Microsoft.Exchange.Data.Storage.EventSink.InternalCreateEventSink[T](StoreSession session, EventWatermark watermark, ConstructSinkDelegate`1 constructEventSinkDelegate)
Microsoft.Exchange.Clients.Owa.Core.OwaFolderCountAdvisor..ctor(UserContext userContext, StoreObjectId folderId, EventObjectType objectType, EventType eventType)
Microsoft.Exchange.Clients.Owa.Core.OwaNotificationManager.CreateOwaFolderCountAdvisor(UserContext userContext, StoreObjectId folderId, EventObjectType objectType, EventType eventType)
Microsoft.Exchange.Clients.Owa.Premium.StartPage.OnInit(EventArgs e)
System.Web.UI.Control.InitRecursive(Control namingContainer)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Inner Exception
Exception type: Microsoft.Mapi.MapiExceptionNetworkError
Exception message: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227) Diagnostic context: ...... Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000 Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x20B3FB3F00000000 Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 3396 Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2011-04-28 21:40:32:79 Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 8 Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060 Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318 Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0 Lid: 24060 StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid: 27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115

Call stack

Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx)
Microsoft.Mapi.ExRpcAdmin.Create(String server, String user, String domain, String password)
Microsoft.Exchange.Data.Storage.EventPump..ctor(EventPumpManager eventPumpManager, String server, Guid mdbGuid)

Post #: 1

Featured Links*

RE: Outlook Web Access could not connect to Microsoft E... - 2.May2011 10:56:43 AM

BrianRoden

Posts: 10
Joined: 19.Jul.2007
Status: offline

It looks like a backup process (we just installed an AccuVault) had a file locked on the DC when the mailbox server rebooted, and it was keeping the COM processes from communicating. Once the backup finished and we started the Exchange processes, everything was good.

I think the overall problem has to do with internal network traffic. The problem with the CAS not being able to access the mailbox server seems to happen mainly when our network backup is running each night.

Is it possible to use the second NIC in each server, and another switch, to set up a redundant inter-server network to either move the backup traffic to that network, or make the CAS-to-MB server traffic use that network?

(in reply to BrianRoden)

Post #: 2

RE: Outlook Web Access could not connect to Microsoft E... - 3.May2011 9:12:14 AM

leederbyshire

Posts: 1346
Joined: 4.Jan.2006
Status: offline

If you add a second NIC, it will have a unique IP address. You should be able to configure your backup to use that IP address, or even use your internal DNS to assign a unique computer name to it. On the other hand, if it just gets everything (server name, etc.) from Active Directory, and you don't get a chance to manually configure a value, you will have less chance to influence what happens.

_____________________________

Lee.
___________________________________

Outlook Web Access for PDA and WAP:
www.leederbyshire.com
___________________________________

(in reply to BrianRoden)

Post #: 3

RE: Outlook Web Access could not connect to Microsoft E... - 3.May2011 9:41:13 AM

BrianRoden

Posts: 10
Joined: 19.Jul.2007
Status: offline

All our servers are static IP anyway. I'm thinking I'll use the second NIC in each server (these servers all came with 2 NICs on the motherboard) set to 192.168.1.xxx, where xxx matches the end of the server's regular IP address.

Then I can use that new network as a backup backbone, making sure in the backup software I specify servers by IP address (or a unique name from DNS, maybe SERVERNAME-BK)

I should leave the default gateway on the second NIC blank, right? Since no traffic will acutally be routed off the 192.168.1.xxx network.

(in reply to leederbyshire)

Post #: 4