Post reply

SSIS Exchange Web Services - Could not load file or assembly

  • October 27, 2012 at 7:43 am

    #266130

    Hi I'm trying to write a Source component in a dataflow task to recover some details from Exchange.

    Unfortunately when I ran it - I get

    [GetEmail [1]] Error: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Exchange.WebServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    File name: 'Microsoft.Exchange.WebServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

    at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)

    at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)

    at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)

    WRN: Assembly binding logging is turned OFF.

    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

    Note: There is some performance penalty associated with assembly bind failure logging.

    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

    I've tried copyto local, moved the Exchange dll to same directory as the pack which is the only cluse from searching google etc.. and can't seem to find anything works

    I would be grateful if anyone's got any ideas

    It's Windows 7 - 64 Bit - and it doesn't make any difference when RunIn64 is set to true or false.

  • January 9, 2013 at 10:55 am

    #1575349

    Hi Mike

    I have same issue, did you find any solution at the end?

    Thanks in advance

  • January 12, 2013 at 1:02 am

    #1576548

    Hi Prakash

    Unfortunately not, in the end I used EWS powershell scripting as part of a SSIS package. Not as elegant but it worked.

    I've still got to sort out impersonation though - I got sidetracked with something more urgent.

    Regards

  • January 6, 2014 at 1:03 pm

    #1677868

    Hello,

    I am wondering you found any solution to the issue and if you may share it with me.

    Thanks,

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply