Just another Microsoft MVPs site

OWA 440 Authentication Timeout

As I mentioned in my earlier post today, I migrated my server here at home this weekend.  Well, once the new server was online, the only hiccup I discovered was that I couln’t access OWA.  I kept getting this bloody ‘440 Authentication Timeout’ page in IE.  And I would get it instantly, so there was no way it was actually timing out.  A quick google on this error returned a half dozen pages of threads, with no resolutions.  As a result, I figured I’d better blog this for future reference . . .


The root cause of this is the IUSR_<servername> and IWAM_<servername> accounts’ passwords being out of sync (between AD & IIS).  Here’s the steps necessary to fix this.  (And make sure to verify that neither of these accounts are locked out in AD!  I missed that the first time around and spent an extra hour and a half trying to figure out why it wasn’t working! :^)


1)  Open AD Users & Computers.  Expand the Users OU, right-click on the IUSR_<servername> account and select ‘Reset password’  Reset the password to anything you want (however, it can’t be blank).



2)  Open this User Account’s properties and verify that the account is not locked out  :^)  Also, make sure that ‘Password never expires’ and ‘User cannot change password’ are selected.


3)  Repeat steps 1 & 2 for the IWAM_<servername> account.  Close AD Users & Computers.



4)  Open Internet Information Services  (Start | Administrative Tools)


5)  Expand <servername> | Web Sites


6)  Right-click on ‘Default Web Site’ and select Properties.


7)  Go to the ‘Directory Security’ tab and click the Edit button under ‘Authentication & Access Control’


8)  Enter the new password for the IUSR_<servername> account and click OK.


9)  Enter the password again to confirm and click OK.


10) Click OK.


11)  Open a command prompt and enter  iisreset


12)  At the command prompt, enter the following commands:
        cd c:\inetpub\adminscripts
        adsutil SET w3svc/WAMUserPass <password>    (Where <password> = the password you entered for the IWAM_<servername> account in AD Users & Computers)
        c:\windows\system32\cscript.exe “c:\inetpub\adminscripts\synciwam.vbs” -v
        iisreset


Voila!  That should fix you right up . . .    :^)

