Hi;
im trying to create sort of a contract in RS, ill get some information from
an employee table, but most of the report is plain-fixed text. Im not sure
but i think the best way to do it is using only a detail band (ill need to
print a contract by employee), and use textboxes for the text...
but... i noticed i cant insert blank lines in a textbox (nothing happends
when i press return) and im not sure about my approach...
Any advice?
TIAOn May 30, 7:41 pm, "Willo" <willobe...@.yahoo.com.mx> wrote:
> Hi;
> im trying to create sort of a contract in RS, ill get some information from
> an employee table, but most of the report is plain-fixed text. Im not sure
> but i think the best way to do it is using only a detail band (ill need to
> print a contract by employee), and use textboxes for the text...
> but... i noticed i cant insert blank lines in a textbox (nothing happends
> when i press return) and im not sure about my approach...
> Any advice?
> TIA
If I understand you correctly, you should concatenate the employee
table info w/the plain-fixed text as part of the stored procedure/
query that sources your report. Also, you could try using a table
control to create spaces if necessary. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Showing posts with label report. Show all posts
Showing posts with label report. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Long Running Reports
I have some reports that need to run for about 10 minutes. I changed the
parameter on the report to "Do not timeout report execution" but I still get
a connection timout error. What else do I need to change?
I get the following error in IE:
10060 - Connection timeout
Internet Security and Acceleration ServerThis error is being returned by your security and acceleration server --
sitting between your browser and the report server. That's where the
timeout needs to be adjusted.
--
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Ed Willis" <ed_willis@.acsi.orgnospam> wrote in message
news:OJktXvm1EHA.2540@.TK2MSFTNGP09.phx.gbl...
>I have some reports that need to run for about 10 minutes. I changed the
>parameter on the report to "Do not timeout report execution" but I still
>get a connection timout error. What else do I need to change?
> I get the following error in IE:
> 10060 - Connection timeout
> Internet Security and Acceleration Server
>|||That Worked. Thanks :)
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:edph0x11EHA.3596@.TK2MSFTNGP12.phx.gbl...
> This error is being returned by your security and acceleration server --
> sitting between your browser and the report server. That's where the
> timeout needs to be adjusted.
> --
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "Ed Willis" <ed_willis@.acsi.orgnospam> wrote in message
> news:OJktXvm1EHA.2540@.TK2MSFTNGP09.phx.gbl...
>>I have some reports that need to run for about 10 minutes. I changed the
>>parameter on the report to "Do not timeout report execution" but I still
>>get a connection timout error. What else do I need to change?
>> I get the following error in IE:
>> 10060 - Connection timeout
>> Internet Security and Acceleration Server
>
parameter on the report to "Do not timeout report execution" but I still get
a connection timout error. What else do I need to change?
I get the following error in IE:
10060 - Connection timeout
Internet Security and Acceleration ServerThis error is being returned by your security and acceleration server --
sitting between your browser and the report server. That's where the
timeout needs to be adjusted.
--
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Ed Willis" <ed_willis@.acsi.orgnospam> wrote in message
news:OJktXvm1EHA.2540@.TK2MSFTNGP09.phx.gbl...
>I have some reports that need to run for about 10 minutes. I changed the
>parameter on the report to "Do not timeout report execution" but I still
>get a connection timout error. What else do I need to change?
> I get the following error in IE:
> 10060 - Connection timeout
> Internet Security and Acceleration Server
>|||That Worked. Thanks :)
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:edph0x11EHA.3596@.TK2MSFTNGP12.phx.gbl...
> This error is being returned by your security and acceleration server --
> sitting between your browser and the report server. That's where the
> timeout needs to be adjusted.
> --
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "Ed Willis" <ed_willis@.acsi.orgnospam> wrote in message
> news:OJktXvm1EHA.2540@.TK2MSFTNGP09.phx.gbl...
>>I have some reports that need to run for about 10 minutes. I changed the
>>parameter on the report to "Do not timeout report execution" but I still
>>get a connection timout error. What else do I need to change?
>> I get the following error in IE:
>> 10060 - Connection timeout
>> Internet Security and Acceleration Server
>
Long running report fails with http error
Hi,
I have a report that takes about an hour to run. When I run it, it runs for
an hour or so with "Generating Report", then the result page is the standard
IE "Action Canceled" page, and there is a javascript error. The javascript
error is Permission denied.
All other reports running on this server (which don't take as long to run)
are fine. I've checked IIS settings and blown the connection timeout to 9000
seconds.
It's as if the report is taking too long...
I've set all the URL stuff in the config files, but like I say, its only one
out of about a hundred reports that is failing.
Any ideas?
SteveHi,
I think this is something to do with your queries some where it is not
optimized. Just check whether the same query / procedure runs in your
management studio.
Amarnath
"Steve" wrote:
> Hi,
> I have a report that takes about an hour to run. When I run it, it runs for
> an hour or so with "Generating Report", then the result page is the standard
> IE "Action Canceled" page, and there is a javascript error. The javascript
> error is Permission denied.
> All other reports running on this server (which don't take as long to run)
> are fine. I've checked IIS settings and blown the connection timeout to 9000
> seconds.
> It's as if the report is taking too long...
> I've set all the URL stuff in the config files, but like I say, its only one
> out of about a hundred reports that is failing.
> Any ideas?
> Steve
I have a report that takes about an hour to run. When I run it, it runs for
an hour or so with "Generating Report", then the result page is the standard
IE "Action Canceled" page, and there is a javascript error. The javascript
error is Permission denied.
All other reports running on this server (which don't take as long to run)
are fine. I've checked IIS settings and blown the connection timeout to 9000
seconds.
It's as if the report is taking too long...
I've set all the URL stuff in the config files, but like I say, its only one
out of about a hundred reports that is failing.
Any ideas?
SteveHi,
I think this is something to do with your queries some where it is not
optimized. Just check whether the same query / procedure runs in your
management studio.
Amarnath
"Steve" wrote:
> Hi,
> I have a report that takes about an hour to run. When I run it, it runs for
> an hour or so with "Generating Report", then the result page is the standard
> IE "Action Canceled" page, and there is a javascript error. The javascript
> error is Permission denied.
> All other reports running on this server (which don't take as long to run)
> are fine. I've checked IIS settings and blown the connection timeout to 9000
> seconds.
> It's as if the report is taking too long...
> I've set all the URL stuff in the config files, but like I say, its only one
> out of about a hundred reports that is failing.
> Any ideas?
> Steve
long running report can not be rendered in Report Manager or through Subscription
I am using a stored procedure which will run about one hour and ten minutes to return a dataset to reporting services to generate a report. The report generation is OK if I run it inside Visual Studio 2005. Once it is deployed, it can not finish. Both cases I set "Do not timeout report execution". I even try to create a subscription to let it run throught. But it still can not finish. The traces information in ReportServer*.Log is like this:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>Central Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServer__06_29_2006_09_58_21.log</Path>
<SystemName>JSONG-XP</SystemName>
<OSName>Microsoft Windows NT 5.1.2600 Service Pack 2</OSName>
<OSVersion>5.1.2600.131072</OSVersion>
</Header>
aspnet_wp!webserver!6!6/29/2006-09:58:21:: i INFO: Reporting Web Server started
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
aspnet_wp!configmanager!6!6/29/2006-09:58:21:: w WARN: WebServiceAccount is not specified in the config file. Using default: JSONG-XP\ASPNET
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
aspnet_wp!resourceutilities!6!6/29/2006-09:58:21:: i INFO: Reporting Services starting SKU: Developer
aspnet_wp!resourceutilities!6!6/29/2006-09:58:21:: i INFO: Evaluation copy: 0 days left
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Database Cleanup (Web Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!library!6!06/29/2006-09:58:23:: i INFO: Call to GetPermissions:/
aspnet_wp!library!6!06/29/2006-09:58:24:: i INFO: Catalog SQL Server Edition = Developer
aspnet_wp!library!6!06/29/2006-09:58:24:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-09:58:40:: i INFO: Call to GetPermissions:/CreditReports
aspnet_wp!library!6!06/29/2006-09:58:40:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!1!06/29/2006-09:58:41:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!1!06/29/2006-09:58:41:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!1!06/29/2006-09:58:44:: i INFO: Call to RenderFirst( '/CreditReports/ExperienceByCoverageSEDEV' )
aspnet_wp!runningjobs!5!6/29/2006-09:59:27:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:03:36:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:06:25:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:06:25:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:13:12:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:16:12:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:16:12:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:23:13:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:26:13:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:26:13:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:33:11:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:36:09:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:36:09:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:43:06:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:46:05:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:46:05:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:53:07:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:56:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:56:07:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!a!6/29/2006-10:57:07:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
aspnet_wp!runningjobs!c!6/29/2006-10:58:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:58:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:59:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:59:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:00:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:00:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:01:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:01:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:02:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:02:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:03:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:03:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:04:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:04:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:05:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:05:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!c!6/29/2006-11:06:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams
aspnet_wp!runningjobs!c!6/29/2006-11:06:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:06:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!session!9!06/29/2006-11:06:52:: e ERROR: Sql Error in GetSnapshotData: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName, ConnectionManager connMgr)
aspnet_wp!library!9!06/29/2006-11:06:52:: 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.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName, ConnectionManager connMgr)
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName)
at Microsoft.ReportingServices.Library.SessionReportItem.Load(DatabaseSessionStorage sessionStorage, LoadAction loadFlags, String sessionId, String reportPath, DateTime snapshotDate, String userName, String userParams, String imageName, DatasourceCredentialsCollection dataSourceCred)
at Microsoft.ReportingServices.WebServer.HttpClientRequest.LoadFromDB(LoadAction loadFlags, CatalogItemContext context)
at Microsoft.ReportingServices.WebServer.SessionStarterAction.CreateExisting()
End of inner exception stack trace
aspnet_wp!library!6!06/29/2006-11:06:54:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:06:54:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:06:55:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:06:55:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:07:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:07:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!8!06/29/2006-11:07:51:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:07:51:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:08:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:08:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetSnapshotLimit( '/CreditReports/ExperienceByCoverageSEDEV' )
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetPolicies:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:21:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:22:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:28:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:08:28:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:37:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:37:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:51:: i INFO: Call to GetPermissions:/CreditReports
aspnet_wp!library!6!06/29/2006-11:08:51:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:55:: i INFO: Call to GetPermissions:/CreditReports/AS400SEDEV
aspnet_wp!library!8!06/29/2006-11:08:55:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:09:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:09:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
I would like know the reason behind it. How to fix that?. I use Sql Server 2005 developer edition.
Thanx
There is a limit for how long a report will run from Report Manager. You can modify the setting at:
Report Manager --> Site Settings-->Report Execution Timeout-->Limit
report execution to the following number of seconds = 3600 (1 hr)
|||
Thank you for your reply.
Actually I set
Report Manager --> Site Settings-->Report Execution Timeout-->Do not timeout report execution. It still can not produce the report.
Another question is after I set localhost/reports and localhost/reportserver session timeout to 3 hrs and these site's asp.net state management session timout to 3hrs, the localhost/reportserver is not accessable. Maybe it is a reporting services bug. Steps to repeat the scenario: Go to IIS, right click localhost/reports-->Properties-->Click Configuration-->Application Configuration-->Options-->Change session timeout to 180 minutes. To set asp.net state management session timout to 3hrs. right click localhost/reports-->Properties-->Report Properties windows-->Click ASP.NET tab-->Edit Configuration-->State Management-->Set Session timout to 180 Minutes.
So far so good. Once repeating above operations to localhost/reportserver, both sites will become unaccessable.
Your response will be appreciated.
|||The exception you are hitting is the session access timeout. The viewer control will try to ping back to the server every N-1 minutes (where N is basically the session expiration time). The default session access timeout is 10 minutes, so if the report takes over an hour to render, you will hit this timeout.
You can run into problems when the time it takes to render the report is longer than the session timeout, I would recommend altering the following system properties (you will have to do this via the SOAP API or an rs.exe script since they are not exposed in the management studio UI) to be more on the order of what you expect the report execution to be:
SessionAccessTimeout|||
Actually, rendering the long running report in the report manager is just for test purpose. I will create a subscription to deliver the report to a shared folder using SOAP API. Even for the subscription, the timeout issue still exists. Could you provide me some examples to set session timeout via SOAP API or a re.exe.
Thank you very much.
|||Any news? I have the same issue. Can you explain please which values should be used for these parameters in order to get the report running for more than 1 hour?|||There is a blog about it herehttp://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
So i did change this for a report that needs 20 minutes but it still fail after 5 minutes with this error in the computer application log
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 10/31/2006 10:08:46 AM
Event time (UTC): 10/31/2006 5:08:46 PM
Event ID: c6233c9a2cff498a90cfa4140a3e932a
Event sequence: 1572
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-128067603886462532
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\
Machine name: ATLANTA
Process information:
Process ID: 6452
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: ReportServerException
Exception message: Execution 'fmnjra45tvj15545rxlxt5ec' cannot be found (rsExecutionNotFound)
Request information:
Request URL: http://reporting.onsemi.com/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=fmnjra45tvj15545rxlxt5ec&ControlID=84b2a2bd-4f03-4c5d-9d73-c305e7883b6e&Culture=1033&UICulture=9&ReportStack=1&OpType=SessionKeepAlive&TimerMethod=KeepAliveMethodctl161TouchSession0&CacheSeed=Tue Oct 31 10:08:44 2006
Request path: /Reports/Reserved.ReportViewerWebControl.axd
User host address: 10.253.138.208
User: ONSEMI\R38851
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 14
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo()
at Microsoft.Reporting.WebForms.ServerReport.SetExecutionId(String executionId, Boolean fullReportLoad)
at Microsoft.Reporting.WebForms.ServerReport.LoadFromUrlQuery(NameValueCollection requestParameters, Boolean fullReportLoad)
at Microsoft.Reporting.WebForms.ReportDataOperation..ctor()
at Microsoft.Reporting.WebForms.HttpHandler.GetHandler()
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Any idea?
Thanks,
Philippe
long running report can not be rendered in Report Manager or through Subscription
I am using a stored procedure which will run about one hour and ten minutes to return a dataset to reporting services to generate a report. The report generation is OK if I run it inside Visual Studio 2005. Once it is deployed, it can not finish. Both cases I set "Do not timeout report execution". I even try to create a subscription to let it run throught. But it still can not finish. The traces information in ReportServer*.Log is like this:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>Central Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServer__06_29_2006_09_58_21.log</Path>
<SystemName>JSONG-XP</SystemName>
<OSName>Microsoft Windows NT 5.1.2600 Service Pack 2</OSName>
<OSVersion>5.1.2600.131072</OSVersion>
</Header>
aspnet_wp!webserver!6!6/29/2006-09:58:21:: i INFO: Reporting Web Server started
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
aspnet_wp!configmanager!6!6/29/2006-09:58:21:: w WARN: WebServiceAccount is not specified in the config file. Using default: JSONG-XP\ASPNET
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
aspnet_wp!resourceutilities!6!6/29/2006-09:58:21:: i INFO: Reporting Services starting SKU: Developer
aspnet_wp!resourceutilities!6!6/29/2006-09:58:21:: i INFO: Evaluation copy: 0 days left
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Database Cleanup (Web Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!library!6!06/29/2006-09:58:23:: i INFO: Call to GetPermissions:/
aspnet_wp!library!6!06/29/2006-09:58:24:: i INFO: Catalog SQL Server Edition = Developer
aspnet_wp!library!6!06/29/2006-09:58:24:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-09:58:40:: i INFO: Call to GetPermissions:/CreditReports
aspnet_wp!library!6!06/29/2006-09:58:40:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!1!06/29/2006-09:58:41:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!1!06/29/2006-09:58:41:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!1!06/29/2006-09:58:44:: i INFO: Call to RenderFirst( '/CreditReports/ExperienceByCoverageSEDEV' )
aspnet_wp!runningjobs!5!6/29/2006-09:59:27:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:03:36:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:06:25:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:06:25:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:13:12:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:16:12:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:16:12:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:23:13:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:26:13:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:26:13:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:33:11:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:36:09:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:36:09:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:43:06:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:46:05:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:46:05:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:53:07:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:56:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:56:07:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!a!6/29/2006-10:57:07:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
aspnet_wp!runningjobs!c!6/29/2006-10:58:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:58:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:59:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:59:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:00:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:00:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:01:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:01:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:02:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:02:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:03:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:03:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:04:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:04:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:05:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:05:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!c!6/29/2006-11:06:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams
aspnet_wp!runningjobs!c!6/29/2006-11:06:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:06:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!session!9!06/29/2006-11:06:52:: e ERROR: Sql Error in GetSnapshotData: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName, ConnectionManager connMgr)
aspnet_wp!library!9!06/29/2006-11:06:52:: 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.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName, ConnectionManager connMgr)
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName)
at Microsoft.ReportingServices.Library.SessionReportItem.Load(DatabaseSessionStorage sessionStorage, LoadAction loadFlags, String sessionId, String reportPath, DateTime snapshotDate, String userName, String userParams, String imageName, DatasourceCredentialsCollection dataSourceCred)
at Microsoft.ReportingServices.WebServer.HttpClientRequest.LoadFromDB(LoadAction loadFlags, CatalogItemContext context)
at Microsoft.ReportingServices.WebServer.SessionStarterAction.CreateExisting()
End of inner exception stack trace
aspnet_wp!library!6!06/29/2006-11:06:54:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:06:54:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:06:55:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:06:55:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:07:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:07:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!8!06/29/2006-11:07:51:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:07:51:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:08:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:08:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetSnapshotLimit( '/CreditReports/ExperienceByCoverageSEDEV' )
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetPolicies:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:21:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:22:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:28:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:08:28:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:37:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:37:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:51:: i INFO: Call to GetPermissions:/CreditReports
aspnet_wp!library!6!06/29/2006-11:08:51:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:55:: i INFO: Call to GetPermissions:/CreditReports/AS400SEDEV
aspnet_wp!library!8!06/29/2006-11:08:55:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:09:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:09:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
I would like know the reason behind it. How to fix that?. I use Sql Server 2005 developer edition.
Thanx
There is a limit for how long a report will run from Report Manager. You can modify the setting at:
Report Manager --> Site Settings-->Report Execution Timeout-->Limit
report execution to the following number of seconds = 3600 (1 hr)
|||
Thank you for your reply.
Actually I set
Report Manager --> Site Settings-->Report Execution Timeout-->Do not timeout report execution. It still can not produce the report.
Another question is after I set localhost/reports and localhost/reportserver session timeout to 3 hrs and these site's asp.net state management session timout to 3hrs, the localhost/reportserver is not accessable. Maybe it is a reporting services bug. Steps to repeat the scenario: Go to IIS, right click localhost/reports-->Properties-->Click Configuration-->Application Configuration-->Options-->Change session timeout to 180 minutes. To set asp.net state management session timout to 3hrs. right click localhost/reports-->Properties-->Report Properties windows-->Click ASP.NET tab-->Edit Configuration-->State Management-->Set Session timout to 180 Minutes.
So far so good. Once repeating above operations to localhost/reportserver, both sites will become unaccessable.
Your response will be appreciated.
|||The exception you are hitting is the session access timeout. The viewer control will try to ping back to the server every N-1 minutes (where N is basically the session expiration time). The default session access timeout is 10 minutes, so if the report takes over an hour to render, you will hit this timeout.
You can run into problems when the time it takes to render the report is longer than the session timeout, I would recommend altering the following system properties (you will have to do this via the SOAP API or an rs.exe script since they are not exposed in the management studio UI) to be more on the order of what you expect the report execution to be:
SessionAccessTimeout|||
Actually, rendering the long running report in the report manager is just for test purpose. I will create a subscription to deliver the report to a shared folder using SOAP API. Even for the subscription, the timeout issue still exists. Could you provide me some examples to set session timeout via SOAP API or a re.exe.
Thank you very much.
|||Any news? I have the same issue. Can you explain please which values should be used for these parameters in order to get the report running for more than 1 hour?|||There is a blog about it herehttp://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
So i did change this for a report that needs 20 minutes but it still fail after 5 minutes with this error in the computer application log
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 10/31/2006 10:08:46 AM
Event time (UTC): 10/31/2006 5:08:46 PM
Event ID: c6233c9a2cff498a90cfa4140a3e932a
Event sequence: 1572
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-128067603886462532
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\
Machine name: ATLANTA
Process information:
Process ID: 6452
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: ReportServerException
Exception message: Execution 'fmnjra45tvj15545rxlxt5ec' cannot be found (rsExecutionNotFound)
Request information:
Request URL: http://reporting.onsemi.com/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=fmnjra45tvj15545rxlxt5ec&ControlID=84b2a2bd-4f03-4c5d-9d73-c305e7883b6e&Culture=1033&UICulture=9&ReportStack=1&OpType=SessionKeepAlive&TimerMethod=KeepAliveMethodctl161TouchSession0&CacheSeed=Tue Oct 31 10:08:44 2006
Request path: /Reports/Reserved.ReportViewerWebControl.axd
User host address: 10.253.138.208
User: ONSEMI\R38851
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 14
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo()
at Microsoft.Reporting.WebForms.ServerReport.SetExecutionId(String executionId, Boolean fullReportLoad)
at Microsoft.Reporting.WebForms.ServerReport.LoadFromUrlQuery(NameValueCollection requestParameters, Boolean fullReportLoad)
at Microsoft.Reporting.WebForms.ReportDataOperation..ctor()
at Microsoft.Reporting.WebForms.HttpHandler.GetHandler()
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Any idea?
Thanks,
Philippe
long running report can not be rendered in Report Manager or through Subscription
I am using a stored procedure which will run about one hour and ten minutes to return a dataset to reporting services to generate a report. The report generation is OK if I run it inside Visual Studio 2005. Once it is deployed, it can not finish. Both cases I set "Do not timeout report execution". I even try to create a subscription to let it run throught. But it still can not finish. The traces information in ReportServer*.Log is like this:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>Central Standard Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\ReportServer__06_29_2006_09_58_21.log</Path>
<SystemName>JSONG-XP</SystemName>
<OSName>Microsoft Windows NT 5.1.2600 Service Pack 2</OSName>
<OSVersion>5.1.2600.131072</OSVersion>
</Header>
aspnet_wp!webserver!6!6/29/2006-09:58:21:: i INFO: Reporting Web Server started
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
aspnet_wp!configmanager!6!6/29/2006-09:58:21:: w WARN: WebServiceAccount is not specified in the config file. Using default: JSONG-XP\ASPNET
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
aspnet_wp!library!6!6/29/2006-09:58:21:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
aspnet_wp!resourceutilities!6!6/29/2006-09:58:21:: i INFO: Reporting Services starting SKU: Developer
aspnet_wp!resourceutilities!6!6/29/2006-09:58:21:: i INFO: Evaluation copy: 0 days left
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Database Cleanup (Web Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!runningjobs!6!6/29/2006-09:58:21:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds
aspnet_wp!library!6!06/29/2006-09:58:23:: i INFO: Call to GetPermissions:/
aspnet_wp!library!6!06/29/2006-09:58:24:: i INFO: Catalog SQL Server Edition = Developer
aspnet_wp!library!6!06/29/2006-09:58:24:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-09:58:40:: i INFO: Call to GetPermissions:/CreditReports
aspnet_wp!library!6!06/29/2006-09:58:40:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!1!06/29/2006-09:58:41:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!1!06/29/2006-09:58:41:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!1!06/29/2006-09:58:44:: i INFO: Call to RenderFirst( '/CreditReports/ExperienceByCoverageSEDEV' )
aspnet_wp!runningjobs!5!6/29/2006-09:59:27:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:03:36:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:06:25:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:06:25:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:13:12:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:16:12:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:16:12:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:23:13:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:26:13:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:26:13:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:33:11:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:36:09:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:36:09:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:43:06:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:46:05:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:46:05:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!5!6/29/2006-10:53:07:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!library!5!6/29/2006-10:56:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 1 running jobs, 0 persisted streams
aspnet_wp!runningjobs!5!6/29/2006-10:56:07:: i INFO: Adding: 1 running jobs to the database
aspnet_wp!runningjobs!a!6/29/2006-10:57:07:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
aspnet_wp!runningjobs!c!6/29/2006-10:58:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:58:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:59:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-10:59:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:00:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:00:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:01:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:01:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:02:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:02:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:03:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:03:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:04:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:04:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:05:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:05:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!c!6/29/2006-11:06:07:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs, 0 persisted streams
aspnet_wp!runningjobs!c!6/29/2006-11:06:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!c!6/29/2006-11:06:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!session!9!06/29/2006-11:06:52:: e ERROR: Sql Error in GetSnapshotData: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName, ConnectionManager connMgr)
aspnet_wp!library!9!06/29/2006-11:06:52:: 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.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName, ConnectionManager connMgr)
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.GetSessionData(String sessionId, String userName)
at Microsoft.ReportingServices.Library.SessionReportItem.Load(DatabaseSessionStorage sessionStorage, LoadAction loadFlags, String sessionId, String reportPath, DateTime snapshotDate, String userName, String userParams, String imageName, DatasourceCredentialsCollection dataSourceCred)
at Microsoft.ReportingServices.WebServer.HttpClientRequest.LoadFromDB(LoadAction loadFlags, CatalogItemContext context)
at Microsoft.ReportingServices.WebServer.SessionStarterAction.CreateExisting()
End of inner exception stack trace
aspnet_wp!library!6!06/29/2006-11:06:54:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:06:54:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:06:55:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:06:55:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:07:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:07:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!8!06/29/2006-11:07:51:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:07:51:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:08:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:08:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:16:: i INFO: Call to GetSnapshotLimit( '/CreditReports/ExperienceByCoverageSEDEV' )
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:19:: i INFO: Call to GetPolicies:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:21:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:22:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:28:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!6!06/29/2006-11:08:28:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:37:: i INFO: Call to GetPermissions:/CreditReports/ExperienceByCoverageSEDEV
aspnet_wp!library!8!06/29/2006-11:08:37:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!6!06/29/2006-11:08:51:: i INFO: Call to GetPermissions:/CreditReports
aspnet_wp!library!6!06/29/2006-11:08:51:: i INFO: Call to GetSystemPermissions
aspnet_wp!library!8!06/29/2006-11:08:55:: i INFO: Call to GetPermissions:/CreditReports/AS400SEDEV
aspnet_wp!library!8!06/29/2006-11:08:55:: i INFO: Call to GetSystemPermissions
aspnet_wp!runningjobs!5!6/29/2006-11:09:07:: w WARN: Previous request for Running Requests Scavengerstill executing, skipping...
aspnet_wp!runningjobs!5!6/29/2006-11:09:07:: w WARN: Previous request for Running Requests DBstill executing, skipping...
I would like know the reason behind it. How to fix that?. I use Sql Server 2005 developer edition.
Thanx
There is a limit for how long a report will run from Report Manager. You can modify the setting at:
Report Manager --> Site Settings-->Report Execution Timeout-->Limit
report execution to the following number of seconds = 3600 (1 hr)
|||
Thank you for your reply.
Actually I set
Report Manager --> Site Settings-->Report Execution Timeout-->Do not timeout report execution. It still can not produce the report.
Another question is after I set localhost/reports and localhost/reportserver session timeout to 3 hrs and these site's asp.net state management session timout to 3hrs, the localhost/reportserver is not accessable. Maybe it is a reporting services bug. Steps to repeat the scenario: Go to IIS, right click localhost/reports-->Properties-->Click Configuration-->Application Configuration-->Options-->Change session timeout to 180 minutes. To set asp.net state management session timout to 3hrs. right click localhost/reports-->Properties-->Report Properties windows-->Click ASP.NET tab-->Edit Configuration-->State Management-->Set Session timout to 180 Minutes.
So far so good. Once repeating above operations to localhost/reportserver, both sites will become unaccessable.
Your response will be appreciated.
|||The exception you are hitting is the session access timeout. The viewer control will try to ping back to the server every N-1 minutes (where N is basically the session expiration time). The default session access timeout is 10 minutes, so if the report takes over an hour to render, you will hit this timeout.
You can run into problems when the time it takes to render the report is longer than the session timeout, I would recommend altering the following system properties (you will have to do this via the SOAP API or an rs.exe script since they are not exposed in the management studio UI) to be more on the order of what you expect the report execution to be:
SessionAccessTimeout|||
Actually, rendering the long running report in the report manager is just for test purpose. I will create a subscription to deliver the report to a shared folder using SOAP API. Even for the subscription, the timeout issue still exists. Could you provide me some examples to set session timeout via SOAP API or a re.exe.
Thank you very much.
|||Any news? I have the same issue. Can you explain please which values should be used for these parameters in order to get the report running for more than 1 hour?|||There is a blog about it herehttp://blogs.msdn.com/jgalla/archive/2006/10/11/session-timeout-during-execution.aspx
So i did change this for a report that needs 20 minutes but it still fail after 5 minutes with this error in the computer application log
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 10/31/2006 10:08:46 AM
Event time (UTC): 10/31/2006 5:08:46 PM
Event ID: c6233c9a2cff498a90cfa4140a3e932a
Event sequence: 1572
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-128067603886462532
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\
Machine name: ATLANTA
Process information:
Process ID: 6452
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: ReportServerException
Exception message: Execution 'fmnjra45tvj15545rxlxt5ec' cannot be found (rsExecutionNotFound)
Request information:
Request URL: http://reporting.onsemi.com/Reports/Reserved.ReportViewerWebControl.axd?ReportSession=fmnjra45tvj15545rxlxt5ec&ControlID=84b2a2bd-4f03-4c5d-9d73-c305e7883b6e&Culture=1033&UICulture=9&ReportStack=1&OpType=SessionKeepAlive&TimerMethod=KeepAliveMethodctl161TouchSession0&CacheSeed=Tue Oct 31 10:08:44 2006
Request path: /Reports/Reserved.ReportViewerWebControl.axd
User host address: 10.253.138.208
User: ONSEMI\R38851
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Thread information:
Thread ID: 14
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: True
Stack trace: at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo()
at Microsoft.Reporting.WebForms.ServerReport.SetExecutionId(String executionId, Boolean fullReportLoad)
at Microsoft.Reporting.WebForms.ServerReport.LoadFromUrlQuery(NameValueCollection requestParameters, Boolean fullReportLoad)
at Microsoft.Reporting.WebForms.ReportDataOperation..ctor()
at Microsoft.Reporting.WebForms.HttpHandler.GetHandler()
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Any idea?
Thanks,
Philippesql
Long report on one page?
I have a very long report that I would like to appear all on one page. I want to be able to scroll from the top to the bottom without having to use the little page selector. How do I do this?
I got it to work for one report so I know it's possible. I just can't figure out why it works for that report and not for other reports.
Thanks,
Greg Van Mullem
Has anyone even tried this?|||
Hi,
Can you try with giving the report size - height as long as you expect the report to be? That will show the report in one page. However, if you try to print that report, it will compact the content and print all the content in one page (depends on what paper size you use)
Regards.
|||Interesting idea. I will give it a try. However, I still think there is an easire/better way. I have a long report where I did nothing special but it appears all on one page. Unfortunately I don't know what I did...Thanks,
Greg
|||I assume you are using HTML or report preview. You can set the InteractiveHeight property on the Report to 0 in order to have everything on one page. You could also get this if you have toggleable or conditionally hidden items in the report.sql
Long report on one page?
I have a very long
report that I would like to appear all on one page. I want to be able to
scroll from the top to the bottom without having to use the little page
selector. How do I do this?
I got it to work for
one report so I know it's possible. I just can't figure out why it works for
that report and not for other reports.
Thanks,
Greg Van
Mullem
Has anyone even tried this?|||Hi,
Can you try with giving the report size - height as long as you expect the report to be? That will show the report in one page. However, if you try to print that report, it will compact the content and print all the content in one page (depends on what paper size you use)
Regards.
|||Interesting idea. I will give it a try. However, I still think there is an easire/better way. I have a long report where I did nothing special but it appears all on one page. Unfortunately I don't know what I did...Thanks,
Greg|||I assume you are using HTML or report preview. You can set the InteractiveHeight property on the Report to 0 in order to have everything on one page. You could also get this if you have toggleable or conditionally hidden items in the report.
Monday, March 26, 2012
Long Queries Hang VS; Other Productivity Killers
Whenever I run long SQL in VS whether it's in the Data tab or in Preview
mode, I can't seem to get a report out of it. I'm talking SQL in excess of
200 lines.
I can run the SQL fine in Query Analyzer but running it in the Data tab, it
freezes VS, and when I run the Preview, the report never renders. I have even
tried hardcoding all parameters, creating a stored procedure, and running the
report off a view. None have resolved the issue.
On a possibly related note, my connection to the database times out
intermittently, saying:
--
Microsoft Development Environment
--
An error occurred while executing the query.
General network error. Check your network documentation.
--
OK
--
This absolutely kills me over the course of a day. I have to shut down VS
and restart it.
Is my Reporting Services VS package install corrupt? What do I do?How many fields are being returned? How many rows of data?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> Whenever I run long SQL in VS whether it's in the Data tab or in Preview
> mode, I can't seem to get a report out of it. I'm talking SQL in excess of
> 200 lines.
> I can run the SQL fine in Query Analyzer but running it in the Data tab,
it
> freezes VS, and when I run the Preview, the report never renders. I have
even
> tried hardcoding all parameters, creating a stored procedure, and running
the
> report off a view. None have resolved the issue.
> On a possibly related note, my connection to the database times out
> intermittently, saying:
> --
> Microsoft Development Environment
> --
> An error occurred while executing the query.
> General network error. Check your network documentation.
> --
> OK
> --
> This absolutely kills me over the course of a day. I have to shut down VS
> and restart it.
> Is my Reporting Services VS package install corrupt? What do I do?|||For one report in particular, about 727 rows, and today it's taking just over
4 minutes to run. The other has over 60,000 rows and I'm just going to have
to work on limiting that severely.
"Bruce L-C [MVP]" wrote:
> How many fields are being returned? How many rows of data?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > Whenever I run long SQL in VS whether it's in the Data tab or in Preview
> > mode, I can't seem to get a report out of it. I'm talking SQL in excess of
> > 200 lines.
> >
> > I can run the SQL fine in Query Analyzer but running it in the Data tab,
> it
> > freezes VS, and when I run the Preview, the report never renders. I have
> even
> > tried hardcoding all parameters, creating a stored procedure, and running
> the
> > report off a view. None have resolved the issue.
> >
> > On a possibly related note, my connection to the database times out
> > intermittently, saying:
> >
> > --
> > Microsoft Development Environment
> > --
> > An error occurred while executing the query.
> >
> > General network error. Check your network documentation.
> > --
> > OK
> > --
> >
> > This absolutely kills me over the course of a day. I have to shut down VS
> > and restart it.
> >
> > Is my Reporting Services VS package install corrupt? What do I do?
>
>|||The 727 rows should not be a problem. Is that one causing an issue from the
data tab?
It doesn't surprise me that the 60,000 row one has problems.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> For one report in particular, about 727 rows, and today it's taking just
over
> 4 minutes to run. The other has over 60,000 rows and I'm just going to
have
> to work on limiting that severely.
> "Bruce L-C [MVP]" wrote:
> > How many fields are being returned? How many rows of data?
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > Whenever I run long SQL in VS whether it's in the Data tab or in
Preview
> > > mode, I can't seem to get a report out of it. I'm talking SQL in
excess of
> > > 200 lines.
> > >
> > > I can run the SQL fine in Query Analyzer but running it in the Data
tab,
> > it
> > > freezes VS, and when I run the Preview, the report never renders. I
have
> > even
> > > tried hardcoding all parameters, creating a stored procedure, and
running
> > the
> > > report off a view. None have resolved the issue.
> > >
> > > On a possibly related note, my connection to the database times out
> > > intermittently, saying:
> > >
> > > --
> > > Microsoft Development Environment
> > > --
> > > An error occurred while executing the query.
> > >
> > > General network error. Check your network documentation.
> > > --
> > > OK
> > > --
> > >
> > > This absolutely kills me over the course of a day. I have to shut down
VS
> > > and restart it.
> > >
> > > Is my Reporting Services VS package install corrupt? What do I do?
> >
> >
> >|||For the most part, Mr. 727 will run on the data tab, but clocks endlessly on
Preview. The report does consist of about 20 fields, but I would still expect
it to render.
Sometimes I just lose connectivity and have to close out VS. I'm not sure if
it's related, but it could be I suppose.
Any ideas?
"Bruce L-C [MVP]" wrote:
> The 727 rows should not be a problem. Is that one causing an issue from the
> data tab?
> It doesn't surprise me that the 60,000 row one has problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > For one report in particular, about 727 rows, and today it's taking just
> over
> > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> have
> > to work on limiting that severely.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > How many fields are being returned? How many rows of data?
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> Preview
> > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> excess of
> > > > 200 lines.
> > > >
> > > > I can run the SQL fine in Query Analyzer but running it in the Data
> tab,
> > > it
> > > > freezes VS, and when I run the Preview, the report never renders. I
> have
> > > even
> > > > tried hardcoding all parameters, creating a stored procedure, and
> running
> > > the
> > > > report off a view. None have resolved the issue.
> > > >
> > > > On a possibly related note, my connection to the database times out
> > > > intermittently, saying:
> > > >
> > > > --
> > > > Microsoft Development Environment
> > > > --
> > > > An error occurred while executing the query.
> > > >
> > > > General network error. Check your network documentation.
> > > > --
> > > > OK
> > > > --
> > > >
> > > > This absolutely kills me over the course of a day. I have to shut down
> VS
> > > > and restart it.
> > > >
> > > > Is my Reporting Services VS package install corrupt? What do I do?
> > >
> > >
> > >
>
>|||Sometimes it runs from the data tab. Sometimes (like now), it hoses VS. The
query is 309 lines long and is pretty complex...Still, I'm having a heck of a
time. Could it be my RS client install, or could it be my machine?
"Bruce L-C [MVP]" wrote:
> The 727 rows should not be a problem. Is that one causing an issue from the
> data tab?
> It doesn't surprise me that the 60,000 row one has problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > For one report in particular, about 727 rows, and today it's taking just
> over
> > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> have
> > to work on limiting that severely.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > How many fields are being returned? How many rows of data?
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> Preview
> > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> excess of
> > > > 200 lines.
> > > >
> > > > I can run the SQL fine in Query Analyzer but running it in the Data
> tab,
> > > it
> > > > freezes VS, and when I run the Preview, the report never renders. I
> have
> > > even
> > > > tried hardcoding all parameters, creating a stored procedure, and
> running
> > > the
> > > > report off a view. None have resolved the issue.
> > > >
> > > > On a possibly related note, my connection to the database times out
> > > > intermittently, saying:
> > > >
> > > > --
> > > > Microsoft Development Environment
> > > > --
> > > > An error occurred while executing the query.
> > > >
> > > > General network error. Check your network documentation.
> > > > --
> > > > OK
> > > > --
> > > >
> > > > This absolutely kills me over the course of a day. I have to shut down
> VS
> > > > and restart it.
> > > >
> > > > Is my Reporting Services VS package install corrupt? What do I do?
> > >
> > >
> > >
>
>|||Did you say you tried it as a stored procedure and you still had problems.
20 fields should not be a problem. 309 lines of a query could be a problem
in the IDE (not necessarily when deployed). I suggest try deploying it and
see if it works to determine if it is an IDE only problem. Next, try having
it in a stored procedure.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
The
> query is 309 lines long and is pretty complex...Still, I'm having a heck
of a
> time. Could it be my RS client install, or could it be my machine?
> "Bruce L-C [MVP]" wrote:
> > The 727 rows should not be a problem. Is that one causing an issue from
the
> > data tab?
> >
> > It doesn't surprise me that the 60,000 row one has problems.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > For one report in particular, about 727 rows, and today it's taking
just
> > over
> > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > have
> > > to work on limiting that severely.
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > How many fields are being returned? How many rows of data?
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > Preview
> > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > excess of
> > > > > 200 lines.
> > > > >
> > > > > I can run the SQL fine in Query Analyzer but running it in the
Data
> > tab,
> > > > it
> > > > > freezes VS, and when I run the Preview, the report never renders.
I
> > have
> > > > even
> > > > > tried hardcoding all parameters, creating a stored procedure, and
> > running
> > > > the
> > > > > report off a view. None have resolved the issue.
> > > > >
> > > > > On a possibly related note, my connection to the database times
out
> > > > > intermittently, saying:
> > > > >
> > > > > --
> > > > > Microsoft Development Environment
> > > > > --
> > > > > An error occurred while executing the query.
> > > > >
> > > > > General network error. Check your network documentation.
> > > > > --
> > > > > OK
> > > > > --
> > > > >
> > > > > This absolutely kills me over the course of a day. I have to shut
down
> > VS
> > > > > and restart it.
> > > > >
> > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > >
> > > >
> > > >
> >
> >
> >|||Yes, I did give it a shot as a stored procedure, with no luck.
Well, tomorrow's another day. I'll try deploying it and seeing what happens.
Thanks for the help.
Mike
"Bruce L-C [MVP]" wrote:
> Did you say you tried it as a stored procedure and you still had problems.
> 20 fields should not be a problem. 309 lines of a query could be a problem
> in the IDE (not necessarily when deployed). I suggest try deploying it and
> see if it works to determine if it is an IDE only problem. Next, try having
> it in a stored procedure.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> The
> > query is 309 lines long and is pretty complex...Still, I'm having a heck
> of a
> > time. Could it be my RS client install, or could it be my machine?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > The 727 rows should not be a problem. Is that one causing an issue from
> the
> > > data tab?
> > >
> > > It doesn't surprise me that the 60,000 row one has problems.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > For one report in particular, about 727 rows, and today it's taking
> just
> > > over
> > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > have
> > > > to work on limiting that severely.
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > How many fields are being returned? How many rows of data?
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > Preview
> > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > excess of
> > > > > > 200 lines.
> > > > > >
> > > > > > I can run the SQL fine in Query Analyzer but running it in the
> Data
> > > tab,
> > > > > it
> > > > > > freezes VS, and when I run the Preview, the report never renders.
> I
> > > have
> > > > > even
> > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > running
> > > > > the
> > > > > > report off a view. None have resolved the issue.
> > > > > >
> > > > > > On a possibly related note, my connection to the database times
> out
> > > > > > intermittently, saying:
> > > > > >
> > > > > > --
> > > > > > Microsoft Development Environment
> > > > > > --
> > > > > > An error occurred while executing the query.
> > > > > >
> > > > > > General network error. Check your network documentation.
> > > > > > --
> > > > > > OK
> > > > > > --
> > > > > >
> > > > > > This absolutely kills me over the course of a day. I have to shut
> down
> > > VS
> > > > > > and restart it.
> > > > > >
> > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Have you tried changing the connection string of the data source to increase
the time out?
try
"data source=ServerName;initial catalog=DatabaseName;Connection Timeout=30"
The connection timeout has a default of 15.
"Bassist695" wrote:
> Yes, I did give it a shot as a stored procedure, with no luck.
> Well, tomorrow's another day. I'll try deploying it and seeing what happens.
> Thanks for the help.
> Mike
> "Bruce L-C [MVP]" wrote:
> > Did you say you tried it as a stored procedure and you still had problems.
> > 20 fields should not be a problem. 309 lines of a query could be a problem
> > in the IDE (not necessarily when deployed). I suggest try deploying it and
> > see if it works to determine if it is an IDE only problem. Next, try having
> > it in a stored procedure.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> > The
> > > query is 309 lines long and is pretty complex...Still, I'm having a heck
> > of a
> > > time. Could it be my RS client install, or could it be my machine?
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > The 727 rows should not be a problem. Is that one causing an issue from
> > the
> > > > data tab?
> > > >
> > > > It doesn't surprise me that the 60,000 row one has problems.
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > > For one report in particular, about 727 rows, and today it's taking
> > just
> > > > over
> > > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > > have
> > > > > to work on limiting that severely.
> > > > >
> > > > > "Bruce L-C [MVP]" wrote:
> > > > >
> > > > > > How many fields are being returned? How many rows of data?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Bruce Loehle-Conger
> > > > > > MVP SQL Server Reporting Services
> > > > > >
> > > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > > Preview
> > > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > > excess of
> > > > > > > 200 lines.
> > > > > > >
> > > > > > > I can run the SQL fine in Query Analyzer but running it in the
> > Data
> > > > tab,
> > > > > > it
> > > > > > > freezes VS, and when I run the Preview, the report never renders.
> > I
> > > > have
> > > > > > even
> > > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > > running
> > > > > > the
> > > > > > > report off a view. None have resolved the issue.
> > > > > > >
> > > > > > > On a possibly related note, my connection to the database times
> > out
> > > > > > > intermittently, saying:
> > > > > > >
> > > > > > > --
> > > > > > > Microsoft Development Environment
> > > > > > > --
> > > > > > > An error occurred while executing the query.
> > > > > > >
> > > > > > > General network error. Check your network documentation.
> > > > > > > --
> > > > > > > OK
> > > > > > > --
> > > > > > >
> > > > > > > This absolutely kills me over the course of a day. I have to shut
> > down
> > > > VS
> > > > > > > and restart it.
> > > > > > >
> > > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||No, I haven't tried that. I don't believe the queries are timing out.
Wouldn't I get an error message to indicate that?
At present, there is no timeout set, which I believe means that the query
will not time out.
I'm going to try the deploy-and-see method...Let's hope it's my IDE.
Mike
"Carl Finnegan" wrote:
> Have you tried changing the connection string of the data source to increase
> the time out?
> try
> "data source=ServerName;initial catalog=DatabaseName;Connection Timeout=30"
> The connection timeout has a default of 15.
> "Bassist695" wrote:
> > Yes, I did give it a shot as a stored procedure, with no luck.
> >
> > Well, tomorrow's another day. I'll try deploying it and seeing what happens.
> > Thanks for the help.
> >
> > Mike
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > Did you say you tried it as a stored procedure and you still had problems.
> > > 20 fields should not be a problem. 309 lines of a query could be a problem
> > > in the IDE (not necessarily when deployed). I suggest try deploying it and
> > > see if it works to determine if it is an IDE only problem. Next, try having
> > > it in a stored procedure.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > > > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> > > The
> > > > query is 309 lines long and is pretty complex...Still, I'm having a heck
> > > of a
> > > > time. Could it be my RS client install, or could it be my machine?
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > The 727 rows should not be a problem. Is that one causing an issue from
> > > the
> > > > > data tab?
> > > > >
> > > > > It doesn't surprise me that the 60,000 row one has problems.
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > > > For one report in particular, about 727 rows, and today it's taking
> > > just
> > > > > over
> > > > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > > > have
> > > > > > to work on limiting that severely.
> > > > > >
> > > > > > "Bruce L-C [MVP]" wrote:
> > > > > >
> > > > > > > How many fields are being returned? How many rows of data?
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Bruce Loehle-Conger
> > > > > > > MVP SQL Server Reporting Services
> > > > > > >
> > > > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > > > Preview
> > > > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > > > excess of
> > > > > > > > 200 lines.
> > > > > > > >
> > > > > > > > I can run the SQL fine in Query Analyzer but running it in the
> > > Data
> > > > > tab,
> > > > > > > it
> > > > > > > > freezes VS, and when I run the Preview, the report never renders.
> > > I
> > > > > have
> > > > > > > even
> > > > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > > > running
> > > > > > > the
> > > > > > > > report off a view. None have resolved the issue.
> > > > > > > >
> > > > > > > > On a possibly related note, my connection to the database times
> > > out
> > > > > > > > intermittently, saying:
> > > > > > > >
> > > > > > > > --
> > > > > > > > Microsoft Development Environment
> > > > > > > > --
> > > > > > > > An error occurred while executing the query.
> > > > > > > >
> > > > > > > > General network error. Check your network documentation.
> > > > > > > > --
> > > > > > > > OK
> > > > > > > > --
> > > > > > > >
> > > > > > > > This absolutely kills me over the course of a day. I have to shut
> > > down
> > > > > VS
> > > > > > > > and restart it.
> > > > > > > >
> > > > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
mode, I can't seem to get a report out of it. I'm talking SQL in excess of
200 lines.
I can run the SQL fine in Query Analyzer but running it in the Data tab, it
freezes VS, and when I run the Preview, the report never renders. I have even
tried hardcoding all parameters, creating a stored procedure, and running the
report off a view. None have resolved the issue.
On a possibly related note, my connection to the database times out
intermittently, saying:
--
Microsoft Development Environment
--
An error occurred while executing the query.
General network error. Check your network documentation.
--
OK
--
This absolutely kills me over the course of a day. I have to shut down VS
and restart it.
Is my Reporting Services VS package install corrupt? What do I do?How many fields are being returned? How many rows of data?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> Whenever I run long SQL in VS whether it's in the Data tab or in Preview
> mode, I can't seem to get a report out of it. I'm talking SQL in excess of
> 200 lines.
> I can run the SQL fine in Query Analyzer but running it in the Data tab,
it
> freezes VS, and when I run the Preview, the report never renders. I have
even
> tried hardcoding all parameters, creating a stored procedure, and running
the
> report off a view. None have resolved the issue.
> On a possibly related note, my connection to the database times out
> intermittently, saying:
> --
> Microsoft Development Environment
> --
> An error occurred while executing the query.
> General network error. Check your network documentation.
> --
> OK
> --
> This absolutely kills me over the course of a day. I have to shut down VS
> and restart it.
> Is my Reporting Services VS package install corrupt? What do I do?|||For one report in particular, about 727 rows, and today it's taking just over
4 minutes to run. The other has over 60,000 rows and I'm just going to have
to work on limiting that severely.
"Bruce L-C [MVP]" wrote:
> How many fields are being returned? How many rows of data?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > Whenever I run long SQL in VS whether it's in the Data tab or in Preview
> > mode, I can't seem to get a report out of it. I'm talking SQL in excess of
> > 200 lines.
> >
> > I can run the SQL fine in Query Analyzer but running it in the Data tab,
> it
> > freezes VS, and when I run the Preview, the report never renders. I have
> even
> > tried hardcoding all parameters, creating a stored procedure, and running
> the
> > report off a view. None have resolved the issue.
> >
> > On a possibly related note, my connection to the database times out
> > intermittently, saying:
> >
> > --
> > Microsoft Development Environment
> > --
> > An error occurred while executing the query.
> >
> > General network error. Check your network documentation.
> > --
> > OK
> > --
> >
> > This absolutely kills me over the course of a day. I have to shut down VS
> > and restart it.
> >
> > Is my Reporting Services VS package install corrupt? What do I do?
>
>|||The 727 rows should not be a problem. Is that one causing an issue from the
data tab?
It doesn't surprise me that the 60,000 row one has problems.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> For one report in particular, about 727 rows, and today it's taking just
over
> 4 minutes to run. The other has over 60,000 rows and I'm just going to
have
> to work on limiting that severely.
> "Bruce L-C [MVP]" wrote:
> > How many fields are being returned? How many rows of data?
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > Whenever I run long SQL in VS whether it's in the Data tab or in
Preview
> > > mode, I can't seem to get a report out of it. I'm talking SQL in
excess of
> > > 200 lines.
> > >
> > > I can run the SQL fine in Query Analyzer but running it in the Data
tab,
> > it
> > > freezes VS, and when I run the Preview, the report never renders. I
have
> > even
> > > tried hardcoding all parameters, creating a stored procedure, and
running
> > the
> > > report off a view. None have resolved the issue.
> > >
> > > On a possibly related note, my connection to the database times out
> > > intermittently, saying:
> > >
> > > --
> > > Microsoft Development Environment
> > > --
> > > An error occurred while executing the query.
> > >
> > > General network error. Check your network documentation.
> > > --
> > > OK
> > > --
> > >
> > > This absolutely kills me over the course of a day. I have to shut down
VS
> > > and restart it.
> > >
> > > Is my Reporting Services VS package install corrupt? What do I do?
> >
> >
> >|||For the most part, Mr. 727 will run on the data tab, but clocks endlessly on
Preview. The report does consist of about 20 fields, but I would still expect
it to render.
Sometimes I just lose connectivity and have to close out VS. I'm not sure if
it's related, but it could be I suppose.
Any ideas?
"Bruce L-C [MVP]" wrote:
> The 727 rows should not be a problem. Is that one causing an issue from the
> data tab?
> It doesn't surprise me that the 60,000 row one has problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > For one report in particular, about 727 rows, and today it's taking just
> over
> > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> have
> > to work on limiting that severely.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > How many fields are being returned? How many rows of data?
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> Preview
> > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> excess of
> > > > 200 lines.
> > > >
> > > > I can run the SQL fine in Query Analyzer but running it in the Data
> tab,
> > > it
> > > > freezes VS, and when I run the Preview, the report never renders. I
> have
> > > even
> > > > tried hardcoding all parameters, creating a stored procedure, and
> running
> > > the
> > > > report off a view. None have resolved the issue.
> > > >
> > > > On a possibly related note, my connection to the database times out
> > > > intermittently, saying:
> > > >
> > > > --
> > > > Microsoft Development Environment
> > > > --
> > > > An error occurred while executing the query.
> > > >
> > > > General network error. Check your network documentation.
> > > > --
> > > > OK
> > > > --
> > > >
> > > > This absolutely kills me over the course of a day. I have to shut down
> VS
> > > > and restart it.
> > > >
> > > > Is my Reporting Services VS package install corrupt? What do I do?
> > >
> > >
> > >
>
>|||Sometimes it runs from the data tab. Sometimes (like now), it hoses VS. The
query is 309 lines long and is pretty complex...Still, I'm having a heck of a
time. Could it be my RS client install, or could it be my machine?
"Bruce L-C [MVP]" wrote:
> The 727 rows should not be a problem. Is that one causing an issue from the
> data tab?
> It doesn't surprise me that the 60,000 row one has problems.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > For one report in particular, about 727 rows, and today it's taking just
> over
> > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> have
> > to work on limiting that severely.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > How many fields are being returned? How many rows of data?
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> Preview
> > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> excess of
> > > > 200 lines.
> > > >
> > > > I can run the SQL fine in Query Analyzer but running it in the Data
> tab,
> > > it
> > > > freezes VS, and when I run the Preview, the report never renders. I
> have
> > > even
> > > > tried hardcoding all parameters, creating a stored procedure, and
> running
> > > the
> > > > report off a view. None have resolved the issue.
> > > >
> > > > On a possibly related note, my connection to the database times out
> > > > intermittently, saying:
> > > >
> > > > --
> > > > Microsoft Development Environment
> > > > --
> > > > An error occurred while executing the query.
> > > >
> > > > General network error. Check your network documentation.
> > > > --
> > > > OK
> > > > --
> > > >
> > > > This absolutely kills me over the course of a day. I have to shut down
> VS
> > > > and restart it.
> > > >
> > > > Is my Reporting Services VS package install corrupt? What do I do?
> > >
> > >
> > >
>
>|||Did you say you tried it as a stored procedure and you still had problems.
20 fields should not be a problem. 309 lines of a query could be a problem
in the IDE (not necessarily when deployed). I suggest try deploying it and
see if it works to determine if it is an IDE only problem. Next, try having
it in a stored procedure.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
The
> query is 309 lines long and is pretty complex...Still, I'm having a heck
of a
> time. Could it be my RS client install, or could it be my machine?
> "Bruce L-C [MVP]" wrote:
> > The 727 rows should not be a problem. Is that one causing an issue from
the
> > data tab?
> >
> > It doesn't surprise me that the 60,000 row one has problems.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > For one report in particular, about 727 rows, and today it's taking
just
> > over
> > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > have
> > > to work on limiting that severely.
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > How many fields are being returned? How many rows of data?
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > Preview
> > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > excess of
> > > > > 200 lines.
> > > > >
> > > > > I can run the SQL fine in Query Analyzer but running it in the
Data
> > tab,
> > > > it
> > > > > freezes VS, and when I run the Preview, the report never renders.
I
> > have
> > > > even
> > > > > tried hardcoding all parameters, creating a stored procedure, and
> > running
> > > > the
> > > > > report off a view. None have resolved the issue.
> > > > >
> > > > > On a possibly related note, my connection to the database times
out
> > > > > intermittently, saying:
> > > > >
> > > > > --
> > > > > Microsoft Development Environment
> > > > > --
> > > > > An error occurred while executing the query.
> > > > >
> > > > > General network error. Check your network documentation.
> > > > > --
> > > > > OK
> > > > > --
> > > > >
> > > > > This absolutely kills me over the course of a day. I have to shut
down
> > VS
> > > > > and restart it.
> > > > >
> > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > >
> > > >
> > > >
> >
> >
> >|||Yes, I did give it a shot as a stored procedure, with no luck.
Well, tomorrow's another day. I'll try deploying it and seeing what happens.
Thanks for the help.
Mike
"Bruce L-C [MVP]" wrote:
> Did you say you tried it as a stored procedure and you still had problems.
> 20 fields should not be a problem. 309 lines of a query could be a problem
> in the IDE (not necessarily when deployed). I suggest try deploying it and
> see if it works to determine if it is an IDE only problem. Next, try having
> it in a stored procedure.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> The
> > query is 309 lines long and is pretty complex...Still, I'm having a heck
> of a
> > time. Could it be my RS client install, or could it be my machine?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > The 727 rows should not be a problem. Is that one causing an issue from
> the
> > > data tab?
> > >
> > > It doesn't surprise me that the 60,000 row one has problems.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > For one report in particular, about 727 rows, and today it's taking
> just
> > > over
> > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > have
> > > > to work on limiting that severely.
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > How many fields are being returned? How many rows of data?
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > Preview
> > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > excess of
> > > > > > 200 lines.
> > > > > >
> > > > > > I can run the SQL fine in Query Analyzer but running it in the
> Data
> > > tab,
> > > > > it
> > > > > > freezes VS, and when I run the Preview, the report never renders.
> I
> > > have
> > > > > even
> > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > running
> > > > > the
> > > > > > report off a view. None have resolved the issue.
> > > > > >
> > > > > > On a possibly related note, my connection to the database times
> out
> > > > > > intermittently, saying:
> > > > > >
> > > > > > --
> > > > > > Microsoft Development Environment
> > > > > > --
> > > > > > An error occurred while executing the query.
> > > > > >
> > > > > > General network error. Check your network documentation.
> > > > > > --
> > > > > > OK
> > > > > > --
> > > > > >
> > > > > > This absolutely kills me over the course of a day. I have to shut
> down
> > > VS
> > > > > > and restart it.
> > > > > >
> > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Have you tried changing the connection string of the data source to increase
the time out?
try
"data source=ServerName;initial catalog=DatabaseName;Connection Timeout=30"
The connection timeout has a default of 15.
"Bassist695" wrote:
> Yes, I did give it a shot as a stored procedure, with no luck.
> Well, tomorrow's another day. I'll try deploying it and seeing what happens.
> Thanks for the help.
> Mike
> "Bruce L-C [MVP]" wrote:
> > Did you say you tried it as a stored procedure and you still had problems.
> > 20 fields should not be a problem. 309 lines of a query could be a problem
> > in the IDE (not necessarily when deployed). I suggest try deploying it and
> > see if it works to determine if it is an IDE only problem. Next, try having
> > it in a stored procedure.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> > The
> > > query is 309 lines long and is pretty complex...Still, I'm having a heck
> > of a
> > > time. Could it be my RS client install, or could it be my machine?
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > The 727 rows should not be a problem. Is that one causing an issue from
> > the
> > > > data tab?
> > > >
> > > > It doesn't surprise me that the 60,000 row one has problems.
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > > For one report in particular, about 727 rows, and today it's taking
> > just
> > > > over
> > > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > > have
> > > > > to work on limiting that severely.
> > > > >
> > > > > "Bruce L-C [MVP]" wrote:
> > > > >
> > > > > > How many fields are being returned? How many rows of data?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Bruce Loehle-Conger
> > > > > > MVP SQL Server Reporting Services
> > > > > >
> > > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > > Preview
> > > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > > excess of
> > > > > > > 200 lines.
> > > > > > >
> > > > > > > I can run the SQL fine in Query Analyzer but running it in the
> > Data
> > > > tab,
> > > > > > it
> > > > > > > freezes VS, and when I run the Preview, the report never renders.
> > I
> > > > have
> > > > > > even
> > > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > > running
> > > > > > the
> > > > > > > report off a view. None have resolved the issue.
> > > > > > >
> > > > > > > On a possibly related note, my connection to the database times
> > out
> > > > > > > intermittently, saying:
> > > > > > >
> > > > > > > --
> > > > > > > Microsoft Development Environment
> > > > > > > --
> > > > > > > An error occurred while executing the query.
> > > > > > >
> > > > > > > General network error. Check your network documentation.
> > > > > > > --
> > > > > > > OK
> > > > > > > --
> > > > > > >
> > > > > > > This absolutely kills me over the course of a day. I have to shut
> > down
> > > > VS
> > > > > > > and restart it.
> > > > > > >
> > > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||No, I haven't tried that. I don't believe the queries are timing out.
Wouldn't I get an error message to indicate that?
At present, there is no timeout set, which I believe means that the query
will not time out.
I'm going to try the deploy-and-see method...Let's hope it's my IDE.
Mike
"Carl Finnegan" wrote:
> Have you tried changing the connection string of the data source to increase
> the time out?
> try
> "data source=ServerName;initial catalog=DatabaseName;Connection Timeout=30"
> The connection timeout has a default of 15.
> "Bassist695" wrote:
> > Yes, I did give it a shot as a stored procedure, with no luck.
> >
> > Well, tomorrow's another day. I'll try deploying it and seeing what happens.
> > Thanks for the help.
> >
> > Mike
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > Did you say you tried it as a stored procedure and you still had problems.
> > > 20 fields should not be a problem. 309 lines of a query could be a problem
> > > in the IDE (not necessarily when deployed). I suggest try deploying it and
> > > see if it works to determine if it is an IDE only problem. Next, try having
> > > it in a stored procedure.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > news:0C35989D-938D-4EE6-B1F3-746130C76E80@.microsoft.com...
> > > > Sometimes it runs from the data tab. Sometimes (like now), it hoses VS.
> > > The
> > > > query is 309 lines long and is pretty complex...Still, I'm having a heck
> > > of a
> > > > time. Could it be my RS client install, or could it be my machine?
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > The 727 rows should not be a problem. Is that one causing an issue from
> > > the
> > > > > data tab?
> > > > >
> > > > > It doesn't surprise me that the 60,000 row one has problems.
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > news:CED42435-B092-427F-A344-1A6F707C67B2@.microsoft.com...
> > > > > > For one report in particular, about 727 rows, and today it's taking
> > > just
> > > > > over
> > > > > > 4 minutes to run. The other has over 60,000 rows and I'm just going to
> > > > > have
> > > > > > to work on limiting that severely.
> > > > > >
> > > > > > "Bruce L-C [MVP]" wrote:
> > > > > >
> > > > > > > How many fields are being returned? How many rows of data?
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Bruce Loehle-Conger
> > > > > > > MVP SQL Server Reporting Services
> > > > > > >
> > > > > > > "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
> > > > > > > news:188CC9BC-F0D3-46A7-A4F7-896E279E5252@.microsoft.com...
> > > > > > > > Whenever I run long SQL in VS whether it's in the Data tab or in
> > > > > Preview
> > > > > > > > mode, I can't seem to get a report out of it. I'm talking SQL in
> > > > > excess of
> > > > > > > > 200 lines.
> > > > > > > >
> > > > > > > > I can run the SQL fine in Query Analyzer but running it in the
> > > Data
> > > > > tab,
> > > > > > > it
> > > > > > > > freezes VS, and when I run the Preview, the report never renders.
> > > I
> > > > > have
> > > > > > > even
> > > > > > > > tried hardcoding all parameters, creating a stored procedure, and
> > > > > running
> > > > > > > the
> > > > > > > > report off a view. None have resolved the issue.
> > > > > > > >
> > > > > > > > On a possibly related note, my connection to the database times
> > > out
> > > > > > > > intermittently, saying:
> > > > > > > >
> > > > > > > > --
> > > > > > > > Microsoft Development Environment
> > > > > > > > --
> > > > > > > > An error occurred while executing the query.
> > > > > > > >
> > > > > > > > General network error. Check your network documentation.
> > > > > > > > --
> > > > > > > > OK
> > > > > > > > --
> > > > > > > >
> > > > > > > > This absolutely kills me over the course of a day. I have to shut
> > > down
> > > > > VS
> > > > > > > > and restart it.
> > > > > > > >
> > > > > > > > Is my Reporting Services VS package install corrupt? What do I do?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
Subscribe to:
Posts (Atom)