I've followed the instructions to download PE, start the client restore service, and create a backup key. When I put the key in the PC (that was backed up over a year, lost the hard drive,.

Latest Updates!

Site Navigation

Download updates from Office Mac or use AutoUpdate under Help in the menu bar. More Info on updates

Support our site SIGNUP FOR HOSTMONSTER.COM

Number Errors

For easy searching use your browser's Find command (cmd-f) under Edit in the menu bar.

For additional help, see

Positive Errors

40, 114, 130, 192, 1025, 1412, 1500, 1503, 2004, 4326, 4359, 4361, 4362, 4363, 5000, 5421, 5452, 5530, 5550, 5552, 5553, 7002, 7010, 8796, 10002, 10091, 16007, 16008, 16013, 16399, 16406, 16999, 19999, 30876

Negative Errors

-34, -36,-39, -40, -50-51, -54, -108, -192, -199, -600, -1409,-2171, -3155, -3170, -3171, -3176, -3211, -3215, -3248, -3253, -3259, -3260, -3280, -5000, -5530, -7129 and -7133, -9705, -10810, -11003, -16999, -17099, -17199, -17747, -17776, -17789, -17796, -17799,-17895, -17897, -17997, -19872, -18493, -18500, -18588, -18595, -18596, -18597, -18599, -19918, -23012, -23016, -30588, -30876, -65535

Negative Errors

Error -34

disk is full.. (do not have the exact text description)

Users have reported the following:

Error -34 means that the disk is full - In other words, there is insufficient disk space to complete an operation. Try deleting data and defrag your hard drive.

Another user found that it was his mailbox that was full. Either uncheck Leave Mail On Server box or don't leave mail on server for extended periods.

A contributor to the Entourage newsgroup came up with a possible explanation and fix for this error – in particular when trying to send or receive large files – that's certainly worth trying. He speculated that there was corruption in his Main Identity and verified the problem by creating a new identity (Edit>Switch Identity). The error disappeared in a new identity.

If this works for you, you'll then need to transfer all your mail and data over to the new identity. Help moving data can be found here.

Error -36

Error -36 is a hardware error.

An I/O error almost always means disk damage (hard drive, optical drive, CD). You probably have a bad disk. Try running Disk Utility > Repair Disk. Disk Utility can be found in Applications/Utilities.

Error -36 is often just a read/write error e.g. when copying from a bad DVD. If you get this error when copying between hard drives you should start to worry.

Try using dot_clean perhaps, as suggested in these threads:

Error -39

the Preferences File Could not be opened. The end of file was reached. -39

1. This issue may occur if you have a damaged Identity database file.

• Rebuild your database. How to rebuild
• Create a new identity, and then manually re-enter account information.

2. The file that has reached it's end is often the preferences file. Move the 'Microsoft' folder out of your local preferences folder and try again. If this fails, end of file means the file is too corrupted to rebuild.

Error -40

Compacting failed. A read/write error has occurred (-40)

Error -40 is a positioning error (tried to position before start of file). This might indicate file system corruption. Try running Apple's Disk Utility: First Aid and repairing the disk till it shows clean.

Error -50

An unknown error (-50) occurred

• One user found this solution: Run 'Remove Office', then run Repair Permissions. Install from your CD and apply all updates. Restart and then run Repair Permissions again.
• Another cause for this error was found by J. Gorman: I had a semicolon in my outgoing server name.
• Another user reported this fixed the issue for them: Try creating a new Entourage identity and setting up your email account. When the email address is verified with the new identity and you receive your e-mail, then try switching back to the identity that you had a problem with and check your mail. This solved the problem for me.
• Christoph Nadig, reported this solution: I found old mails in my outbox that were never delivered (for an unknown reason), but everytime I wrote a new mail, Entourage tried to send them again, leading to a -50 error everytime. Deleting these old entries in my outbox resolved the problem.

Error -51

a read/write error has occurred (-51)

Error -50 is parameter error, which you'd likely get if you ran incompatible versions of Office and its components. Run the Remove Office and reinstall Office on that machine. Also, try setting up a different user on that machine and see if it fixes the problem. Last resort would be to reinstall the OS.

Error -54

Can't read file 'Database', error -54 (file is busy/locked), path: 'Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database'.

You may find that there are other processes which still have the database open, specifically the 'Microsoft Database Daemon'. Entourage uses the Daemon as a centralized DB engine. If you use Retrospect's facility to run an Applescript prior to a backup, both Entourage and the Daemon can be shutdown, albeit with some annoying caveats. More info on Microsoft Database daemon

Error -108

Error -108 (not enough memory)

1. Upping memory does not seem to help. One user reported this error started after updating. The update put new language encodings in the system folder without removing the old ones. Remove the old ones manually.

2. The following has been suggested as a fix if the problem occurs when trying to receive mail:

The problem is caused by a bad message.

