Address Book/Exchange Connection - HTTP 500 Errors RRS feed

  • Question


    Hi Everyone,


    For the last few days I have been working on setting up OCS. We have a Windows 2003 64-bit server with Exchange 2007 installed. OCS is installed on the same server. I am unable to sync with the address book and I get a exchange connection error in the client.


    Here is the errors that I get from the vaildation tool:


    URL: https:///GroupExpansion/Int/service.asmx
    Received a failure HTTP response.: HTTP Response: 500 Internal Server Error
    Cache-ControlStick out tonguerivate
    Content-Type:text/html; charset=utf-8
    Date:Fri, 18 Jul 2008 12:19:15 GMT

    Received a failure HTTP response.: InternalServerError


    URL: https:///Abs/Int/Handler/D-0abc-0abd.dabs
    Received a failure HTTP response.: HTTP Response: 500 Internal Server Error
    Date:Fri, 18 Jul 2008 12:19:15 GMT
    %1 is not a valid Win32 application.


    I have tried everything from this forum that I can find. I'm stumped. Could someone lend a hand?

    Friday, July 18, 2008 12:27 PM

All replies

  • OCS on Windows 64-bit is supported


    Have a look at the supportablity guide



    You might need to check the Identity on the Application pools for OCS

    If you changed the WebComponents service account you have to change the identity information

    And Restart IIS

    Friday, July 18, 2008 3:18 PM
  • Thank you for the response. I did look through the supportablity guide and did not find reference to Exchange directly. The guide did mention that the 64-bit .NET framework needed to be used if WOW64 was in use. Is there something I'm missing?




    Friday, July 18, 2008 6:02 PM
  • Hi there,

    You can install OCS on 64 bit just fine. However, OCS and Exchange on the same box aren't recommended or (to the best of my knowledge) supported. OCS and Exchange aren't really designed to play together, although if you are careful to avoid port conflicts etc, you might be able to get it to work. But I definitely don't recommend it in production.


    Anyway, your error looks like the webcomponents pieces of the front-end failed to install properly. The URL that you've posted looks strange and doesn't seem like it has a servername in the URL. It should look more like:




    And that servername should be your OCS pool's internal name (or the name of your standard edition server. A lot of people foul this up during the install. I recently posted a blog entry about how to remedy it if you've goofed the internal webfarmfqdn.


    If all else fails, you can try to remove the webcomponents service from Add/Remote Programs and re-run OCS setup.




    Friday, July 18, 2008 10:05 PM

    Can you check the OCS Service Accounts and verify if they are set to NOT EXPIRE (expiration is not configured when accounts are created)

    If passwords are expired then configure the password to not expire and restart OCS Application pools by restarting the IIS

    Wednesday, July 23, 2008 10:49 AM