Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

IMAP4SVC Not starting automatically


  • Please log in to reply

#1
Dave Kruger

Dave Kruger

    Member

  • Member
  • PipPip
  • 44 posts
Hi, lately on the exchange 2003 server I have, I have been having an issue with the IMAP4 service not starting when the server is restarted. It could be that it never did this properly, since we have only one users phone that needs imap on the server, and so has only just be turned on a few weeks ago. Anyway, if I start the service manually it operates properly and without generating errors in the event log, but if it tries to start it automatically I get the following two error messages which show up in the application event log:

source: imap4svc
event id: 1040
Desc: An error occurred while starting the Microsoft Exchange IMAP4 Service: the call to DsctxGetContextEx() failed with error 0x8007077f.

&

source: imap4svc
event id: 1040
desc: An error occurred while starting the Microsoft Exchange IMAP4 Service: the call to IIS_SERVICE::StartServiceOperation() failed with error 0x8007077f.

When checking some of the other logs, there are some other errors, which to me sortof sound like the network connection for the server is not yet available when it attempts to start the imap4svc, such as not finding any DS servers, one related to not being able to process group policy events...I may do some more checking in to those errors, incase they are the cause of the issues with imap. Does anyone have other ideas I could check?

Thanks!
  • 0

Advertisements


#2
Dave Kruger

Dave Kruger

    Member

  • Topic Starter
  • Member
  • PipPip
  • 44 posts
Got the problem resolved, it turns out that something was corrupt with the computer account in active directory. After manually removing that and rejoining to the domain, correcting group permissions for the exchange server, etc. the problem has gone away.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP