Installing PeoplePassword on Windows 2008 Server with Exchange 2013 64 bit

  1. Home
  2. Knowledge Base
  3. PeopleUpdate
  4. Installing PeoplePassword on Windows 2008 Server with Exchange 2013 64 bit
  1. Home
  2. Knowledge Base
  3. PeoplePassword
  4. Installing PeoplePassword on Windows 2008 Server with Exchange 2013 64 bit

In this case, if you install PeoplePassword along-side Exchange 2013 on a 64-bit machine, the application pool may not start  The administrative or other application interfaces give a 503 error in your browser in this case.  If this is happening, you may have another application installed on your server (such as Exchange 2013) that’s forcing some DLLs to be loaded in 64-bit mode.  It’s possible to change your IIS configuration to run them in 64-bit mode only when needed by 64-bit applications.

Solution

Open a text editor or XML editor with elevated privileges (for instance, from the Start menu right-click Notepad and selectRun as Administrator).  In the file %windir%\system32\inetsrv\config\applicationhost.config:

  1.  change the line
    <add name=”PasswordExpiryModule” image=”C:\Windows\system32\RpcProxy\RpcProxy.dll” />to the following
    <add name=”PasswordExpiryModule” image=”C:\Windows\system32\RpcProxy\RpcProxy.dll”
    preCondition=”bitness64″ />
  2. If Outlook Web Access is installed on the server, perform the following additional steps.Note that the “path” part of the entries will depend on your local installation and you should not change it. Not all of these entries are present in every installation. You can ignore any entries that are not present.In the file %windir%\system32\inetsrv\config\applicationhost.config:
    •  change the line
      <filter name=”Exchange OWA Cookie Authentication ISAPI Filter”
      path=”C:\Exchange\ClientAccess\owa\auth\owaauth.dll” enabled=”true”  />to the following
      <filter name=”Exchange OWA Cookie Authentication ISAPI Filter”
      path=”C:\Exchange\ClientAccess\owa\auth\owaauth.dll” enabled=”true” preCondition=”bitness64″ />
    • change the line
      <filter name=”Exchange ActiveSync ISAPI Filter”
      path=”C:\Exchange\ClientAccess\sync\bin\AirFilter.dll” enabled=”true”   />to the following
      <filter name=”Exchange ActiveSync ISAPI Filter”
      path=”C:\Exchange\ClientAccess\sync\bin\AirFilter.dll” enabled=”true”
      preCondition=”bitness64″ />
    • change the line
      <add name=”exppw”
      image=”C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll”  />to the following
      <add name=”exppw”
      image=”C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll”
      preCondition=”bitness64″ />
    • change the line
      <add name=”kerbauth”
      image=”C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll”  />to the following
      <add name=”kerbauth”
      image=”C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll”
      preCondition=”bitness64″ />
    • change the line
      <add name=”exppw” />to the following
      <add name=”exppw” preCondition=”bitness64″ />

Restart IIS and you should see the problems resolve.

Other errors will show up in your Windows Events log that are characteristic of these problems indicating problems loading each of these DLLs (until you make the change in the configuration file for them).

Source:

http://devfarm.it/asp-net-mvc-2/install-website-windows-2008-64-bit-ms-exchange/

Was this article helpful?

Related Articles

Sign in
classic
Forgot password?
×
Sign up

(*) Required fields

I agree with OptimaSales Terms & Privacy Policy

×