Built a Skype for Business Client (Endpoint) App using the UCMA 6.0 SDK. It is a C# console app or placng test calls. Application runs as designed on Windows 10 Dell laptop where it was developed using Visual Studio 2017.
When ported to a 2nd Windows 10 Dell laptop, the calls complete but the recording feature from Class RTC.Collaboration.AudioVideo.Recorder gives an error message:"Recorder cannot start due to I/O Error."
Snopper analysis of the OCS log: TL_ERROR, TF_Component, SinkRecorderImpl.StartRecord.Imp.
Even tried building the app on the target laptop. Same issue. Any ideas on why the I/O error?
You must create the log folder on the target computer. I had created the parent folder but not the specific subfolder for recordings. Manually creating the subfolder solved the problem.
Related
I have .net framework 4.8 web site deployed on IIS 10. And It's pool stops on every first request after each start.
Here is the list of programs and features on server:
Programs and features
In Application Windows log I found 10 errors per each request. Everyone error is:
The Module DLL C:\Windows\system32\inetsrv\aspnetcore.dll failed to
load. The data is the error.
And in System log I have warning:
A listener channel for protocol 'http' in worker process '2968' serving application pool '{MyPoolName}' reported a listener channel failure. The data field contains the error number.
With binary data in details tab: In Words 0000: 8007007E
I tried to repair installed version of .net 5. Also tried to install .net framework 4.8, but installer didn't allow to do it because of:
.NET Framework 4.8 or a later update is already installed on this
computer.
I even tried to create site with empty directory. When I create one on my computer it shows "403.14 — Forbidden" as it should. But after doing the same on server empty site pool stops as my site's pool.
Have you ever faced such a problem? I have no idea how to fix it!
I have .net framework 4.8 web site deployed on IIS 10. And my IIS pool stopped on first request. Researching similair issues I found this artcle on the Microsoft Monitoring Agent APM service. This service was disabled, I removed the Microsoft Monitoring Agent APM as it was not being used. My application now successfully launches.
https://kevingreeneitblog.blogspot.com/2017/03/scom-2016-agent-crashing-legacy-iis.html
Thank you for your help. I solve the problem with complete reinstallation of server OS and components. My consider is that the problem was into iis or OS component.
I am using the Azure service bus for message transfer between different services. I have written a simple windows application to give to the 3rd party customer to test that their system can talk to the service bus. All it does is post a message on a button click and receive the message back from the same queue.
This system works fine on my development machine but when I test it on another machine it fails timing out when trying to post. Microsoft.ServiceBus.dll & Microsoft.WindowsAzure.Configuration.dll have both been deployed with the application.
Is there an SDK that I need to install on the deployment machine as well. I have looked but all I seem to find are SDK's for VS. The application is running in .NET 4.0 due to target the old target machines that we have to work with.
Problem was due to a network issue on some machines. Nothing else needed to be installed
I have a solution which basically contains three components:
• WCF Service that is hosted locally having a back-end SQL Server Express DB and this WCF service is hosted from a Windows Service
• A console application
• A Windows Store Application
This is what they are meant to do:
• WCF service his hosted locally and is used by the console app and the store app for communicating with the database
• The console app adds an image for processing to the database by contacting the WCF service
• The store app will at regular time look for unprocessed images in database via the WCF service and will process them
Now, the difficulty is:
• The WCF service is hosted successfully and is working absolutely fine and I can check that by hitting its URL http://localhost:8081/XYZ
• The console app is also able to submit images to the WCF service and add their local paths to the database
• The store app however always throws the EndpointNotFoundException when accessing the service at that same localhost path
What have I tried:
• I have tried almost everything from searching through stackoverflow to googling and haven't found a solution yet
• I was thinking that it might be a port issue and so I turned off the firewall to check this, but it did not work, and the store app kept throwing the EndpointNotFoundException
What have worked:
• The complete set-up has, however, worked perfectly on my machine. It is strange that its not working on my client's Windows 8 machine.
Point to be noted:
• The complete solution has been developed in Visual Studio 2013 and the App is for Windows 8.1
• I am not sure, but it seems my client has a Windows 8 machine and we are installing the app on that. (Possibly, that might be a problem. But I'll check)
If there is any help someone could provide me, I'll be really greatful. Thanks in advance!
This is expected. Windows Store apps cannot connect back to the local system in production. This loopback prohibition is disabled for debugging.
See How to enable loopback and troubleshoot network isolation
If your app is to be side-loaded rather than deployed through the store then see Using network loopback in side-loaded Windows Store apps
I'm trying to make my store app communication with desktop app through websockets.
I know we can make metro app as a client and do WinRT way of communicating over.
For the desktop server part, i'm planning to write a dll that will contain server code and receive metro texts being sent over.
Can someone please tell if this is possible and how to write server code in a dll and if so should we be using winhttp for wbesockets in server side ?
Windows Store (WInRT) apps are executing in a sandbox which isolates them from network communication with other applications on the local machine (localhost). That being said, this protection can be disabled using CheckNetIsolation.exe. Visual Studio automatically does the same for debugging purposes, allowing you to call e.g. a web service on your local machine during development.
As for the desktop side; to communicate with web sockets client, you can make advantage of WinHTTP. There's a working example on MSDN.
Keep in mind, though, that any application communicating with localhost will not be certified for Windows Store and will require several additional steps to install it:
The Windows Store application package will need to be sideloaded since it won't be published in Windows Store.
Any desktop component it communicates with will need to be installed separately the same way as any other desktop application.
Using CheckNetIsolation.exe loopback exemption will need to be added for the Windows Store app.
If you can avoid it, I definitely suggest you don't try communicating directly with a desktop application from you Windows Store app.
I know there are more articles of this on the internet i think i found them all but still cant solve my problem for the client PC's.
i have a windows forms project installed on a server that every client PC's useses. I added the reference 2 my project and installed the EwsManagedApi on my own computer for testing and changed the location of where 2 find the references to the folder that EwsManagedApi installs.
When i am trying to use the module that uses the Exchange Web Services i get the error.
I only have the shotcut on my pc and the application is running good. i know the reference path is good i checked this more than 5 times. but when i just copy the dll to my folder where the shortcut is it is working good. what do i have to do to get the dll from the server where the aopplication is installed.
Tanx
You have to install the Microsoft Exchange WebServices API 2.0 in every client
to be sure you have all the necesary assemblies.
Microsoft Exchange Web Services Managed API 2.0
In addition, check out the the server version. Maybe it is 64 bits and the
clients are running 32 bits.