July 11, 2007 at 1:37 pm
We recently upgraded several servers to SQL Server 2005 Standard Edition on Windows 2003. They are running fine. The problem we are having is that our Windows XP clients are not on the latest and greatest version of the SQL Server Management Studio (as shown below). I have tried complete re-install of the client, with regclean in between reboots. Going through SP1 step by step, then SP2, etc.
I'm mostly wanting to know if others are having the same problem? Have you solved it? Do I need to open a case with M$?
The 9.00.1399.00 is the OEM release. Not even the SP1.
Microsoft Windows XP SP2: Microsoft SQL Server Management Studio9.00.1399.00 Microsoft Analysis Services Client Tools2005.090.1399.00 Microsoft Data Access Components (MDAC)2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML2.6 3.0 4.0 6.0 Microsoft Internet Explorer6.0.2900.2180 Microsoft .NET Framework2.0.50727.42 Operating System5.1.2600 Microsoft Windows Server 2003: Microsoft SQL Server Management Studio9.00.3042.00 Microsoft Analysis Services Client Tools2005.090.3042.00 Microsoft Data Access Components (MDAC)2000.086.1830.00 (srv03_sp1_rtm.050324-1447) Microsoft MSXML2.6 3.0 4.0 6.0 Microsoft Internet Explorer6.0.3790.1830 Microsoft .NET Framework2.0.50727.42 Operating System5.2.3790 Prod_Ver Prod_Lvl Edition 9.00.3054.00 SP2 Standard Edition
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
July 11, 2007 at 1:47 pm
Does your install fail? Or not reporting back in the version information that it has been upgraded?
I had zero problems upgrading my XP clients from RTM to SP2 at all.
July 11, 2007 at 2:08 pm
The upgrades report success until GDR1 & GDR2. SQL Server 2005 Service Pack 2 (SP2) Re-release and post fixes explained
So far it is on 2 machines that had the SQL2K EM on it. I'm going to try firing it onto a laptop that has never seen SQL2k. This is just frustrating me. I've wasted a portion of several days on this problem.
----------------
Jim P.
A little bit of this and a little byte of that can cause bloatware.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply