An error occurred while generating report the given key was not present in the dictionary - Исправление ошибок и поиск оптимальных решений проблем

Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Service Pack 1 Windows Server 2008 Standard Windows Server 2008 Enterprise Windows Server 2008 Service Pack 2 More…Less

Symptoms

Consider the following scenario:

You create a new Group Policy setting and configure some registry items under Preferences (user or Computer). To do this, you use the registry wizard to add keys or values to the registry. For example, under Computer configuration Preferences Registry, you right-click and then select New -> Registry Wizard. This opens a user interface that enables you to manipulate registry items.
On Windows Server 2008 R2 and Windows Server 2008, you run the Group Policy Modeling Wizard against the new Group Policy setting.

In this scenario, you experience one of the following symptoms, depending on your version of Internet Explorer:

In Internet Explorer 8, you receive the following error message and error code 80131577:

An error occurred while generating report. The given Key was not present in the dictionary
In Internet Explorer 9, the wizard runs but does not report any registry settings. Additionally, the Registry Preferences section is empty.

Cause

There is a faulty registry item in the XML file that is associated with the Group Policy registry settings.

Resolution

To fix this issue, re-create the Group Policy and registry settings. However, while you are using the registry browser to select values in a registry key, do not select the parent key together with the values in it. The parent key is auto-selected. This is, when you select a value in a key, a red tick appears automatically on the parent key folder. It is not necessary also to select the parent key.

Need more help?

Источник

Remove From My Forums

Question
I am attempting to run the Group Policy Modeling wizard against a specific computer and user (or their respective OUs) in my domain. In the wizard, I specify this computer and user, and specify no other options. When the wizard completes, the following message
appears in the «Summary» and «Settings» tabs:
```
An error occurred while generating report:
The given key was not present in the dictionary.
```
I get this error whether I run the wizard on the domain controller itself (Server 2008 SP2) or on my Windows 7 client with the RSAT. It seems to be specific to certain OUs, but I haven’t been able to narrow down if it’s a specific GPO that is causing it
yet. Any ideas what might be causing this?

Answers

To finally answer this question

This happens when you add GPP Registry items through the registry wizard. Running this wizard creates a registry item that only has the registry key in it and no value. Delete this item and you’re fine.

BTW: Obviously this is a bug, and we already reported it to PSS. But I doubt they will fix it for Win7 — there’s almost no impact in the above workaround…

regards, Martin

NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I’m glad about a rating!
- Proposed as answer by
  
  Thursday, July 24, 2014 12:58 AM
- Marked as answer by
  Ryan G. Steele
  Thursday, July 24, 2014 4:31 PM
- Edited by
  Gopi-JiJiTechnologies
  Thursday, July 24, 2014 6:52 AM
- Marked as answer by
  Ryan G. Steele
  Thursday, July 24, 2014 4:32 PM

Источник

I came across with the same issue. The problem was that I had no issues when I deploy my report and I tried to access it through URL, but when I tried to access programmatically the browser launch this error ‘The given key was not present in the dictionary’.I investigated and found that I was not set up the visibility flag as ‘false’ on the code.

https://msdn.microsoft.com/en-us/library/microsoft.reporting.webforms.reportparameter.aspx

ReportParameter(String, String, Boolean)
Instantiates a new ReportParameter with a name, a value, and a visibility flag.

Finally, my code was something sort of this:

            this.rptViewer.Reset();

            rptViewer.ProcessingMode = Microsoft.Reporting.WebForms.ProcessingMode.Remote;
            MyReportServerCredentials credencial = new MyReportServerCredentials();
            rptViewer.ServerReport.ReportServerCredentials = credencial;

            this.rptViewer.ServerReport.ReportServerUrl = new System.Uri(this.ReportServerUrl);
            this.rptViewer.ServerReport.ReportPath = ReportUrl;

            this.rptViewer.ServerReport.ReportServerUrl = new System.Uri(this.ReportServerUrl);
            this.rptViewer.ServerReport.ReportPath = ReportUrl;

            ReportParameter p1 = new ReportParameter("param1", new string[] { null }, false);
            ReportParameter p2 = new ReportParameter("param2", new string[] { null }, false);
            ReportParameter p3 = new ReportParameter("param3", new string[] { null }, false);
            ReportParameter p4 = new ReportParameter("param4", new string[] { null }, false);


            this.rptViewer.ServerReport.SetParameters(new ReportParameter[] { p1, p2, p3, p4 });

            this.rptViewer.AsyncRendering = false;
            this.rptViewer.SizeToReportContent = true;
            this.rptViewer.ServerReport.Refresh();

I hope it helps!

Источник

An System.Collections.Generic.KeyNotFoundException “The given key was not present in the dictionary” can be the result of using a too old MySQL Connector/NET version in your ASP.NET web application. A KeyNotFoundException is thrown when an operation attempts to retrieve an element from a collection using a key that does not exist in that collection. An unsupported character set like utf8mb4 can be such a key, if your Connector/NET doesn’t support this character set. Luckily there is an easy workaround for this.

MySQL (Oracle) Connector/NET versions prior to 6.0.8, 6.1.6, 6.2.5, 6.3.6 lack a mapping for UTF8MB4 as charset. Connecting to a MySQL database and querying a table that has been created with CHARSET=utf8mb4 results in a .NET exception:

Exception Details: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at MySql.Data.MySqlClient.CharSetMap.GetCharacterSet(DBVersion version, String CharSetName) at MySql.Data.MySqlClient.CharSetMap.GetEncoding(DBVersion version, String CharSetName) at MySql.Data.MySqlClient.Driver.Configure(MySqlConnection connection) at MySql.Data.MySqlClient.MySqlConnection.Open() at ASP.mysql_data_aspx.MySQLConn()

A more extended exception is:

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at MySql.Data.MySqlClient.CharSetMap.GetCharacterSet(DBVersion version, String CharSetName) at MySql.Data.MySqlClient.MySqlField.SetFieldEncoding() at MySql.Data.MySqlClient.NativeDriver.GetColumnData(MySqlField field) at MySql.Data.MySqlClient.NativeDriver.GetColumnsData(MySqlField[] columns) at MySql.Data.MySqlClient.Driver.GetColumns(Int32 count) at MySql.Data.MySqlClient.ResultSet.LoadColumns(Int32 numCols) at MySql.Data.MySqlClient.ResultSet..ctor(Driver d, Int32 statementId, Int32 numCols) at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId) at MySql.Data.MySqlClient.MySqlDataReader.NextResult() at MySql.Data.MySqlClient.MySqlDataReader.Close() at MySql.Data.MySqlClient.MySqlCommand.ResetReader() at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() at ASP.mysql_data_aspx.MySQLConn()

Googling for a fix, some suggestions were to add CharSet=utf8; to your connection string. Unfortunately I was unable to resolve the exception with this added.

The best way to fix this System.Collections.Generic.KeyNotFoundException with Connector/NET is to simply update your Connector/NET version. Support for utf8mb4 charset is built in in versions 6.0.8, 6.1.6, 6.2.5, 6.3.6+:

MySQL Connector/NET did not support the utf8mb4 character set. When attempting to connect to utf8mb4 tables or columns, an exception KeyNotFoundException was generated. (Bug #58244)

https://dev.mysql.com/doc/relnotes/connector-net/en/news-6-0-8.html

And MySQL Connector/NET now supports MySQL servers configured to use utf8mb4 as the default character set in version 8.0.9.

MySQL Connector/NET now supports MySQL servers configured to use utf8mb4 as the default character set.

https://dev.mysql.com/doc/relnotes/connector-net/en/news-8-0-9.html

If, for some reason, you cannot or will not update your MySQL Connector/NET version anytime soon, there is an easy workaround available; SET NAMES 'utf8'. Yes, that’s right: as your first statement, set the three session system variables

character_set_client
character_set_connection
character_set_results

to the given character set utf8. You can even use latin1, but that may give some undesired encoding issues…

Imaging the following C# MySql.Data.MySqlClient test script for querying your MySQL database table:

string sql = "select * from aspnet_site_comments";
MySqlCommand cmd = new MySqlCommand(sql, conn);
MySqlDataReader rdr = cmd.ExecuteReader();

while (rdr.Read()) {
	Response.Write(rdr[0]+ "<br/>");
}
rdr.Close();
}

catch (Exception ex) {
	Response.Write(ex.ToString());
}
Code language: C# (cs)

Are you looking for rock solid, eco-friendly, .NET hosting? Look no further! UmbHost offers powerful hosting services for websites and businesses of all sizes, and is powered by 100% renewable energy!

If your MySQL database server has in its my.cnf server config:

character_set_server utf8mb4
collation_server = utf8mb4_unicode_ci
Code language: SQL (Structured Query Language) (sql)

And your table aspnet_site_comments is created using ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci, it throws an System.Collections.Generic.KeyNotFoundException exception. Alter your code to first set the character_set_* to utf8 (don’t mind my pseudo-code, you’ll get the idea) as a workaround for this issue:

string setcharset = "SET NAMES 'utf8'";	// <-- !!
MySqlCommand charsetcmd = new MySqlCommand(setcharset, conn);
MySqlDataReader charsetrdr = charsetcmd.ExecuteReader();
charsetrdr.Close()

string sql = "select * from aspnet_site_comments";
MySqlCommand cmd = new MySqlCommand(sql, conn);
MySqlDataReader rdr = cmd.ExecuteReader();

while (rdr.Read()) {
	Response.Write(rdr[0]+ "<br/>");
}
rdr.Close();
}

catch (Exception ex) {
	Response.Write(ex.ToString());
}
Code language: C# (cs)

Only use this as a temporary fix, you should still update Connector/NET ASAP. That’s it!

Источник

by Tashreef Shareef

Tashreef Shareef is a software developer turned tech writer. He discovered his interest in technology after reading a tech magazine accidentally. Now he writes about everything tech from… read more

Updated on October 4, 2021

XINSTALL BY CLICKING THE DOWNLOAD FILE

To fix various PC problems, we recommend DriverFix:
This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:

Download DriverFix (verified download file).
Click Start Scan to find all problematic drivers.
Click Update Drivers to get new versions and avoid system malfunctionings.

DriverFix has been downloaded by 0 readers this month.

Power BI key errors can occur in different ways with a different error message. Some of the Power BI error key messages reported by the Power BI users include Power BI error the given key was not present in the dictionary, power bi error the key didn’t match any rows, and power bi error generating an asymmetric key.

Follow the troubleshooting steps for each error below to resolve Power BI key error.

How to fix various Power BI key errors

1. Power BI error generating an asymmetric key

Change the Virtual Machine

If you are using a Virtual Machine and getting the Power BI error generating an asymmetric key, try to install the gateway in a different Virtual Machine.
Users have reported that installing the Gateway on a different virtual machine has resolved the error.

Upgrade the OS (Windows Server)

If you are installing the Gateway on an older version like the 2008 Windows Server, try upgrading to the newer version Windows Server 2012 or later.
Due to incompatibility issues or other glitches, the gateway installation may fail in the older version of Windows Server 2012.
Simply install the Windows Server on a virtual machine and try to install the gateway.
Check if the generating an asymmetric key error is resolved.

Install Data Gateway Manually

In case the issue is at the Power BI end, you can try to install each gateway manually.
To install the On-Premises data gateway, go to Install On-Premises.
To install the On-premises data gateway (Personal Mode) go to Install On-Premises (Personal Mode) link.
Download and install the data gateways manually and check if the error is resolved.

Change Logon User for Service

If you haven’t already, try changing the logon user for Service.
Press Windows Key + R to open Run.
Type services.msc and click OK.
In the Services window, locate and double-click on Power BI Gateway – Enterprise Service.
In the Logon tab, select the “Local System Account” option.
Click Apply and OK to save the changes.
Now try to install the gateway and check if the error is resolved.

