By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.

(T0276) 503.3 Service unavailable while viewing a portal.

Would you like to...

Print this page
Email this to a friend

This occurs when a portal is installed on a 64 bit SBS server with exchange or T/S gateway.

  • Locate and backup the following file:
  • Locate and edit any of the following entries by adding preCondition="bitness64" near the end (when you search the file for them, you will need to search without bitness64 since it may not be there yet):
    • <add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" preCondition="bitness64" />
    • <add name="exppw" image="C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\auth\exppw.dll" preCondition="bitness64" />
    • <add name="exppw" preCondition="bitness64" />
  • Restart the web server.

These two, under isapiFilters will also need preCondition="bitness64":

  • <filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="D:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitness64" />
  • <filter name="Exchange ActiveSync ISAPI Filter" path="D:\Program Files\Microsoft\Exchange Server\ClientAccess\sync\bin\AirFilter.dll" enabled="true" preCondition="bitness64" />

And also, under modules on the one that has exppw.dll in its name, a little further down than the RpcProxy one.

Additional modules may require this preCondition--the Application Log in the Windows Event Viewer can be used to determine which modules, if any, are causing bitness issues.

Related Questions:


No attachments were found.

ServiceLedger KnowledgeBase Copyright © 2020
Powered by AcitveKB Knowledgebase Software