The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.


Server Error in '/' Application. 

The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error. 

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.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

 

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

 

 

Stack Trace: 

 

[CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.]

   System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) +10257978

   System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) +539

   Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustContract.Issue(Message message) +0

   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) +61

   Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst) +36

   Microsoft.SharePoint.SPSecurityContext.SecurityTokenForContext(Uri context, Boolean bearerToken, SecurityToken onBehalfOf, SecurityToken actAs, SecurityToken delegateTo) +26071489

   Microsoft.SharePoint.SPSecurityContext.SecurityTokenForFormsAuthentication(Uri context, String membershipProviderName, String roleProviderName, String username, String password) +172

   Microsoft.SharePoint.IdentityModel.Pages.FormsSignInPage.GetSecurityToken(Login formsSignInControl) +188

   Microsoft.SharePoint.IdentityModel.Pages.FormsSignInPage.AuthenticateEventHandler(Object sender, AuthenticateEventArgs formAuthenticateEvent) +123

   System.Web.UI.WebControls.AuthenticateEventHandler.Invoke(Object sender, AuthenticateEventArgs e) +0

   System.Web.UI.WebControls.Login.AttemptLogin() +152

   System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +124

   System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +70

   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +29

   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2981

 

 

 

Version Information: Microsoft .NET Framework Version:2.0.50727.4952; ASP.NET Version:2.0.50727.4927

When you get the error above, go to the Security Token Service Application under “SharePoint Web services” from and go to the “Authentication” of the Virtual Directory. and make sure all of the Anyonomous and Windows authentication is only ENABLED, rest of it has to be disabled. If you don’t follow this guideline , STS will behave like a JERK.

image

About these ads

5 Comments on “The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.”

  1. darshan September 14, 2011 at 3:11 am #

    Hey that worked well, you saved my time..thanks a lot

  2. rakesh December 31, 2011 at 11:58 am #

    Great!.-. Saved hell of a time

  3. Vena January 17, 2012 at 8:23 pm #

    I get this error for a certain request. Other requests works good.
    any idea why??

    • Manoj December 12, 2012 at 3:54 pm #

      I am having the same issues… it works on one method in webservice and the other method gives this error. dont know y… still trying to figure it out.

  4. gayathiri January 19, 2012 at 12:36 am #

    Still i’m getting the same error

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 81 other followers

%d bloggers like this: