Answered by:
Report.config has invalid schema, and could not be loaded error.

Question
-
We am facing a issue intermittently that on clicking report link in MS CRM it is giving error "Report.config has invalid schema, and could not be loaded error". Once we do IIS Reset on web server it again start working.
We have different server for Web and SQL.
You help is highly appreciated.
Wednesday, December 1, 2010 12:02 AM
Answers
-
In that case, please find a solution in the KB: http://support.microsoft.com/default.aspx?scid=kb;EN-US;914079
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Jackie Chen Microsoft Online Community Support- Proposed as answer by Curt Spanburgh MVP ModeratorMVP, Moderator Wednesday, March 2, 2011 6:30 PM
- Marked as answer by Donna EdwardsMVP Sunday, March 6, 2011 1:01 PM
Wednesday, March 2, 2011 5:53 AM -
Hi Experts,
The above proposed KB article use to work for me but use to be temporary solution and after sometime use to throw same error. Out of all suggested steps in KB only doing IIS Reset use to resolve the issue.
From last say 1 month I am not getting any error. The only change I did is there were some callouts which use to fetch some of the configuration data from machine.config file. On analysis I saw that before getting this errors there were some errors related to callout and from the day removed the configuration details from machine.config to some other config file it's working fine.
Apology if it was to verbose.
Thanks everybody for assistance.
- Marked as answer by MSCRM 3.0 Wednesday, March 30, 2011 10:29 PM
Wednesday, March 30, 2011 10:29 PM
All replies
-
That error occured from time to time on a CRM 3.0 server and the issue was that the .net version in the web extensions on the IIS server. Also there were issues where the .net version had to be reregistered.
Your on 4.0?
Seems like a .net issue. Are CRM and SSRS using the same App Pool?
Curtis J SpanburghThursday, December 2, 2010 5:25 AMModerator -
I am in CRM 3.0
I have different Web and SQL Server.
When I face this issue and check Web Extensions all seems to be fine and only doing IIS Reset reolves the issue.
Monday, December 6, 2010 6:53 AM -
Hi All,
Do anyone have a fix for this issue.
Your help is highly appreciated.
Cheers,
Parthaw
Wednesday, February 16, 2011 9:58 PM -
Please find the resolution in this KB http://support.microsoft.com/kb/916163
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Jackie Chen Microsoft Online Community Support- Proposed as answer by Jim Glass Jr Thursday, February 24, 2011 9:54 PM
Friday, February 18, 2011 7:17 AM -
Please let me know on which server i.e Report or Application we have to perform step 5
At the command prompt, type the following command, and then press ENTER:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe –rAlso is that can be issue as the error is intermittent and once we do IIS Reset it starts working fine.Thursday, February 24, 2011 9:33 PM -
Please run the command on Report server, since the cause for this issue is because Microsoft SQL Server Reporting Services does not support using the .NET Framework 2.0 in the virtual folders that Microsoft CRM uses if you are using SQL Server Reporting Services 2000.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Jackie Chen Microsoft Online Community Support- Proposed as answer by Curt Spanburgh MVP ModeratorMVP, Moderator Friday, February 25, 2011 2:28 PM
Friday, February 25, 2011 6:44 AM -
Hi Chen,
We are using SSRS 2005.
Tuesday, March 1, 2011 3:44 AM -
In that case, please find a solution in the KB: http://support.microsoft.com/default.aspx?scid=kb;EN-US;914079
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Jackie Chen Microsoft Online Community Support- Proposed as answer by Curt Spanburgh MVP ModeratorMVP, Moderator Wednesday, March 2, 2011 6:30 PM
- Marked as answer by Donna EdwardsMVP Sunday, March 6, 2011 1:01 PM
Wednesday, March 2, 2011 5:53 AM -
Hi Experts,
The above proposed KB article use to work for me but use to be temporary solution and after sometime use to throw same error. Out of all suggested steps in KB only doing IIS Reset use to resolve the issue.
From last say 1 month I am not getting any error. The only change I did is there were some callouts which use to fetch some of the configuration data from machine.config file. On analysis I saw that before getting this errors there were some errors related to callout and from the day removed the configuration details from machine.config to some other config file it's working fine.
Apology if it was to verbose.
Thanks everybody for assistance.
- Marked as answer by MSCRM 3.0 Wednesday, March 30, 2011 10:29 PM
Wednesday, March 30, 2011 10:29 PM