"The given key was not present in the dictionary"

I have a report that will not run in "preview" mode in VS 2005. Whereas the
deployed report runs correctly and shows results in about 15 seconds, the
same report (downloaded from the report server) tries to run in preview for
about 60 seconds and then displays "The given key was not present in the
dictionary".
Each of the 4 datasets (3 used for runtime parameter selections and one for
the report's data) run fine.
I've tried some of the other reports developed in SSRS and don't seem to
have this problem elsewhere. (I've not tried all my reports yet though.)
I've recently downloaded and installed .NET 3.0 and the variouls
add-ons/extensions for WCF, WPF and WWF and wonder if this is the root of the
problem.
I've seen some postings related to AJAX and this message but have not yet
downloaded AJAX.
Thanks for any help.
JonThis report had a relatively simple pic chart at the very bottom that
displayed summary data from the prime dataset. The error goes away if I
delete the chart.
(This is the only report I have that includes a chart.)
So, having isolated the problem a little, anyone have an idea what was
happening? This report has been in place for almost 2 years now.
Jon|||why hasn't this been answered. I have the same problem with a chart
From http://www.developmentnow.com/g/115_2007_3_0_0_950996/The-given-key-was-not-present-in-the-dictionary.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com|||On Aug 20, 11:26 am, Jonathon<nos...@.developmentnow.com> wrote:
> why hasn't this been answered. I have the same problem with a chart.
> Fromhttp://www.developmentnow.com/g/115_2007_3_0_0_950996/The-given-key-w...
> Posted via DevelopmentNow.com Groupshttp://www.developmentnow.com
This link might be helpful.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=528044&SiteID=1
Regards,
Enrique Martinez
Sr. Software Consultant|||Has anyone found anything other than deleting the rdl.data? I copied a report.rdl and pulled it into the same solution so I could try working some objects slightly differently. But now when I try to run the modified report I am getting this message. It seems to be related to the document map and bookmarks, but I can't see anything wrong with them. I've refreshed all the fields on the datasets, I've deleted the rdl.data, but still getting the same error ...
From http://www.developmentnow.com/g/115_2007_3_0_0_950996/The-given-key-was-not-present-in-the-dictionary.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

"Live" queries in sql 2005 ?

A colleague was telling me the other day that in Sql Server 2005 there is a
special type of query you can do, whereby it runs in the background and
brings back results automatically, whenever they change. He referred to it
as something called a "live" query, but I'm not sure that's correct
terminology.
In theory you could run such a query, and sit back and watch the results
change in Query Analyser (or wherever). For example if you were monitoring
total sales, you could literally run the query and it would "auto update" in
front of your eyes, as sales increased.
Then you could theoretically write a client application with, say, a grid
which was bound to the "live query" and updated itself magically.
One could write a client app which polled the database every 2 seconds or
whatever, but that's not as efficient as picking up data *only* when it
changes.
Obviously it depends on the client limitations, but has anyone heard of such
a thing in SQL 2005?
Thanks,
Owen"Owen" <spam@.spam.com> wrote in message
news:lZOdnfeFS9oemgbZnZ2dnUVZ8smdnZ2d@.pi
pex.net...
>A colleague was telling me the other day that in Sql Server 2005 there is a
>special type of query you can do, whereby it runs in the background and
>brings back results automatically, whenever they change. He referred to it
>as something called a "live" query, but I'm not sure that's correct
>terminology.
>
Query Notification.
Query Notifications in ADO.NET 2.0
http://msdn.microsoft.com/library/d...otification.asp
David|||"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:uaX3ADllGHA.3740@.TK2MSFTNGP02.phx.gbl...
> "Owen" <spam@.spam.com> wrote in message
> news:lZOdnfeFS9oemgbZnZ2dnUVZ8smdnZ2d@.pi
pex.net...
> Query Notification.
> Query Notifications in ADO.NET 2.0
> http://msdn.microsoft.com/library/d...otification.asp
> David
Sounds about right, thanks very much indeed. !
Owen.
http://www.riptheuglybluevoidfromyourhead.com

"Drop Table" at Stored Procedure

Hello folks,
i like to change a sql-skript to a procedure. The skript includes 20
statements like
select ... into #temp
and
drop table #temp
It runs as a batch if i use
drop table #temp
go
In order to change it to a procedure i change all "drops" to
drop table #temp;
but i can't create the procedure.
The SQL-Server error message was
'Es gibt bereits ein Objekt #Temp'
(translated 'Object #temp still exists')
This Message was shown five times and point to the Select-Staments (not to
all).
To move the drop - Statement direct before the select does'nt help to solve
this behaivor;
I have no idea to solve this problem.
Thanks in advance for any help.
NielsCREATE PROC mysp
AS
IF OBJECT_ID('TempTable') IS NOT NULL
DROP TABLE TempTable
"nieurig" <nieurig@.discussions.microsoft.com> wrote in message
news:045E2CDA-E8BF-4F55-8668-EC1B47139314@.microsoft.com...
> Hello folks,
> i like to change a sql-skript to a procedure. The skript includes 20
> statements like
> select ... into #temp
> and
> drop table #temp
> It runs as a batch if i use
> drop table #temp
> go
> In order to change it to a procedure i change all "drops" to
> drop table #temp;
> but i can't create the procedure.
> The SQL-Server error message was
> 'Es gibt bereits ein Objekt #Temp'
> (translated 'Object #temp still exists')
> This Message was shown five times and point to the Select-Staments (not to
> all).
> To move the drop - Statement direct before the select does'nt help to
solve
> this behaivor;
> I have no idea to solve this problem.
> Thanks in advance for any help.
> Niels
>|||It's a resolution issue. Consider naming the temporary table differently in
each create. The other option is to use dynamic execution, but such approach
involves many issues of its own.
BG, SQL Server MVP
www.SolidQualityLearning.com
"nieurig" <nieurig@.discussions.microsoft.com> wrote in message
news:045E2CDA-E8BF-4F55-8668-EC1B47139314@.microsoft.com...
> Hello folks,
> i like to change a sql-skript to a procedure. The skript includes 20
> statements like
> select ... into #temp
> and
> drop table #temp
> It runs as a batch if i use
> drop table #temp
> go
> In order to change it to a procedure i change all "drops" to
> drop table #temp;
> but i can't create the procedure.
> The SQL-Server error message was
> 'Es gibt bereits ein Objekt #Temp'
> (translated 'Object #temp still exists')
> This Message was shown five times and point to the Select-Staments (not to
> all).
> To move the drop - Statement direct before the select does'nt help to
> solve
> this behaivor;
> I have no idea to solve this problem.
> Thanks in advance for any help.
> Niels
>|||Thanks to Itzik and Uri !!
I will use the workaround with different names of my temp-table.
Have a nice day.
Niels