HTTP error. The resource is not found.
Error: -18596
Has any body run into this and if so, have you been able to resolve
the problem?
Thanks,
-Rob
Make sure you are using Office 2004 SP1
Waiting to know your response
Naren
--------------------
From: robbie...@gmail.com (Rob)
Newsgroups: microsoft.public.mac.office.entourage
Subject: Error: -18596 HTTP error. The resource is not found.
Date: 20 Oct 2004 14:23:19 -0700
Organization: http://groups.google.com
Lines: 12
Message-ID: <fdfcf02a.04102...@posting.google.com>
NNTP-Posting-Host: 12.152.168.132
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1098307399 32205 127.0.0.1 (20 Oct 2004
21:23:19 GMT)
X-Complaints-To: groups...@google.com
NNTP-Posting-Date: Wed, 20 Oct 2004 21:23:19 +0000 (UTC)
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!newsfeed00.sul.t-online.de!t-online.de!news.glorb.com!postnews1.goo
gle.com!not-for-mail
Xref: cpmsftngxa10.phx.gbl microsoft.public.mac.office.entourage:43424
X-Tomcat-NG: microsoft.public.mac.office.entourage
Several users on my Exchange server have the problem. This didn't fix
it. The one common characteristic that I'm aware of concerning the
users for whom the problem exists is that they used a Windows Outlook
client to access their accounts before configuring Entourage on a Mac.
This is a serious issue for affected Mac users at our institution who
have recently been offered hope that they may no longer need to be
fettered to the crippled Outlook 2001 client.
I did solve the issue by using this advice after all, but not without
further investigation.
The information I was given initially about using Entourage with our
Exchange server stipulated that a user's account could be resolved for
Entourage by the server even if the name of the particular server
hosting the account was different from the one specified during setup.
Anyway, after getting positive results by entering the URL in the
above format, it appears that entering a specification for the precise
Exchange server on which the particular user's account is hosted
rather than just naming one of the Exchange servers on the network is
indeed necessary. The only way I know of to find out precisely which
server is correct for a user is to look at a successful configuration
of the Outlook 2001 client in Mac OS 9 or Classic, which apparently
can resolve the correct server regardless of which one is named during
setup. By doing that I was able to determine what Exchange server URL
to enter to solve the problem for the affected user. So thanks after
all!