February 9, 2007 at 3:44 pm
I haven't used reporting services on my xp laptop for some time. The report manager opens but when I try to run a report I get the following error message. I've never seen it before and I can't find any information about this. Anybody seen this before?
@AwaitingFirstExecution is not a parameter for procedure CreateSession
Thanks
February 12, 2007 at 8:00 am
This was removed by the editor as SPAM
April 5, 2007 at 11:24 am
I just encountered this today when moving a database from my production environment to my development environment. This is caused by what appears to be a difference in the 2005 RTM and 2005 SP2 Reporting Services database stored procedures and the page calls to them. If you install the RTM and do not add any Service Pack, you will have a procedure in your ReportServer Database that is defined as:
ALTER PROCEDURE [dbo].[CreateSession]
@SessionID as varchar(32),
@CompiledDefinition as uniqueidentifier = NULL,
@SnapshotDataID as uniqueidentifier = NULL,
@IsPermanentSnapshot as bit = NULL,
@ReportPath as nvarchar(440) = NULL,
@Timeout as int,
@AutoRefreshSeconds as int = NULL,
@DataSourceInfo as image = NULL,
@OwnerName as nvarchar (260),
@OwnerSid as varbinary (85) = NULL,
@AuthType as int,
@EffectiveParams as ntext = NULL,
@HistoryDate as datetime = NULL,
@PageHeight as float = NULL,
@PageWidth as float = NULL,
@TopMargin as float = NULL,
@BottomMargin as float = NULL,
@LeftMargin as float = NULL,
@RightMargin as float = NULL
Under SP2, you get:
ALTER PROCEDURE [dbo].[CreateSession]
@SessionID as varchar(32),
@CompiledDefinition as uniqueidentifier = NULL,
@SnapshotDataID as uniqueidentifier = NULL,
@IsPermanentSnapshot as bit = NULL,
@ReportPath as nvarchar(440) = NULL,
@Timeout as int,
@AutoRefreshSeconds as int = NULL,
@DataSourceInfo as image = NULL,
@OwnerName as nvarchar (260),
@OwnerSid as varbinary (85) = NULL,
@AuthType as int,
@EffectiveParams as ntext = NULL,
@HistoryDate as datetime = NULL,
@PageHeight as float = NULL,
@PageWidth as float = NULL,
@TopMargin as float = NULL,
@BottomMargin as float = NULL,
@LeftMargin as float = NULL,
@RightMargin as float = NULL,
@AwaitingFirstExecution as bit = NULL
It would appear to me that you have applied SP2, but the DB is still sitting in a RTM state. I don't know if this helps you solve this problem, as I have yet to do anything that has proven a solution. I can't upgrade my Production environment to SP2 until I resolve a problem with a vendor refusing to support an app if the DB is in SP2. I am working now on starting over with my dev server from RTM, and then applying SP2 to it to see if it resolves the problem. I will repost when I know for sure.
Jon
Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]
September 23, 2008 at 5:24 am
SQL Server 2005 Books Online (September 2007)
rsInternalError
New: 17 July 2006
Details
Product Name
SQL Server
Product Version
9.0
Product Build Number
9.00.1399
Event ID
rsInternalError
Event Source
Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings
Component
Reporting Services
Message Text
An internal error occurred on the report server. See the error log for more details.
Explanation
This is a generic error message that is often followed by a more descriptive error that provides more detail.
Internal errors are uncommon and difficult to diagnose. If you get this error, you can look in report server trace logs for more information. In addition, if you are running as local administrator on the same computer on which the error occurs, you can view the call stack for more information.
User Action
To determine the specific reason that caused this message to appear, review the report server log files, which are located at \Microsoft SQL Server\ \Reporting Services\LogFiles.
To view the call stack, right-click the page on which the error occurs and point to View Source.
If there is no additional information to work with, you can try refreshing the report or reset IIS.
September 26, 2008 at 4:03 am
I experienced same problem and manage to fix it by adding the field AwaitingFirstExecution with bit datatype in table SessionData in ReportServerTempDB database
Hope it helps...
April 10, 2009 at 8:55 pm
That works!!! Thanks Jim
June 30, 2009 at 10:14 am
jim_raynor24 (9/26/2008)
I experienced same problem and manage to fix it by adding the field AwaitingFirstExecution with bit datatype in table SessionData in ReportServerTempDB databaseHope it helps...
THANKS JIM!!! This worked for me as well.
June 30, 2009 at 8:06 pm
I'm glad that my 1 year old post was able to help. Happy coding to all 😉
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply