Error -18576 syncing Entourage calendar to Exchange 2003 SP2

J

Jay Maynard

My employer recently had to update their Exchange 2003 server to SP2.
I had been using Entourage 2004 (11.3.3) just fine until they applied
that update. Now, when I connect to the server, it loops continuously
trying to sync calendar entries from my system. The only message in
the box when I click on the Details icon is "Error -18576". There's no
other explanation.

I asked the guy who administers the server to please put whatever
settings he changed back the way they were, and he told me that
Exchange 2003 SP2 wouldn't allow that.

I can't find any debugging information, and a net search is less than
useful. Unfortunately, I'm stuck with this piece of crapware. How do I
get it to work again?
 
J

Jay Maynard

My employer recently had to update their Exchange 2003 server to SP2.
I had been using Entourage 2004 (11.3.3) just fine until they applied
that update. Now, when I connect to the server, it loops continuously
trying to sync calendar entries from my system. The only message in
the box when I click on the Details icon is "Error -18576". There's no
other explanation.
Click to expand...

I just tried it from my laptop, and that worked. I've set the
configuration the same on both; the desktop still gets the same
errors.

The difference is that the desktop has calendar items that need to be
updated on the Exchange server, and the laptop does not. Those are the
items that Entourage loops trying to sync.
 
W

William Smith

Jay Maynard said:
I just tried it from my laptop, and that worked. I've set the
configuration the same on both; the desktop still gets the same
errors.

The difference is that the desktop has calendar items that need to be
updated on the Exchange server, and the laptop does not. Those are the
items that Entourage loops trying to sync.
Click to expand...

Hi Jay!

Use Entourage's Switch Identity... command under the Entourage menu to
create a new identity that will resync with the Exchange Server. Then
add your calendar entries while using the new identity. If this works
then just continue using the new identity.

Hope this helps! bill
 
J

Jay Maynard

Use Entourage's Switch Identity... command under the Entourage menu to
create a new identity that will resync with the Exchange Server. Then
add your calendar entries while using the new identity. If this works
then just continue using the new identity.
Click to expand...

Unfortunately, it didn't work. I still get the same -18576 errors when
syncing calendar items from my desktop system to the Exchange server.

Is there any place where these error numbers are even documented? Is
there any debugging information that can be enabled, so I can see just
what is failing? Right now, it's all a black box, and there's no way
to figure out what's going wrong.
 
W

William Smith

Jay Maynard said:
Unfortunately, it didn't work. I still get the same -18576 errors when
syncing calendar items from my desktop system to the Exchange server.

Is there any place where these error numbers are even documented? Is
there any debugging information that can be enabled, so I can see just
what is failing? Right now, it's all a black box, and there's no way
to figure out what's going wrong.
Click to expand...

After a little research I've found a few folks have reported this
problem before. Someone I recognize as an Entourage developer posted
this comment in another forum:

"Do you have URLSCAN installed on your network? Errors like this are
usually caused by blocking DAV commands that Entourage relies on.

"http://support.microsoft.com/default.aspx?scid=kb;en-us;823175"

More information about URLScan can be found here
<http://www.microsoft.com/technet/security/tools/urlscan.mspx>.

Provide this to your Exchange Server administrator and he may understand
what's happening.

Hope this helps! bill
 
J

Jay Maynard

"Do you have URLSCAN installed on your network? Errors like this are
usually caused by blocking DAV commands that Entourage relies on.
Click to expand...

I forwarded the links you provided to my Exchange admin, and he came
back and told me he doesn't have URLScan installed. Any other ideas?
Anyone have any thoughts on how we can see what the problem really is
beyond just the nebulous -18576 error?
 
Top