Re: Error using ReportViewer control and SQL Session State
- From: "Andrew Teece" <enate@xxxxxxxxxxxxx>
- Date: Mon, 30 Apr 2007 15:17:08 +0100
Sorry for any confusion here, but it is on the same database server, but it is not in the same database.
Regards
Andrew
"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message news:0NyZNNwiHHA.5688@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Andrew,
Thanks for your reply and the further info.
So normal sessionstate accessing work well. In your previous message, you
mentioned that the SQL Server session database is on the same server
instance with your report or any other application data's database,
correct? I think this is possibly the potential cause. Have you tried
separate the database to see if it would help some?
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- Error using ReportViewer control and SQL Session State
- From: Andrew Teece
- RE: Error using ReportViewer control and SQL Session State
- From: Steven Cheng[MSFT]
- Re: Error using ReportViewer control and SQL Session State
- From: Andrew Teece
- Re: Error using ReportViewer control and SQL Session State
- From: Andrew Teece
- Re: Error using ReportViewer control and SQL Session State
- From: Steven Cheng[MSFT]
- Error using ReportViewer control and SQL Session State
- Prev by Date: Re: ASP.NET Search Engine
- Next by Date: Using forms authentication, but you can get at a file if you know the name of it.
- Previous by thread: Re: Error using ReportViewer control and SQL Session State
- Next by thread: Error using ReportViewer control and SQL Session State
- Index(es):
Relevant Pages
|