Geek Answers Handbook

SIPEPS error, version = 5.0.0.0 UCMA 4.0 VS2010 / VS2013

I developed the UCMA 4.0 application on VS 2013 and VS 2010. When I started the project, I got this error:

Failed to load file or assembly "SIPEPS, Version = 5.0.0.0, Culture = neutral, PublicKeyToken = 31bf3856ad364e35" or one of its dependencies. The system cannot find the specified file.

I used .NET 4 and installed the target build platform on x64 . Checked dependwalker_x64 and the file is missing.

I also used the App.config file from Sample, but did not work, so I modified the App.config file as follows:

 <runtime> <assemblyBinding> <dependentAssembly> <assemblyIdentity name="SIPEPS" publicKeyToken="31bf3856ad364e35" culture="neutral"/> <bindingRedirect oldVersion="0.0.0.0-4.5.0.0" newVersion="5.0.0.0"/> </dependentAssembly> </assemblyBinding>

How do I make this problem? Thanks so much for any help!

+5
c # visual-studio-2010 ucma lync-server-2013
source share
4 answers

An exception can be very confusing, as UCMA projects do not require an explicit reference to this SIPEPS DLL , and you will often get an exception even if you find the DLL and move it to the same directory as your expression.

It turns out that it is usually caused by one of two things:

  • You are targeting the wrong version of the .NET Framework.
  • You are targeting the wrong type of processor.

Open the properties for your project in Visual Studio and make sure the .NET Framework 4.5 is selected.

If you are not using Visual Studio 2012, you have a slightly larger problem.

because you cannot use .NET 4.5 with Visual Studio 2010 and earlier. If you had an earlier version of the selected frame, change it, rebuild the project and try again. UCMA 4.0 lists .NET 4.5 as a requirement.

If you still get an exception,

check the target platform and make sure that it is Any processor or x64 for all projects.

UCMA only works with 64-bit machines from version 3.0, and sometimes it happens that the project will be unintentionally installed on x86 and therefore will try to load the 32-bit version of SIPEPS.dll at startup. Well, there is no 32-bit version of SIPEPS.dll; hence a somewhat misleading exception.

Link

+13
source share

You may also receive this error message if your application server is not configured correctly for UCMA applications.

In particular, this message appears if replication does not work. To view replication status, run get-csManagementStoreReplicationStatus and verify that the "UpToDate" field is true for your application server.

+2
source share

EDIT: If you try to install the UCMA application on a non-lync server, you must install RuntimeApi, if you try to run UCMA on the lync / skype server, you do not need to install RuntimeApi, you must try the above answer, which will recompile to 32/62 / auto ...

if recompiling does not make your day better, maybe you are missing
UCMA API Runtime



Install / reinstall
Unified Communications Managed API 4.0 Runtime for SIPEPS = 5.0.0.0
Unified Communications Managed API 5.0 Runtime for SIPEPS = 6.0.0.0

(dancing with the right partner - ucma sdk 4.0 / 5.0 Microsoft.Rtc.Collaboration.dll)

Runtime Installation Requirements:

PS> Install-WindowsFeature server-media-foundation

on the target / host computer on which you want to run it (which is probably not related to any Lync / SKF territory) OR on a development machine with recompilation to correspond with the update / update

+2
source share

In addition to a great reply rate. Please note that you must change the platform to x64 in debug mode and in release mode. Platforms can be different in different modes. I had such a problem in VS2015 with UCMA4, .net4.5. In debug mode, my application works fine, but after building the release, it crashes with the exception "Could not load the file or SIPEPS assembly."

+1
source share

More articles:


All Articles