Can somebody suggest how to do SignalR scaleout using Windows server service bus 2 as messaging backplane (pl not this is not Azure service bus) in an Asp.net application.
After adding the following line, the run time error comes as "Network Error 500 for /signalr/hubs" :
File: Global.ascx.cs
Method: Application_Start()
Line: GlobalHost.DependencyResolver.UseServiceBus(svcBusConnectionString, MyChatApplication");
To troubleshoot, enable server logging like in this web.config file. Then, start your server and read the log file contents. You could also debug and see what exceptions are thrown.
Related
I have a GRPC client only application using Quarkus 2.1 and get the following error when the application starts:
[io.qua.grp.run.GrpcServerRecorder] (vert.x-eventloop-thread-2) Unable to start the
gRPC server: java.io.IOException: Failed to bind to address /0.0.0.0:9000
at io.grpc.netty.NettyServer.start(NettyServer.java:268)
at io.grpc.internal.ServerImpl.start(ServerImpl.java:183)
How can I disable the GRPC server service and other associated services if I am only interested in the client part? Are there configuration properties that can be set for this?
You can disable it by flag - quarkus.grpc.dev-mode.force-server-start=false
dependency io.quarkus:quarkus-grpc-deployment
works for me with quarkus v2.8.X
I get the following error message when I try to send message to Microsoft Message Queue to server on the local network from BizTalk 2016 using the MSMQ adapter:
Could not load file or assembly
Microsoft.BizTalk.Adapter.MSMQ.MsmqLargeMessageWrapper.dll or one of
its dependencies. The specified module could not be found.
BizTalk, BizTalk Adapter Packs and BizTalk Enterprise Adapters are installed, and I am able to configure send and receive handlers and the send port itself.
Are there any pre-requisities I need to install?
Not very often you google and find four irrelevant answers...so what am I not getting?
Ok, got it. I was unlucky while I was thinking... ;|
MSMQ Adapter is built to call Windows Message Queuing queue on a Windows Server. If you call a remote queue, you need to activate Microsoft Messaging feature on the local server too - otherwise you end up with a simlar error message like above. It will forward the queue processing to the remote server.
We have a WebApp & WCF service running under AppPools A1(using service account User1) & A2(using service account User2) respectively.
While webapp is trying to connect to wcf service, we are getting following error System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
The only way I can make webapplication access the wcf service is if I'm logged in to the web server using the service account User2.
Once the service account user logs off the server, the same error appears.
Here is the web server/app configuration
.NET version : v 4.0
IIS : 10.0.14393.0
OS : Windows Server 2016
I am trying to integrate Jenkins and Web deploy v3.5 over "HTTP" connection. The server has IIS 10 and Windows Server 2016. The build is getting failed with an error,
Web deployment task failed. (Could not complete the request to remote agent URL 'http://IPAddress:8172/MSDeploy.axd?site=WebSite'.)
I am using the following command,
/property:configuration=Dev /p:DeployOnBuild=True /p:DeployTarget=MsDeployPublish /p:CreatePackageOnPublish=False /p:AllowUntrusted=True /p:MsDeployPublishMethod=WMSvc /p:MsDeployServiceUrl="http://IpAddress:8172/MSDeploy.axd" /p:DeployIisAppPath="WebSite" /p:AllowUntrustedCertificate=True /p:Username=SomeUsername /p:Password=SomePassword
Troubleshooting:
8172 port is allowed for Jenkins.
Web deployment services are running.
Users have been given with sufficient rights to the directory.
WebDeploy user is added to administrator group.
I am suspecting if Web deploy tool doesn't work over HTTP connection, is that true?
Web Deploy is actually just a way of deploying. The services are running on a server and listening on the port 8172. I do not get why you are using a whole web adress, when all you need is the connection to the server (ip or domain only!).
Example: 0.00.000.000 or example.org
Check if you installed the handler too. You need the web deploy service and handler running.
Regards,
Maheshvara
I encountered the problem by taking following steps,
Ms web deploy works under the secure connection. it should be called by https://
Configured three rules as mentioned under Management Service Delegation Rule
2.1 ---- createApp with WDeployConfigWriter User
2.2 ---- setAcl
2.3 ---- contentPath_intiApp
Reference: https://learn.microsoft.com/en-us/iis/publish/using-web-deploy/configure-the-web-deployment-handler
In 2.1 step, WDeployConfigWriter user needs to be created manually. Web deploy tool use two users WDeployAdmin and WDeployConfigWriter
Reference: https://blog.richardszalay.com/2013/08/02/manually-creating-wdeployadmin-and-wdeployconfigwriter/
I am New to biztalk
I have created two way port and publish my biztalk project as a biztalk service in my local machine.
Then I have Created Small Client App and access the Biztalk app through published biztalk service. Successfully send the schema and received the response. But For same Application I have created an another web service in seperate server, which has biztalk.
I want the biztalk application in my local machine as it is , and access that biztalk application from seperate server biztalk service.
When I consumed the seperate server web service and try to call the web method, it says:
System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure
My Soap Transport Properties page web asmx:
/SampleBiztalkApp_Proxy/WebService_SampleBiztalkApp.asmx
My Soap Transport Properties page Public Address:
{RemoteMechineName}/SampleBiztalkApp_ProxyGID /SampleBiztalkApp_SampleOrchestration_PortRR.asmx
Is there any other configuration to do so?
If you have any idea about publishing biztalk service in seperate machine.
Thank's
BizTalk Server has to be installed and configured on the other machine as well. This is because the Receive Location is running in an Isolated Host within IIS but it's still BizTalk.