Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Foundation Windows Server 2008 R2 Standard Windows Server 2008 R2 Web Edition Windows 7 Enterprise Windows 7 Home Basic Windows 7 Home Premium Windows 7 Professional Windows 7 Starter Windows 7 Ultimate More…Less
Symptoms
Assume that you use Active Directory cmdlets to interrogate Active Directory objects on a computer that is running Windows Server 2008 R2 or on a Windows 7-based computer that has the Remote Server Administration Tools feature installed. When you try to run the Get-ADObject cmdlet, you receive an error message that resembles the following:
The given key was not present in the dictionary.
Cause
This issue occurs because the cmdlet query returns an attribute that is not listed in the aggregate schema. When the Windows PowerShell cmdlet formats the attributes for the result of cmdlet query, the cmdlet retrieves a list of interesting attributes from Active Directory to track the formatting operation. Then, the cmdlet compares this list against the list of attributes that are retrieved for the aggregate schema. When the cmdlet query returns an attribute that is not listed in the aggregate schema, the issue that is described in the «Symptoms» section occurs.
Resolution
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under «Windows 7/Windows Server 2008 R2» on the page. Always refer to the «Applies To» section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.1.760
1.22xxxWindows 7 and Windows Server 2008 R2
SP1
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows 7 and for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Microsoft.activedirectory.management.dll |
6.1.7601.22079 |
774,144 |
06-Aug-2012 |
17:12 |
x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Microsoft.activedirectory.management.dll |
6.1.7601.22079 |
774,144 |
06-Aug-2012 |
18:11 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
|
File name |
X86_a72e15df5fd0ce2c991e6e8f403daead_31bf3856ad364e35_6.1.7601.22079_none_8aa6ed2c8a8746ce.manifest |
|
File version |
Not applicable |
|
File size |
706 |
|
Date (UTC) |
07-Aug-2012 |
|
Time (UTC) |
09:46 |
|
Platform |
Not applicable |
|
File name |
X86_microsoft.activedirectory.management_31bf3856ad364e35_6.1.7601.22079_none_1aeb5954edaf626a.manifest |
|
File version |
Not applicable |
|
File size |
2,809 |
|
Date (UTC) |
06-Aug-2012 |
|
Time (UTC) |
17:33 |
|
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
Amd64_6d4f87cd9f3324175b411631038a43a5_31bf3856ad364e35_6.1.7601.22079_none_215c5e0ff5ba5791.manifest |
|
File version |
Not applicable |
|
File size |
710 |
|
Date (UTC) |
07-Aug-2012 |
|
Time (UTC) |
09:46 |
|
Platform |
Not applicable |
|
File name |
Amd64_a72e15df5fd0ce2c991e6e8f403daead_31bf3856ad364e35_6.1.7601.22079_none_e6c588b042e4b804.manifest |
|
File version |
Not applicable |
|
File size |
708 |
|
Date (UTC) |
07-Aug-2012 |
|
Time (UTC) |
09:46 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft.activedirectory.management_31bf3856ad364e35_6.1.7601.22079_none_7709f4d8a60cd3a0.manifest |
|
File version |
Not applicable |
|
File size |
2,813 |
|
Date (UTC) |
06-Aug-2012 |
|
Time (UTC) |
18:46 |
|
Platform |
Not applicable |
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
Trying to get simple count from table results in exception bellow.
Tried different select statemens which also makes exception: «SELECT * FROM goods«, but «SELECT col1, col2 FROM goods» — works without exception. What am I doing wrong? From workbench these selects works.
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.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, Boolean force) 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 MySqlSybaseComparer.DbTester.Test(String& error) in
c:MySqlSybaseComparerDbTester.cs:line 68
code snippet:
using (MySqlConnection conn = new MySqlConnection(ConStrMySql))
{
try
{
conn.Open();
using (MySqlCommand cmd = new MySqlCommand("SELECT count(*) FROM goods", conn))
{
using (MySqlDataReader reader = cmd.ExecuteReader())
{
if (reader.Read())
MessageBox.Show(reader[0].ToString());
}
}
}
catch (Exception ex)
{
MessageBox.Show(ex.Message + Environment.NewLine + ex.ToString(););
}
conn.Close();
}
Connection string to DB: Server=localhost; Database=art; Uid=ramunas; Pwd=xxxx; AllowUserVariables=True;
asked Jan 30, 2017 at 6:22
4
Year 2017
I have solved your same error simply adding the charset to the connection string:
Server=myServer;Port=3306;Database=myDB15;User ID=usr33;Password=usr33P;CharSet=utf8;
In my case I’m using MySql Connector for .Net version 6.9.3. to connect to 30 equal databases with the same structure, same collation (utf8_unicode_ci) and different table contents.
When I use the MySqlCommand.ExecuteReader() method to select content from user table, in some databases (4 of 30) a got the same error The given key was not present in the dictionary.
Year 2022
Some years later I had the same problem with ObjectContext.ExecuteStoreQuery(), but right now using MySql.Data and MySql.Data.EntityFramework both on version 8.0.27 and when migrating a database from MySQL 5.7.38 to 8.0.28 or 8.0.30.
Adding CharSet or Allow User Variables to the connection string didn’t work (and it wasn’t possible to change my SELECT or Server settings).
Only updating MySql.Data and MySql.Data.EntityFramework to version 8.0.30 solved the problem.
answered Aug 4, 2017 at 7:26
Rafael NetoRafael Neto
9969 silver badges15 bronze badges
1
After spending 5 hours researching how to fix it!!!.. i finally figured it out… all you need to do is to make sure that your ‘MySql.Data.dll’ is up to date! you can download it somewhere. or you can find it here C:Program Files (x86)MySQLMySQL Installer for WindowsMySql.Data.dll.. 
answered Jul 23, 2018 at 8:29
1
Code is correct and all suggestion also should work. Just removed «collation-server» settings and restarted server and everything works as expected.
answered Jan 31, 2017 at 6:56
RamunasRamunas
9951 gold badge11 silver badges19 bronze badges
Try using
SELECT count(*) as count FROM goods
answered Jan 30, 2017 at 6:28
Ali BaigAli Baig
3,8094 gold badges33 silver badges47 bronze badges
0
In place of this statement:
using (MySqlCommand cmd = new MySqlCommand("SELECT count(*) FROM goods", conn))
Use:
using (var cmd = new MySqlCommand("SELECT COUNT(*) FROM goods", conn))
and then convert it to int value by using ExecuteScalar(). Something like this:
int count = Convert.ToInt32(cmd.ExecuteScalar());
answered Jan 30, 2017 at 7:14
AsthaUndefinedAsthaUndefined
1,1111 gold badge11 silver badges24 bronze badges
2
I had same problem using .net core 2.1, mysql, nhibernate.
After i added "Allow User Variables=True" to connection string in appsettings.json my problem solved.
answered Oct 19, 2018 at 13:42
For anyone with the error «the given key ‘0’ was not found in the dictionary», it seems it’s looking for the MySQL DLL. Adding MySql.Data through your package manager or adding the DLL manually from the connector should solve it.
lee-m
2,27317 silver badges29 bronze badges
answered Jul 26, 2022 at 5:46
I tried all of these answers and none helped me.
I eventually tracked it down. The message was that .NET does not support the characterset (in my case utf8mb3) that the database was reporting.
Changed the default charset of the database and it worked perfectly.
answered Jul 16, 2021 at 0:09
Do update your mysql connector for .net, Then remove the old reference mysql.data.dll in your application project and add the updated one from program files(x86)/mysql/MySQL Connector Net 8.0.26Assembliesv4.5.2MySql.Data.dll
answered Jul 26, 2021 at 10:54
You may try going to «Server explorer» and delete the instance of your server that you are trying to connect. Once the instance is deleted trying connecting to the database once again with correct credentials. And if you are working with ADO.NET model be careful the versions of component that you are installing and referencing.
answered Mar 12, 2022 at 3:02
To get compatability you will need to use specific versions of the MySql.EntityFrameworkCore, MySql Connector/NET and entity framework to avoid these issues.
See https://dev.mysql.com/doc/connector-net/en/connector-net-entityframework-core-scaffold-example.html for examples
<PropertyGroup>
<TargetFramework>net6.0</TargetFramework>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="6.0.10">
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
<PrivateAssets>all</PrivateAssets>
</PackageReference>
<PackageReference Include="MySql.EntityFrameworkCore" Version="6.0.4" />
</ItemGroup>
Update the entity framework tool with
dotnet tool update --global dotnet-ef
The scaffolding command should look like
dotnet ef dbcontext scaffold "Server=[Host];Database=[DBName];User Id=[Username];Password=[Password];" MySql.EntityFrameworkCore -o [OutputContextName] --no-pluralize --no-onconfiguring -f
For details check out https://learn.microsoft.com/en-us/ef/core/cli/dotnet and search for dotnet ef dbcontext scaffold
answered Nov 2, 2022 at 8:00
XavierXavier
1,3836 silver badges6 bronze badges
use Database name in your query and Port in connection String
strMySqlConnection =
"server=localhost;Port=3306; user id=root; password=; database=art;
pooling=false;Charset = utf8 ;";
SELECT * FROM goods ==> SELECT * FROM `art`.`goods`
Update MySql.Data & use .Netframework 4.6
answered Apr 6 at 6:01
in my case i use MySQL Connector NET 6.3.0 and the solution that i got is to change connection string key
from
Server=127.0.0.1;Uid=root;Pwd=xxxx;Database=dbname;CharSet=utf8
to this
server=127.0.0.1;user id=root;password=xxxx;database=dbname;charset=utf8;pooling=false
answered Mar 5, 2020 at 14:12
1
- Remove From My Forums
-
Question
-
I am using following code to filter out some data from one datatable to another
if (dtKeys.Rows.Count > 0 && objEntryPlanningReport.PostageCalculationTable != null && objEntryPlanningReport.PostageCalculationTable.Rows.Count > 0) { dt = objEntryPlanningReport.PostageCalculationTable.Clone();//cloning the structure try { foreach (DataRow dr in dtKeys.Rows) { DataView datavw = new DataView(); datavw = objEntryPlanningReport.PostageCalculationTable.DefaultView;//Getting the default view datavw.RowFilter = " JobID = '" + dr["fkJobID"].ToString() + "' and fkContainerID='" + dr["csmContainerID"].ToString() + "' "; //filter out the data i wanted to extract if (datavw.Count > 0) { foreach (DataRow drMatched in datavw.ToTable().Rows)//error in this line.The given key was not present in the dictionary. { dt.ImportRow(drMatched);//copying the matched rows in my desired table } } } } catch (Exception ex) { //throw; } dt.AcceptChanges(); } return dt;But On random basis On the line I have highlighted I am getting following error
The given key was not present in the dictionary.
How can i avoid it
Kamran Shahid Principle Engineer Development (MCP,MCAD,MCSD.NET,MCTS,MCPD.net[web])
Answers
-
This is not really an «exception», it’s just a problem with the debugger. The debugger attempted to get the Capacity of thet able, but it took too long, so it aborted the attempt. Usually that just means the computer doesn’t have enough resources to do everything
it needs to do within the time that Visual Studio allows.I would recommend looping through dr directly (instead of the view). Add dr[«fkJobID»] and dr[«csmContainerID»] to your Waches window, and put a breakpoint somewhere in your loop. Keep hitting F5 until you see where one of those two calls returns an exception
instead of a legitimate value.
Check out
My Blog. Now updated to actually work!-
Marked as answer by
Wednesday, May 9, 2012 3:34 AM
-
Marked as answer by
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
utf8mb4character set. When attempting to connect toutf8mb4tables or columns, an exceptionKeyNotFoundExceptionwas 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_ciCode 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!
Protip: Donate $10, 20 or 30 through Paypal (or see my donate page) and support this site. Thank you <3
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_enlistedTransactionwas being set, ors_transactionConnectionswas 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.