entourage 2004 errors

C

Charles Hibbits

I do not see a specific managed newsgroup for Entourage, so I assume this is
the place. We have some Entourage 2004 users that have been working for a
few weeks on Exchange 2003, but recently several stopped working. One user
I
am working with gets an error:

Error
Entourage is unable to access the mail account you are using with the mail
server configured for that account

Error: -18597


Another error from another user is:

Error
An unknown error (4362) occured.

Error: 4362Is there a log or something where more detail can be found?
 
C

Corentin Cras-Méneur

Hi Charles,
I do not see a specific managed newsgroup for Entourage, so I assume this is
the place. We have some Entourage 2004 users that have been working for a
few weeks on Exchange 2003, but recently several stopped working. One user
I
am working with gets an error:

Error
Entourage is unable to access the mail account you are using with the mail
server configured for that account

Error: -18597
Click to expand...


Here is what I found:
Entourage 2004 Exchange Error:

Attempting to send anything yields either 'Unknown Error -17199' or
'HTTP Error. Access to the resource is forbidden. Error -18597.'

This is probably because the e-mail address you typed in the Exchange
account dialog does not exactly match the one the server expects. Since
the addresses don't match, it doesn't allow you to send.

Another error from another user is:

Error
An unknown error (4362) occured.
Click to expand...

For this one:
Error 4362 in Entourage X

The action could not be completed. An unknown error (4362) occurred.

When you try to use Microsoft Entourage X to send or to receive e-mail,
you receive this error message: Error 4362. The solution is typically
resolved by performing a typical or advanced rebuild of the database
file.

Sometimes this error indicates a problem Entourage is having with the
Microsoft Database Daemon. Quit the daemon

Then go to System preferences/Login and remove any entries of the
database daemon from the 'login items' window. Now start up Entourage
again and hopefully the problem will have been resolved.

Note: Some users reported this error when clicking on a corrupt email.
4362 is not the usual error for a corrupt message. If deleting the
message does not solve the problem, try a rebuild. If this is your
problem, then try the following:

Go to View menu/Preview Pane, or press command-\, to turn the Preview
Pane off. Now when he click on the message, you will be able to delete
it. If this is a POP account and a local folder, then go to Tools/Run
Schedule/Empty Deleted Items Items Folder. If it is an IMAP account set
up with its own Deleted Items Folder, quit Entourage so it will get
purged, or if set up to "mark for deletion" press command-K to connect
to the account to purge it.


Error: 4362Is there a log or something where more detail can be found?
Click to expand...


Most error codes can be found on
http://entourage.mvps.org/error/page.html

Corentin
 
C

Charles Hibbits

Thanks.

Unfortunately the user has the same email address that is listed as the
primary smtp address in exchange. As the user reports it, nothing has
changed. It just stopped working one day. Is there some remote possibility
it is case sensitive?

As for the second problem's solution, I will check with the user tomorrow.
 
C

Corentin Cras-Méneur

Charles Hibbits said:
Thanks.

Unfortunately the user has the same email address that is listed as the
primary smtp address in exchange. As the user reports it, nothing has
changed. It just stopped working one day. Is there some remote possibility
it is case sensitive?
Click to expand...

It could be... Or some changes on the server triggered the error (eg
workgroup name),

Corentin
 
C

Charles Hibbits

the email address and all other information is correct. We even attempted
to make a new exchange connection and it still did not work.

As for the other error, The user in not getting the error anymore, but now
when she tries opening Entourage it's like she's opening her mailbox for the
first time. Not seeing her normal mailbox view.
 
C

Corentin Cras-Méneur

Charles Hibbits said:
the email address and all other information is correct. We even attempted
to make a new exchange connection and it still did not work.
Click to expand...

You're not missing aaa subdomain for instance ?? I had that one when
using [email protected] instead of [email protected].

You can always try to perform some port-sniffing to capture whatever
Entourage is sending to the server to try and find out where the problem
lays (you can use tcpflow, tcpdump or Interarchy for instance).

As for the other error, The user in not getting the error anymore, but now
when she tries opening Entourage it's like she's opening her mailbox for the
first time. Not seeing her normal mailbox view.
Click to expand...

Does she get all the e-mails already in the mailbox or not ??
It could be worth rebuilding the database...

Corentin
 
C

Charles Hibbits

I will try and sniff the first problem.

As for rebuilding the database, I was unable to follow the instructions from
your previous post. I have limited exposure to OSx enironvment. I'm not
sure how to "quit the daemon" for the microsoft database. I thought
possibly to kill the process froma command line, but the terminal
application seems to be behavign abnormally, creating a window that is only
large enough to hold the close icon. for step of going into
preferences/login, I did not see login as one of the available tools.

Thanks
 
C

Charles Hibbits

I captured the data, but it is encrypted with ssl. Is there antoher way to
get this data, or is there enough data in the frames to tell us the problem?
 
C

Corentin Cras-Méneur

Hi Charles,
I will try and sniff the first problem.

As for rebuilding the database, I was unable to follow the instructions from
your previous post. I have limited exposure to OSx enironvment. I'm not
sure how to "quit the daemon" for the microsoft database. I thought
possibly to kill the process froma command line, but the terminal
application seems to be behavign abnormally, creating a window that is only
large enough to hold the close icon. for step of going into
preferences/login, I did not see login as one of the available tools.
Click to expand...


You can sure kill the daemon throught the Terminal or the Activity
Monitor application, but there is an easier (and nicer) way: in
Entourage, select the "Turn off notifications" command under the
Entourage menu.

As far as the Terminal is concerned, you should rpobably trash the
corresponding prefs in this account.

Corentin
 
C

Corentin Cras-Méneur

Charles Hibbits said:
I captured the data, but it is encrypted with ssl. Is there antoher way to
get this data, or is there enough data in the frames to tell us the problem?
Click to expand...

ouch... if it's encrypted, I'm not sure we'll be able to understand
anything at all from the log :-(

Corentin
 
M

Mark Barnes (Jao)

I've had this before. About 2 weeks ago we bought new Macs with Tiger and
Office 2004. They worked fine for about a week before I started getting the
same error, on all the Macs at the same time. An update maybe?

Anyway after fiddling about for about a week I found what seemed to fix the
problem for me, and a couple of mates who also got the same problem.

Originally my Entourage settings were set to:-

Account Name - [email protected]
AccountID - markbarnes
Password - ********
Domain - mydomain.local (also mydomain.com as this setting was inconsistent
across clients)
Exchange Server - 192.168.1.10
Name - Mark Barnes
Email.Address - [email protected]

When I changed the settings to

Account Name - [email protected]
AccountID - markbarnes
Password - ********
Domain - mydomain.local
Exchange Server - http://192.168.1.10/exchange
Name - Mark Barnes
Email.Address - [email protected]

It started working. Strange but it seems that Entourage seems to like using
the HTTP interface, even though we are using it internally. I havent tried
this using our externally resolvable OWA address which is
http://mail.mydomain.com/exchange to see if it works with machines outside
the firewall.

Let me know if this helps.
 
Top