Hi there,
We have an SBS 2003 server that had a disk fault.
We managed to get everything backup and working, but as the log files were
corrupt we had to remove all log files and do an eseutil /p to reapir the
databse.
One user was not receiving e-mail after the fix, so a restart of the IS was
ca
Did you run an isinteg after the db repair?
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Graeme Carstairs [mailto:loonyto...@gmail.com]
Sent: Monday, July 25, 2011 8:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 cannot start information
eme Carstairs [mailto:loonyto...@gmail.com]
> *Sent:* Monday, July 25, 2011 8:37 AM
> *To:* MS-Exchange Admin Issues
> *Subject:* Exchange 2003 cannot start information store 1053 error
>
> ** **
>
> Hi there,
>
> ** **
>
> We have an SBS 2003 server that had
EXCHMEM.DLL - has the version been changed for any reason (EG installing
Exmerge)?
From: Graeme Carstairs [mailto:loonyto...@gmail.com]
Sent: Monday, July 25, 2011 8:37 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 cannot start information store 1053 error
Hi there,
We have
xmerge)?
>
> ** **
>
> *From:* Graeme Carstairs [mailto:loonyto...@gmail.com]
> *Sent:* Monday, July 25, 2011 8:37 AM
> *To:* MS-Exchange Admin Issues
> *Subject:* Exchange 2003 cannot start information store 1053 error
>
> ** **
>
> Hi there,
>
> ** **
>
&g
*From:* Graeme Carstairs [mailto:loonyto...@gmail.com]
>> *Sent:* Monday, July 25, 2011 8:37 AM
>> *To:* MS-Exchange Admin Issues
>> *Subject:* Exchange 2003 cannot start information store 1053 error
>>
>> ** **
>>
>> Hi there,
>>
>> ** **
