July 9, 2003 at 9:15 am
I installed Windows 2000 SP4 on my system and on reboot I got a message stating my Sql Server 2000 installtion was corrupt or tampered with and to uninstall and reinstall.
Anyone had or know about this error? Can I fix this or do I REALLY have to re-install?
Man, way to go MS!
Bill Kirkman
DAX Innovations, Inc.
Bill Kirkman
DAX Innovations, Inc.
July 14, 2003 at 12:00 pm
This was removed by the editor as SPAM
July 14, 2003 at 1:36 pm
I am quite curious about this as well due to the vulnerabilities that are supposed to be addressed by SP4 (see thread under Security). Anyone else care to share their expriences, good or bad, with loading Win2K SP4?
My hovercraft is full of eels.
July 16, 2003 at 9:55 am
Procrastinators - here is your justification for postponing installation of W2K SP4: http://www.w2knews.com/anecdotes.htm.
Note that 2 post SP SQL Server problems are mentioned along with a successful multi-server upgrade. I guess I should never entertain the thought of installing a MS SP unless it ends in a letter.
Regards,
Sandman
My hovercraft is full of eels.
July 16, 2003 at 10:14 am
I installed SP4 on a test machine with SQL 2000 Enterprise. Seemed ok, so after a couple of days I put it on a production machine -- no problems so far -- note this machine only runs SQL 2000 Enterprise and IIS5.0, and a few services that just can't be eliminated.
Hoping you all have the same experience and also that I don't have to eat this posting in a few days time ...
July 28, 2003 at 8:55 am
Having a very odd issue of one of my Primary DB Servers (WIN2K SP4 /SQL2K SP3) one of my replicated DBs when I exec a stored proc just sits and returns no results... A exact copy (not a publisher or /subscriber) returns the results in under 1 sec... Any clues ?
Jim Babington
Jbabington
Jbabington@hotmail.com
July 28, 2003 at 9:44 am
Installed it early here on the SSC server. Been running almost 3 weeks with no issues.
Steve Jones
August 19, 2003 at 3:18 am
I ran into the the following problem after installing Windows 2000
Service Pack 4 on a Cluster.
The SQL Server Agent jobs that run operating system commands, and were
running and enabled prior to the upgrade, don't seem to run after
installing Sp4 of Windows.
T-SQL jobs don't seem to be affected. I noticed this after some of my
jobs, which were scheduled to run every 15 minutes didn't run for a
couple of hours. I had to delete the schedule and re-create it before
it started working.
Other CmdExec jobs that I didn't do this for also didn't run.
Re-starting SQL Server Agent did not help either.
(I have installed Sp4 on a couple of other machines, and did not
experience this problem)
Any help on this matter would be greatly appreciated.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy