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
Showing posts with label key. Show all posts
Showing posts with label key. Show all posts
Friday, March 16, 2012
Friday, February 24, 2012
"key not valid for use in the specified state"
I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
valid for use in the specified state" on any page of the Report Manager that
I try to access.
I've tried deleting and recreating the keys with no success. The search that
I've done in the MS Site have all pointed me to EFS errors. Anybody have any
ideas where I should go next?
Thanks.
DerrickI had that problem 6 months ago. After opening a support call with MS
and after many attempts to fix it, in the end the only process that
worked was to completely erase all traces of RS from the system and then
do a fresh install. Below is a list of the steps to take (note
especially step 5 - this was the deciding factor for me on the reinstall
fixing the problem)
1. Backup your existing solution files, such as .sln, .rdl, .rds files.
2. If the machine is a domain controller, do not install Reporting
Service on it. Use another machine instead.
3. Run Setup.exe of the SQL Server 2000 Reporting Services to launch the
Setup window.
4. Click "Remove Microsoft SQL Server 2000 Reporting Service" button in
the Setup window.
5. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20 and delete all
files located in this folder.
6. Delete all Reporting services related files under this folder
"x:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services" if present
7. Delete all Reporting Services Virtual Directories (ReportServer and
Reports) from IIS Manager if present.
8. Delete all Reporting Services Databases (ReportServer and
ReportServerTempDB) from SQL Server Enterprise Manager if present.
9. Re-boot the machine and log on using an Administrators group account.
10. Reinstall SQL Server 2000 Reporting Service on the machine.
brian smith
Derrick Powell wrote:
> I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
> valid for use in the specified state" on any page of the Report Manager that
> I try to access.
> I've tried deleting and recreating the keys with no success. The search that
> I've done in the MS Site have all pointed me to EFS errors. Anybody have any
> ideas where I should go next?
> Thanks.
> Derrick
>
valid for use in the specified state" on any page of the Report Manager that
I try to access.
I've tried deleting and recreating the keys with no success. The search that
I've done in the MS Site have all pointed me to EFS errors. Anybody have any
ideas where I should go next?
Thanks.
DerrickI had that problem 6 months ago. After opening a support call with MS
and after many attempts to fix it, in the end the only process that
worked was to completely erase all traces of RS from the system and then
do a fresh install. Below is a list of the steps to take (note
especially step 5 - this was the deciding factor for me on the reinstall
fixing the problem)
1. Backup your existing solution files, such as .sln, .rdl, .rds files.
2. If the machine is a domain controller, do not install Reporting
Service on it. Use another machine instead.
3. Run Setup.exe of the SQL Server 2000 Reporting Services to launch the
Setup window.
4. Click "Remove Microsoft SQL Server 2000 Reporting Service" button in
the Setup window.
5. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20 and delete all
files located in this folder.
6. Delete all Reporting services related files under this folder
"x:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services" if present
7. Delete all Reporting Services Virtual Directories (ReportServer and
Reports) from IIS Manager if present.
8. Delete all Reporting Services Databases (ReportServer and
ReportServerTempDB) from SQL Server Enterprise Manager if present.
9. Re-boot the machine and log on using an Administrators group account.
10. Reinstall SQL Server 2000 Reporting Service on the machine.
brian smith
Derrick Powell wrote:
> I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
> valid for use in the specified state" on any page of the Report Manager that
> I try to access.
> I've tried deleting and recreating the keys with no success. The search that
> I've done in the MS Site have all pointed me to EFS errors. Anybody have any
> ideas where I should go next?
> Thanks.
> Derrick
>
"Key Column Information...."
Hi everybody!
I have the following problem: I have many tables in my database and for
some columns it happens that when I try to update them, I get the error
message, that the update doesn't work properly, because of "Key column
information insufficient or incorrect". This happens only for a few
columns in the table.
Example:
Table "tabProductColorPackage"
ID (INT, AutoSeed, Pkey)
Number (DECIMAL(18,2))
Unit (DECIMAL(18,2))
My VB-Code:
Recordset.Open "SELECT Unit FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Works fine!
Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Produces the error given in my description.
What the hell is going wrong here?
Thanks in advance,
BerndHi!
Sorry, the VB-Code that produces the error is as follows:
> Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
> Recordset.Fields("Number") = 1
> Recordset.Update
Thanks,
Bernd
I have the following problem: I have many tables in my database and for
some columns it happens that when I try to update them, I get the error
message, that the update doesn't work properly, because of "Key column
information insufficient or incorrect". This happens only for a few
columns in the table.
Example:
Table "tabProductColorPackage"
ID (INT, AutoSeed, Pkey)
Number (DECIMAL(18,2))
Unit (DECIMAL(18,2))
My VB-Code:
Recordset.Open "SELECT Unit FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Works fine!
Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Produces the error given in my description.
What the hell is going wrong here?
Thanks in advance,
BerndHi!
Sorry, the VB-Code that produces the error is as follows:
> Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
> Recordset.Fields("Number") = 1
> Recordset.Update
Thanks,
Bernd
"Key Column Information...."
Hi everybody!
I have the following problem: I have many tables in my database and for
some columns it happens that when I try to update them, I get the error
message, that the update doesn't work properly, because of "Key column
information insufficient or incorrect". This happens only for a few
columns in the table.
Example:
Table "tabProductColorPackage"
ID (INT, AutoSeed, Pkey)
Number (DECIMAL(18,2))
Unit (DECIMAL(18,2))
My VB-Code:
Recordset.Open "SELECT Unit FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Works fine!
Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Produces the error given in my description.
What the hell is going wrong here?
Thanks in advance,
BerndHi!
Sorry, the VB-Code that produces the error is as follows:
> Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
> Recordset.Fields("Number") = 1
> Recordset.Update
Thanks,
Bernd
I have the following problem: I have many tables in my database and for
some columns it happens that when I try to update them, I get the error
message, that the update doesn't work properly, because of "Key column
information insufficient or incorrect". This happens only for a few
columns in the table.
Example:
Table "tabProductColorPackage"
ID (INT, AutoSeed, Pkey)
Number (DECIMAL(18,2))
Unit (DECIMAL(18,2))
My VB-Code:
Recordset.Open "SELECT Unit FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Works fine!
Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
Recordset.Fields("Unit") = 1
Recordset.Update
--> Produces the error given in my description.
What the hell is going wrong here?
Thanks in advance,
BerndHi!
Sorry, the VB-Code that produces the error is as follows:
> Recordset.Open "SELECT Number FROM tabProductColorPackage WHERE ID=2"
> Recordset.Fields("Number") = 1
> Recordset.Update
Thanks,
Bernd
Sunday, February 19, 2012
"Insufficient key column information for updating and refreshing"
"Insufficient key column information for updating and refreshing"
What does this message mean. All that I am trying to do is manually update
2 rows in one table with one join to another table with the updated values.
Thanks.
ArcherThis message means that SQL Server can determine which value you want to
update because is the relation is not that clear for him. That could be
caused if you want to update a joined table for common data which can be
changed in particular only one ROW. But the best thing would be if you could
send some DDL and the query to find your problem.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"bagman3rd" <bagman3rd@.discussions.microsoft.com> schrieb im Newsbeitrag
news:3EA65F99-EC00-4156-B1B1-1C1A0E52DAB9@.microsoft.com...
> "Insufficient key column information for updating and refreshing"
> What does this message mean. All that I am trying to do is manually
> update
> 2 rows in one table with one join to another table with the updated
> values.
> Thanks.
> Archer|||Hi,
See the KB :-
http://support.microsoft.com/defaul...kb;en-us;814893
Thanks
Hari
SQL Server MVP
"bagman3rd" <bagman3rd@.discussions.microsoft.com> wrote in message
news:3EA65F99-EC00-4156-B1B1-1C1A0E52DAB9@.microsoft.com...
> "Insufficient key column information for updating and refreshing"
> What does this message mean. All that I am trying to do is manually
> update
> 2 rows in one table with one join to another table with the updated
> values.
> Thanks.
> Archer|||It means that there is no primary key declared on the table
by which the row you want to update can be identified
uniquely. When you "view" a table, you can point to a
row by where it is on the screen, but for the update to
succeed, the row must be identified by the value of a
declared primary key, not where you see it on the screen.
Non-database programs, like Excel, keep track of data
by physical position (row number), but database systems
do not. What you see on the screen when you do a "manual
update" is not the actual data, but a result set, like a printout.
It's a dubious convenience of most database systems to
provide an interface whereby someone can change something
in a printout and have the change propogate back to the data.
An UPDATE statement is the best way to modify data,
and my guess is that you can't specify what you want to
update uniquely in a WHERE clause.
Steve Kass
Drew University
bagman3rd wrote:
>"Insufficient key column information for updating and refreshing"
>What does this message mean. All that I am trying to do is manually update
>2 rows in one table with one join to another table with the updated values.
>Thanks.
>Archer
>
What does this message mean. All that I am trying to do is manually update
2 rows in one table with one join to another table with the updated values.
Thanks.
ArcherThis message means that SQL Server can determine which value you want to
update because is the relation is not that clear for him. That could be
caused if you want to update a joined table for common data which can be
changed in particular only one ROW. But the best thing would be if you could
send some DDL and the query to find your problem.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"bagman3rd" <bagman3rd@.discussions.microsoft.com> schrieb im Newsbeitrag
news:3EA65F99-EC00-4156-B1B1-1C1A0E52DAB9@.microsoft.com...
> "Insufficient key column information for updating and refreshing"
> What does this message mean. All that I am trying to do is manually
> update
> 2 rows in one table with one join to another table with the updated
> values.
> Thanks.
> Archer|||Hi,
See the KB :-
http://support.microsoft.com/defaul...kb;en-us;814893
Thanks
Hari
SQL Server MVP
"bagman3rd" <bagman3rd@.discussions.microsoft.com> wrote in message
news:3EA65F99-EC00-4156-B1B1-1C1A0E52DAB9@.microsoft.com...
> "Insufficient key column information for updating and refreshing"
> What does this message mean. All that I am trying to do is manually
> update
> 2 rows in one table with one join to another table with the updated
> values.
> Thanks.
> Archer|||It means that there is no primary key declared on the table
by which the row you want to update can be identified
uniquely. When you "view" a table, you can point to a
row by where it is on the screen, but for the update to
succeed, the row must be identified by the value of a
declared primary key, not where you see it on the screen.
Non-database programs, like Excel, keep track of data
by physical position (row number), but database systems
do not. What you see on the screen when you do a "manual
update" is not the actual data, but a result set, like a printout.
It's a dubious convenience of most database systems to
provide an interface whereby someone can change something
in a printout and have the change propogate back to the data.
An UPDATE statement is the best way to modify data,
and my guess is that you can't specify what you want to
update uniquely in a WHERE clause.
Steve Kass
Drew University
bagman3rd wrote:
>"Insufficient key column information for updating and refreshing"
>What does this message mean. All that I am trying to do is manually update
>2 rows in one table with one join to another table with the updated values.
>Thanks.
>Archer
>
Thursday, February 16, 2012
"Ghost" primary key column
Hello,
I have a table 'customers', with 2 records:
I have a table 'customers', with 2 records:
SELECT * FROM customers;
customerID | customerName
------+--------
myFriend | myFriend's Name
test | testing user
(2 rows)
but when I'm asking about customerID column, I get the answer:
SELECT customerID FROM customers;
ERROR: column "customerid" does not exist
What happens? I'm using PostgreSQL 8.1.3>> What happens? I'm using PostgreSQL 8.1.3 <<
Why are you positng to a SQL Server Newsgroup? And why did you fail to
provide DDL, anyway?|||(chrisek@.poczta.neostrada.pl) writes:
> I have a table 'customers', with 2 records:
> SELECT * FROM customers;
> customerID | customerName
> ------+--------
> myFriend | myFriend's Name
> test | testing user
> (2 rows)
> but when I'm asking about customerID column, I get the answer:
> SELECT customerID FROM customers;
> ERROR: column "customerid" does not exist
> What happens? I'm using PostgreSQL 8.1.3
The interesting part is that your sample output has customerID, and
so has the your query that generates the error message. But the
message complains that "customerid" in all lower case is missing!
Either PostgreSQL is a very strange beast, or your actual query
used "customerid" and PostgreSQL is case-sensitive, just like
MS SQL Server may be depending on the collation. I will have to admit
that my bets are on the latter.
And, no, I don't mention MS SQL Server on a whim. This newsgroups
is devoted to MS SQL Server, and not very packed with people who
can assist you with PostgreSQL.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1151263386.915461.288040@.p79g2000cwp.googlegr oups.com...
>>> What happens? I'm using PostgreSQL 8.1.3 <<
> Why are you positng to a SQL Server Newsgroup?
Who knows why people post non-SQL Server-related stuff to an MS SQL Server
newsgroup? It seems to happen an *awful* lot these days though.|||"--CELKO--" <jcelko212@.earthlink.net> wrote in message
news:1151263386.915461.288040@.p79g2000cwp.googlegr oups.com...
> >> What happens? I'm using PostgreSQL 8.1.3 <<
> Why are you positng to a SQL Server Newsgroup? And why did you fail to
> provide DDL, anyway?
I suspect they're the same answer. Not knowing better.
In any case, I think Erland was able to at least try to help.
Thursday, February 9, 2012
"cannot decrypt the symmetric key"
I was wondering if anyone has any ideas on this error I am seeing on the
Reporting Services server. The server has been working fine for several
months and now we get these errors.
When I go to the Report Manager
http://servername/Reports/pages/folder.aspx
I get the following error: "Response is not well-formed XML"
When I goto the Report Server
http://servername/ReportServer
I get the following error: "The report server cannot decrypt the symmetric
key used to access sensitive or encrypted data in a report server database.
You must either restore a backup key or delete all encrypted content."
I have done some searching and I have found that it is possible that my
ASPNet account has had its password changed which could cause the above
errors. But I am not sure if this would be the issue.
Any thoughts out there?
Thanks
RobI think you are asking on how to determine if the ASPNet password has been
changed. Depends on what is being audited on the box, but how about looking
in the Security evnet log?
Steve MunLeeuw
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:36F2557C-5914-4C85-AB61-E3D7D7C82FA5@.microsoft.com...
>I was wondering if anyone has any ideas on this error I am seeing on the
> Reporting Services server. The server has been working fine for several
> months and now we get these errors.
> When I go to the Report Manager
> http://servername/Reports/pages/folder.aspx
> I get the following error: "Response is not well-formed XML"
> When I goto the Report Server
> http://servername/ReportServer
> I get the following error: "The report server cannot decrypt the symmetric
> key used to access sensitive or encrypted data in a report server
> database.
> You must either restore a backup key or delete all encrypted content."
> I have done some searching and I have found that it is possible that my
> ASPNet account has had its password changed which could cause the above
> errors. But I am not sure if this would be the issue.
> Any thoughts out there?
> Thanks
> Rob
>|||The same thing just began happening to me as well. I've been attempting to install a custom rendering extension I've been writing - I thought it was that but when I undo all the config changes I'm still getting the same message.
I don't have an answer yet but if you've managed to sort yours out I'd be interested in hearing how.
If not, then I'll post back when I've fixed it.
Pete.
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Reporting Services server. The server has been working fine for several
months and now we get these errors.
When I go to the Report Manager
http://servername/Reports/pages/folder.aspx
I get the following error: "Response is not well-formed XML"
When I goto the Report Server
http://servername/ReportServer
I get the following error: "The report server cannot decrypt the symmetric
key used to access sensitive or encrypted data in a report server database.
You must either restore a backup key or delete all encrypted content."
I have done some searching and I have found that it is possible that my
ASPNet account has had its password changed which could cause the above
errors. But I am not sure if this would be the issue.
Any thoughts out there?
Thanks
RobI think you are asking on how to determine if the ASPNet password has been
changed. Depends on what is being audited on the box, but how about looking
in the Security evnet log?
Steve MunLeeuw
"Rob" <Rob@.discussions.microsoft.com> wrote in message
news:36F2557C-5914-4C85-AB61-E3D7D7C82FA5@.microsoft.com...
>I was wondering if anyone has any ideas on this error I am seeing on the
> Reporting Services server. The server has been working fine for several
> months and now we get these errors.
> When I go to the Report Manager
> http://servername/Reports/pages/folder.aspx
> I get the following error: "Response is not well-formed XML"
> When I goto the Report Server
> http://servername/ReportServer
> I get the following error: "The report server cannot decrypt the symmetric
> key used to access sensitive or encrypted data in a report server
> database.
> You must either restore a backup key or delete all encrypted content."
> I have done some searching and I have found that it is possible that my
> ASPNet account has had its password changed which could cause the above
> errors. But I am not sure if this would be the issue.
> Any thoughts out there?
> Thanks
> Rob
>|||The same thing just began happening to me as well. I've been attempting to install a custom rendering extension I've been writing - I thought it was that but when I undo all the config changes I'm still getting the same message.
I don't have an answer yet but if you've managed to sort yours out I'd be interested in hearing how.
If not, then I'll post back when I've fixed it.
Pete.
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Subscribe to:
Posts (Atom)