77 Comments

  1. Nelson Morris

    I am an Exchange noob, but I can confirm the above does work!

  2. Gerry

    You ARE DE MAN!

    Your magic has successfully got my OWA Rocking!

    Thanks Bud

    G

  3. Bigscout79

    After reading your post I realized what I had done to make mine not work – I was changing ports and also changed the allow anonymous access to no or basically don’t allow anonymous access. Changing this back also fixed my problem – thanks for getting me on track.

  4. iRonTech

    Yes! It works fine after follow the command to reset iusr_server-name & iwam_server-name password and to the IIS.

  5. julian

    yea!!!

    this work!!!

    thanks man!!!!!!!!

  6. Tim Jenni

    Excellent Blog, thank you very much!! Ive been working on this for eight hours now!!!!

    You are the man!

  7. Alec Poon

    Been on the job for about 4 hours… and you gave me the answer I needed in less than 5 mins…

    Cheers Man… Peace

  8. Stephen Harrington

    Awesome job! Been stuck on this one for a few!

  9. aramus

    I get following message when running synciwam.vbs script.

    Out of process applications defined:

    Count: 2

    {3D14228D-FBE1-11d0-995D-00C04FD919C1}

    {3C768906-140D-4BEF-9E04-7B3C69783E3F}

    OWA continues giving 440 login timed out error.

  10. Steve Chitekulu

    My Owa too continues giving 440 login timed out error.

  11. netnolimits

    Thanks! The above worked great! The only difference was mine was using the IUSR_servername account. I followed the same procedure on this account and we’re back up. Thanks again!!!

  12. Kevin

    You de’ MAN!

  13. Rachiano Haselhoef

    Many thanks!

    Your solution works.

  14. techop

    didn’t work

  15. Chris J

    Not working here either.

    Tried using the local IUSR_servername account and the AD one. Also get the Out of process messages.

  16. Darrell Turner

    Check your logon hours!!! Don’t know how it happened, but mine were set to 8-5pm M-F.

  17. Onur

    vous etes d’lomme πŸ™‚

  18. JohnnyT

    Thanks – excellent work! Who needs to RTFM when there’s stuff like this around.

  19. JK

    Back in December of 2003/January of 2004, I worked with this problem for a long time before we finally figured out what was wrong. We had even more of a rough time because we had the passwords synched, but the problem was that it was the LOCAL IWAM and IUSR accounts, and not the ones on the actual domain. Use caution with that.. Also, ours would work for a while then give out about the same time everyday, and IIS needed to be recycled. I am noticing that more and more people have gotten the problem since then.. I’m wondering if MSFT is going to have a patch (or does it already have the patch) for this..

  20. CS

    Didn’t work for me at first but found the the logon hours were set to deny all. Once I changed this, it worked perfectly.

  21. SG

    Not working ……………

  22. Lare'

    If I read this right, there are four lines to type. Is there a space before and after quotes in third line?

    Was successful after first two lines.

    12) At the command prompt, enter the following commands:

    (—1)cd c:\inetpub\adminscripts

    (—2)adsutil SET w3svc/WAMUserPass <password> (Where <password> = the password you entered for the IWAM_<servername> account in AD Users & Computers)

    (—3)c:\windows\system32\cscript.exe "c:\inetpub\adminscripts\synciwam.vbs" -v

    (—4)iisreset

  23. alex@orangecountycomputer.com

    Well, it got past the 440 timeout error,

    I get the login screen but no login account works!

    I Tried reseting the accounts and or creating a new user, no login will work.

    I also tried the admin login no luck.

    All other services work, as far as company web, and remote desktop, etc.

    Sound like a authentication error again.

    I check to make sure anonymous access was check also.

    HELPPPPPPPPPPPPPP!

  24. Trish

    THANK YOU!!!!!! WORKS LIKE A CHAMP!!!!!

  25. Hugh

    Actually I had the same issue and the fix didn’t work for me. What DID work was to go under the Exchange System Manager and drill down to:Servers>{your server name}>Protocols>HTTP>Exchange Virtual Server.

    Right click it and properties. Then click on the settings tab. Unclick Enable Forms Based Authentication, and then apply. Stop and restart the web page in IIS. Then go back in and re-enable it. Say okay. It worked for me. I can now authenticate with any user.

    Good luck

  26. Y

    Thank you!

    My the IUSR_<servername> account was disabled.

  27. Mark Beck

    Hey, thanks much for the help. New SBS 2003 install and no formal training = wonderful & challenging combination.

    Any chance of getting an assist on the next step, accssing the OWA from the external world??? I have a xyz.net domain regsitered with my ISP and just can’t seem to get to the OWA URL from the outside. My internal domain is yyy.local and the OWA page comes up fine with the https://servername/exchange string.

    Thanks

    Mark

  28. Ihab Moneer

    Thanks alot my problem is solved.

    However, when i followed your steps i got this error after cscript synciwam.vbs -v

    IIS Applications Defined:

    Name, AppIsolated, Package ID

    w3svc, 0, {3D14228C-FBE1-11d0-995D-00C04FD919C1}

    Root, 2,

    Root, 2,

    root, 2,

    bin, 2,

    Microsoft-Server-ActiveSync, 2,

    Exadmin, 2,

    Root, 2,

    Out of process applications defined:

    Count: 1

    {3D14228D-FBE1-11d0-995D-00C04FD919C1}

    Updating Applications:

    Name: IIS Out-Of-Process Pooled Applications Key: {3D14228D-FBE1-11D0-995D-00C04FD919C1}

    Error: 80110414:

    any idea what is this??

    also is there a way to know the default permissions on each folder created by Exchange since first install.

    i kinda messed my settings and i modified alot of permissions from System manager and IIS and i hope there is a way to restore them back

    .

    Thanks.

  29. Nilesh Patel

    The Problem with

    3D14228C-FBE1-11d0-995D-00C04FD919C1

    Have you looked in your system event? You should see a event id of 10004 from DCOM.

    The message is I\O overlap error with IWAM user unable to logon.

    See eventid.net and Microsoft also so a google search on

    3D14228C-FBE1-11d0-995D-00C04FD919C1

    and you will find heaps of solutions. I managed to clear it off our 2000 server but it took serveral tries.

    Thanks for the blogger solution worked a treat…. first solution i found on this problem.

  30. Rahul

    Thanx a ton man. I was trying to solve the OWA problem for a week now. But this simple solution solved my problem within seconds.

  31. ddowns

    This worked for me, but I needed to add a step at the end (alex@orangecounty, this should fix your issue too)

    Yopu need to also Disable FBA in Exchange, iisrest, then re-enable it again, and iisreset again

    see http://hellomate.typepad.com/exchange/2003/11/formsbased_auth.html

  32. Schink

    Life saver

  33. Marjan

    thanks, You’re Tha Man

  34. Jeremii

    AWESOME!!! I was working all day trying to get this to work. This came up as the 1st hit in google and 5mins later, Bob’s my uncle. BOOYAA!!

  35. Michael Freidgeim

    In my case the reason for the same error was in

    settings of the Exchange virtual directory in Microsoft Internet Information Server (IIS).Exchange virtual directory was configured to accept only Secure Sockets Layer (SSL) connections and Integrated Windows authentication was not enabled on the Exchange virtual directory.

    see support.microsoft.com/default.aspx?kbid=817379

  36. Ian

    This sorted out my problem in a flash, top man!

  37. Joey Dunagan

    Great article. I’ve setup a few sbs boxes but never been a regular user. I can’t say how the site behaved before in terms of redirecting http:// requests over to the https://, but after the exchange reinstall and IIS configuration the redirect wasn’t happening for some clients. So I setup a redirect method.

    This assumes that:

    – you have a "default web site" entry in IIS

    – the "default web site" just performs sbs tasks for owa and remote access and doesn’t actually host a "www" style main web site

    – you have alread setup a certificate and enable ssl for your "default web site" entry in IIS manager

    1) Disable port 80 communication on the "default web site" by entering a random name (not dns resolvable) in the host field under the "default web site"’s advanced IP properties. I used "secure"

    2) Create a new web site

    – called "httpredirect"

    – point it to a new folder called c:\inetpub\httpredirect.

    – allow it to answer on port 80 with no defined host name

    3) in the c:\inetpub\httpredirect folder create folders for any virtual directories you think your clients might have bookmarked (ie. /exchange /tsweb /remote)

    4) create a "default.asp" file in each of the new directories (including c:\inetpub\httpredirect) containing the following text:

    (Note if the formatting in this comment blows the symbols away, the "default.asp" document should start with a less than symbol and a percent symbol, and then end with a percent sign and a greater than symbol)

    —-Beginning of File ——

    <%

    ‘Set the buffer so that a redirect is possible

    Response.Buffer = True

    ‘pull the requested url or host name

    varRequestURL = Request.ServerVariables("SERVER_NAME")

    varRedirect = "https://&quot; & varRequestURL

    ‘redirect to the https website for those that for whatever reasons don’t automatically

    Response.Redirect varRedirect

    ‘if they still don’t redirect, give them a nice link to click instead of the "USE HTTPS extension crap

    response.write "<html><body><br><a href=" & varRedirect & _

    ">Click here to be redirected to the secured version of the " & _

    varRequestURL & " site.</a></body></html>"

    %>

    —–End of File——

    Hope this helps somebody πŸ™‚

    Joey

  38. Joey Dunagan

    Great article. I’ve setup a few sbs boxes but never been a regular user. I can’t say how the site behaved before in terms of redirecting http:// requests over to the https://, but after the exchange reinstall and IIS configuration the redirect wasn’t happening for some clients. So I setup a redirect method.

    This assumes that:

    – you have a "default web site" entry in IIS

    – the "default web site" just performs sbs tasks for owa and remote access and doesn’t actually host a "www" style main web site

    – you have alread setup a certificate and enable ssl for your "default web site" entry in IIS manager

    1) Disable port 80 communication on the "default web site" by entering a random name (not dns resolvable) in the host field under the "default web site"’s advanced IP properties. I used "secure"

    2) Create a new web site

    – called "httpredirect"

    – point it to a new folder called c:\inetpub\httpredirect.

    – allow it to answer on port 80 with no defined host name

    3) in the c:\inetpub\httpredirect folder create folders for any virtual directories you think your clients might have bookmarked (ie. /exchange /tsweb /remote)

    4) create a "default.asp" file in each of the new directories (including c:\inetpub\httpredirect) containing the following text:

    (Note if the formatting in this comment blows the symbols away, the "default.asp" document should start with a less than symbol and a percent symbol, and then end with a percent sign and a greater than symbol)

    —-Beginning of File ——

    <%

    ‘Set the buffer so that a redirect is possible

    Response.Buffer = True

    ‘pull the requested url or host name

    varRequestURL = Request.ServerVariables("SERVER_NAME")

    varRedirect = "https://&quot; & varRequestURL

    ‘redirect to the https website for those that for whatever reasons don’t automatically

    Response.Redirect varRedirect

    ‘if they still don’t redirect, give them a nice link to click instead of the "USE HTTPS extension crap

    response.write "<html><body><br><a href=" & varRedirect & _

    ">Click here to be redirected to the secured version of the " & _

    varRequestURL & " site.</a></body></html>"

    %>

    —–End of File——

    Hope this helps somebody πŸ™‚

    Joey

  39. Anders

    Thanks. Worked last week. Today it doesn’t. Reset passwords. When resetting password in IIS I was prompted by Child Nodes (Exadmin, Exchange, Microsoft-Server-ActiveSync, OMA, Public) Selected All. OK. Command prompt – iisreset. Did not do adsutil… (got error message "this script does not work with WScript" Would you like to register CScript as your default host fr VBscript?" OK, however OWA now works!

  40. George

    You are a ‘Genius’ πŸ™‚

    For those of you who are still having problems then I suggest you try going to this link then perform Method 1 under the heading:

    ‘Exchange 2003

    Method 1: Reset the HighWaterMarks’

    after performing method 1 then perform method 2.

    Once you have performed both methods then try following the ‘Genius’ fix as described below:

    1) Open AD Users & Computers. Expand the Users OU, right-click on the IUSR_<servername> account and select ‘Reset password’ Reset the password to anything you want (however, it can’t be blank).

    2) Open this User Account’s properties and verify that the account is not locked out :^) Also, make sure that ‘Password never expires’ and ‘User cannot change password’ are selected.

    3) Repeat steps 1 & 2 for the IWAM_<servername> account. Close AD Users & Computers.

    4) Open Internet Information Services (Start | Administrative Tools)

    5) Expand <servername> | Web Sites

    6) Right-click on ‘Default Web Site’ and select Properties.

    7) Go to the ‘Directory Security’ tab and click the Edit button under ‘Authentication & Access Control’

    8) Enter the new password for the IUSR_<servername> account and click OK.

    9) Enter the password again to confirm and click OK.

    10) Click OK.

    11) Open a command prompt and enter:

    iisreset

    press Enter

    12) At the command prompt, enter the following commands:

    cd c:\inetpub\adminscripts

    adsutil SET w3svc/WAMUserPass <password> (Where <password> = the password you entered for the IWAM_<servername> account in AD Users & Computers)

    c:\windows\system32\cscript.exe "c:\inetpub\adminscripts\synciwam.vbs" -v

    iisreset

  41. George

    You are a ‘Genius’ πŸ™‚

    For those of you who are still having problems then I suggest you try going to this link then perform Method 1 under the heading:

    ‘Exchange 2003

    Method 1: Reset the HighWaterMarks’

    after performing method 1 then perform method 2.

    Once you have performed both methods then try following the ‘Genius’ fix as described below:

    1) Open AD Users & Computers. Expand the Users OU, right-click on the IUSR_<servername> account and select ‘Reset password’ Reset the password to anything you want (however, it can’t be blank).

    2) Open this User Account’s properties and verify that the account is not locked out :^) Also, make sure that ‘Password never expires’ and ‘User cannot change password’ are selected.

    3) Repeat steps 1 & 2 for the IWAM_<servername> account. Close AD Users & Computers.

    4) Open Internet Information Services (Start | Administrative Tools)

    5) Expand <servername> | Web Sites

    6) Right-click on ‘Default Web Site’ and select Properties.

    7) Go to the ‘Directory Security’ tab and click the Edit button under ‘Authentication & Access Control’

    8) Enter the new password for the IUSR_<servername> account and click OK.

    9) Enter the password again to confirm and click OK.

    10) Click OK.

    11) Open a command prompt and enter:

    iisreset

    press Enter

    12) At the command prompt, enter the following commands:

    cd c:\inetpub\adminscripts

    adsutil SET w3svc/WAMUserPass <password> (Where <password> = the password you entered for the IWAM_<servername> account in AD Users & Computers)

    c:\windows\system32\cscript.exe "c:\inetpub\adminscripts\synciwam.vbs" -v

    iisreset

  42. Alex Catlow

    i have this same problem… i think that it is my IIS settings so can somebody send me the screen prints for all the IIS settings for OWA

    i think it would be

    /exchange/*

    /exchweb/*

    /public/*

    /rpc/*

    and i need to set up external and internal to look at the same address…

    external = mail.faithcc.com.au

    internal = gabriel.faithcc.office

    could somebody plz help me out here… stuck for almost 2 weeks in total… unhappy chappy’s round here…

    but i tell you what stress does make u cry no matter how many ppl tell you it doesnt

    alex catlow

    acatlow at gmail dot com

  43. Alex Catlow

    Hi Guys… much easier solution and it worked for me… not saying it will work for anybody or everybody but if none of the above will work for you try this…

    owalogon.asp comes up with 440 login timeout replace it with your country’s desired logon.asp page..

    example australia uses usa so i find usa’s logon.asp page…

    "C:\Program Files\Exchsrvr\exchweb\bin\auth\usa"

    and copy into

    "C:\Program Files\Exchsrvr\exchweb\bin\auth"

    delete the original "owalogon.asp" and rename update "logon.asp" to the original’s name "owalogon.asp

    hopefully that can solve a few people’s problems…

    make sure you backup before alterations… this is always a must

    Alex Catlow

    alesis_c @ hotmail.com

    acatlow @ gmail.com

  44. Scott

    Alex, your solution of copying the "logon.asp" into the C:\Program Files\Exchsrvr\exchweb\bin\auth directory and then renaming it to "owalogon.asp" worked. Nothing else I tried worked before that so thank you!

    I’ve since gone back and figured out why that fixed the problem. Maybe this solution will help others too.

    Anyway, the "owalogon.asp" is supposed to direct you to the appropriate "logon.asp" depending on what language you are using. If you are in the USA, it will direct you to the "logon.asp" file in the "C:\Program Files\Exchsrvr\exchweb\bin\auth\usa" directory. By replacing the "owalogon.asp" file with the "logon.asp" from the USA directory and renaming it, it never needs redirected to the actual logon.asp file and therefore the problem goes away.

    The problem I was having is that I was editing and moving around various "logon.asp" files trying to customize it. In the process of doing that, the permissions were lost. Only Administrators had rights to the "logon.asp" file! So I went into the properties of the file and configured it to inherit the permissions. I then went back to the original "owalogon.asp" file instead of using the renamed "logon.asp" file.

    That fixed the problem. Your workaround pointed me in the right direction but I thought other people might have this problem and want to fix it a different way.

  45. Chris

    Hi great site, followed your instructions. Got rid of the authentication timeout error but now none of my users are able to log in to OWA.

    Says "You could not be logged on to Outlook Web Access. Ensure that your user name and password are correct, and then try again."

    Please Help!!!!

  46. humbletech99

    didn’t work, I can get a logon box if I didable forms-based authentication but the OWA is a bit screwed up (it doesn’t look fully loaded).

    I’ve tried everything I can find.

    I NEED HELP!!!!!

  47. Mark

    Hugh, nice one… your reply about disabling and reenabling forms based authentication did it for me – fanTAStic!

  48. James

    god bless the internet and bloggers like yourself – our OWA is alive once again after following your advice!!!!!

    Very Many thanks!

  49. Scott MCP

    Worked after disabling FBA resetting IIS, re-enabling FBA, then reseting IIS again. Thanks a ton…

  50. Jeff MCSE

    This saved my life today.

    Thanks

  51. Ran

    Mate, thank you so much You have saved my day.
    Worked like a dream

  52. Raf

    Thanks Thanks and Thanks again !

  53. JP

    Hey man,

    You saved me an afternoon of troubleshooting, thanks!!!

  54. Joe Schmuckitelli

    Duuuuuuuude!

    I had been banging my head against the wall. I tried all of the MS KBA’s, along with other very well known tech sites. This fixed me right up.

    Kudos and thanks.
    JS

  55. Rod

    Resetting the FBA worked nicely! Thanks!

  56. Leeman

    A little more info…

    Worked after disabling FBA resetting IIS, re-enabling FBA, then reseting IIS again.

    Also doesn’t work on the actual server (just in case you are trying to test it from there), but works fine from an outside client and internal clients. That’s all we need!!!!

  57. Bronski Pete

    Yep, thanks for this, I just moved my server and hit the same glitch.

  58. Matthew

    Thank you for your posting… It saved me hours of work…

  59. Soenke

    Great sequence of comments following a great blog!
    cgross’ and Alex’s comments got me fixed up…. think my problem was permissions related….
    All I’m left with now is the OWA calendar – getting session expiries left right and centre, but email is up – makes the users happy. Thanks!!

  60. Jon

    Hi worked great whit the 440 error … but now, all i get after the login screen is a blank page and https:///exchweb/bin/auth/owaauth.dll in the address bar … any one got an solution ?? .. i’m all out of iders …

  61. Khang Nguyen

    Thank your for your solution. It worked!

  62. Brian

    You are THE shit! You solution worked very well. One thing that some need to remember is that for FBA to work you must allow basic AND Integrated authentication. FBA will not work without the basic authentication. Thanks,

    Brian

  63. Bingo!

    Gawd, what a lifesaver you are. Thanks.

  64. Jim

    figured I’d add my praise. There’s no way in h3ll I would’ve come up with this. Thanks much.

  65. Walter

    Fantastic, I had an exchange problem with the installation of SP2 which stripped the machine of it’s AD components, I had to trouble shoot the AD machine permissions, reinstall AD on the machine, manually troubleshoot the services not starting, I had access to pst’s again through outlook but OWA wasnt working, this cleared it up straight away, Incidently I also got the out of process error message, however it still worked.

    Cheers!

  66. Tim

    I would have to agree, this solution (just applied) will hold up under my 2000 user organization.

  67. adminapo

    i open my web outlook access through a local network and i put my domain\username i put my password but it doesn’t accept them…. any solution????? my password and my account is right

  68. Christian

    OK if you do the above and get the this reply,
    IIS Applications Defined:
    Name, AppIsolated, Package ID
    w3svc, 0, {3D14228C-FBE1-11d0-995D-00C04FD919C1}
    Root, 2,
    Root, 2,
    root, 2,
    bin, 2,
    Microsoft-Server-ActiveSync, 2,
    Exadmin, 2,
    Root, 2,

    Out of process applications defined:
    Count: 1
    {3D14228D-FBE1-11d0-995D-00C04FD919C1}

    Updating Applications:
    (it stops here)

    Then do the following.

    Open a command prompt and go to:

    %windir%\system32\inetsrv

    type:

    rundll32 wamreg.dll, CreateIISPackage

    This is case-sensitive!

    followed by

    iisreset

    This will re-create the IIS Packages.

    Now run,

    c:\windows\system32 cscript.exe “c:\inetpub\adminscripts\synciwam.vbs” -v

    iisreset

    Should work fine now.

  69. Bryan

    I’m expierencing the same error:
    IIS Applications Defined:
    Name, AppIsolated, Package ID
    w3svc, 0, {3D14228C-FBE1-11d0-995D-00C04FD919C1}
    Root, 2,
    Root, 2,
    root, 2,
    bin, 2,
    Microsoft-Server-ActiveSync, 2,
    Exadmin, 2,
    Root, 2,

    Out of process applications defined:
    Count: 1
    {3D14228D-FBE1-11d0-995D-00C04FD919C1}

    I’ve migrated SBS2003 server to new hardware. After the migration I’m unable to load the companyweb site, or any of the wed driven managment tools. I’m able to reach the server from outside of the network which will load the “Welcome to Windows Small Business Server 2003 To get started, click a link.”

    From this point on none of the links work they all 404.

    I’m pulling out my hair, I’ve tried all of the fixes listed in the Blog except the OWA copy logon fix.

    Any ideas?

  70. EdgeMan

    Another note of thanks to you for your excellent words. Had this issue and this just worked.

    Many many thanks for this…

  71. sam

    This is a great post gone through all the solutions on here to no avail though, still get the auth timeout though. (disabling FBA gets me in but stuff doasnt display properly) Also my monitoring and reporting SBS management will not display…

  72. sam

    OK! For me it was permissions on the exchweb folder. Thanks

  73. Km2cyber

    I tried the steps in this post and it failed to work for me. So here are the steps that I followed.

    1) Uninstall the Certificate Services
    2) Disable Forms based Authentication
    3) Delete and Recreate the exchange Virtual directories – see http://msmvps.com/blogs/kwsupport/archive/2004/10/02/14723.aspx
    4) Re-install Certificate Services
    5) Re Enable forms Based Authentication
    6) Run IISRESET.

    Hope this helps out someone.

  74. Adam

    Worked exactly as blogged.

    Many….. MANY thanks πŸ˜‰

  75. Staceman

    While installing FTP on my already well preforming SBS2003 box, IIS Broke. After hitting Google about this error and locating your blurb I would like to thank you for the great tip!

    It worked a treat, 1st time.

    Stace Hema

  76. Brian

    WOW, thanks for the help. I did not have to type in anything after I used iisreset.

    Thanks again, you are indead THE MAN!!

  77. Fernando Esposito

    Thanks a lot for make me save a few hours searching and testing. Many thanks again from the South lands (Argentina).

    Fernando Esposito

Leave a Reply

Your email address will not be published. Required fields are marked *