Re: Strange Exchange server 2003 on SBS 2003 behaviour

Thanks for th feedback Pavel.

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


"Pavel" <Pavel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AC8E1AD2-EA49-44C4-B8F7-F268B0651ECF@xxxxxxxxxxxxxxxx
Hi,
to close the the thread:

today we made the last experiment. As we supposed and Microsoft suggested
we decided to move exchange databases to separate disk. Now it is on the
the
disk connected to the different ide channel and everything seems to work
fine. Users can connect work with outlook and server does not freez. Seems
that the problem is solved. Do not why the server started to behave in
this
way (any hotfix or SP2?), or the free size of the disk reached some amount
or
it was combination of all problems together. I am glad the we do not have
to
reinstall the server and hope that it will work well. Thank you all for
your
help.

Pavel

"Pavel" wrote:

Hi,
I downloaded and started both BPAs. Results:

- SBS BPA 2 errors:
- to disable Offloading
- to disable Chimney

both functions are present in windows SP2. May this can be the cause

- ES BPA no errors

So I change settings recommended from SBS BPA and will see whether it
helps.
Let's hope:-)

Pavel


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

Pavel,

Download and run both Exchange BPA and SBS BPA.

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


"Pavel" <Pavel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:83E5C2B4-C535-4FC1-9B3B-08475D5658C1@xxxxxxxxxxxxxxxx
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: Error c1041724 SBS 2000
    ... Exchange Domain Server: Full ... I have tried to disable McAfee antivirus and then restart information store ... service and tried to mount database. ... Attemting to start the Microsoft Exchange Information Store "First Storage ...
    (microsoft.public.windows.server.sbs)
  • Re: big problem after applying critial updates remotely
    ... Can you go into services and manually start any stopped Exchange service? ... > My policy was to apply critical updates to my test setup ... > The Microsoft Exchange Server computer is not available. ... > Microsoft Exchange Server Information Store ...
    (microsoft.public.windows.server.sbs)
  • Re: Transaction Log Growth in Exchange Server 2003
    ... that had been looping for months...finally discovered that by manually ... one Exchange 2003 Server on ... I moved old mailboxes into a different information store on another ...
    (microsoft.public.exchange.admin)
  • Re: ExMerge - What am I doing wrong?
    ... I then went into the user's exchange advanced tab that is being merged and made sure that they had Send/Receive available for that specific user. ... I also made sure that on the information store itself that the temporary Power User had full control and wasn't denied anything. ... I gave the user full control on the exchange server in the exchange management tool. ...
    (microsoft.public.windows.server.sbs)
  • Information Store and MTA fail to start after reboot
    ... When I reboot our Exchange 2003 SP2 server the Information Store and MTA ... The server has GFI mail essentials, Microsoft Live ...
    (microsoft.public.exchange.admin)