SQL2014 Profiler fails to connect to SQL 2005 - by RichardMunn

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.


60
0
Sign in
to vote
ID 864021 Comments
Status Closed Workarounds
Type Bug Repros 19
Opened 4/30/2014 3:20:46 AM
Access Restriction Public

Description

Connection to a SQL2005 instance from SSMS 2014 is OK, but when I hit up the Tools>SQLServer Profiler option to start Profiler, an error is returned and Profiler won't connect.

Error text:
"SQL Server Profiler cannot perform this action on database servers earlier than SQL 2005. Please use SQL Server 2005 or later."

Instance I'm trying to connect to is build 9.0.5292.

SSMS 2014 details:
Microsoft SQL Server Management Studio						12.0.2000.8
Microsoft Analysis Services Client Tools						12.0.2000.8
Microsoft Data Access Components (MDAC)						6.1.7601.17514
Microsoft MSXML						3.0 6.0 
Microsoft Internet Explorer						8.0.7601.17514
Microsoft .NET Framework						4.0.30319.18063
Operating System						6.1.7601

SQL Profiler details:
SQL Server Profiler						12.0.2000.8
Microsoft .NET Framework						4.0.30319.18063
Operating System						6.1.7601
Sign in to post a comment.
Posted by Sethu Srinivasan on 2/19/2015 at 1:24 PM
Fix is available in http://blogs.msdn.com/b/sqlreleaseservices/archive/2015/02/17/cumulative-update-6-for-sql-server-2014-rtm.aspx

Please keep us posted if this works for you

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Posted by Sethu Srinivasan on 2/4/2015 at 9:16 AM
Thanks for reporting this issue. We have identified the defect in profiler code and we are working on a fix. We shall keep you posted when the fix is available for you to download.

Thanks
Sethu Srinivasan [MSFT]
SQL Server
http://blogs.msdn.com/sqlagent

Posted by Newfangled Old-fashioned Stuff on 7/30/2014 at 7:46 AM
Note: I actually meant coming from SSMS 2014 RTM CU2, which the build number I copy/pasted clearly indicates. Sorry - I am unable to edit the comment.
Posted by Newfangled Old-fashioned Stuff on 7/30/2014 at 7:45 AM
I can also confirm this is happening with fully up date to date versions of both 2014 and 2005 as of today:

Coming from SSMS 2012 RTM CU2:
        Microsoft SQL Server Management Studio    12.0.2370.0

Going to SQL 2005 SP4 MS12-070 QFE:
        Microsoft SQL Server 2005 - 9.00.5324.00 (Intel X86)
    Aug 24 2012 14:24:46
    Copyright (c) 1988-2005 Microsoft Corporation
    Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

As with the original poster, the error message clearly indicates that SQL 2005 targets should work.
Posted by Ryan McCauley on 5/8/2014 at 8:08 AM
I've verified that this occurs with both a SQL 2005 SP4 server (9.0.5000) and SP1 + hotfix (9.0.2050). I'm have the same version on SSMS/Profiler (12.0.2000.8), but with the following component versions (if it matters):

SSMS:
MDAC: 6.3.9600.16384
IE: 9.11.9600.17031
.NET Framework: 4.0.30319.34014
OS: 6.3.9600 (Windows Server 2012 R2)

Profiler:
.NET Framework: 4.0.30319.34014
OS: 6.3.9600 (Windows Server 2012 R2)