Microsoft.ReportingServices.Proces singObjectModel Error
I have been creating reports using VS2005 and deploying to SQL 2005 without any problems.
Today I created2 reports, build, deploy fine. When I created the third the deploy failed with:
Code SnippetAn unexpected error occurred in Report Processing., ;Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: An unexpected error occurred in Report Processing. ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.ReportingServices.ProcessingObjectModel, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.
Each report within VS2005 has the error "An unexpected error occurred in Report Processing."
Removing the third report didn't help, removing all reports allowed me to deploy a shared datasource. When in SQL Management Studio (Reporting Services), I get the same error when trying to import the .RDL file. I have 200GB free on the SQL disk and have increased the disk allocation for RS and RSTemp DBs.
I have tried opening permissions (unlikely as it is to be the source of the issue) and rebooted to a clean environment to rule out memory issues.
I have completely stuck, my next recourse is to re-install SQL/RS but clearly that is a last resort and not guaranteed to solve the problem either.
There looks to be an issue with and assembly DLL but there have been no mods to my environment and no MS Updates either...
I am really struggling and hope someone can come up with some ideas I haven't tried.
Thanks in advance
August 14th, 2008 5:15pm
Update: Resolved the problem by deleting the IIS Virtual Directories for Reports and ReportServer and re-creating them using Report Services Configuration Manager. Hope this helps any others who find themselves in the same position.
Should have tried that earlier!
Free Windows Admin Tool Kit Click here and download it now
August 14th, 2008 6:37pm
Hmmm, a new day not quite a new problem.
Now getting exactly the same as yesterday and removing and adding virtual directories is not fixing it.
Any help? PLEASE?
August 15th, 2008 3:42pm
Additional NEW info from Log:
w3wp!library!4!08/15/2008-15:29:23:: i INFO: Exception dumped to: c:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\LogFiles flags= ReferencedMemory, AllThreads, SendToWatsonw3wp!library!7!08/15/2008-15:31:40:: Call to GetItemTypeAction(/Reports).w3wp!library!7!08/15/2008-15:31:40:: Call to GetItemTypeAction(/Data Sources).w3wp!library!7!08/15/2008-15:31:40:: Call to GetItemTypeAction(/Data Sources/Patients).w3wp!library!7!08/15/2008-15:31:40:: Call to CreateDataSourceAction(Patients, /Data Sources, True).w3wp!library!7!08/15/2008-15:31:40:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.ReportingServices.ProcessingCore, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.File name: 'Microsoft.ReportingServices.ProcessingCore, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' at Microsoft.ReportingServices.Library.SetDataSourceContentsAction.Update(CatalogItem item) at Microsoft.ReportingServices.Library.CreateDataSourceAction.UpdateExistingItem(CatalogItem item) at Microsoft.ReportingServices.Library.CreateItemAction`1.CreateOverwrite(CatalogItem item) at Microsoft.ReportingServices.Library.CreateItemAction`1.PerformActionNow() at Microsoft.ReportingServices.Library.RSSoapAction`1.Execute()
InternalCatalogException and unable to load Microsoft.ReportingServices.ProcessingCore
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2008 5:35pm
From the exception it seems that ProcessingCore.dll cannot be loaded due to missing file security or code access security permissions.
This would not happen unless those settings were explicitly changed after installation. Did you happen to change any of the settings in RSSrvPolicy.config and/or changed security permissions on the reportserver\bin folder?
-- Robert
August 15th, 2008 7:53pm
Hi Robert, thanks for the reply.
I have made no permission changes at all. Everything was working fine, was deploying then the next deploy failed. No system changes in the interim.
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2008 7:57pm
I have not seen this problem before. Any changes on the IIS application pools or the RS Windows service account?
-- Robert
August 16th, 2008 5:26am
None at all. I can check permissions if you could point out what should be there.
I have (through trying to resolve the issue) changed application pools without any success. I haven't changed permissions or accounts at all. I have run Reporting Services Configuration and re-created the Virtual Directories and re-created the SQL Reports Databases, none of this seems to make any difference. I should say that I can deploy the datasource ok now, any time I add any of my report files back into the project they fail. Even creating an incredibly basic report fails.
Remy
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2008 12:20pm
I have applied permissions to C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files directory for the ASP.Net Service Account and given the account modify permissions and this allowed me to deploy. There was no reference to this Service Account in existence. I have no idea why that would be as I certainly didn't change anything. Thanks for pointing me in the right direction, any idea why this account would have no permissions or have I fudged the issue?
regards,Remy
August 16th, 2008 3:52pm
This is getting beyond a joke, after my previous *answer* I got the problem, I tried re-creating the virtual directories and re-checked the permissions. No joy. I then checked the permissions for "C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer\bin" and added NETWORK SERVICE account with modify permissions. This worked.
I now have the error AGAIN and now have nothing else to look at, boy do I wish I had done this in Virtual PC.
I think I am going to have to uninstall SQL/VS/Reporting Services unless anyone has any other suggestions.
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2008 12:47am
Ok, after a lot of mucking about, I got it working again, this time I used Report Services Configuration Manager to re-assert the settings that were already there in Database Setup.
I'm not convinced about my environment, seems to fail randomly are resolve itself when it feels like it.
No doubt I will be back on tomorrow with the latest in this saga.
August 18th, 2008 1:43am
Problem has arisen again. Done the usual checks and can't resolve it at all.
Can someone explain or map what the permissions should be for Windows and Web Service Identity accounts and folders? Seems to be a permissions issue of some description but ******** if I can see what the problem is. As you can see from my various posts a number of things seems to have resolved it at different times.
Is there a quick way to *reset* the reporting environment to default other ran uninstall/re-install as I think that would be the way to go?
Free Windows Admin Tool Kit Click here and download it now
August 21st, 2008 2:52pm
My odyssey continues apace, I have modified the permissions on "C:\Windows\Microsoft.NET\Framework\v2.0.50727
" to give EVERYONE full access and it works, if I remove these permissions, it fails. Now I know I can'topen up the permissions like this for security reasons.The question is what is wrong with my file permissions? Report Services Configuration Manager has the ASP.NET service account set to "NT Authority\NetworkService" and "NETWORK SERVICE" account has Modify rights to this directory. Is there a possibility that the config file that RS is reading from is corrupt and reporting the wrong details or ASP.NET is running under another account?
Any view would be appreciated, I feel very lonely
August 21st, 2008 10:30pm
We're experiencing the exact same problems, we fixed the first round by editing the security for the asp.net folder, but now we have the same problem again, and the permissions are still there. Help is greatly appriciated at this point.Regards Niklas
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2008 12:18pm
Niklas A wrote:
We're experiencing the exact same problems, we fixed the first round by editing the security for the asp.net folder, but now we have the same problem again, and the permissions are still there. Help is greatly appriciated at this point.Regards NiklasI had to relax the permissions on the folder to include "Everyone", this is on my dev environment so it isn't causing me any real issues however if this is on a production system it is clearly not a proper solution.
September 29th, 2008 12:27pm
And now its up and running again.... wierd.It's a production server but the access is not set for Everyone but for the RS Web account.The only thing we could see in the logs were that a http discovery service had gone down before the test and up again when it was working to deploy.
Free Windows Admin Tool Kit Click here and download it now
September 29th, 2008 2:48pm
I fixed this problem in IIS 7.0:on the /Reports and /ReportServer Virtual Directories do this:1. In the features view, under the IIS sections double click on Authentication.2. Enable ASP.NET Impersonation3. Select ASP.NET Impersonation and select "Edit..." under the actions pane4. Select Authenticated userTry this and let me know how it works our for you.
December 30th, 2008 2:31am
Sounds like a reasonable answer: RS 2005 uses IIS for authentication. If someone is mucking with machine.config on the local box, or changing the Application Pool identity used by the RS Vdirs, then you can get lots of trouble with your configuration. Suggestion would be:1) create a separate app pool just for SSRS Vdirs2) ensure you track changes to the environment for changes to ASP.Net settings. Hope that helps,-LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com.
This posting is provided "AS IS" with no warranties, and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2009 7:37pm
so anyone get the problem solved? After two years later, someone newbie, me, getting the same problem. I still using 2005. Appreciate someone help
August 3rd, 2011 10:16am