Based on your question, this may be a few things, so I will look at the list that I always look at when I do this. If that doesn't work, give a little more background, and I could give you a more useful answer.
Fortunately, UCMA 4.0 installs a lot easier than previous versions. UCMA 4.0 applications must (must, must) be compiled 64-bit to run in production. The SDK will allow 32-bit compilation, but the SDK requires installing Visual Studio for installation. Due to the problems you are facing, I am convinced that you can set the wrong "look" of the UCMA bit on the server.
Make sure you are using the UCMA 4.0 Runtime and not the SDK
On the server, you want to install the UCMA 4.0 Runtime , not the SDK. This should give you your addictions. In the links in your application, you only need the Microsoft.Rtc components that you use. SIPEPS.DLL , and they are used by them, but in the projects that I wrote against UCMA, it does not refer directly to any of them.
Check prerequisites
I have UCMA 4.0 working and working (excellent, for the first time) on Windows Server 2008 R2. I noticed that in preliminary order he had a requirement to install Service Pack 1 (my environment comes to the latest levels of fixes at all).
You did not specify your patch levels, and since you indicate that you have no problems in later versions, I suspect that this may have something to do with it.
You will also need:
- .Net Framework 4.5 (the last 4.5 - I think 4.5.2 at the moment). Make sure it is installed before running the UCMA installer.
- The server must be 64-bit (all Lync has this requirement)
- If you can get up and work, but have difficulty doing the basic things related to connecting, etc., check your software. I came across a situation where Symantec Endpoint Protection interfered with UCMA, despite having firewall rules that did not present a problem.
source share