SQL 2000 EM does not reflect SP4

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

jremmc - 14 Jul 2008 22:02 GMT

Moved SQL to new hardware with same name and IP. All went well except SQL
Enterprise Manager "About" reflects RTM not SP4 level. (SQL Instance does
reflect SP4 level.) Did not notice discrepancy until after we brought up and
started using the front-end apps (e.g. WSS 3.0 and 3rd party).

Should we simply reapply SP4 to server? Will this affect databases in any way?

Also, incidentally, based on an unrelated comment I came across googling
issue (comment caught my eye), could this discrepancy have happened because I
stopped all SQL services (as per readme) prior to applying SP4?

Thanks,
jremmc

Reply to this Message

Andrew J. Kelly - 15 Jul 2008 02:30 GMT

Is EM on the server itself? If not you need to apply the service pack to
that machine as well. If it is you might not have applied it to the client
tools. But in any case are you sure the about is showing the SQL Server info
and not the MMC? I don't have 2000 to see what it looks like anymore.

Signature

Andrew J. Kelly SQL MVP
Solid Quality Mentors

> Moved SQL to new hardware with same name and IP. All went well except SQL
> Enterprise Manager "About" reflects RTM not SP4 level. (SQL Instance does
[quoted text clipped - 12 lines]
> Thanks,
> jremmc

Reply to this Message

Charles Wang [MSFT] - 15 Jul 2008 08:54 GMT

Hi Jremmc,
Regarding your concern, "could this discrepancy have happened because I
stopped all SQL services (as per readme) prior to applying SP4?", no, it
would not cause the discrepancy. I never saw this behavior before. Could
you please let me know how you moved your SQL to your new hardware with
same name and IP?

To eliminate the discrepancy, you need to reapply SQL Server 2000 SP4 to
the server. Before you install your SQL Server 2000 SP4, I recommend that
you first backup your SQL Server databases, stop all applications and
services that make connections to the SQL Server instance. For more
information, you can refer to:
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b
0d2a3/ReadmeSql2k32sp4.htm#_prepare_for_sp4_installation_wluf

Hope this helps. If you have any other questions or concerns, please feel
free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
===========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
===========================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
============================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

=========================================================

Reply to this Message

jremmc - 15 Jul 2008 16:14 GMT

Hi Charles,

I posted question here about moving and followed procedure based on replies
plus my experience (moving both an Exchange 2003 server and a file server to
new servers with same name and IP). The basics below: ("SQL Server Old" is
original server and "SQL Server New" is new server)

I just found out I need to install SQL Server 2000 Analysis Services. My
plan is to reapply SP4 to resolve EM issue, make sure it is resolved, then
install Analysis Services, then reapply SP4. Is that the right way to go?

SQL Move Procedure:
1. Set up a new server with temporary name, same partitions, same OS and OS
settings (e.g. environment), SP level and hotfixes/patches. Do not join
domain; leave in workgroup
2. Record locations of all databases and files/folders on SQL Server Old
3. Take screen shots of SQL settings in Enterprise Manager (I used OneNote,
worked great)
4. Shut Down all servers that connect to SQL (e.g. WSS 3.0)
5. Stop all SQL Services on SQL Server Old
6. Copy database location folders from SQL Server Old to a temporary
location on SQL Server New (databases are in default location of C:\Program
Files\Microsoft SQL Server\MSSQL\Data folder)
7. Take SQL Server Old offline
8. Reset SQL Server account in Active Directory
9. Rename SQL Server New to SQL Server Old and set IP to Old’s IP; reboot
10. Join SQL Server to domain, reboot
11. Check Event Log, ipconfig, connectivity, etc. and add SQL Service
Account to server’s Administrators group
12. Verify permissions on files and folders match old server
13. Install SQL 2000 with same settings
14. Stop all SQL Services as per SP4 readme
15. Install SQL SP4; reboot
16. Check Event Viewer for errors
17. Check Settings in SQL Enterprise Manager against screen shots taken of
old server
18. Stop all SQL Services (MSSQLServer, SQLSERVERAGENT, Distributed
Transaction Coordinator)
19. Copy all existing contents of C:\Program Files\Microsoft SQL
Server\MSSQL\Data folder to another location (just in case)
20. Copy all contents of the database location folders from temporary
location to same location as on old server, overwriting existing contents
21. Check NTFS permissions on the SQL folders (should match old)
22. Check NTFS permissions on the databases and the logs (should match old)
23. Start SQL Services
24. Test
25. Start up other servers that connect to SQL (e.g. WSS 3.0)
26. Test
27. Done

Everything seemed to go fine; no errors in Event Logs on SQL server or the
connecting servers (e.g. WSS 3.0). The new server has been up several weeks.

Thanks,
jremmc

> Hi Jremmc,
> Regarding your concern, "could this discrepancy have happened because I
[quoted text clipped - 43 lines]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================

Reply to this Message

Charles Wang [MSFT] - 17 Jul 2008 07:41 GMT

Hi Jremmc,
I agree with your steps. You can first apply SP4 to check if the original
issue is resolved and then install SSAS and reapply SP4. Regarding your
original procedure, I could not find any problem though it is not an
official support way, that means, you need to perform test to check if it
can work for you before you take such action. :)

If you have any other questions or concerns, please feel free to let me
know.

Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
=========================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

=========================================================

Reply to this Message

jremmc - 17 Jul 2008 15:14 GMT

Hi Charles,

Thanks. I will SP4, reboot, then SSAS followed by SP4 immediately after,
then reboot.

I forgot to mention that the actual SQL EM files (flat files on hard drive)
are SP4 version. When I found that SQL EM "About SQL EM" dialog box showed
RTM version, I checked the actual EM flat files (most, anyway, including what
I thought were the key files), thinking I would try simply copying the SP4
versions over, but the files (at least those I checked) were already SP4
version.

jremmc

> Hi Jremmc,
> I agree with your steps. You can first apply SP4 to check if the original
[quoted text clipped - 20 lines]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> =========================================================

Reply to this Message

Charles Wang [MSFT] - 21 Jul 2008 04:48 GMT

Hi Jremmc,
Thank you for your detailed description. If the existing files are already SP4, but the displayed
information in EM is RTM, I think that the registry information is not updated correctly. In this
case, re-applying SQL Server 2000 SP4 installation should help.

Please feel free to post back when you encounter any further issues or questions. I am very glad
to work with you for further assistance.

Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@microsoft.com.
=========================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

=========================================================

Reply to this Message