Home Dashboard Directory Help
Search

Incorrect Version (build) number in SSMS with SSRS and SSIS by Dan English


Status: 

Closed
 as Fixed Help for as Fixed


10
1
Sign in
to vote
Type: Bug
ID: 422562
Opened: 3/11/2009 9:33:39 AM
Access Restriction: Public
0
Workaround(s)
view
6
User(s) can reproduce this bug

Description

When connected to Reporting Services or Integration Services with SQL Server Management Studio (SSMS) the version (build) number displayed when connected to the instance is incorrect - displays the RTM version 10.0.1600 - even though CU1, CU2, CU3, or CTP SP1 has been installed. If you check the properties window when c onnected to Reporting Services you will see the correct Version number displayed in the General tab. For SSIS you don't have a properties window to validate against. The Database Engine and Analysis Services display the correct version number, only issue is with SSRS and SSIS.
Details
Sign in to post a comment.
Posted by Microsoft on 5/7/2010 at 11:27 AM
Thank you for filing this bug.

This should be fixed in the upcoming SSRS 2008 SP1 CU8 update. Please let us know if this is not the case.

thanx,
Prash
Posted by gtsdba on 4/18/2010 at 11:26 AM
I also experience this issue 2008 SP1 CU1.I have no intention of upgrading to 2008 R2, when will it be fixed in SQL 2008.?
Posted by Phil Brammer on 3/2/2010 at 9:42 AM
This should be fixed in R2 and forward, so 'Closed as Fixed' is a correct status.

See Matt's comments on my post here: http://www.ssistalk.com/2010/01/04/ssis-2008-beware-of-incorrect-version-stamp-in-ssms/
Posted by James M Manning on 2/12/2010 at 7:11 AM
danenglish - do "Edit this Item" to change the state from Closed back to Active, please.
Posted by jsmoberley on 12/29/2009 at 9:43 AM
I can confirm the bug still exists in SQL Server 2008 SP1 CU5.
Posted by Phil Brammer on 12/16/2009 at 7:26 AM
I can confirm this behavior even after installing 2008 SP1, which is version 10.0.2531. When connecting to the Integration Services service, SSMS is still showing 10.0.1600 as the version number.
Posted by gayle on 9/23/2009 at 7:43 PM
this is NOT fixed in sp1
Posted by Dan English on 4/9/2009 at 2:48 AM
This has not been fixed with SQL Server 2008 SP1 - build 2531. This is still an issue so is there a new patch that is available to fix this and how can this be reactivated?
Posted by Microsoft on 4/5/2009 at 7:24 PM
Thank you for filing this bug.

To clarify, this bug should be fixed in Katmai PCU1 also called Katmai SP1. If you do not find this to be the case, please re-activate this issue or file a new bug in this regard.

HTH
Prash
Posted by Dan English on 4/4/2009 at 5:58 AM
By next release do you mean Kilimanjaro? Or would this be part of a SP2 since SP1 is going to be released any day now?

I have more details about this issue here - SQL Server 2008 Management Studio (SSMS) displaying incorrect build number? (http://denglishbi.spaces.live.com/blog/cns!CD3E77E793DF6178!1204.entry)
Posted by Microsoft on 4/3/2009 at 4:23 PM
The problem with SSMS and SSRS has been fixed for the next release. We are following up on the IS problem.
Posted by Microsoft on 4/3/2009 at 4:15 PM
This bug has been fixed for the next release of SQL Server.
Sign in to post a workaround.