HTTP ERROR 500.22 – Internal Server Error. An ASP.NET setting has been detected that does not apply in Integrated Managed Pipeline mode.


Issue
---------------------
HTTP ERROR 500.22 – Internal Server Error.”
  “An ASP.NET setting has been detected that does not apply in Integrated Managed Pipeline mode.”

Solution
------------------
Ensure the application pool configured for the MS Dynamics CRM application is correct and has the correct privileges.


Comments

Post a Comment

Popular posts from this blog

The famous Vanilla story --

This is a weird but true  story ...  A complaint was received by the Pontiac Division of General Motors:  This is the second time I have written you, and I don't blame you for not answering me, because I kind of sounded crazy, but it is a fact that we have a tradition in our family of ice cream for dessert after dinner each night. But the kind of ice cream varies so, every night, after we've eaten, the whole family votes on which kind of ice cream we should have and I drive down to the store to get it.  It's also a fact that I recently purchased a new Pontiac and since then my trips to the store have created a problem. You see, every time I buy  vanilla ice cream, when I start back from the store my car won't start. If I get any other kind of ice cream, the car starts just fine.  I want you to know I'm serious about this question, no matter how silly it sounds: 'What is there about a Pontiac that makes it not start when I get vanilla ice crea...
Read more

HOW TO REMOVE THE TFS ASSOCIATION FROM MPP FILE.

HOW TO REMOVE THE TFS ASSOCIATION FROM MPP FILE.   Close Microsoft Project Right click on the mpp file and choose Properties. Choose the Custom tab in the Properties window. Choose any Property listed there named "VS  Team System Data Do Not Edit" and click Remove. Click Apply or Ok. Open the mpp file, and you will get a message saying its not associated with any TFS server. Click Ok and Save it. You will not get the error message every time you open the mpp file as long as you save it once after the message is received.
Read more

Convert fetchXML to SQL Query in MSCRM 4.0

If for some sane reasons if fetchxml needs to be converted to a SQL Query in MSCRM 4.0, it is possible. It actually requires the below DLL's which are avilable in the folder Server\setup Microsoft.Crm.dll, Microsoft.Crm.Platform.Server.dll and Microsoft.Crm.Reporting.dll The code looks as below : Microsoft.Crm.BusinessEntities.ExecutionContext myContext = new Microsoft.Crm.BusinessEntities. ExecutionContext (OrganizationId from the context); myContext.OnBeginRequest(UserId, false); Microsoft.Crm.Reporting.ReportQueryBuilder myreportQueryBuilderObj = new ReportQueryBuilder(); string Query = myreportQueryBuilderObj.BuildReportQuery(fetchXml, myContext); The query will be returned as string. The Query is not readable but it works, -:)
Read more