I have a .net 2.0 app on a win2003 VM that calls a WCF service hosted in IIS7 on a win 2008 VM. After developing the client and service and testing (all was good) I took the opportunity to take a snapshot of both VMs.
I come back to the VMs two weeks later and when I make the WCF call from the client I get a message dialog on the win 2008 server with the caption "Visual Studio Just-In-Time Debugger". The dialog then reads "An unhandled Microsoft .Net Framework exception occurred in w3wp.exe etc.
I take a look at the WCF service log an now see the following in the "WebHeaders" element:
"VsDebuggerCausalityData" AwAAAOEhpa2...lots of AAA
I've tried reverting both VMs to the previous snapshot but get the same problem.
In the WCF service trace file, I can see the logs entries from just before I took the snapshot and the request / response messages look perfect.
Could anyone please advise next step for diag and fix?
Many thanks
Rob.
Try to invoke WCF from wevservice studio. If you can do it , the problem
is in server.
If problem is in server , you can trace where exactly do you fail
Trace can be done using
http://msdn.microsoft.com/en-us/library/ms732023.aspx
Related
I have an Asp.Net Core 3.2 Blazor Webassembly application that has been published to a server running Windows Server 2016 with IIS 10.
After publishing to the server I can browse the login page to the site, However, when I attempt to login which calls a service and signs in with Entity Framework Core 3.1.5.
However when I attempt to call a linq query on the DbContext it seems to fail (This is deduced from log files).
Interestingly, if I remote into the server whilst running a login I get a JIT popup with the following error;
In the Windows System Log can see the following error;
A process serving application pool 'myapppool(domain)(4.0)(pool)' suffered a fatal communication error with the Windows Process Activation Service. The process id was '10188'. The data field contains the error number.
It seems to sometime crashes the apppool as well so if I then refresh the page i get 502 error on the site?
Below is a screen shot of the application pool advanced settings;
The server is running Windows 2016 with Plesk Obsidian installed on it (I'm not sure if this can interfere in any way??)
Does anyone know whats going on here please?
I don’t know what’s going on since I can not reproduce your issue. Here is a workaround.
Please ensure that IIS Application pool’s Advanced Settings has set ”Enable 32-Bit Application” to true.
Check below link for troubleshooting the issue.
How to diagnose IIS fatal communication error problem
Am planning to build a WCF Web service using Visual Studio 2015. I came up with a sample web service that i can launch from visual studio and this works fine when i call the APIs from browser on local host.
Now i want to deploy it in a server. Am not sure how I can deploy in a server. The final out put of the web service is a DLL.
Can someone explain to me how to deploy this in a Windows server?
Do i need to run this web service DLL as a service?
Does it got anything to do with IIS?
As per your request, I have made this an answer.
If you're looking to host a WCF service which is exposed to the outside world then the best solution is to host the service via IIS which you can find out how to do by reviewing the following article.
You can find a more visual tutorial here.
If you encounter errors after publishing to IIS then please refer to the following StackOverflow answer to see which Windows Features must be enabled.
I have a WCF Service that I am consuming in a web-application and I get strange behaviour from my Windows 8 machine:
When I compile the project from Windows 8, I get the following exception when trying to connect to the WCF Service:
The underlying connection was
closed: A connection that was expected to be kept alive was closed by
the server.
I get the same exception when I deploy it onto a Windows Server 2008.
However, if I compiled the project from Windows 7 and deploy it to the server, it works just fine.
I am using Visual Studio 2012 in both cases, although one is Premium and one is Ultimate.
After a lot of testing, it seems like when I just build and deploy the project often enough, at some point it will work, without having changed anything. It seems like the chance of getting a working project is about one in five. The Service works consistently, then, though.
If any of you have an idea what could be going on, that would be nice. If you need more info let me know.
I am getting the following error when I run web deploy:
>C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets (3588): Web deployment task failed.
((3/25/2011 4:41:36 PM) An error occurred when the request was processed on the remote computer.)
(3/25/2011 4:41:36 PM) An error occurred when the request was processed on the remote computer. The entry type 'Unknown' was not expected at this time. The serialization stream may be corrupted.
I have successfully done this on other IIS6 machines with no issues so I don't understand what is going on. The Remote Deployment Service is running and just to see if it mattered I started the service under an administrative group. That did not help.
Any help would be great.
I found that the 2008 server with IIS 7 did not have all of the components installed. Even though Web Deployment 2.0 seemed to have been installed by the Web Platform Installer, there were components that were incomplete due to communication issues with the MS servers. In order to resolve this, I had to download the installation files on a separate machine, copy them to the server and then reinstall everything. Very vague error for such an odd issue.
We have been using a Windows 7 Enterprise machine for development and we have 7 wcf services.... All of them worked fine in the development machine... When we hosted the same services in Windows Server 2003 and IIS 6, we are facing a couple issues... One of the services is throwing a "An existing connection was forcibly closed by the remote host" error... the underlying connection gets closed right in the service call.... I have turned on logging with log4net and I have turned on tracing... In trace logs I found out that it completes almost all the steps and stops at the end of Execute step... So I put log4net debug statements in the code and it looks like the code is executing fine, retrieving the values from the database fine but it is shutting down the connection at the point when its returning the data. So right at the moment of returning the data some exception is closing down the connection... And I am not able to figure out why or whats causing the error... And the same code works fine in Windows 7 Enterprise machine... So I wasnt sure to look for code problems or is it some special setup that IIS 6.0 needs... Do you guys have any idea what might be wrong with the situation... thanks for any help.
And there is another service that shows an error "The requested service, 'XXXXXXXXXXXXXXXXX' could not be activated"... Frequent calls like immediate calls to same service seems to be causing this error.. Is there a way this can be avoided because some of the services seem to exhibit this behavior in Windows server 2003- IIS 6 and they all run just fine on the windows 7 machine?
Yes I enabled MessageLogging and found whats the first error.... It is failing to serialize the reason for that being - the response is assigned the objects from the request. So in Windows 7 it is allowing it and keeping the references alive but Windows Server 2003 discards all request objects so by the time response serializes some of the object references are no longer valid in windows 2003 and hence shuts down the connection. So that solves the first. So I just created a new object at the service and copied over the values and it started working.