WCF goes offline automatically - wcf

I have hosted a WCF service application on IIS8 (Windows Server 2012 R2). These services automatically goes offline sometimes an the other applications which uses these services throw this error,
The requested service, 'http://10.230.245.156:8086/Apis/ILQ/Services/ILQInfoService.svc' could not be activated. See the server's diagnostic trace logs for more information.
When I open the Web.config of the WCF application and save it again, the services starts working back again.

Related

How publish ASP.NET Core to a server without stop iis (error : The process cannot access the file because it is being used by another process)

When we publish our ASP.NET Core application and upload to the server, we get an error:
The process cannot access the file because it is being used by another process.
And when stop iis not error. How to upload without stopping IIS?
If you use web deploy to push to an IIS you own (a machine located in your datacenter) you can try to recycle the AppPool used by the web application you are trying to redeploy.
Go to your IIS Management Console
Right click the AppPool in question
Choose the recycle option
Be aware that this would also 'restart' all other apps which are associated to this AppPool.
This 'should' work in most cases.
If you deploy to Azure you might consider using either a Linux App Service or some Docker deployment mechanism altogether. You cannot use the In-Process IIS ASP.NET Core modules in these cases as far as I am aware of but at least deployments don't randomly fail.

What rights are required for IIS to talk a WCF service hosted on a different machine?

In this question: ASP.NET web application unable to connect to WCF hosted as windows service
it's stated that the reason IIS could not talk to a WCF service hosted on a different machine is due to rights not assigned the app pool identity.
I'm facing the same problem I believe. What are these rights, and where do I set them?
Thanks.
This depends on the configuration of the service you're trying to access. However, if you're having trouble connecting to a different machine, you most likely don't have rights to access that computer using the machine account for the server hosting IIS. You could try adding [domain][iismachine] access to the target server (the one hosting the WCF service).
This overview has some pretty good information on what needs to be done in different scenarios.

Are there any special deployment requirements for a REST Service to Azure?

I have written a REST service with windows azure using the WCF Rest Service Templates.
Locally everything runs fine. However when I deploy to Azure then all my requests return 500 Server Error.
Are there any special deployment requirements for a REST Service to Azure ?
I don't see anything in my project that points to local.
I left everything in the web.config set to defaults.
You should remote desktop into the Azure instance and check the Application Log. See this post on how to connect to the remote server instance. Most likely you are missing an assembly reference.

VsDebuggerCasualityData

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

How to debug a remotely hosted WCF web service

I am new to WCF web service development and I can use some help.
I have a simple web service written in C# that I'm hosting on a remote server (it's hosted on IIS 5.1).
I've written a client application for that web service that I'm running on my workstation.I am able to connect to the service without any problems.
However, I would like to be able to debug the web service.I need to be able to step through the code, set breakpoints, etc.How do I achieve that from my local machine? I'm using Visual Studio 2010.
Thank you in advance.
I see two possibilities:
Local debugging: For debugging, run your service on your local machine. If you want to run it on the local IIS, simply start a second instance if VS2010 and attach to the w3wp.exe process (menu Tools -> Attach to process)
Remote Debugging: You have to install and start the VS2010 remote debugger on the server. Start a second instance of VS2010 on your development box and connect to the remote debugger with menu Tools -> Attach to process.
See msdn for more information about remote debugging with VS2010.