February 3, 2005 at 8:46 am
2 problems - i cant access the http://localhost/reports folder - keeps coming up Directory Listing Denied, so i allowed directory browsing, it goes thru to http://localhost/Reports/Pages/Folder.aspx - request http status 404: not found
Also, the log has suddenly become massive 30meg every 10 mins - investigating it is writing the same 4 lines every second! Any ideas?
ReportingServicesService!resourceutilities!538!03/02/2005-15:13:50:: i INFO: Running on 1 physical processors, 1 logical processors
ReportingServicesService!resourceutilities!538!03/02/2005-15:13:50:: i INFO: Reporting Services starting SKU: Standard
ReportingServicesService!runningjobs!538!03/02/2005-15:13:50:: i INFO: Database Cleanup (NT Service) timer enabled: Cycle: 600 seconds
ReportingServicesService!runningjobs!538!03/02/2005-15:13:50:: i INFO: Running Requests Scavenger timer enabled: Cycle: 60 seconds
ReportingServicesService!runningjobs!538!03/02/2005-15:13:50:: i INFO: Running Requests DB timer enabled: Cycle: 60 seconds
ReportingServicesService!runningjobs!538!03/02/2005-15:13:50:: i INFO: Execution Log Entry Expiration timer enabled: Cycle: 38769 seconds
ReportingServicesService!runningjobs!538!03/02/2005-15:13:50:: i INFO: Memory stats update timer enabled: Cycle: 60 seconds
ReportingServicesService!dbcleanup!a08!03/02/2005-15:13:50:: i INFO: Expiring old execution log entries
ReportingServicesService!runningjobs!538!03/02/2005-15:13:51:: w WARN: Previous request for Execution Log Entry Expirationstill executing, skipping...
ReportingServicesService!crypto!1094!03/02/2005-15:13:55:: i INFO: Initializing crypto as user: NT AUTHORITY\SYSTEM
ReportingServicesService!crypto!1094!03/02/2005-15:13:55:: i INFO: Exporting public key
ReportingServicesService!crypto!1094!03/02/2005-15:13:56:: i INFO: Performing sku validation
ReportingServicesService!crypto!1094!03/02/2005-15:13:56:: i INFO: Importing existing encryption key
ReportingServicesService!dbcleanup!a08!03/02/2005-15:13:57:: i INFO: Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!a08!03/02/2005-15:13:58:: i INFO: Cleaned 0 broken snapshots, 0 chunks
ReportingServicesService!runningjobs!a08!03/02/2005-15:13:58:: i INFO: Execution Log Entry Expiration timer enabled: Cycle: 38761 seconds
ReportingServicesService!dbcleanup!538!03/02/2005-15:13:58:: i INFO: Expiring old execution log entries
ReportingServicesService!dbcleanup!538!03/02/2005-15:13:58:: i INFO: Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!538!03/02/2005-15:13:58:: i INFO: Cleaned 0 broken snapshots, 0 chunks
ReportingServicesService!runningjobs!538!03/02/2005-15:13:58:: i INFO: Execution Log Entry Expiration timer enabled: Cycle: 38761 seconds
ReportingServicesService!dbcleanup!a08!03/02/2005-15:13:58:: i INFO: Expiring old execution log entries
ReportingServicesService!dbcleanup!a08!03/02/2005-15:13:58:: i INFO: Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!a08!03/02/2005-15:13:58:: i INFO: Cleaned 0 broken snapshots, 0 chunks
ReportingServicesService!runningjobs!a08!03/02/2005-15:13:58:: i INFO: Execution Log Entry Expiration timer enabled: Cycle: 38761 seconds
ReportingServicesService!dbcleanup!538!03/02/2005-15:13:58:: i INFO: Expiring old execution log entries
ReportingServicesService!dbcleanup!538!03/02/2005-15:13:58:: i INFO: Expiration of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!538!03/02/2005-15:13:58:: i INFO: Cleaned 0 broken snapshots, 0 chunks
February 3, 2005 at 9:28 am
ok, found a link to http://support.microsoft.com/Default.aspx?kbid=885286 for the log file problem - no fix, you have to ring product support
Still havent a clue avout the webserver problem
February 4, 2005 at 12:43 am
Reinstall Reporting Services.
It sounds like IIS or the Reporting Services Service has lost some configuration. IIS should be bringing up reporting services, without any meddling with IIS configuration.
Julian Kuiters
juliankuiters.id.au
September 16, 2005 at 5:31 pm
This is how we controlled the issue. The settings are explained in the following location:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/arp_configfiles_v1_1pia.asp
We modified the file: ReportingServicesService.exe.config in the C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin folder.
The modifications were changed the DefaultTraceSwitch from the default of 3 (see below) to 1
DefaultTraceSwitch - Specifies the level of information that is reported to trace logs. Each level includes the information reported by all lower-numbered levels. Disabling tracing is not recommended.
0= Disables tracing
1= Exceptions and restarts
2= Exceptions, restarts, warnings
3= Exceptions, restarts, warnings, status messages (default)
4= Verbose mode
The files created now are much smaller. I would think even setting it to 2 would produce smaller files.
Also, the following setting was modified KeepFilesForDays from 14 to 3.
KeepFilesForDays - Specifies the number of days after which a trace log file will be deleted. 0 to max integer. The default is 14.
Hope this helps. We are at the base install of the Reporting Server (not at any SP level).
Subsequently, I also found this earlier post with similar recommendations.
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=162&messageid=157778
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply