ACT 13 Web portion changed exchange 2010 to 32 bit on SBS2011

Posted on 2012-09-19
Last Modified: 2012-10-06
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 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.

Changes that were made:

Orig: <add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll" />
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\Owa\auth\exppw.dll" />
Change: <add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\exppw.dll" preCondition="bitness64" />

Orig: <filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll" enabled="true" />
Change: <filter name="Exchange ActiveSync ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\sync\bin\AirFilter.dll" enabled="true" />
Question by:kaceyjames
    LVL 63

    Expert Comment

    by:Simon Butler (Sembee)
    I have lost count the number of servers I have seen screwed up by Sage and their consultants. They all work on the basis of their product being the most important and sod everything else.

    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.


    Author Comment

    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?
    LVL 63

    Expert Comment

    by:Simon Butler (Sembee)
    I don't think reinstall 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.


    Author Comment

    MS fixed it.  Waiting on summary and I will post the fix
    LVL 30

    Expert Comment

    by:Mike Lazarus
    Exchange can't be changed to a 32bit app ... but, ACT! for Web needs IIS to be able to run 32bit apps as well

    Author Comment

    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.
    LVL 30

    Expert Comment

    by:Mike Lazarus
    It can ... but has issues if you're using Sharepoint
    You also need to set the APFW pool to 32bit

    Accepted Solution

    Here is what MS did to solve the issue, seems like there is more to it, but that is the summary of the case that they provided.  Another tech worked with MS, so this is all I have.  Hope it helps someone.

    1.       Opened event viewer and did not find any errors related to exchange management console
    2.        opened IIS and checked for Default website's Bindings. All default and OK
    3.       Checked SSL settings and they were not default. Set the settings to Default
    4.       Checked application pool of Powershell Virtual Directory --> 32 bit was set to false
    5.       Checked Powershell Virtual Directory in IIS and got the following error message
    There was an error while performing this operation.
    Error: Cannot read configuration file
    6.       Tried to right click and explore but nothing happened
    7.       Navigated to C:\Program Files\Microsoft\Exchange\V14\ClientAccess\Powershell and checked the files --> all default files were present
    8.       Tried to restore the file from the previous version but the versions before september 11th were not present since that was the day SAGEACT software was installed which caused the issue in the first place
    9.       Transferred a copy of the C:\Program Files\Microsoft\Exchange\V14\ClientAccess\Powershell folder from a working machine and to the user's server
    10.   Renamed the old files and replaced them with working files
    11.   Tried to open EMC but got the same error message
    12.   Checked the Modules of Powershell Virtual Directory in IIS
    13.   Found Kerbauth to be Blank
    14.   Entered the value C:\Program Files\Microsoft\Exchange\v14\Clientaccess\Powershell
    15.   Opened the applicationhost.config file  in C:\Windows\System32\Inetsrv
    16.   Noticed that the search string "Powershell (Default Web Site)" was present and compared it to the working machine
    17.   Replaced the search string "Powershell (Default Web Site)" with only the word "Powershell"
    18.   Ran iisreset in CMD
    19.   Refreshed the Exchange Management Console
    20.   Scoped Issue resolved
    LVL 30

    Expert Comment

    by:Mike Lazarus
    So wasn't related to ACT! at all ....

    Author Closing Comment

    Called MS for fix

    Featured Post

    How your wiki can always stay up-to-date

    Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
    - Increase transparency
    - Onboard new hires faster
    - Access from mobile/offline

    Join & Write a Comment

    Suggested Solutions

    Title # Comments Views Activity
    Outlook exchange 2 44
    Add Server Certificate in IIS from C# 6 33
    Event 9327, MSExchangeSA 1 25
    EXCH2013 and DAG 11 16
    Email statistics and Mailbox database quotas You might have an interest in attaining information such as mailbox details, mailbox statistics and mailbox database details from Exchange server. At that point, knowing how to retrieve this information …
    Set OWA language and time zone in Exchange for individuals, all users or per database.
    In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
    In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now