I am deploying Exchange 2007, all was going well, until i
installed
rpc over https and tried to get that working, this broke
OWA and its
forms based authentication, with 440 login timeout. I
eventually
fixed this by using exchange management shell with
removing the
OWA virtual drives, and recreating them, NOW all is fab
OWA works in
forms based authentication again, internal and external,
superb.
My problem is now Direct file access in open location is
now broken,
and it is on in the exchange management console.
It come sup with :-
LOCATION BLOCKED
! For security reasons , Outlook Web Access is configured
to prevent
access to this type of document or foler. For more
information,
contact technical support for your organization ?
DOES ANY BODY knows how to fix this please, as this is
delaying my
role out for this function that everybody wants.
Thank you all in advance.
PLEASE IGNORE I HAVE FIXED IT, i missed a settings,but
hopefully my post will help people know how to fix the
owa problems with 440login timeout
- Follow via:
- RSS
- Email Alert
Question
0
Votes
Exchange 2007 OWA
Updated - 22nd Mar 2007
Answers (2)
0
Votes
Specifics
Hello,
I have been wrestling with Exchange 2007 for quite awhile now, and have run into the same issues you have.
If you would not mind, what were the specific steps you took to fix the 440 Login issue?
Any help would be appreciated.
Thank You
Marc Schlesinger
info@mcshelp.com
I have been wrestling with Exchange 2007 for quite awhile now, and have run into the same issues you have.
If you would not mind, what were the specific steps you took to fix the 440 Login issue?
Any help would be appreciated.
Thank You
Marc Schlesinger
info@mcshelp.com
31st Mar 2007
Replies
here's what i did to solve the problem on my server:
We have only one Exchange server (2007), so everything described here is made on the same machine.
a) In the Exchange management console, I copied all the properties of OWA.
Go to "server configuration\ClientAccess", then pick up the correct server, then "OWA" tab, right click owa (default web site): properties . I had to restore them later on.
b) use the Exchange Management shell and run the following:
(please refer to http://technet.microsoft.com/en-us/library/aa998624.aspx for details)
1) Get-OwaVirtualDirectory -Server to check the settings
2) Remove-OwaVirtualDirectory -Identity to remove the existing virtual dir (only owa in this case, I didn't touch the others)
3) New-OWAVirtualDirectory --Name "owa" (I only used the -name parameter, that worked for me)
c)Go back to the management console and restore properties of owa.
d) restart IIS via command iisreset /noforce
Web Outlook was running again after that.
Good luck
We have only one Exchange server (2007), so everything described here is made on the same machine.
a) In the Exchange management console, I copied all the properties of OWA.
Go to "server configuration\ClientAccess", then pick up the correct server, then "OWA" tab, right click owa (default web site): properties . I had to restore them later on.
b) use the Exchange Management shell and run the following:
(please refer to http://technet.microsoft.com/en-us/library/aa998624.aspx for details)
1) Get-OwaVirtualDirectory -Server to check the settings
2) Remove-OwaVirtualDirectory -Identity to remove the existing virtual dir (only owa in this case, I didn't touch the others)
3) New-OWAVirtualDirectory --Name "owa" (I only used the -name parameter, that worked for me)
c)Go back to the management console and restore properties of owa.
d) restart IIS via command iisreset /noforce
Web Outlook was running again after that.
Good luck
BeeGee33
4th May 2007
I had a problem when I changed some of the permissions within the 'exchange' and 'owa' folders. I could not get them back to working defaults. Your steps worked great. Just make sure that when you enter the Virtual Directory ID Parameter, you need to make it "servername\owa (Default Web Site)" or just how the name appears in step 1.
newsletters@...
15th Jun 2007
Btw your fix worked great!!
Thanks for posting. I had been struggling with this for the past 2 days. I was very skeptical/scared at first to remove OWA completely, but I had exhausted everything else to no resolve.
I thank you very much.
Thanks for posting. I had been struggling with this for the past 2 days. I was very skeptical/scared at first to remove OWA completely, but I had exhausted everything else to no resolve.
I thank you very much.
rajk@...
11th Dec 2007
Struggled with this one for a day, tried the IUSR/IWAM account resets without any luck. Removing and recreating the OWA virtual directory per these instructions worked! Thanks.
adegutis@...
3rd Jan 2008
Awesome that did the trick for me too.
Thanks for sharing.
Cheerz!!!
Thanks for sharing.
Cheerz!!!
mailtomohsin@...
30th Jan 2008
Thank you very much BeeGee you helped me too much
Hoper88
11th Oct
0
Votes
OWA 440 TImeout may be because IWAM and IUSR Account out of Sync
I found this solution on http://msmvps.com/blogs/cgross/archive/2004/08/08/11472.aspx
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_ and IWAM_ 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_ 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_ account. Close AD Users & Computers.
4) Open Internet Information Services (Start | Administrative Tools)
5) Expand | 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_ 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 (Where = the password you entered for the IWAM_ account in AD Users & Computers)
c:\windows\system32\cscript.exe "c:\inetpub\adminscripts\synciwam.vbs" -v
iisreset
Voila! That should fix you right up . . . :^)
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_ and IWAM_ 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_ 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_ account. Close AD Users & Computers.
4) Open Internet Information Services (Start | Administrative Tools)
5) Expand | 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_ 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 (Where = the password you entered for the IWAM_ account in AD Users & Computers)
c:\windows\system32\cscript.exe "c:\inetpub\adminscripts\synciwam.vbs" -v
iisreset
Voila! That should fix you right up . . . :^)
19th Sep 2007
Replies
Thanks mikeyb, I spend a lot of time reading post on the web for this exchange issue, and nothings works until this...
Thank you very much!
JP
Thank you very much!
JP
jdenegri@...
9th Oct 2007
thanks, good job.
btuncay@...
3rd Apr 2008
