OK... Looks like it's defintiely an issue with the [B]way the service is being hosted by WinHost [/B] or I need to update the service settings in the config file to resolve the issue.

I found this link while searching on the web:
http://forum.winhost.com/archive/index.php/t-2949.html

I'm using Entity Framework 4.1 which obviously uses LINQ to retrieve and update data.

Note that executing these service method on my local machine via my local service works abosultely fine!!!

The below code is an example of a class in my web service which is serialized back to my local client fine without an issue.

using System;
using System.Collections.Generic;
using System.Runtime.Serialization;
using System.ServiceModel;

namespace YeagerTechModel
{
    [Serializable]
    [DataContract(IsReference = true)]
    public partial class Category
    {
        public Category()
        {
            this.Projects = new HashSet<Project>();
        }
   
     [DataMember]
        public short CategoryID { get; set; }
     [DataMember]
        public string Description { get; set; }
   
     [DataMember]
        public virtual ICollection<Project> Projects { get; set; }
    }
   
}

If you look at the link I provided above and search for the below context, you will see the [B]same thing [/B]that is happening to my situation.

japinthebox02-06-2010, 03:11 PM
I've isolated the problem to a small portion of code tested here: [url]http://www.japinthebox.com/ServiceTest/Default.aspx[/url]

The service is implemented in App_Code/Service.cs. It seems to have nothing at all to do with circular references; it just doesn't want to send any [DataContract] objects generated by Linq to SQL.

02-17-2010, 01:32 AM
Hello,

We checked the application logs and the error is:

"A process serving application pool 'customerPool_2872' suffered a fatal communication error with the Windows Process Activation Service. The process id was '21412'. The data field contains the error number."

This is usually caused by a coding error that creates a stack overflow.

Sincerely,

Lukas
WinHost

There's a known stack overflow issue with returning Linq to SQL objects over WCF; when you have mutual references between two tables in the ORM, it'll crash with this same error message. I thought that may have been the case for me, but the same code works fine on my machine, and even when the ORM table has no references to other tables (or to itself, just to be sure), it still crashes.

What is the next step that can be taken in order to resolve this issue?