Kacey Fern
asked on
ACT 13 Web portion changed exchange 2010 to 32 bit on SBS2011
Greetings Experts,
We had an Act specialist install ACT 13 on our sbs2011 server. They also installed the web portion, which we just found out was not compatible, per SAGE. After the install, OWA, Active-Sync and the exchange mgt console do not work.
From what I'm getting, is that ACT changed exchange to a 32 bit application. I was able to go through the event log and fix some of the errors by editing the applicationhost.config.
See below for the changes that I made:
If I open the EMC, I cannot expand and get the following response:
Connecting to remote server failed: WinRM client cannot process the request. (abreviated)
If I try and connect to owa from the server:
I receive the Cert warning, due to using the IP/owa, then get a http Error 500.19 Module: exppw could not be found.
I checked the physical path and the file is there. C:\pf\mic\exch serv\v14\clientaccess\owa
Also getting event id 1, autodiscover can not start
Also getting asp.net 2 warnings
Has anyone seen this? Any quick fixes, or should I call MS?
ACT web has been uninstalled, and server rebooted.
Any help would be great... Thank you for any attempts.
Kacey
Changes that were made:
Orig: <add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dl l" />
Change: <add name='kerbauth' image='C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth. dll ' preCondition='bitness64' />
Orig: <add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Ow a\auth\exp pw.dll" />
Change: <add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Ow a\auth\exp pw.dll" preCondition="bitness64" />
Orig: <filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ow a\auth\owa auth.dll" enabled="true" />
Change: <filter name="Exchange ActiveSync ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\sy nc\bin\Air Filter.dll " enabled="true" />
We had an Act specialist install ACT 13 on our sbs2011 server. They also installed the web portion, which we just found out was not compatible, per SAGE. After the install, OWA, Active-Sync and the exchange mgt console do not work.
From what I'm getting, is that ACT changed exchange to a 32 bit application. I was able to go through the event log and fix some of the errors by editing the applicationhost.config.
See below for the changes that I made:
If I open the EMC, I cannot expand and get the following response:
Connecting to remote server failed: WinRM client cannot process the request. (abreviated)
If I try and connect to owa from the server:
I receive the Cert warning, due to using the IP/owa, then get a http Error 500.19 Module: exppw could not be found.
I checked the physical path and the file is there. C:\pf\mic\exch serv\v14\clientaccess\owa
Also getting event id 1, autodiscover can not start
Also getting asp.net 2 warnings
Has anyone seen this? Any quick fixes, or should I call MS?
ACT web has been uninstalled, and server rebooted.
Any help would be great... Thank you for any attempts.
Kacey
Changes that were made:
Orig: <add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dl
Change: <add name='kerbauth' image='C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth. dll ' preCondition='bitness64' />
Orig: <add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Ow
Change: <add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Ow
Orig: <filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ow
Change: <filter name="Exchange ActiveSync ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\sy
ASKER
I did not, will run it now.
Was also thinking of uninstalling and reinstalling asp 2, what do you think?
Can that mess anything up further?
Was also thinking of uninstalling and reinstalling asp 2, what do you think?
Can that mess anything up further?
I don't think reinstall asp.net is going to make much difference. The issues are probably around IIS more than anything. Removing the CAS role, then IIS and reinstalling both - which is documented on Technet or the MS KB might be an option to sort the mess out, but my suggestion to call Microsoft would be the best thing to do. The more you try and fix it unsuccessfuly, particularly if you aren't 100% sure what the issue is or what was done, the more difficult you make it to resolve.
Simon.
Simon.
ASKER
MS fixed it. Waiting on summary and I will post the fix
Exchange can't be changed to a 32bit app ... but, ACT! for Web needs IIS to be able to run 32bit apps as well
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/22988
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/22988
ASKER
The new ACT 2013 web portion can not run on SBS2011 per Sage. That was the problem, it messed up IIS. Still waiting on the case details.
It can ... but has issues if you're using Sharepoint
You also need to set the APFW pool to 32bit
You also need to set the APFW pool to 32bit
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So wasn't related to ACT! at all ....
ASKER
Called MS for fix
I presume that you have run the fix my network wizard in the SBS management console?
You cannot change Exchange to a 32 bit application, they might have screwed up .net framework though.
Personally I would call Microsoft, as it may require a reinstall of Exchange, probably the client access role. Then pass the bill to the consultant.
Simon.