System.IO.FileNotFoundException
in [Reports]
|
Prev: Audemars Piguet Edward Piguet 25911bc/oo/d002cr/01, Best Luxury Watch - www.luxury-gift.org
Next: Problems Passing MDX Parameters through “Jump to URL”
From: JoeAZ on 1 Jul 2008 11:32 We recently had our 3 year old server decide to take a vacation so we migrated ReportingServices to a new machine. This machine is running in an AD domain and everything is working fine except the following. Reporting Services will generate a FileNotFound exception occasionaly. This can be between 1-3 days and the problem was much more frequent when we dropped the Application Pool recycle time to 60 minutes. Below is the output from one of the log files located at C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles. urceutilities!17d0!6/17/2008-18:51:47:: i INFO: Running on 2 physical processors, 4 logical processors w3wp!resourceutilities!17d0!6/17/2008-18:51:47:: i INFO: Reporting Services starting SKU: Enterprise w3wp!runningjobs!17d0!6/17/2008-18:51:47:: i INFO: Database Cleanup (Web Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds w3wp!runningjobs!17d0!6/17/2008-18:51:47:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds w3wp!runningjobs!17d0!6/17/2008-18:51:47:: i INFO: Running Requests DB timer enabled: Next Event: 120 seconds. Cycle: 120 seconds w3wp!runningjobs!17d0!6/17/2008-18:51:47:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds w3wp!crypto!17d0!06/17/2008-18:51:47:: i INFO: Initializing crypto as user: OURDOMAIN\OURUSER w3wp!crypto!17d0!06/17/2008-18:51:47:: i INFO: Exporting public key w3wp!webserver!17d0!06/17/2008-18:51:47:: e ERROR: Internal error: System.IO.FileNotFoundException: The system cannot find the file specified. at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode, IntPtr errorInfo) at RSManagedCrypto.RSCrypto.ExportPublicKey() at Microsoft.ReportingServices.Library.ConnectionManager.GetEncryptionKey() at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage() at Microsoft.ReportingServices.Library.ConnectionManager.VerifyConnection() at Microsoft.ReportingServices.Library.ConnectionManager.get_Connection() at Microsoft.ReportingServices.Library.Storage.get_Connection() at Microsoft.ReportingServices.Library.Storage.NewStandardSqlCommand(String storedProcedureName) at Microsoft.ReportingServices.Library.DBInterface.GetOneConfigurationInfo(String key) at Microsoft.ReportingServices.Library.CachedSystemProperties.GetSystemProperty(String name) at Microsoft.ReportingServices.Library.CachedSystemProperties.Get(String name) at Microsoft.ReportingServices.Library.CachedSystemProperties.GetParameter(String name) at Microsoft.ReportingServices.Library.RSService.get_MyReportsEnabled() at Microsoft.ReportingServices.Library.RSService.PathToInternal(String source) at Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String path, Boolean validate, Boolean convert, Boolean translate) at Microsoft.ReportingServices.Diagnostics.CatalogItemContext.SetPath(String path) at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent() at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage() w3wp!library!17d0!06/17/2008-18:51:47:: 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.FileNotFoundException: The system cannot find the file specified. The fix is always the same, log onto the server and go to the application pool that ReportingServices runs under and perform a Recycle. We're not seeing any entries in the Application or System logs and the user sees the generic FNF error above. The application pool is running under a user that is an admin on the box and again reports run file for long periods and then, at some point, generate the following error and no other things we've tried fix the problem except for a App Pool recycle. Server Specs: 4GB RAM Windows Server 2003 SP2 Sql Server 2000 SP4 Sql Server 2000 Reporting Services SP2 |