Re: Exchange 2007 OWA Broken - Please help!

On Nov 12, 10:07 am, Wayne (CDX) <Wayne...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Well it'd working... sort of. When I ran the install CA roles command it
almost finished and then displayed an error that an unknown error occurred.
Something about an non-existent object. But when I looked in IIS, there were
all the virtual directories, except the "exchange". So I ran the cmdlet to
create the "exchange" directory. It completed fine.

But when I try to connect to the "exchange" directory it just fails.

The good news is I can connect to the "owa" directory and it works perfect.
All the correct authentication screens and everything. I'm going to live
with it as is. I don't know how to fix the "exchange" directory. I guess I'll
just chalk up the experience.

The issues with x86 and x64 I resolved earlier when I was messing around
with the sharepoint services on the W2K3 installation CD. It runs in x86 mode
and broke everything. I figured out the commands to revert back to x64. Thank
God for the Internet and forum sites.

Thanks again for your help.

~Wayne



"beowulfs" wrote:
i think the problem is because sharepoint drops iis down to 32-bit and
exchangehas problems with that. it's been a while since i tried it. you
may have to run this as well:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2361710&Site...
http://msmvps.com/blogs/cgross/archive/2004/08/08/11472.aspx

OWA440 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 accessOWA. 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 . . .

cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 "false"

"Wayne (CDX)" wrote:

Troy - Thanks for the help so far. You were right about the two services
(sharepoint andOWA) not co-existing together. I had to uninstall sharepoint
3.0 to get the commands to complete successfully. And as we speak, it
occurred to me that the .Net Framework 3.0 (which was installed with
Sharepoint) wasn't uninstalled so I am doing that now.

The pages stilll don't load yet, though. When you navigate to domainname/owa
you get the correct login page, but it fails on the owaauth.dll call. I'm
hoping the removal of .Net framework 3.0 corrects this, followed by a repair
of the .Net 2.0.

I'll post the results...

~Wayne

"beowulfs" wrote:

FYI even though it may be possible, I never got Sharepoint 3.0 andExchange
2007All Roles to coexist happily.

"Wayne (CDX)" wrote:

I recently stood up a new domain controller (Windows 2003 Standard x64). I am
a small business, so I can't afford multiple servers. Instead I invested into
a decent single server, dual Xeon processor, 4GB RAM, 500 GB HDD (RAID 5). I
installedExchange2007and after fumbling my way through, all was working.
"domainname.com/Exchange" brought me to theExchangelogin andOWAscreens. I
could send and receive messages. All was well. To complete the server I
needed two more components, Blackberry Enterprise Server 4.1 Express (BES)
and SharePoint Services 3.0. To install BES and have it work I had to install
the "MicrosoftExchangeServer MAPI Client and Collaboration Data Objects
1.2.1" It installed without issue and the BES server functions to date.
I installed Sharepoint services 3.0 and I think this is where myOWAgot
broken.
OWAwas on port 80, all IPs and when sharepoint installed, it took port 80
without a warning. Sharepoint is working without issue. To resolve the port
issues, I made the sharepoint site point only to my internal network card and
the Default Web Site to the external. That way they can both share port 80
listening on different IPs.

When you try to connect to the Outlook Web Access, it prompts for a
username/password (Windows Alert box) to connect, not the defaultExchange
login page and then reports there is no page to display.

In theExchangeHelp I found code to create a newOWA. I thought that may
fix it, but when run, it reports that theOWAdirectory already exists on
default web site. So I deleted theOWAvirtual directory. Restarted the IIS.
Ran the command again, same result. Still says it already exists.

So I tried recreating the "owa" virtual directory. Foolishly, I didn't note
the original settings, but found the directory that contains the
"OWA/default.aspx" and pointed it to that folder.

With a browser (external to my network) I can now connect to theOWAand see
my mailbox, but I can't send messages. Get a 404 error, access denied.

I observed that the other virtual directories had Wildcard application apps
in the [default web site\Exchange|Properties|"Application settings" -
"Configuration..." button, "C:\Program Files\Microsoft\Exchange
Server\Bin\davex.dll" was listed. So I tried adding that to theOWAvirtual
directory. Now theOWAvirtual directory acts like the "Exchange", "ExAdmin",
"Public", etc. Prompts for username/password and then fails, no page to
display.

Is there a way to remove the wholeOWAand rebuild it without having to
reinstall the wholeExchange2007again. That would be painful and it is in
use. I really don't want to take it down again. Everything else works fine.

Anyone have any ideas? Please help!- Hide quoted text -

- Show quoted text -

I was also getting IIS timeout errors and was unable to get OWA and
Forms Based Authentication to work on a new Microsoft Windows Server
2003 R2 build with Exchange 2007. I enabled "Outlook Anywhere" from
the "Client Access" menu under "Server Configuration" in the Exchange
Management Console. I validated IIS was configured properly and used
the Client Access Server Cmdlets to validate as well.

Turns out I had installed Windows SharePoint Services when building
the server. Once I removed WSS and SQL Desktop Edition OWA came right
up. I did not even have to restart IIS Admin or W3SVC. There is
definitely some conflict between OWA and WSS.
.