Open Tools/Accounts/that account/Options. Check Allow online access. Now you'll see a server account for the account in your Folder list. Go to it. You're now looking at the messages on the server. If you know which is the problem message (the oldest one there if you don't normally leave messages on the server, or the oldest one with a jagged icon indicating not downloaded otherwise), turn off the preview pane in View menu (or command-). Select the bad message and delete it. Now everything will be fine - send & receive all.

Error -192

The script could not run. End of file was reached.

or

The script could not be run. An error has occurred(-192)

This was fixed in the update Office 10.1.2

Since the original error popped up and was fixed, the error has continued. Users have found these things to cause or resolve the error.

1. This error could be involved with fast user switching and running Entourage in more than one user.
2. This error is also associated with printing errors.
3. -192 error could be coming from the OS. I would suggest checking the hard disk for errors. Run Disk First Aid or Disk Warrior and see if that solves the problem. See #5 below.
4. Updating my Office suite did the trick. I suggest using 'Remove Office' then reinstall from the CD and update before opening Entourage. Also run Apple's latest Combo updater. It will overwrite files that might have been damaged. Several users have reported this fixed some odd problems they were having with Entourage.
5. It appears that the root of this conflict may be a font problem. I turned on Suitcase 10 today and it prevented the opening of duplicate fonts, but duplicate fonts were requested by html mail. So, as Entourage tried to read these html emails, my program started getting regular 192 errors, blank screens, freezes and crashes. See Dealing with bad fonts.
6. Download the latest combo updater from Apple and run it again rather than using Software Update. Doing so overwrites potentially problem-causing files. Combo updaters will install on the same version as they’re applying—no need to roll back or do a clean install.

Suggestion: Testing in a new User will quickly tell you if the problem is system wide or if it's your User's folder that contains the problem.

Error -199

no error message available

User creates new e-mail. User attempts to add attachment by clicking on paper clip icon in message window. User chooses file to attach. User receives error -199.

Dragging and dropping the file into the attachment area did not produce an error, but it also didn't attach the file.

User reports: We were finally able to resolve the issue by copying and pasting the data from the Word file into a new Word file. This new Word file was able to be attached without any problems. Chances are the error -199 was caused by junk data within the original Word document.

Error -600

An error occurred while launching.

An unknown error (-600) occurred.

This is the standard Macintosh error procNotFound. It is usually a response when trying to send an AppleEvent to a nonexistent target (or, more technically, when the mach port for AppleEvents for that target cannot be found). This would usually be generated by the toolbox, but Entourage generates that error in these cases:

(1) if Entourage cannot find the Alerts Daemon (usually found in the Office subfolder) to launch to show the 'toasts' (notifications that new mail has been received),

(2) if Entourage is trying to open a document and cannot find the Finder application (this is usually when you're opening Entourage on a system that is too old, so probably not your case), and

(3) in some generic process code that tracks whether other processes (e.g., the Database Daemon) are running.

Error: -1409

Macintosh system error (-1409) * Named fork does not exist */ error

The info we have on this error means that some part of the OS is damaged or missing, (assuming that the HD directories & such aren't messed up). Try reinstalling the last big combo update from Apple. It's possible that you will have to do an 'Archive & Install' to repair your system files.

Error: -2171

Lost mailbox lock

Accessing one or more IMAP accounts may experience an issue where the server response time is sluggish, files are incorrectly moved and/or deleted, and an error about a 'lost mailbox lock' appears. This is a known issue with Entourage where it, by default, attempts to send set of commands to the mail server simultaneously, instead of individually. Bulk commands can confuse the server and cause commands to be applied to incorrect messages, as well as cause the server to reject the commands. To solve this problem, uncheck Send commands to server simultaneously. More info on how to set up account

Error -3155

Error: Mail could not be sent using account account_name. An error of type -3155 has occurred.

This error is usually associated with an e-mail that contains too much data. See this Microsoft Knowledge Base article for more information:

Error -3170

LDAP Server Error: The specified server could not be found.:

Solution 1: This is because none of the installed Directory Services are still active. Go to Mail and News Preferences, then click the Compose tab. Uncheck the option to Automatically check names when sending messages. Also, go to Tools -> Accounts, click the Directory Service tab, then delete all of the pre-installed servers.

Solution 2: It could be a problem anywhere in the network chain: your network isn't connected (can you browse the web?), the server name isn't right in the account, the DNS server is not working properly, you're proxy server is misconfigured.

Solution 3: The LDAP server is not the same as the Exchange server. Things to check:

1. Are you connecting to an Exchange 2000 server?

2. Ask your admin for the Global Catalog Active Directory server. That is what you want to use for LDAP in Entourage

Error -3171

A network error has occurred (-3171).

We have limited info on this error. Errors around that number are all Open Transport Error numbers. Entourage is just passing them along.

Error -3176

You may receive these error messages if one of the following conditions is true:
• An incorrect server name is used for the POP3 server or for the SMTP server.
• The server computer is unavailable or is unreachable.

Check under advanced settings for SMTP. Most ISPs require advanced settings now for SMTP. Check your ISP’s website for exact info on SSL and ports required. See Account setup for examples

More info: http://support.microsoft.com/kb/909457

Error -3211

The Domain Name Servers are not responding

OS X: Open System Preferences from the Dock or the Apple menu. Open Network Preferences, then click the TCP/IP tab. Then clear the DNS Servers field, click 'Apply Now', and close.

OS 8-9: In Entourage 2001, go to Apple -> Control Panels -> TCP/IP. Clear the field called Name server addr. entirely. Close the control panel, choose to save/apply if asked, and retry. Note: Copy the DNS Servers entries to a TextEdit document or someplace where you have them, in case the results are undesirable.

unknown error (-3211) occurred

User reported this fix Dec. 2009:

I seem to have stumbled on to the solution. I turned off Norton Firewall Location Awareness, Connection Blocking and Application Blocking, but I left on the 3 Advanced Settings. When this was done Entourage works OK. I turned on the Firewall settings in the Security Preferencs.

(Problem started with 11/18/09 Norton update)

Error -3215

Could not retreive mail from the account 'Mail Account'

Error -3215 is caused because you are not online when trying to send & receive mail.

Error -3248

unknown error (-3248) in Exchange Server Contacts or Check Names

User reported fix: Somehow, the LDAP default port was overridden and set to zero (0). To fix:

In Entourage

1. Go to Tools->Accounts
2. Click on the Exchange account in the list
3. Select Edit Account
4. Across the top of the new window are a bunch of selections, select 'Advanced'
5. There are 3 check boxes
6. Uncheck the 'override default port' (which is checked and set at 0)
7. When unchecked, the proper LDAP port number will appear.
8. Apply the setting

Now it will all work. No more unknown error -3248

Error -3253

'Communication to server failed or was dropped. Mail could not be sent. Error -3253'

One user reported: The sent mail folder was too large. Moved 18 months of e-mails and their attachments to a new folder and it worked like a champ.

Error -3259

No description..exchange error

User, Jeremy Reichman reports that -3259 seems to be solved by actually making Global Catalog servers available for LDAP lookups.

Error -3260

Exchange error. See the Microsoft Knowledge Base for an explanation and possible solutions.

Error -3280

Could not retrieve mail from the account, a connection failure has occurred, error:-3280

This error is the same as Error 16999. See below.

Error -5000

Messages with an attachment creates Error -5000

Attachments are stored in the Entourage Temp folder inside the Microsoft User Data folder. This is where Entourage is trying to save the file before it opens. Check the permissions on this folder.

• Owner Access: Read Write
• Group Access: Read only
• Others: Read only

You can delete the Entourage Temp folder, and Entourage will create a new one when launched.

Error -5530

No description..exchange error

User, Jeremy Reichman , reports a -5530 error with SMTP against an Exchange 2003 front end server. This happened on Entourage v.X and lower (including Entourage 2001 and Outlook Express for classic) only. We ended up enabling and disabling SSL for SMTP on our front end servers. We also disabled (on the Exchange 2003 servers): <front end server> Properties > Access tab > Secure communication > Communication button > 'Require secure channel' option

Error -7129 and -7133

This error occurs when trying to receive mail. It is almost always caused by a corruption in the the mail account configuration. To resolve, create a new mail account then try again. Do not just erase and re-enter the info. Delete the account and create a new one. In addition, run Keychain FirstAid in Apple's Keychain Access application.

Error -9705

SYMPTOM: Entourage will not print messages that contain HTML.

User reports this solution: the Font Cache must have been corrupt. I deleted the folder /Library/Caches/com.apple.ATS and restarted the machine. All appears well now.

Error -10810

Basically, it means that the Launch Services framework is misbehaving and is encountering errors when trying to launch an application. When you encounter this error message, it is probably best to restart the machine. More info

Error -11003

You Receive Error Messages When You Try to Open a Microsoft Exchange Server Folder in Entourage X for Mac

An error Occurred on the IMAP server. Invalid account or password. Check your account settings. Error -11003

This problem occurs if any of the following conditions are true:

The Exchange account is not configured correctly.

-or-

There is a problem with the Microsoft Exchange server. For example, either the Internet Message Access Protocol version 4 (IMAP4) or the Microsoft Exchange Information Store services is not running.

-or-

There is a network configuration problem that is preventing communication with the Exchange server.

WORKAROUND

To work around this problem, verify that the Exchange account settings are correct, that the network configuration is correct, and that the Exchange server is operating correctly with all the required services running.

Error -16999

Solution: Try using account with secure password selected and not selected.

In the Account window, select 'Click here for advanced receiving options button'. Toggle 'Always use secure password' Try to receive mail again.

Error -17099

Relaying to <the email address> prohibited by administrator Email could not be sent Account name (my account name) Error -17099

Error -17099 is an Entourage error kSMTPServerReplyErr, and is returned when the SMTP server has returned a permanent or transient error or returns an unexpected result code.

This error is coming from your ISP.

Users have reported this error when sending to large groups. ISPs limit the number in a group. Usual number is 50 recipients to avoid spammer misuse. Entourage has no limit. You should contact your mail provider to ascertain the maximum number of recipients per message and note it. You can use the free 'Split Recipients' script to send a mass e-mail in separate mailings automatically:

Most ISPs also require you to use their SMTP address when sending.

Error -17199 and -18587

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.

Entourage 2001

A message in your outbox could not be sent, the account which created it cannot be found

Messages in your Outbox cannot be delivered because of an addressing problem. RESOLUTION To resolve this behavior, delete or remove messages that cannot be sent from your Outbox, and then click Send & Receive . MORE INFORMATION The error message can occur when an Entourage Identity has been configured with multiple e-mail accounts, and one of the e-mail accounts has either been removed or is not functioning. When you click the Send & Receive button, Entourage attempts to deliver the messages in your Outbox, but cannot because it cannot access one of the e-mail accounts.

Entourage 2008:

Error -18597, can also happen when a user's Active Directory account password has expired.

Resetting the password - say through OWA - then launching Entourage resolves. (fix provided by Pete C.)

Error -17747

-17747 = -17800 + unwillingToPerform (53).

Every time I try to access the GAL with LDAP, I receive error #-17747.

SP2 includes a fair amount of enhancements to Entourage's general LDAP capabilities. As a result, some of your previous LDAP settings may need to be updated. The most common solution for error -17747 is to remove the search base from your directory configuration. Go to Tools menu : Accounts : Your Exchange Account : Advanced and empty the Search Base field.

Error -17776

can't connect to the directory server too many matches

One of the lesser known problems with Active Directory is that they return sizeLimitExceeded (which is translated into -17796) when they really should return adminLimitExceeded in the case where there is a server-side, administrative limit to the number of records it will return. If you set your size limit to 400 and ask for 400 records, but the server only allows 300 records, you'll get this error and there's nothing you can do about it. Furthermore, the error indicates you should be able to do something about it (i.e., change your size limit), so it's doubly problematic. If you would like this behavior to be different, I suggest escalating through PSS to the Active Directory team.

Error -17789

Error -17789 means that the LDAP server says it hit the time limit that the Server Admin set.

Error -17796

Error: The directory server cannot complete the search. Too many matches were found. Narrow the search by entering more specific criteria or increase the maximum number of results allowed in the Edit Account dialog box.

Explanation: LDAP server error.

This error appears if the search times out, most often because there are so many results that the set cannot be returned by the search time limit. The search time limits are usually set by the server, so see if that can be changed. Or use more specific criteria in your search.

Error -17799

Error on addressing message/checking names

In Entourage 2004, go to Tools > Accounts, and open your Exchange Account. Click the 'Directory' tab, and then click the 'Advanced Options' button. Toggle the option indicating 'My server requires me to log on,' and click OK.

In Entourage X, go to /Applications/AppleScript/, and launch Script Editor. Paste in this script, and click 'Run.'

Error -17895

Connection to the server failed or was dropped. Explanation: Could not retrieve mail.
Account name: 'xxxxxxxx' Error: -17895'

This is an Entourage internal error netLostConnectionErr, and is generated when Entourage hits eofErr trying to read a network stream from the server and expects more data to be coming. It could also be generated if, when trying to create a connection, Entourage (apparently) successfully authenticates, but then the network connection closes immediately thereafter.

A network sniff could help determine whether or not the server is doing the losing of the connection (and possibly why) or whether Entourage is expecting more data than it should.

User reports: It turned out to be a mail server issue, which our ISP managed to resolve using the information provided above. back to top

Error -17897

Sending email error 'Authentication failed. Error 17897' in Outlook 2011 for Mac

Receive error trying to send mail, or receive mail

Entourage doesn't support the requested authentication method It includes an error code of -17897.

Error when trying to send from a remote location:

None of the authentication methods are recognized

If you are traveling and getting error messages from Entourage when you send mail that 'none of the authentication methods are recognized,' see these steps to connect.

Entourage no longer works with POP3-based MSN accounts. You'll need to convert the account to a Hotmail-based account, which Entourage can then handle just fine. To do this, download MSN for Mac OS X and walk through the setup assistant. It will convert the account for you automatically.

Error -17997

'Unexpected Data was Encountered error
Error -17997'

Can connect to Exchange server and receive mail, but when sending, the messages hang in the Outbox with error -17997, unexpected data was encountered.

Users reported these fixes:

Option 1:

1: Changed the server name to the URL of used to access OWA via the your browser.
2: Tick Override default port in the Outlook 2011 settings and changed the port to 442

Option 2:

The solution I had to take was to create a new identity a second time. The first time I created a new identity didn't work. I suppose there may have been something I had done to complicate matters, but I'd be hard-pressed to say what it was. Once I was sure I had all the user's mail synced and his locally-stored messages complete, I exported an .olm file, created a new identity as the default and imported the .olm file. This time I was able to send messages from the identity.

An unknown error (-18493) occurred.

An unknown error (-18493) has occurred. Your mailbox has exceeded the size limit. Account name: 'Username'

Being over ones mailbox quota is a possible cause of this error.

I sent a message with an attachment that was too large. I now receive an error every time I send and receive.

This behavior is a result of RFC 2822 compliance in Entourage To work around the behavior I suggest that you increase the message size limit, this will allow you to send files that are Encoded.

More info here: Microsoft KB article 889525:http://support.microsoft.com/default.aspx/kb/889525

Error -18500

sync error -18500 exchange

User reported this fix: I was running into a similar issue, and ended up editing the 'httpRuntime maxRequestLength' in Outlook Web Access as described here: http://support.microsoft.com/kb/935848

Error -18588

Authentication problem with using the POP and SMTP servers at MSN.

Unfortunately it's not an Entourage problem, it's Hotmail's.

Error -18595

This error occurs if your company uses Microsoft's ISA Proxy Server, and your Mac is trying to retrieve mail through the Proxy Server. It won't work, to my knowledge. The Mac OS must talk to the mail server directly, so make sure the mail server's IP address is in the System Preferences->Network->Advanced [button]->Proxies [tab]->'Bypass proxy settings for these Hosts & Domains:' field. (fix provided by Jason C.)

Error -18596

The folder cannot be found on the Exchange Server. The folder might be deleted or moved or it cannot be accessed (-18596).

Add the affected folder within Entourage to your favorites.

Also see Microsoft KB KB884985 for more info.

Error -18599

Error tied to password. Open Keychain Access in Applications/Utilities. You'll probably find multiple entires for your email account. You should see a modified date for each entry. Delete the older entries. Run Keychain First Aid under Keychain Access in the menu bar after your delete the duplicate entries.

Error -19872

Item type is invalid for AcceptItem action.

In this tutorial, electrodes will be created using Cimatron’s easy to follow Electrode Guide.Blank & Electrode UCSIn Cimatron E different colors can be set to the blank wire bodies. Electrodes IntroductionWelcome to the Cimatron E Electrodes Tutorial. These colors act as NC Criteria, allowing automatic machining in the NC environment.ExtensionElectrode TemplateFurther ElectrodesAdd ElectrodeDrafting & Drafting TemplateAdvanced ElectrodesIn the following tutorial, advanced functionality of the electrodes application will be discussed.Blank & Electrode UCSExtensionTemplateA template of the features used in this electrode will now be created.Electrode OptionsAdd ElectrodeTrimEDM SetupAn EDM Setup for a standard machine will now be created. Cimatron tutorial guide.

Issue: When sending a message, users on Outlook 2011 and people viewing the message via web mail can see the message fine. It reports that it's a digitally signed message (just one sentence), and the certificates look fine. Via the web, the message appears fine. It says:

'This message has a digital signature. The digital signature could not be validated because the S/MIME control is not available.' However, it comes up fine.

FortiClient 6.2 Fabric Agent with Endpoint Protection and Cloud Sandbox. Fabric Integration Endpoint Fabric Telemetry. Download for Windows Download for MacOS. Get FortiClient 6.0 for Windows. Windows 7 or higher supported. Download; Get FortiClient 6.0 for Mac OSX. Mac OSX v10.12 Sierra or higher. Forticlient 5.6 download mac.

However, users on Outlook for PC (my version is 2010), cannot read it. I first get a preview pane error 'This item cannot be displayed in the Reading Pane. Open the item to read its contents.' And when I double-click on the message, I get a pop up window 'Your Digital ID name cannot be found by the underlying security system.'

User reports fix: I found the following answer from another thread to work for me:

'I had set the Hashing algorithm to SHA512 on my Outlook configuration and by changing that back to SHA1 all email recipients were now able to open the message. '

How to: Outlook for Mac >Preferences -> Accounts -> <choose the account effected> -> Click 'Advanced' button -> Click on 'Security' tab -> Change Signing Algorithm to SHA-1

Error -19918

'Could not synchronize record: Sync Issues to Exchange server: [company name]' error with Details: 'The folder save operation failed due to invalid property values.'

User reported this fix:

I resolved this problem. Here's what I did (not sure if all of these steps are required).

1. Run outlook.exe /resetfolders via a Windows copy of Outlook. I was hoping this would restore the Sync folder.
2. Remove the account from Outlook 2011 Mac.
3. Add the account to Outlook 2011 Mac.

Error -23012

An error occurred on the IMAP server. A connection failure has occurred.

It could be either something miss-configured on the client end or on the server end for the users. On the server end you can try comparing the settings of a good user and a bad user in Active Directory (you can bring up the account dialogs for both, and compare the items in all 15 tabs..) On the client side you can do the same in Entourage. It might also be worth looking in the System network preferences to make sure nothing is different there. You can also create new identities in Entourage on the various machines which will allow you to try to configure one of the failing users on a machine that was working, and the other way around too. That may help figure out if it is a client side or server side problem.

Error -23016

commandTimeout The specified command action was not completed in the specified time period.

This is a communications error.

Option 1:

It's possible that one side indicates that it's done (sends the QUIT) and shuts down the stream before ever looking for the OK

It has also been suggested that something is preventing your ISP from connecting to port 25 on your server. It could be a firewall or something blocking port 25.

The error seems to be specific to Earthlink connections. The following is suggested:

1. In OS 10 open the HD>Applications>Utilities folder and launch the 'network utility' 2. Use the lookup tab to search for the mail server and obtain the IP address 3. Open Tools/Accounts and edit the mail account 4. Place the IP address in the 'receiving mail' section for POP server Make sure you have applied all the latest Office updates.

Option 2

Mail could not be sent using the account _____@__________.com. A connection failure has occurred. Error: -23016

It is possible that your ISP has changed their security settings. The first thing to try is to see if you need to use Authenticated SMTP. Under the account settings (in the Tools menu), open the account giving you problems for editing. Then, under the last entry box Sending Mail:

click on the button that it titled 'click here for advanced sending options'. Select:

Print error -30876

I am unable to print Notes, Addresses, or Tasks. Notes and Address print jobs sometimes return the message indicating error -30876. Printing Tasks provides the spinning beachball of death. E-mail messages and Calendar Events print fine.

It sounds like you might have a corrupt printing form. Delete this folder: /Users/<Your User>/Documents/Microsoft User Data/Printing Forms/

Edit Account Settings Error Message (error -30588)

the action could not be completed. An error (-30588) occurred.

After switching from X-2004, when I double click on any of the accounts in my Accounts list, I get the following error message: the action could not be completed. An error (-30588) occurred. I've tried rebuilding the databases but that didn't seem to work. The account settings work fine, I just can't edit them (but I can delete and create new ones)

This is a known bug for Office X->2004 upgrades (not an issue on full install)

Errors -65535 and 7002 are both related to authentication issues. Delete Account and enter your info again. Be careful if you copy/paste that you do not add an extra character.

Positive Errors

Error 40

This error is associated with the database. A rebuild of the database is suggested. Try the Typical Rebuild first. If that does not work, then do Advanced Rebuild. See Database for rebuild instructions.

The Database Corruption page has some hints for totally unusable databases.

Error 192

This error could be involved with fast user switching and running Entourage in more than one user.

This error is also associated with printing errors. Sorry but we have no further info on solutions at this time.

Error 114

Exchange 2004- This error indicates a proxy error from netlib. Check Proxy support setup. Try requires authentication.

Error 130

This error has been seen when one tries to connect to a newsgroup and download messages and/or headers. This can be corrected by rebuilding the database. If you're in Entourage X, first go to Entourage in the menu bar and select Turn Off Office Notifications. Quit Entourage, and then restart Entourage holding down the Option key. When the Rebuild dialog box comes up, choose to do a Typical Rebuild.

I've seen this error when trying to connect to a newsgroup that was having problems. Don't assume it's database corruption.

Error 1025

AOL error 1025 'You have not correctly assigned folders.'

Don't assign any folders. All of the boxes under 'Special Folders' in the 'Advanced' tab should be unchecked.

Error 1412

Error: Mail could not be sent using the account 'Hotmail.' Explanation: HTTP error. The request cannot be fulfilled Error: 1412

Hotmail has these rules:

1. Max 50 emails at a time
2. Max 100 mails in a 24 hour period

Error 1500

HTTP error. The server cannot fulfill the request

Updaters have been issued to fix this problem. See the Version Page for the latest updaters.

In addition, Hotmail accounts require passwords with 8 characters. So, if you are using an old short password, look up your account in your web browser and change it.

Check for a bad message. The infamous '116Kb, <no subject> message' is still around. Go to the Hotmail website using your web browser to delete this message.

Sometimes sending a message will allow a download to work.

Error 1503

Could not receive mail from the account Hotmail.com: username

CAUSE On July 16, 2001 the MSN Simple Mail Transfer Protocol (SMTP) servers were upgraded to protect against unsolicited commercial e-mail messages, frequently referred to as spam. To continue to use your MSN account to send e-mail messages, you must also upgrade Entourage X. RESOLUTION To resolve this issue, download and install Microsoft Office v. X for Mac Service Release 1 (SR-1). This service release contains the changes that you must have to upgrade Entourage X so that it will work properly with your Hotmail account.

Note Office 10.1.2 is a combined updater that includes SR-1 and 10.1.1.

Error 2004

Security failure. Data decryption error.

This happens after waking from sleep. The outgoing e-mail stays in the Outbox. After that, sending e-mail works just fine (including the first e-mail, which transmits OK on the second try).

Possible solution: I suspect your ISP denies spam forwarding by requiring you to successfully access your POP account before it allows you to send. Once you do, you have a fixed amount of time to send mail before you need to authenticate again (5 to 15 minutes is typical).

Error 4326

Do a database rebuild. Start Entourage holding down the Option key. When the Rebuild dialog box comes up, choose to do a Typical Rebuild.

Error 4359

An error has occurred. Unexpected end of file. Memory is full. An unknown error 4359 occurred.

The most common cause of these errors is a damaged preference file for the currently selected identity. This preference file stores the settings for the accounts and other settings for the identity. The default location for identities is: Drive:Documents:Microsoft User Data:Office 2001 Identities

To rebuild the identity preferences file:

1. Quit Entourage if Entourage is currently running. Locate the preferences file in the currently active identity. 2. Place the Preferences file in the Trash on the Macintosh Desktop. 3. Restart Entourage. The Setup Assistant rebuilds the account for this identity.

If rebuilding the preferences file does not resolve the behavior and enables Entourage to start without any error, you may need to perform the following troubleshooting procedures, in the order given. 1. Rebuild the Entourage database. 2. Remove the Entourage application preferences file. 3. Rebuild the Macintosh Desktop.

To remove and rebuild the Entourage application preferences file:

1. Quit Entourage if it is currently running. Locate the preferences file in the following path: Drive:System Folder:Preferences:Microsoft 2. Place the Preferences file in the Trash on the Macintosh Desktop. 3. Restart Entourage.

To rebuild the Macintosh Desktop, restart the computer while you hold both the OPTION and COMMAND (Apple) keys down. Click OK when you are prompted to rebuild the Desktop.

Error 4361

Compacting failed. An unknown error (4361) occurred.

If you are unable to start Entourage, you might not need to rebuild the database to fix the problem. Instead, delete the following files from your hard disk:

Entourage 2001

* Internet Preferences (System Folder:Preferences folder) * Preferences (Documents:Microsoft User Data:Office 2001 Identities:<your identity name> folder, where <your identity name> is the name of your Entourage identity)

Entourage X and 2004

Preferences can be found in your ~/Library/Preferences/Microsoft/

Delete: The entire MS folder all com.Microsoft.*.plist

After deleting the preceding files, start Entourage again. If you are still unable to start the program, you should perform a Typical Rebuild.

Entourage 2001: Do a database rebuild. Start Entourage 2001 holding down the Option key. When the Rebuild dialog box comes up, choose to do a Typical Rebuild.

Error 4362

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

When you try to use Microsoft Entourage 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.

Error 4362 can also show:

The message could not be sent. An unknown error (4362) occurred.

If this occurs when sending a message with attachments, open the draft message window, and remove the attachments. Re-attach the files, and try sending again.

More Info on Error 4362

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

Then go to System preferences/Startup Items 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 4362 in Entourage 2001:

Do a database rebuild. Start Entourage holding down the Option key. When the Rebuild dialog box comes up, choose to do a Typical Rebuild. For more info see the Database Page.

Error 4363

4363 'Unknown Error'

If you get error 4363 on a transmission attempt, and you have one or more attachments, try deleting and re-attaching the file or files.

Error 5000

Access Permission Denied

If you're receiving this error, it could be due to incorrect permission settings for files within the Office folder. It's recommended you remove and re-install Office and then apply the latest updates.

Error 5530

Toggling the SMTP server requires authentication setting in Advanced sending options of the account settings may fix the problem.

Error: 5421 (three different error descriptions)

Mail could not be sent using the account .Mac.

Explanation: asmtp01.mac.com more than 50 recipients received from xxx.xxx.xx.xxx [xxx.xxx.xx.xxx]

Entourage has no limit. You should contact your mail provider to ascertain the maximum number of recipients per message and note it. You can use the free 'Split Recipients' script to send a mass e-mail in separate mailings automatically:

Error 5421

Server is busy (only with messages that contain an attachment)

This behavior can be caused by incorrect Maximum Transmission Unit (MTU) settings. Verizon is using an MTU setting of 1492 and Entourage uses a setting of 1500. Apple has a Knowledge Base article that will walk you through the steps. It article number 107474.

Set MTU setting in router to 1492. Be sure your router has the latest firmware update.

For a full explanation see User experience here.

Error 5421

Server is busy.

When sending or replying email, I get: 'Mail error. The server is busy; try again later.' Error: 5421 Odd part is that it doesn't happen to all addresses. I try sending myself an email and a couple other addresses (with the same domain as the initial address) immediately after the initial attempt, and they are sent successfully. I'm positive all addresses used are correct, some are merely replies to messages received. So why do I get error messages with certain addresses and not others? Is it an issue with the server or client?

Since the error message says the server is busy, I think it's safe to assume it's a server issue. I know, for instance, that I've clicked on a newsgroup message header and received a similar error, moved on to the next header which downloads with no problem, then back to the first header and now it opens. These things just happen. However, if it becomes a consistent problem, you might want to talk to your ISP to see if they have an explanation.

Error 5550

A message in your Outbox could not be sent using account xxx. The server did not recognize the recipients or the server refuses to allow you to send mail.

Explanation: 5.7.1 Unable to relay for <outgoing address>/ Relaying is prohibited

See Glossary for more info on relaying.

Possible solutions for Exchange Accounts:

This might be caused by a folder name in your Exchange account having a character that Entourage isn't handling well. For example, a / or. Check your folder names, get rid of these characters, and try again.

You may need to turn on authentication for your SMTP server.

Your network guy needs to allow relaying on their SMTP server. Are you trying to send e-mail from an address other than your work e-mail address ??? Some net admin forbid sending e-mails if the e-mail address you use is not one of 'theirs'..

User comment: In my case, the error was on the server side. The account has not been correctly configured with the full email address of the user. In a working account I could go into Outlook for Mac and view the properties of the account. The email address was properly configured as username@somecompany.com. The account that wasn't working only showed username. The Exchange server was rejecting this person's mail because it didn't recognize the user as being a part of somecompany.com.

Error 5452 or Error 5552 (when sending out mass e-mails)

Too Many Recipients

This error is being passed on by your mail server, because your mail provider has a limit to how many recipients you can send to in one message. Entourage has no limit. You should contact your mail provider to ascertain the maximum number of recipients per message and note it. You can use the free 'Split Recipients' script to send a mass e-mail in separate mailings automatically:

Error 5553:

sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

There are multiple solutions for this error:

1. Go to Preferences -> Mail & News -> Compose and make sure the option to check names [Automatically check names when sending messages] is off (the first option on that screen).
2. It's also possible that your recipient has some fierce anti-spam procedures in place that can only accept mail from a 'white-list' that he has created. There is nothing you can do about it other than try and contact recipient some other way and tell him the address you are trying to send from and he may add it to the white list.
3. Many hosts will not permit mail to be sent unless they have captured your IP address - a feature to prevent anonymous spammers. The first time you try and send the email, the email server will reject it (hence your host is not logged message) until the server has captured your IP. If you get the message, wait 60 seconds and try again - the message send. To avoid getting the message, send your mail AFTER you have picked it up, rather than the other way around.

Error 7010

The server returned the following error: Invalid command; valid commands: USER, QUITCheck the username/password or security settings.

This error can occur if is trying to receive mail using SPA (Secure Password Authentication). To resolve this problem...Open Account; Click here for advanced sending option ; Uncheck SMTP server requires authentication.

Error 8796

The action could not be completed:

Do a database rebuild. Start Entourage holding down the Option key. When the Rebuild dialog box comes up, choose to do a Typical Rebuild. More info on rebuilding your database.

Error 10002

Entourage 10.1.4 has no support for LDAPv2 servers, unlike all previous builds. However, LDAP v3 servers work. You'll either have to ask for the server to be updates to version 3, or revert to a previous version to remain connected to the server.

Error 10091

When you attempt to verify your network configuration by using the TCP/IP Ping.exe command-line utility (Ping Localhost or Ping 127.0.0.1), you may receive the following command-line error message:

PING: transmit failed, error code 10091

You may not be able to connect to (ping) another local computer or another computer on the local network or on the Internet.

This issue can occur if an incorrect Windows Sockets dynamic link library (DLL) file is in the current path or there is more than one simultaneous Windows Sockets implementation. If there is more than one Winsock.dll file on your computer, be sure the first one in the path is appropriate for the network subsystem currently loaded.

This issue can also occur if the Windows Sockets implementation is not currently installed or is configured incorrectly.

To resolve this issue, remove and then reinstall your networking components. For directions see MS KB 302861

Error 16007

This error indicates a corrupt or faulty installation of Entourage. Use the Remove Office tool to remove Office, and then re-install and apply the latest updates.

Error 16008 This error is related to several different problems with different solutions.

Symptom: Accessing your Microsoft User Data folder from a network volume sometimes caused problems. Sometimes, when you tried to access the folder, you received an error message that is similar to one of the following:

Entourage cannot access your data. To try to fix the problem, rebuild your database. An unknown (16008) error occurred.

Symptom: Mail could not be retrieved from POP account. Could mention error with Microsoft Database daemon.

Try deleting this preference: com.microsoft.OfficeNotifications.plist

Make sure you have only one daemon in your Startup Items. If you see more than one Microsoft Database daemon delete them all and let Entourage recreate a new one.

Symptom: If the problem is that it can't be copied in the file system, and he is getting I/O errors, this indicates a corrupted disk. I *strongly* suggest reformatting his hard drive. (Entourage developer tip)

User reported this fix.

File>Export. Export all items to an Entourage archive. All items. Entourage creates a file with .rge extension.

Use Remove Office

Install Office 2004 and Update

File. Import. Import information from your Entourage archive.

Error 16013

Error: An unknown error has occurred in Outlook.
Details:
Mail could not be received at this time.
Error code: 16013 '

User reported this fix:

The fix was checking in the IMAP mail via Apple Mail or the web and looking for any messages that are blank. When I say blank I mean they have no sender, no subject, and are 0 file size. This person had four blank messages. Once we deleted those their mail began to work normally.

Error 16406

There is a suggestion for a similar problem on the Microsoft site, which recommends increasing the (minimum) memory allocation to HotSync Manager.

Check out this page for the details: http://www.microsoft.com/mac/products/office/2001/entourage/palm/troubleshoot.htm#SynchronizingFailed

Error 16399 and 268452867 errors while syncing Palm

User reports: I seemed to have solved the problem by removing my Vindigo conduit from the active conduit folder, and synching now works. It seems to be a problem with Vindigo, and since I don't use it that much, I don't mind not having it active. No real detail on what the actual problem is, but at least I'm synching!

Error 16999

The POP Server Returned an Unexpected Reply (16999) Error Message and You Cannot Receive E-mail

When you attempt to receive e-mail, you may receive one of the following error messages: The POP server returned an unexpected reply (16999) -or- Could not retrieve mail from the account, a connection failure has occurred, error:-3280

CAUSE This behavior can occur if a damaged message on your e-mail server prevents access to the rest of your e-mail.

RESOLUTION To resolve this behavior, use one of these three methods to get rid of the message that is causing the problem.

Method 1 If your Internet account allows you to interact directly with your e-mail account over the Web, this method is the preferred way to remove damaged e-mail messages from your e-mail server. For instructions about how to do this, refer to your Internet service provider (ISP) documentation about e-mail and e-mail services.

Method 2 If your Internet account does not let you interact directly with your e-mail server, you can ask your ISP to remove the damaged messages from your e-mail account. Make this request by phone so that you can immediately check to see whether you can now receive e-mail after the suspected messages are removed.

Method 3 NOTE: This method involves the use of a third party application or software and should be used after methods 1 and 2 are attempted. Microsoft makes no warranty, implied or otherwise, regarding these products' performance, reliability or security. Delete the damaged message by using the tools that are available on the Internet. To do this, follow these steps:

1. Go to the following Web site: http://www.mail2web.com
2. Select Secure Login.
3. Type your e-mail address and password in the appropriate boxes, and then click Check Mail.
4. Click to select the check box next to the first e-mail message, and then click Delete Selected.
5. When the confirmation message appears, click Yes.
6. Try to receive e-mail in Entourage
7. If the error message still appears, continue to delete e-mail messages, one at a time, and try to receive e-mail after each deletion until the error message no longer appears.

Error 19999

Permission Error. Changes to the event ' could not be saved because you do not have the appropriate permission.

User reported: I wanted to look at another schedule - actually a conference room schedule, on Exchange / OfficeMAC/Outlook 2011 - and made the mistake of using the 'Open Calendar' button. Since then I have a constant 'Permission error' updating a couple of times a minute, forever, as though I'm trying to make an unauthorized change. Now I CANNOT remove that calendar from the navigation page - menu option is grayed out.

This is an Exchange issue. Ask on the Exchange forum:

Error : I receive this error when attempting to print a calendar in Entourage 2004. I can print email without any problem. Try this work around for the problem. Users have reported the problem while using the Franklin Monarch layout. The problem went away when switching to the Day Runner format.

MVP, Mickey Stevens provides this solution: It sounds like you might have a corrupt printing form. Delete this folder: /Users/<Your User>/Documents/Microsoft User Data/Printing Forms/ It will be recreated next time you print something, most likely eliminating the corruption that did not allow you to print earlier.