« Previous Next »
Last post 02-23-2009 5:04 PM by AaronR. 6 replies.
Average Rating Rate It (5)Thank you for the rating!
Page 1 of 1 (7 items)
Sort Posts: Oldest to newest Newest to oldest
I had to re-install all of framework (according to mssupport) to fix an automatic updates issue - during this process i entered a command - cscript %SystemDrive%\Inetpub\AdminScripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 in order to complete it. currently my IIS server is no longer working (only my users ability to access OWA) can anyone point me in the right direction of how to revert this back to being operational or tell me what other information they may need?
Hi,
Which version of OWA are you using and which version version of the .Net framework does it require ? Was your web server working correctly before you configured the Enable32bitAppOnWin64 setting ?
Regards,
I fixed it with this KB article http://support.microsoft.com/kb/894435 - but I've got another problem (possibly unrelated but I would assume OT) that exists with "autodiscovery" I have not researched it yet claiming "the name of the security certificate is invalid or does not match the name of the site." I'm going to research it soon but if you think by chance it is related please send me a heads up - I'm still subscribed to the topic
thanks!
This error (or warning to be more accurate) occurs if you browse to an SSL enabled site and the name you put in your browser's address bar doesn't match the common name of the certificate. If your certificate has a common name of owa.company.com then you should type https://owa.company.com in your browser's address bar.
hmmm it only appears to show itself when using outlook 2007 (to exchange svr 2007)
using owa appears to be fine and the warning does not appear - it only appears when I startup outlook 2007 - This article appears to be exactly my problem although I'm wearing of implementing it yet. especially during the business day. http://www.pro-exchange.be/modules.php?name=News&file=print&sid=345I will look more into Microsofts KB http://support.microsoft.com/default.aspx/kb/940726 let me know if you think im totally on the wrong track otherwise I'll let you if/when I implement one and the result.
neither solution worked :( any ideas anyone? when someone tried to create an OOF message it said server unavilable (from outlook) I can create an oof from owa though.... has anyone seen anything similar in the past?
The solution to this problem ended up requiring me to recreate all virtual directories in IIS through the exchange management console
... this helped (STEP 1 ONLY)
http://support.microsoft.com/kb/941201