Did you know how to refresh data in Power BI? Learn how by following these guides.

2. Fix Power BI error the given key was not present in the dictionary

Update the Power BI App

If the issue is occurring after installing Windows update, then Microsoft will most likely release an update to fix the issue.
Launch the Microsoft Store app and look for the Power BI.
Download and install if any update is available for the Power BI App.

Upload the files in a Zip File

To upload a brand pack with multiple files it is important that you zip the folder containing the files and then upload it.
So include the Metadata.xml, logo.png and color.json file in a folder.
Now compress the folder using free compressing software.
Upload the compressed file to the Branding section.

3. Fix Power BI error the key didn’t match any rows

Revert the Changes Made to Table in Database

If you have recently made any changes to any table in the database and getting this error, then try to revert the changes to resolve the error.
Click Home and select Edit Queries.
Under Applied Steps, remove the navigation.
Click Close and Apply.
Now try to access the table in the database and check if the error is resolved.

RELATED STORIES YOU MAY LIKE:

How to refresh data in Power BI [STEP-BY-STEP GUIDE]
5 free cloud accounting software to keep your books updated on the fly
Top 3 browsers for seamless SharePoint use

Still having issues? Fix them with this tool:

SPONSORED

If the advices above haven’t solved your issue, your PC may experience deeper Windows problems. We recommend downloading this PC Repair tool (rated Great on TrustPilot.com) to easily address them. After installation, simply click the Start Scan button and then press on Repair All.

Источник

I have created some log output to help with the search.

I have replaced the nuget package reference by a direct project reference, and logged wherever either:

m_enlistedTransaction was being set, or
s_transactionConnections was being mutated.

Timestamps are from bottom to top. Note how the first run of my Quartz job has no problems, but the second run (after a few minutes of inactivity) seems to think that it can reuse some existing connection.

Unfortunately, I’ve logged the hash code of the enlisted transaction rather than the underlying System.Transactions.Transaction.

My comments should help provide some insight into what’s going on. Note that the first run performs a couple of (unrelated) transactions back-to-back, successfully, but the second run throws on its very first attempt.

@bgrainger Any idea why FindExistingEnlistedSession() in OpenAsync() finds an existing connection on my subsequent job run, for a brand new transaction?

I could only find the .NET Framework source, but it looks like the hash code and even equality of Transaction is based entirely on its InternalTransaction.TransactionHash. Perhaps such hash codes end up getting reused, and the new transaction is seen as identical to an old one? Then again, the old one is being removed from the dictionary, so it still doesn’t explain.

SUBSEQUENT JOB RUN:

	// Step 3: Throw when attempting to find the related Transaction in s_transactionConnections
	Jun 1, 2021 @ 17:10:22.550	System.Collections.Generic.KeyNotFoundException: The given key 'System.Transactions.Transaction' was not present in the dictionary.
	   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
	   at MySqlConnector.MySqlConnection.DoCloseAsync(Boolean changeState, IOBehavior ioBehavior) in /app/MySqlConnector/MySqlConnection.cs:line 1004
	   at MySqlConnector.MySqlConnection.CloseAsync(Boolean changeState, IOBehavior ioBehavior) in /app/MySqlConnector/MySqlConnection.cs:line 972
	   at MySqlConnector.MySqlConnection.Dispose(Boolean disposing) in /app/MySqlConnector/MySqlConnection.cs:line 653
	   at System.ComponentModel.Component.Dispose()
	// Step 2: Close after the first of our two queries within our transaction, passing the enlistment on to a new dummy 
	Jun 1, 2021 @ 17:10:22.545	message:DoCloseAsync: Setting (stealing) m_enlistedTransaction: transaction 41727345 for connection 17882254. 
	Jun 1, 2021 @ 17:10:22.543	message:DoCloseAsync: Unsetting (donating) m_enlistedTransaction: transaction 41727345 for connection 20809629. 
	// Step 1: Enlist, which does not add to s_transactionConnections, presumably because the "TryGetValue" condition concludes the dictionary already has that transaction
	Jun 1, 2021 @ 17:10:22.524	message:EnlistTransaction: Setting m_enlistedTransaction: transaction 1 for connection 20809629.

