Outlook 2003 - Event ID 27 - Mail not sending

B

BrianWalshCork

Hello All,

After upgrading from Outlook 2000 / Exchange 2000 to Outlook 2003 / Exchange
2003, I am having a problem on one computer.

The user can start outlook, and can receive emails, but outgoing emails
remain in the outbox and will not send. When I click the Send/Receive toobar
button the "Outlook Send/Receive Progress" dialog box does not appear and the
following is logged in the Application Event Log:


=======================================
Event Type: Information
Event Source: Outlook
Event Category: None
Event ID: 27
Date: 10/11/2006
Time: 5:03:26 AM
User: N/A
Computer: FC010
Description:
The operation failed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
=======================================

The user's account is a member of the local machines Users group and Power
Users Group.

If I make the user an administrator on the local machine, then the emails
will leave the outbox as normal - but I don't want to leave the user as a
local admin, so this is not an acceptable workaround.

If I log onto a different computer then the user can also send emails as
normal, so this problem seems to be a user rights/security settings issue on
the affected computer.

Through google, I have found other people that experienced the same problem,
but nobody seems to have found a solution.


The problem computer was moved from a poorly configured Windows 2000 domain
to a new Windows 2003 server domain. The user was previously using both a
local machine account (which had local admin rights) and a domain based user
account from the old domain (which also had admin local rights), and the
user probably played around with the security settings to cause this problem.

The OS is Windows XP so my next step is to run the:

secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb
/verbose /log c:\seceditlog.txt

command to reset the windows XP security settings to the original defaults,
I think that this will fix the problem, but this is a bit drastic so I would
like to try any other suggestions first.

Thanks in Advance,
Brian Walsh
 
B

BrianWalshCork

Apoligies for the duplicate post - I received an error message the first time
I tried to post to say that the message could not be posted.

This is an update on the problem below. I actually had this problem on a
second computer, so I have ran the SECEDIT command on that computer and it
fixed the problem.

I haven't ran this on the first problem computer yet in case anyone has any
other suggestions.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top