Results 1 to 6 of 6

Thread: Entourage Error : Could not open that feature mail

  1. #1
    Join Date
    Oct 2009
    Posts
    5

    Entourage Error : Could not open that feature mail

    Hi,

    I'm using Entourage X on a PowerBook G4 with 10.5.2. The error message began to appear from when I tried to check email yesterday morning. All other features of the entourage appears to be accessible. When I click the e-mail function that opens a blank on my computer category. Try clicking on any of the categories below (Inbox, Outbox, Sent, personal folders, etc.) I get the error message "Could not open that feature. Entourage gets stuck and this error message comes over and over again until I force quit Entourage. Any suggestions?

  2. #2
    Join Date
    Dec 2007
    Posts
    263

    Re: Entourage Error : Could not open that feature mail

    Before giving answer to your question, can you tells us the below things :
    * Make sure you have a problem rather than a network or server failure.
    * What is your email provider?
    * What is the e-mail protocol POP3 or IMAP?
    * How much free space do you have on your hard drive?

  3. #3
    Join Date
    May 2008
    Posts
    244

    Re: Entourage Error : Could not open that feature mail

    Try rebuilding the database. In Entourage X, first go to Entourage> Turn Off Office Notifications. Now, quit Entourage, and then restart Entourage holding down the Option key. When the Rebuild dialog box appears, choose for a typical reconstruction. If this does not solve the problem, repeat procedure, opting instead for advanced Rebuild.

  4. #4
    Join Date
    May 2008
    Posts
    376

    Re: Entourage Error : Could not open that feature mail

    Try dragging the folder on the desktop. This creates an mbox file. Now switch to a new identity in Entourage under File. Drag the MBOX file into the folder list. Now you can see the mail. If mail is fine, then return to their original identity and remove the problematic folder. Drag the MBOX file back to the folder list and test it.

  5. #5
    Join Date
    Mar 2008
    Posts
    672

    Re: Entourage Error : Could not open that feature mail

    If you are using Mac OS X 10.4 or later, you must use Disk Utility instead of fsck, whenever possible. In some situations, file system errors may prevent the computer from booting. This can occur after an improper shutdown, forced restart, or power outage. If your computer shows any of these symptoms at the start, use a disk repair utility.

  6. #6
    Join Date
    May 2008
    Posts
    279

    Re: Entourage Error : Could not open that feature mail

    "Could not open that feature mail" means that the demon of the database has crashed or been quit. To resolve this issue try the below steps :
    1) Open the Activity Monitor, select all the processes: the type of demon. You see the Database Daemon Microsoft and the Microsoft AU daemon (that launches the automatic update program.) Allow the daemon Microsoft Database (s). You may need to Force Quit.
    2) Open System Preferences -> Accounts -> Startup Items. Remove all if more than one database daemon Microsoft.
    3) Open / Users / Library / Preferences. Remove the com.microsoft.OfficeNotifications.plist

Similar Threads

  1. Entourage Error 3260 - Could not retrieve mail
    By Justin23 in forum Windows Software
    Replies: 6
    Last Post: 20-09-2011, 11:34 AM
  2. Replies: 5
    Last Post: 12-03-2010, 04:52 AM
  3. Entourage Error 3155 : Unable to send mail
    By avit in forum Windows Software
    Replies: 5
    Last Post: 10-02-2010, 12:48 AM
  4. Importing Entourage into Apple Mail
    By avvia in forum Windows Software
    Replies: 3
    Last Post: 25-06-2009, 09:37 AM
  5. Mail going to the wrong inbox in Entourage
    By mathews in forum Operating Systems
    Replies: 3
    Last Post: 09-06-2009, 05:11 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,938,628.78102 seconds with 17 queries