ActiveSync, so no. Which is a fine, fine thing.
Kurt On Mon, Aug 12, 2013 at 2:22 PM, Michael B. Smith <[email protected]> wrote: > That is true in Exchange 2003. > > If Airwatch uses MAPI to connect to Exchange (vs. ActiveSync), then yes it > will need to be shut down. > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Monday, August 12, 2013 4:54 PM > To: [email protected] > Subject: Re: [Exchange] Exchange 2003 SP2 running on Server 2003 R2, fully > patched, database won't mount > > Problem (temporarily) resolved. > > Ran into the issue where the e00* logs came to the end of their naming string > - the last log was named E00FFFEF.log, and Exchange decided it couldn't go > any further. > > Renamed the log directory, created a new log directory, and the database > mounted just fine. > > However, there's one other maintenance task I need to perform: The database > is ~400gb. I'm going to be creating several new databases and moving > mailboxes out of the old database. > > From memory (and implied by this article: > http://support.microsoft.com/kb/821829/en-us), Outlook for the > mailbox(es) to be moved cannot be connected - however, we also are using > Airwatch for our MDM. Will that need to be shut down as well? > > Kurt > > On Mon, Aug 12, 2013 at 11:37 AM, Michael B. Smith <[email protected]> > wrote: >> That' a downstream error, you've got earlier errors that are more important. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Kurt Buff >> Sent: Monday, August 12, 2013 2:32 PM >> To: [email protected] >> Subject: Re: [Exchange] Exchange 2003 SP2 running on Server 2003 R2, >> fully patched, database won't mount >> >> Never mind. >> >> Calling PSS now... >> >> Kurt >> >> On Mon, Aug 12, 2013 at 11:12 AM, Kurt Buff <[email protected]> wrote: >>> All, >>> >>> Getting several errors for the main database, which is currently >>> dismounted - but the message journaling database is fine. All was >>> working up until approximately 8am this morning, AFAICT. >>> >>> I've tried to manually mount the database and get a Exchange System >>> Manager error, >>> "An internal processing error has occurred. Try restarting the >>> Exchange System Manager >>> or the Microsoft Exchange Information Store service, or both. >>> Examine the Application log >>> for events related to this error. The description fields of >>> these events will contain specific >>> error code and may contain links to Microsoft Knowledgebase >>> articles on troubleshooting >>> this problem. >>> ID no: c1041724 Exchange System Manager" >>> >>> >>> Errors in the event log are: >>> >>> Event Type: Error >>> Event Source: MSExchangeSA >>> Event Category: Monitoring >>> Event ID: 1005 >>> Date: 2013-08-12 >>> Time: 10:42:31 >>> User: N/A >>> Computer: ZXCH >>> Description: >>> Unexpected error <<0xc1050000 - The attempt to log on to the >>> Microsoft Exchange Server computer has failed. The MAPI provider failed. >>> Microsoft Exchange Server Information Store ID no: >>> 8004011d-0512-00000000>> occurred. >>> >>> >>> Event Type: Error >>> Event Source: MSExchangeSA >>> Event Category: MAPI Session >>> Event ID: 9175 >>> Date: 2013-08-12 >>> Time: 10:42:31 >>> User: N/A >>> Computer: ZXCH >>> Description: >>> The MAPI call 'OpenMsgStore' failed with the following error: >>> The attempt to log on to the Microsoft Exchange Server computer has failed. >>> The MAPI provider failed. >>> Microsoft Exchange Server Information Store ID no: >>> 8004011d-0512-00000000 >>> >>> I've restarted the Exchange services, and am still seeing the above >>> errors - ditto for rebooting the machine. >>> >>> The disks are not full. I've got 147gb free out of 278gb on the disk >>> for logs, and 121gb free out of 558gb on the disk for the database. >>> The message journaling database is at 530gb out of a 1tb drive. >>> >>> Everything mentioned in this article looks good: >>> >>> http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=E >>> x >>> change&ProdVer=6.5.6940.0&EvtID=1005&EvtSrc=MSExchangeSA&LCID=1033 >>> >>> This KB article does not apply, as I have not yet used ESEUTIL: >>> http://support.microsoft.com/kb/822449 >>> >>> I'm running through this article >>> >>> http://technet.microsoft.com/en-us/library/aa996027%28v=exchg.65%29.a >>> s >>> px >>> right now. >>> >>> Any further suggestions? >>> >>> Kurt >>> >>> >> >> > >
