Re: Strange Exchange server 2003 on SBS 2003 behaviour

Hi,
the server is original IBM x206 server and we also thought that this
is hardware problem. We contacted official service office and discussed
the problem. They told us that this seems to be software problem. We
upgraded all drives and firmware but it did not help. So we decided to
do original hardware tests in this service office. They made all tests
and did not find any problem. Scan disk did not find any error. Now we
are trying to find software problem before we made fresh installation.
As I wrote after creating new offline .ost file it worked fine till
another user with old .ost file tried to synchronize with Exchange
server. That is why we are looking for software problem. As for the BPA I
did not run any of them. Database is small (around 500 MBs for both private
and public store), there is around 50 GBs of free space on the disk.

Pavel

"John Oliver, Jr. [MVP]" wrote:

Have you verified or ruled out your hardware, ie, hard drives, controller?
If you are getting drive errors then it could be one of your drives is
failing. Have you downloaded and run Exchange BPA and Small Business BPA?
Any related errors in the Event Viewer Application log? Have you verified
you are not running low on disk space or database file reaching its limit?

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Pavel Naplava" <pavel.naplava@xxxxxxxxxx> wrote in message
news:eaiABNKIIHA.6068@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
in lastg 3 weeks we discover following strange behaviour of our SBS 2003
Standard server. What happens:
- server have started to freez after some time and we had to provide hard
reset it
- in logs there were informations about NTFRs error, and the aarich drive
errors
- we thought that the problem is connected with NTFRs error and provided
all recommended steps found on Internet (stop service, change timeouts
etc.) and also discovered broken information store databes so we repaired
it with eseutil
- it seemed that everything is working well, opening outlook on server was
fine, all files and service were accessible and working well
- but when the first user connected to the server and started outlook the
server again started to freez and the behaviour was the same.
- we made some test and discovered that the information store database was
again broken. So we disabled local caching (offline store of messages) on
user client PC with outlook, deleted OST file and repaired information
store database
- after restart of the server and new logon of the user we started
outlook. It synchronized, we reenabled offline store and everything seems
working well.
- today another user with similar client configuration came to the office,
loggged on to the network, started outlook and the behaviour was the same.
Server freezed and we had to restard. Information store database seems to
be broken again.

My question - why it happpens? Where is the problem? Everything worked
well and we do not know why it started to do this problems. Why the
information store database is broken after starting synchronization
between outlook and exchange server? If we repair database and start
outlook on server, it works without problems any time. Any help?

Our configuration:
- SBS 2003 standard, SP2 for both server and ES, all hotfixes, emails
downloaded to server by using POP3 connector
- windows XP, office 2003

Thank you for any help and recommendation.

Regards,

Pavel Naplava



.

Relevant Pages

  • Re: SBS 2003 Exchange problem
    ... the server is original IBM x206 server and we also thought that this is hardware problem. ... So we decided to do original hardware tests in this service office. ... - but when the first user connected to the server and started outlook the server again started to freez and the behaviour was the same. ... So we disabled local caching on user client PC with outlook, deleted OST file and repaired information store database ...
    (microsoft.public.windows.server.sbs)
  • Re: Strange Exchange server 2003 on SBS 2003 behaviour
    ... Have you verified or ruled out your hardware, ie, hard drives, controller? ... Standard server. ... - but when the first user connected to the server and started outlook the ... Information store database seems to ...
    (microsoft.public.exchange.admin)
  • Re: SBS 2003 Exchange problem
    ... in lastg 3 weeks we discover following strange behaviour of our SBS ... 2003 Standard server. ... - but when the first user connected to the server and started outlook the server again started to freez and the behaviour was the same. ... So we disabled local caching on user client PC with outlook, deleted OST file and repaired information store database ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Information Store Unresponsive
    ... I know it's very hard to disable AV software in a production environment especially it is your client's server not your own. ... Exchange related engine and database files. ... By the way, I saw you have Backup Exec software installed, if you use it to backup Exchange database, please also consider excluding Exchange backup job to have a try. ... As I mentioned in my last email, finally you may also consider creating a new Information Store database and use "two-step" Exmerge tool to migrate Mailbox data to new Information Store database ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Exchange problem
    ... the server is original IBM x206 server and we also thought that this ... timeouts etc.) and also discovered broken information store databes so ... - but when the first user connected to the server and started outlook ... - we made some test and discovered that the information store database ...
    (microsoft.public.windows.server.sbs)
Loading