Link to home
Start Free TrialLog in
Avatar of agdickinson
agdickinsonFlag for United States of America

asked on

Active Sync IP-AUTD failed to initialize error [0x80004005)

Server: SBS 2003 R2
Email: Exchange 2003 SP2

Recently installed new microsoft fix: KB950159

Since installing the fix, and some other recent fixes I've been seeing the following errors in Event Log under Applications


Source: Server ActiveSync
Event ID: 3024
Type: Error
IP-based AUTD failed to initialize.  Error code: [0x80004005].

Source: Server ActiveSync
Event ID: 3015
Type: Error
IP-based AUTD failed to initialize because the processing of notifications
could not be setup.  Error code [0x80004005].  Verify that no other
applications are currently bound to UDP port [2883], or try specifying a
different port number.

This seems to happen everytime a message is pushed to a device, but the devices do seem to be functioning correctly.

I've followed some microsoft articles to do a

netstat -ano

And verified that 2883 is shown:


  UDP    0.0.0.0:2883           *:*                                    2024

The PID is the same as DNS, which I'm guessing is okay.

Whilst these errors don't seem to be affecting functionality I would like them resolved, unfortunately there isn't much out there suggesting a solution.

Other than the fix installed nothing else has changed.

Any help would be appreciated.

Andrew Dickinson
ASKER CERTIFIED SOLUTION
Avatar of agdickinson
agdickinson
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of scottjones936
scottjones936

I experienced this same problem. Restarting the DNS Server Service resolved the problem for me, also.

Thanks!
Thanks for that - had the same error for a day or two...
I read your post and retstarted the DNS Server service and all is resolved.

Cheers
I think your solution is temporary..your problem is going to pop-up again when you reboot. The problem is the result of installing MS08-037 (951746 and 951748) and needs a registry edit to resolve the problem permanently or until a new patch from MS is produced.

Check this out:
http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx

And this:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;812873
Thanks Arcaex

That fix worked great for me had the error pop up yesterday did the reg tweak and restart and no more error.

thanks

jjanknegt
Same problem - restarted DNS fixed the problem then added the registry entry as arcaex stated.
accepted solution worked for me aswell
diddo -- trying to find a solution on Palm forums yielded nothing.... glad i found this post.  resetting DNS server fixed problem.  Thanks.
Restarting DNS fixed issue, many thanks.
YEA THANKYOU
had the same problem but only started looking for it because all my iphones ios 3.0 and 4.0 started consuming a lot of battery. they would use an entire battery in half a day.

after doing the fix above works great again.

found that the active sync devices would ping the server several time per minute using all the battery.

Can be confirmed by looking in the IIS logs on the client access server and searching for "DeviceType=iPhone&Cmd=Ping"
Last nights updates did the same and restart of DNS service fixed it, thanks!
Restarting the DNS service fixed the issue. Thank you.
This same solution just worked for me!

Thank you
Thank you, restarting the DNS service fixed the problem for me! you guys are Awesome!!
Awesome.  Thank you so much for the fix.  Experts Exchange comes through again!
Restared the dns and ...boum !!! Thanks
Restarted DNS server service - Sorted the issue.

Gonna reserve the port for the future though - thanks
Reserved the port in registry then restarted DNS service and everything looks fine. Thanks for this!
Thanks restarted the DNS server service and error has vacated! will add port exceptions into registry if error re-occurs.
Restarting the DNS Server fixed this problem immediately.
Thanks
Restarting DNS worked perfectly.  Thank you to those involved.