• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Exchange failing weekly

B

Billy Gareth

#1
Scenario: Usually every 4-5 days, sometimes more, sometimes less users will
say that Outlook is saying that it is connected but no emails are coming
through. If they restart Outlook then it doesn't connect properly to Exchange.

If I try and restart Exchange server, it takes ages then fails with a 1053
error. The state then gets stuck in the "stopping" state and the only way to
resolve in a complete server restart.

May not happen for weeks then happens weekly again for a few weeks.
Failure generally seems to happen overnight at some time as compliants
already come through first thing in the morning.

Has done this since install 2 years ago but not consistent. So think that it
is all good for months then starts again.

These errors show in event viewer
LDAP Bind was unsuccessful on directory server.servername.local for
distinguished name ''. Directory returned error:[0x51] Server Down. 8026

The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified
component could not be found in the configuration information. The service
could not be initialized. Make sure that the operating system was installed
properly. 8250

Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
responding:
server.server.local.local

Have run toubleshooting assistant many times and fixed issues that were
found or found no issues.

Am out of ideas...

SBS 2003 standard
Exchange SP3
17 mailboxes
Prviate DB = 13.4GB
Public DB = 28MB
DB limit patch applied

Thanks,

Billy
 
L

Larry Struckmeyer[SBS-MVP]

#2
Hi Bill:

Using www.eventid.net, or a search engine, have you tracked down the cause
and tried to repair any of those errors?

Have you run the SBS BPA and fixed everything it finds? Also the health
monitor?

Microsoft Windows Small Business Server 2003 Best Practices Analyzer

http://www.microsoft.com/downloads/...7A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Microsoft IT Environment Health Scanner
http://www.microsoft.com/downloads/...DF-1A5B-4FB6-A8A6-657A7968BD11&displaylang=en

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com
 
B

Billy Gareth

#3
Hi Larry,
Thanks for your post.
Yes have looked up various event IDs and gone an various goose chases search
as disabling desktop search and various other suggestions but to no avail

Have run BPA and sorted out the few issues such as bottlenecks that it found

Will try the Health scanner

Billy

"Larry Struckmeyer[SBS-MVP]" wrote:

> Hi Bill:
>
> Using www.eventid.net, or a search engine, have you tracked down the cause
> and tried to repair any of those errors?
>
> Have you run the SBS BPA and fixed everything it finds? Also the health
> monitor?
>
> Microsoft Windows Small Business Server 2003 Best Practices Analyzer
>
> http://www.microsoft.com/downloads/...7A-DE19-49BB-800F-352F3B6F2922&displaylang=en
>
> Microsoft IT Environment Health Scanner
> http://www.microsoft.com/downloads/...DF-1A5B-4FB6-A8A6-657A7968BD11&displaylang=en
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>
> .
>
 
A

Ace Fekay [MVP - Directory Services]

#4
On Mon, 19 Apr 2010 15:01:02 -0700, Billy Gareth
<BillyGareth@newsgroup> wrote:

>Hi Larry,
>Thanks for your post.
>Yes have looked up various event IDs and gone an various goose chases search
>as disabling desktop search and various other suggestions but to no avail
>
>Have run BPA and sorted out the few issues such as bottlenecks that it found
>
>Will try the Health scanner
>
>Billy
>
Billy,

Can you post an unedited ipconfig /all, please? That will help us
eliminate any basic configuration issues that may exist.

Thanks
Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.
 
M

Michael D

#5
On Apr 19, 2:50 am, Billy Gareth
<BillyGar...@newsgroup> wrote:

> Scenario: Usually every 4-5 days, sometimes more, sometimes less users will
> say that Outlook is saying that it is connected but no emails are coming
> through. If they restart Outlook then it doesn't connect properly to Exchange.
>
> If I try and restart Exchange server, it takes ages then fails with a 1053
> error. The state then gets stuck in the "stopping" state and the only wayto
> resolve in a complete server restart.
>
> May not happen for weeks then happens weekly again for a few weeks.
> Failure generally seems to happen overnight at some time as compliants
> already come through first thing in the morning.
>
> Has done this since install 2 years ago but not consistent. So think thatit
> is all good for months then starts again.
>
> These errors show in event viewer
> LDAP Bind was unsuccessful on directory server.servername.local for
> distinguished name ''. Directory returned error:[0x51] Server Down.  8026
>
> The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified
> component could not be found in the configuration information.  The service
> could not be initialized.  Make sure that the operating system was installed
> properly. 8250
>
> Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
> responding:
> server.server.local.local
>
> Have run toubleshooting assistant many times and fixed issues that were
> found or found no issues.
>
> Am out of ideas...
>
> SBS 2003 standard
> Exchange SP3
> 17 mailboxes
> Prviate DB = 13.4GB
> Public DB = 28MB
> DB limit patch applied
>
> Thanks,
>
> Billy
Antivirus can do this. Symantec for Microsoft Exchange can lock up
Exchange like this. If the server has less than 3 GB of real memory it
will be a random problem. I have had trouble when users try to update
meetings. You should see errors in Symantec a few minutes or hours
before Exchange locks up.
 
A

Al Williams

