Re: Strange Exchange server 2003 on SBS 2003 behaviour

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: Strange Exchange server 2003 on SBS 2003 behaviour
    ... Download and run both Exchange BPA and SBS BPA. ... the server is original IBM x206 server and we also thought that this ... Information store database seems ...
    (microsoft.public.exchange.admin)
  • Re: The target principal name is incorrect. (-2146893022)
    ... I was reading about the BPA, I will give these a try. ... I did re-run the CEICW ... Microsoft Internet Security and Acceleration Server Best Practices ... Are you running ISA Server on your SBS box? ...
    (microsoft.public.windows.server.sbs)
  • Re: Strange Exchange server 2003 on SBS 2003 behaviour
    ... we decided to move exchange databases to separate disk. ... Users can connect work with outlook and server does not freez. ... SBS BPA 2 errors: ... etc.) and also discovered broken information store databes so we ...
    (microsoft.public.exchange.admin)
  • Re: SBS server cant browse internet, but can see lan
    ... I should slap myself for nothing thinking of triying the bpa. ... Let's see what the SBS 2003 BPA has to say about your configuration... ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... secondary on all of my workstations so they could get out to the world ...
    (microsoft.public.windows.server.sbs)
  • Re: best practice analyzer help
    ... you're feeding to BPA. ... Trace files should be files generated by SQL Server ... > the log file cannot be found anywhere on the server or in my pc that I run> it from... ...
    (microsoft.public.sqlserver.tools)