Answered by:
WCF Error The server was unable to process the request due to an internal error.

Question
-
Hello Experts
I have created some WCF services using WCF Application . Till Visual Studio Development Server everything is fine . I publish the WCF services project on IIS . When i try to consume the services it gives me following error .
Here is Web.config file code which is deployed on server .
Looking for your help
Regards
<?xml version="1.0"?>
<configuration>
<connectionStrings>
<add name="IntegrationDBConnectionString" connectionString="Data Source=myserver;Initial Catalog=IntegrationDB;Integrated Security=True" providerName="System.Data.SqlClient" />
<add name="PerfDBConnectionString" connectionString="Data Source=myserver;Initial Catalog=PerfDB;Integrated Security=True" providerName="System.Data.SqlClient" />
<add name="IntegrationDBEntities" connectionString="metadata=res://*/Integration.csdl|res://*/Integration.ssdl|res://*/Integration.msl;provider=System.Data.SqlClient;provider connection string="data source=EICSRV05;initial catalog=IntegrationDB;integrated security=True;multipleactiveresultsets=True;App=EntityFramework"" providerName="System.Data.EntityClient" /></connectionStrings>
<system.web>
<compilation targetFramework="4.0"><assemblies><add assembly="System.Data.Entity, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /></assemblies></compilation>
</system.web>
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior>
<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
<serviceMetadata httpGetEnabled="true" />
<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="false" />
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" aspNetCompatibilityEnabled="false" />
</system.serviceModel>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
</system.webServer>
</configuration>Server Error in '/' Application.
The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
Source Error:Line 48: Line 49: public void RequestQueue(string messageCommand, string messageParameters, System.DateTime messageDate, string userId, string processStatus) { Line 50: base.Channel.RequestQueue(messageCommand, messageParameters, messageDate, userId, processStatus); Line 51: } Line 52: }
Source File: C:\EIC Development Projects\AccentureIntegratoinServices\AccentureIntegrationServices\ServiceCosumerClient\Service References\ServiceREquestQueue\Reference.cs Line: 50
Stack Trace:[FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.] System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +9440287 System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +345 ServiceCosumerClient.ServiceREquestQueue.IRequestsQueue.RequestQueue(String messageCommand, String messageParameters, DateTime messageDate, String userId, String processStatus) +0 ServiceCosumerClient.ServiceREquestQueue.RequestsQueueClient.RequestQueue(String messageCommand, String messageParameters, DateTime messageDate, String userId, String processStatus) in C:\EIC Development Projects\AccentureIntegratoinServices\AccentureIntegrationServices\ServiceCosumerClient\Service References\ServiceREquestQueue\Reference.cs:50 ServiceCosumerClient.About.Page_Load(Object sender, EventArgs e) in C:\EIC Development Projects\AccentureIntegratoinServices\AccentureIntegrationServices\ServiceCosumerClient\ServiceConsumer.aspx.cs:18 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35 System.Web.UI.Control.OnLoad(EventArgs e) +91 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207
Tabbasi
Thursday, February 28, 2013 11:14 AM
Answers
-
Hi dev00,
Welcomes you to msdn forums..
May be this post will help you http://social.msdn.microsoft.com/Forums/en-US/dotnetstocktradersampleapplication/thread/750f7c35-5b3f-47b8-873e-4afd58228e2a/
Additonaly
1.Make sure that the service name and the contract contain full name(e.g namespace.ClassName), and the service name and interface is the same as the name attribute of the service tag and contract of endpoint in web.config.
2.When you create an IIS application the only /bin or /App_Code folder is in the root directory of the IIS app.So just remember put all the code in the root /bin or /App_code directory.
http://blogs.msdn.com/b/chrsmith/archive/2006/08/10/wcf-service-nesting-in-iis.aspx
Aslo
Pls look at the following link also
I hope this will helps you to solve your problems...
If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful"
- Marked as answer by Haixia_Xie Thursday, March 7, 2013 10:14 AM
Thursday, February 28, 2013 12:09 PM
All replies
-
Hi dev00,
Welcomes you to msdn forums..
May be this post will help you http://social.msdn.microsoft.com/Forums/en-US/dotnetstocktradersampleapplication/thread/750f7c35-5b3f-47b8-873e-4afd58228e2a/
Additonaly
1.Make sure that the service name and the contract contain full name(e.g namespace.ClassName), and the service name and interface is the same as the name attribute of the service tag and contract of endpoint in web.config.
2.When you create an IIS application the only /bin or /App_Code folder is in the root directory of the IIS app.So just remember put all the code in the root /bin or /App_code directory.
http://blogs.msdn.com/b/chrsmith/archive/2006/08/10/wcf-service-nesting-in-iis.aspx
Aslo
Pls look at the following link also
I hope this will helps you to solve your problems...
If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful"
- Marked as answer by Haixia_Xie Thursday, March 7, 2013 10:14 AM
Thursday, February 28, 2013 12:09 PM -
I have removed this error by changing the date format to default setting. it was so simple
Change Date and Time Format to following:
Date Formats
Short Date MM/dd/yyyy
Long Date dddd, MMMM d, yyyy
Tuesday, December 3, 2013 7:35 AM -
It's good that you're posting to the link that might solve the issue but pasting in the most relevant part of the answer would probably have been not only more awesome but saved a lot of time, both for OP and people coming along. (It's bad enough that people are sinking time into the project, debugging and research, save them a little bit...)
And for those coming along behind me, here's a most relevant part of the problem:
------------------------------Dear Ankush,
change wcf web.config file as below:
<behaviorname="wcf.servicename">
<serviceMetadatahttpGetEnabled="true"/>
<serviceDebughttpHelpPageEnabled="true"includeExceptionDetailInFaults="true"/>
</behavior>
- Edited by zephris Thursday, August 7, 2014 1:15 PM
Thursday, August 7, 2014 1:14 PM