FIRST JOB RUN:

	// Second iteration of open transaction scope, perform query, commit:

	// Step 5: Unenlist at the end of the transaction, which also removes from s_transactionConnections
	Jun 1, 2021 @ 16:41:39.451	message:UnenlistTransaction: Removing from s_transactionConnections: transaction 11 for connection 33771145. 
	Jun 1, 2021 @ 16:41:39.449	message:UnenlistTransaction: Unsetting m_enlistedTransaction: transaction 11 for connection 33771145. 
	// Step 4: Close after the second of our two queries within our transaction, passing the enlistment on to a new dummy transaction (used to hold the session)
	Jun 1, 2021 @ 16:41:39.410	message:DoCloseAsync: Setting (stealing) m_enlistedTransaction: transaction 35287174 for connection 33771145. 
	Jun 1, 2021 @ 16:41:39.408	message:DoCloseAsync: Unsetting (donating) m_enlistedTransaction: transaction 35287174 for connection 52697953. 
	// Step 3: Open the new connection, but actually reuse the previous one within the transaction
	Jun 1, 2021 @ 16:41:39.258	message:OpenAsync: Setting (stealing) m_enlistedTransaction: transaction 35287174 for connection 52697953. 
	Jun 1, 2021 @ 16:41:39.257	message:OpenAsync: Unsetting (donating) m_enlistedTransaction: transaction 35287174 for connection 44419000. 
	// Step 2: Close after the first of our two queries within our transaction, passing the enlistment on to a new dummy transaction (used to hold the session)
	Jun 1, 2021 @ 16:41:39.254	message:DoCloseAsync: Setting (stealing) m_enlistedTransaction: transaction 35287174 for connection 44419000. 
	Jun 1, 2021 @ 16:41:39.253	message:DoCloseAsync: Unsetting (donating) m_enlistedTransaction: transaction 35287174 for connection 41300193. 
	// Step 1: Enlist (caused by OpenAsync), which also adds to s_transactionConnections
	Jun 1, 2021 @ 16:41:39.190	message:EnlistTransaction: Adding to s_transactionConnections: transaction 11 for connection 41300193. 
	Jun 1, 2021 @ 16:41:39.133	message:EnlistTransaction: Setting m_enlistedTransaction: transaction 11 for connection 41300193. 

	// First iteration of open transaction scope, perform query, commit:
	
	Jun 1, 2021 @ 16:41:39.108	message:UnenlistTransaction: Removing from s_transactionConnections: transaction 10 for connection 9779853. 
	Jun 1, 2021 @ 16:41:39.106	message:UnenlistTransaction: Unsetting m_enlistedTransaction: transaction 10 for connection 9779853. 
	Jun 1, 2021 @ 16:41:39.018	message:DoCloseAsync: Setting (stealing) m_enlistedTransaction: transaction 17561922 for connection 9779853. 
	Jun 1, 2021 @ 16:41:39.017	message:DoCloseAsync: Unsetting (donating) m_enlistedTransaction: transaction 17561922 for connection 60800190. 
	Jun 1, 2021 @ 16:41:37.623	message:OpenAsync: Setting (stealing) m_enlistedTransaction: transaction 17561922 for connection 60800190. 
	Jun 1, 2021 @ 16:41:37.621	message:OpenAsync: Unsetting (donating) m_enlistedTransaction: transaction 17561922 for connection 48950176. 
	Jun 1, 2021 @ 16:41:37.593	message:DoCloseAsync: Setting (stealing) m_enlistedTransaction: transaction 17561922 for connection 48950176. 
	Jun 1, 2021 @ 16:41:37.592	message:DoCloseAsync: Unsetting (donating) m_enlistedTransaction: transaction 17561922 for connection 57171047. 
	Jun 1, 2021 @ 16:41:37.305	message:EnlistTransaction: Adding to s_transactionConnections: transaction 10 for connection 57171047. 
	Jun 1, 2021 @ 16:41:37.262	message:EnlistTransaction: Setting m_enlistedTransaction: transaction 10 for connection 57171047.