#6
Ensure your server anti-virus is not scanning the exchange database files
and LOG files (google "sbs2003
antivirus exclusions" for a specfic list). They can corrupt things and
cause issues (and not just with exchange).

--
Allan Williams




Billy Gareth wrote:

> Scenario: Usually every 4-5 days, sometimes more, sometimes less
> users will say that Outlook is saying that it is connected but no
> emails are coming through. If they restart Outlook then it doesn't
> connect properly to Exchange.
>
> If I try and restart Exchange server, it takes ages then fails with a
> 1053 error. The state then gets stuck in the "stopping" state and the
> only way to resolve in a complete server restart.
>
> May not happen for weeks then happens weekly again for a few weeks.
> Failure generally seems to happen overnight at some time as compliants
> already come through first thing in the morning.
>
> Has done this since install 2 years ago but not consistent. So think
> that it is all good for months then starts again.
>
> These errors show in event viewer
> LDAP Bind was unsuccessful on directory server.servername.local for
> distinguished name ''. Directory returned error:[0x51] Server Down.
> 8026
>
> The Win32 API call 'DsGetDCNameW' returned error code [0x862] The
> specified component could not be found in the configuration
> information. The service could not be initialized. Make sure that
> the operating system was installed properly. 8250
>
> Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
> responding:
> server.server.local.local
>
> Have run toubleshooting assistant many times and fixed issues that
> were
> found or found no issues.
>
> Am out of ideas...
>
> SBS 2003 standard
> Exchange SP3
> 17 mailboxes
> Prviate DB = 13.4GB
> Public DB = 28MB
> DB limit patch applied
>
> Thanks,
>
> Billy
 
D

Dave Nickason [SBS MVP]

#7
Two quick thoughts:

Does this happen with all users at the same time? If not, try shutting down
Outlook and deleting the user's OST file. Restart Outlook and let it create
a new OST, and see if that solves the problem. Obviously if all the users
are seeing the symptom at the same time, it wouldn't be this.

Also, in ESM, in the properties of the Default SMTP Virtual Server ->
General -> Advanced -> Edit, is the Sender ID Filter enabled? I had this
symptom after enabling Sender ID when Exchange services would restart - for
example, IMF updates, services restart, incoming mail stops flowing. At
that point, I'd get the service hang at "stopping" as you describe and have
to reboot the server. It might explain the seemingly random nature of this
if you have Exchange restarting from something like WSUS. This KB is what
fixed it for me, even though the symptom didn't really match the KB.

Messages from some organizations may remain in the queue folder when you
enable the Sender ID filter feature in Exchange 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;927478



"Billy Gareth" <BillyGareth@newsgroup> wrote in message
news:DE2D05A5-69F8-44E7-8EE9-9F423A614149@newsgroup

> Scenario: Usually every 4-5 days, sometimes more, sometimes less users
> will
> say that Outlook is saying that it is connected but no emails are coming
> through. If they restart Outlook then it doesn't connect properly to
> Exchange.
>
> If I try and restart Exchange server, it takes ages then fails with a 1053
> error. The state then gets stuck in the "stopping" state and the only way
> to
> resolve in a complete server restart.
>
> May not happen for weeks then happens weekly again for a few weeks.
> Failure generally seems to happen overnight at some time as compliants
> already come through first thing in the morning.
>
> Has done this since install 2 years ago but not consistent. So think that
> it
> is all good for months then starts again.
>
> These errors show in event viewer
> LDAP Bind was unsuccessful on directory server.servername.local for
> distinguished name ''. Directory returned error:[0x51] Server Down. 8026
>
> The Win32 API call 'DsGetDCNameW' returned error code [0x862] The
> specified
> component could not be found in the configuration information. The
> service
> could not be initialized. Make sure that the operating system was
> installed
> properly. 8250
>
> Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
> responding:
> server.server.local.local
>
> Have run toubleshooting assistant many times and fixed issues that were
> found or found no issues.
>
> Am out of ideas...
>
> SBS 2003 standard
> Exchange SP3
> 17 mailboxes
> Prviate DB = 13.4GB
> Public DB = 28MB
> DB limit patch applied
>
> Thanks,
>
> Billy
>
>
>
 
B

Billy Gareth

#8
Hi All and thanks for suggestions. I hadn't replied earlier as about 2 days
after my original post was made, it seemed to disappear and I could not find
it anywhere. I assumed that it had been deleted for some reason. I have just
stumbled across it now.

Yes have checked the folders that AV is scanning
Yes it does happen to everyone at the same time
Robbin, that link didn't work so I have grabbed what appears to be a similar
tool and will send the results.

Thanks

Billy

"Dave Nickason [SBS MVP]" wrote:

> Two quick thoughts:
>
> Does this happen with all users at the same time? If not, try shutting down
> Outlook and deleting the user's OST file. Restart Outlook and let it create
> a new OST, and see if that solves the problem. Obviously if all the users
> are seeing the symptom at the same time, it wouldn't be this.
>
> Also, in ESM, in the properties of the Default SMTP Virtual Server ->
> General -> Advanced -> Edit, is the Sender ID Filter enabled? I had this
> symptom after enabling Sender ID when Exchange services would restart - for
> example, IMF updates, services restart, incoming mail stops flowing. At
> that point, I'd get the service hang at "stopping" as you describe and have
> to reboot the server. It might explain the seemingly random nature of this
> if you have Exchange restarting from something like WSUS. This KB is what
> fixed it for me, even though the symptom didn't really match the KB.
>
> Messages from some organizations may remain in the queue folder when you
> enable the Sender ID filter feature in Exchange 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;927478
>
>
>
> "Billy Gareth" <BillyGareth@newsgroup> wrote in message
> news:DE2D05A5-69F8-44E7-8EE9-9F423A614149@newsgroup

> > Scenario: Usually every 4-5 days, sometimes more, sometimes less users
> > will
> > say that Outlook is saying that it is connected but no emails are coming
> > through. If they restart Outlook then it doesn't connect properly to
> > Exchange.
> >
> > If I try and restart Exchange server, it takes ages then fails with a 1053
> > error. The state then gets stuck in the "stopping" state and the only way
> > to
> > resolve in a complete server restart.
> >
> > May not happen for weeks then happens weekly again for a few weeks.
> > Failure generally seems to happen overnight at some time as compliants
> > already come through first thing in the morning.
> >
> > Has done this since install 2 years ago but not consistent. So think that
> > it
> > is all good for months then starts again.
> >
> > These errors show in event viewer
> > LDAP Bind was unsuccessful on directory server.servername.local for
> > distinguished name ''. Directory returned error:[0x51] Server Down. 8026
> >
> > The Win32 API call 'DsGetDCNameW' returned error code [0x862] The
> > specified
> > component could not be found in the configuration information. The
> > service
> > could not be initialized. Make sure that the operating system was
> > installed
> > properly. 8250
> >
> > Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
> > responding:
> > server.server.local.local
> >
> > Have run toubleshooting assistant many times and fixed issues that were
> > found or found no issues.
> >
> > Am out of ideas...
> >
> > SBS 2003 standard
> > Exchange SP3
> > 17 mailboxes
> > Prviate DB = 13.4GB
> > Public DB = 28MB
> > DB limit patch applied
> >
> > Thanks,
> >
> > Billy
> >
> >
> >
> .
>
 
B

Billy Gareth

#9
Thanks all for your replies. I have not replied as a couple of days after
originally posting, my post disappeared and I could not find it anywhere. I
just happened to stumble across this post tonight.

Have checked the AV scans
All people have the same issue at the same time
Robbin, the link didn't work but I have found what appears to be a simialr
tool so will send the results to you.

Thanks

Billy

"Dave Nickason [SBS MVP]" wrote:

> Two quick thoughts:
>
> Does this happen with all users at the same time? If not, try shutting down
> Outlook and deleting the user's OST file. Restart Outlook and let it create
> a new OST, and see if that solves the problem. Obviously if all the users
> are seeing the symptom at the same time, it wouldn't be this.
>
> Also, in ESM, in the properties of the Default SMTP Virtual Server ->
> General -> Advanced -> Edit, is the Sender ID Filter enabled? I had this
> symptom after enabling Sender ID when Exchange services would restart - for
> example, IMF updates, services restart, incoming mail stops flowing. At
> that point, I'd get the service hang at "stopping" as you describe and have
> to reboot the server. It might explain the seemingly random nature of this
> if you have Exchange restarting from something like WSUS. This KB is what
> fixed it for me, even though the symptom didn't really match the KB.
>
> Messages from some organizations may remain in the queue folder when you
> enable the Sender ID filter feature in Exchange 2003
> http://support.microsoft.com/default.aspx?scid=kb;en-us;927478
>
>
>
> "Billy Gareth" <BillyGareth@newsgroup> wrote in message
> news:DE2D05A5-69F8-44E7-8EE9-9F423A614149@newsgroup

> > Scenario: Usually every 4-5 days, sometimes more, sometimes less users
> > will
> > say that Outlook is saying that it is connected but no emails are coming
> > through. If they restart Outlook then it doesn't connect properly to
> > Exchange.
> >
> > If I try and restart Exchange server, it takes ages then fails with a 1053
> > error. The state then gets stuck in the "stopping" state and the only way
> > to
> > resolve in a complete server restart.
> >
> > May not happen for weeks then happens weekly again for a few weeks.
> > Failure generally seems to happen overnight at some time as compliants
> > already come through first thing in the morning.
> >
> > Has done this since install 2 years ago but not consistent. So think that
> > it
> > is all good for months then starts again.
> >
> > These errors show in event viewer
> > LDAP Bind was unsuccessful on directory server.servername.local for
> > distinguished name ''. Directory returned error:[0x51] Server Down. 8026
> >
> > The Win32 API call 'DsGetDCNameW' returned error code [0x862] The
> > specified
> > component could not be found in the configuration information. The
> > service
> > could not be initialized. Make sure that the operating system was
> > installed
> > properly. 8250
> >
> > Process MAD.EXE (PID=4152). All Global Catalog Servers in use are not
> > responding:
> > server.server.local.local
> >
> > Have run toubleshooting assistant many times and fixed issues that were
> > found or found no issues.
> >
> > Am out of ideas...
> >
> > SBS 2003 standard
> > Exchange SP3
> > 17 mailboxes
> > Prviate DB = 13.4GB
> > Public DB = 28MB
> > DB limit patch applied
> >
> > Thanks,
> >
> > Billy
> >
> >
> >
> .
>