SQL Agent Job History Viewer - "The given key was not present in the dictionary. (mscorlib)" - by Chris Howarth

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 709764 Comments
Status Closed Workarounds
Type Bug Repros 13
Opened 11/30/2011 12:14:33 AM
Access Restriction Public


I'm receiving the above error in SSMS 2012 RC0 64-bit (11.0.1750.32) when attempting to to view the history of a specific job. SSMS is running on a Windows 7 SP1 desktop PC.

The server hosting the jobs is a SQL 2008R2 instance:

Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) 
	Jun 17 2011 00:54:03 
	Copyright (c) Microsoft Corporation
	Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

The properties from the SSMS About form on the client machine are as follows:

Microsoft SQL Server Management Studio						11.0.1750.32
Microsoft Analysis Services Client Tools						11.0.1750.32
Microsoft Data Access Components (MDAC)						6.1.7601.17514
Microsoft MSXML						3.0 4.0 5.0 6.0 
Microsoft Internet Explorer						8.0.7601.17514
Microsoft .NET Framework						4.0.30319.237
Operating System						6.1.7601
Sign in to post a comment.
Posted by Steve Annetts on 2/18/2016 at 12:32 AM
We are experiencing the same issue with a job with a comma in the name. The job is running fine but you can't view the history, the error "The given key was not present in the dictionary." occurs.
Other jobs without a comma in the name work fine and the history can be viewed.
Just thought I'd confirm we are seeing the same conclusion as others.
Version: SQL Server 11.0.3000
Posted by Steve Annetts on 2/18/2016 at 12:31 AM
Test post - ignore.
Posted by wvoyek on 5/15/2014 at 11:43 AM
I'm still having this issue. What SP is supposed to have resolved this?

My SQL version info:

Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
    Dec 28 2012 20:23:12
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
Posted by JACitro on 2/10/2014 at 3:07 PM
When will the next SP be released? I am running SQL Server 2012 (SP 1) - 11.0.3000.0 (X64) and still receiving this message.
Posted by Microsoft on 7/3/2012 at 7:39 AM
Thank you for reporting the issue. We have made the fix and it will be included in the next service pack. Thanks again for using the Microsoft Connect tool to provide product feedback.

Sam Lester
Posted by Microsoft on 6/4/2012 at 10:34 AM
Thanks everyone for reporting this issue!

We are considering to fix this issue in SQL Server 2012's next service pack.

Posted by Becke on 4/6/2012 at 1:16 PM
I too am experiencing this issue using SSMS 2012 rtm - was there any resolution?
Posted by bborder on 3/9/2012 at 11:11 AM
I am having the same problem. I'm using SQL 2012 RTM Studio to view the JOB HISTORY log of jobs in a SQL2008R2 instance. If the job name has a comma, I get this error.
Posted by Sethu Srinivasan on 2/13/2012 at 11:12 AM
Hello Chris,
Can you check if any of the jobs on SQL 2008 R2 server has a comma "," it its name?

Sethu Srinivasan [MSFT]
SQL Server
Posted by Chris Howarth on 11/30/2011 at 2:14 PM
Hi Alex

I did attempt to upload the file, but it appears that it may have failed.

I've sent you an email with the relevant files attached.

Posted by Microsoft on 11/30/2011 at 1:54 PM
Hey Chris, for some reason I didn't get any related attachments for this issue. Based on your feedback I understand that issue is related only to specific job, can you provide some details about this job (type of each step etc.)? I will appriciate if you can script it out and send it over to me via email so I can take a look into this issue. My email is algrach@microsoft.com

Thank you
Posted by Microsoft on 11/30/2011 at 1:38 PM
Thank you for reporting this issue - we are investigating and we will get back to you shortly.


Alex Grach [MSFT]