Источник

All forum topics
Previous Topic
Next Topic

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎05-25-2021

07:43 AM

Hello,

I am having a refresh problem and I need help,

Currently, I am using Power BI Desktop (January 2021), after applying changes, it takes long time then I get the following error:

»The given key was not present in the dictionary»

It does occur after the Windows update, I have done some research and it seems like this is due to the Windows update and I need to install the latest Power BI Desktop version. However, I am publishing the dashboard into the power BI report Server which doesn’t have may 2021 version yet.

What is confusing is that I have this error only in one dashboard. Isn’t I supposed to have this error in all dashboards?

Please be advised that I am using an Excel file and SQL Server databases in my dashboard.

Thanks a lot for your help,

Message 1 of 7

24,621 Views

2 ACCEPTED SOLUTIONS

All forum topics
Previous Topic
Next Topic

6 REPLIES 6

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎01-16-2023

09:23 PM

Holy smoke I think I solved the same error message on my dashboard. So I have a column of numeric values, but I vaguely recall that that column had a value that was crazy high. So I specified that it should be int64 and that resolved to stop the error message. I hope my solve applies to yours or at least someone else looking.

Message 7 of 7

1,450 Views

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

‎01-16-2023

09:22 PM

Message 6 of 7

1,453 Views

Источник

Reference Support Article: https://support.qlik.com/articles/000068974

Description

April 26, 2019 Update:

This issue is resolved in the April 2019 Release of NPrinting which is now available for download from the Qlik Downloads site
Link: Qlik Support Downloads site

This problem occurs when a user connected to the NPrinting Web Console with Internet Explorer tries to edit a report. The problem is affecting only updated Windows machines.

To replicate the problem:
1. Install the Windows update KB4489881 (Monthly Rollup)

https://support.microsoft.com/en-us/help/4489881/windows-8-1-update-kb4489881

2. Connect to NPrinting Internet Explorer
3. Go to Reports and open a report or create a new one
4. Click on Edit Template
5. Click «Allow» if requested,

The»The given key was not present in the dictionary» error message is shown. Only the option to click OK is given. NPrinting Designer cannot be opened. NPrinting designer was working correctly before the mentioned Windows update.

Environment:

NPrinting 17 any releases
NPrinting 18 any releases
NPrinting 19 February release

Cause

The problem is due to a change introduced with the mentioned Windows update — KB4489881 (Monthly Rollup). Further analysis are currently performed by Qlik Development team to resolve the problem.

Update: This issue is resolved in the upcoming April 2019 Release of NPrinting which should be available for download from the Qlik Downloads site by mid April 2019.

Resolution

NOTE: There are two possible workarounds:

1. The problem is affecting Internet Explorer only. Connect to the NPrinting Web console using a different browser. Firefox, Chrome and Edge have been tested successfully.
2. The problem can be solved by removing the Windows update KB4489881 (Monthly Rollup)

NOTE: If you are still experiencing this issue after installing April 2019 or later releases of NPrinting, please report it as a new defect to the Qlik Support desk or your Qlik support partner. Subsequent windows updates may be affecting/reintroducing this issue.

Disclaimer

Access to this article is provided to you as part of your subscription to Qlik Maintenance. This article is deemed to be “Documentation” under the terms of the license agreement applicable to your Qlik software. All rights reserved © QlikTech International AB.

Источник

Symptoms

Cause

Resolution

Need more help?

Question

Answers

How to fix various Power BI key errors

1. Power BI error generating an asymmetric key

2. Fix Power BI error the given key was not present in the dictionary

3. Fix Power BI error the key didn’t match any rows

Newsletter

Description

Cause

Resolution

Disclaimer