My Message Broker service from "Service bus for Windows Server 1.1" was running ok until I installed "Microsoft Azure Service Fabric SDK Preview - 1.4.187".
After installing Service Fabric, my "Service Bus Message Broker" service remains in the status: StartPending.
I guess that, with the installation of Service Fabric, I replaced/updated the "Windows Fabric" that Service Bus runs on and that Service Bus cannot run on the newer Fabric. Is this true? Are there plans to get these two to work together?
Unfortunately this isn't supported. Service Bus on Win Server runs on an old version of Service Fabric (as you can tell by the old Windows naming convention) which isn't compatible with the current version.
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
If it supports, is the API exactly similar to the public cloud based Azure Servicebus.
No it does not. Relay is scheduled for a later release. That's why we call this release "Service Bus messaging engine" in the fine print.
Clemens
Just Came to know, the upcoming AzurePack includes this feature.
I have a program for Windows Application with the Bank uses a WCF service.
Several Windows 7 client using this service are working well, one of the Windows XP client, and when the service is connected and started working, service to any of the other client does not respond; until Windows XP client relationship is discontinued.
Thanks and respect.