locked
CommunicatorAPI.dll & Windows 2008 64 bits RRS feed

  • Question

  • Hi,

    I made an App using "Communicator Automation API"  and it works fine in stand-alone workstation with windows XP SP2 and on Terminal Services Sessions over Windows 2003 R2.

    Now I'm testing the Terminal Services sessions on Windows 2008 64 bits, and its not working.

    I have an error when creating an object of  MessengerClass:

    Could not load file or assembly 'CommunicatorAPI, Version=2.0.6362.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An attempt was made to load a program with an incorrect format. 

    NOTE: The CommunicatorApi.dll is there, and on the same path of the App. OC 2007 R2 is installed and running. the APP is compile for .NET Framework 3.5 and this version is installed on that Server (both 32 and 64 )

    Anyone can welp?

    Monday, March 29, 2010 2:47 PM

Answers

  • Hi,

    I made an App using "Communicator Automation API"  and it works fine in stand-alone workstation with windows XP SP2 and on Terminal Services Sessions over Windows 2003 R2.

    Now I'm testing the Terminal Services sessions on Windows 2008 64 bits, and its not working.

    I have an error when creating an object of  MessengerClass:

    Could not load file or assembly 'CommunicatorAPI, Version=2.0.6362.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An attempt was made to load a program with an incorrect format. 

    NOTE: The CommunicatorApi.dll is there, and on the same path of the App. OC 2007 R2 is installed and running. the APP is compile for .NET Framework 3.5 and this version is installed on that Server (both 32 and 64 )

    Anyone can welp?

     


    The solution is given in the book Programming for Unified Communications with Microsoft Office Communications Server 2007 R2, page 329 / 415.

    Basically, you have to add a COM reference to "Microsoft Office Communicator 2007 API" instead of going directly to the x86 DLL in "Program Files x86\Microsoft Office...".

    • Proposed as answer by Dinesh Bolkensteyn Saturday, June 5, 2010 9:46 PM
    • Marked as answer by DevDiver Tuesday, July 6, 2010 2:35 PM
    Saturday, June 5, 2010 9:32 PM

All replies

  • Hi,

    I made an App using "Communicator Automation API"  and it works fine in stand-alone workstation with windows XP SP2 and on Terminal Services Sessions over Windows 2003 R2.

    Now I'm testing the Terminal Services sessions on Windows 2008 64 bits, and its not working.

    I have an error when creating an object of  MessengerClass:

    Could not load file or assembly 'CommunicatorAPI, Version=2.0.6362.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. An attempt was made to load a program with an incorrect format. 

    NOTE: The CommunicatorApi.dll is there, and on the same path of the App. OC 2007 R2 is installed and running. the APP is compile for .NET Framework 3.5 and this version is installed on that Server (both 32 and 64 )

    Anyone can welp?

     


    The solution is given in the book Programming for Unified Communications with Microsoft Office Communications Server 2007 R2, page 329 / 415.

    Basically, you have to add a COM reference to "Microsoft Office Communicator 2007 API" instead of going directly to the x86 DLL in "Program Files x86\Microsoft Office...".

    • Proposed as answer by Dinesh Bolkensteyn Saturday, June 5, 2010 9:46 PM
    • Marked as answer by DevDiver Tuesday, July 6, 2010 2:35 PM
    Saturday, June 5, 2010 9:32 PM
  • The selected answer for this is a bit vague for general users of this forum who might be browsing for an answer, so I'll detail it a bit further.

    The error here looks like a 64-bit platform is trying to load a 32-bit assembly... you need to install the specific assembly for whatever platform you are using:

     

    x86 - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=768EFA33-6606-4B2B-809A-6C69274621D3

    x64 - http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b20967b1-6cf5-4a4b-b7ae-622653ac929f&displaylang=en


    - Stefan Camilleri
    Tuesday, February 1, 2011 10:31 AM
  • Stefan,

    The original question was on the Communicator Automation API which is implemented by a 32-bit application since OC is a 32-bit app.  Your links are for the UCMA API which is available in both 32-bit and 64-bit versions.

     


    Oscar Newkerk Oscarnew Consulting
    Wednesday, February 2, 2011 12:21 AM
  • Stefan,

    Facing the same issue on 64 bit platform even after installing "Microsoft Unified Communications Managed API 2.0 SDK (64 bit)" as suggested by you above from here http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b20967b1-6cf5-4a4b-b7ae-622653ac929f&displaylang=en

    I am not able to find communicatorapi.dll 64 bit version after installing "Microsoft Unified Communications Managed API 2.0 SDK (64 bit)". 


    Please suggest, provide more details to resolve this.

    Thanks in advance.

    Thursday, January 2, 2014 5:59 AM