SQL Server SP4 has serious issues that should be addressed by Microsoft.
We had to devise a work-around to get it to work(SQL Server SP4 if it failed on the replsys.sql script) but it does work as proved by installation on 8 servers, so it is full proof. It was tested without doing this special method on the other servers and they bombed on replsys.sql as well.
After detailed research (10 hours), it was determined that no one on Earth including Microsoft knew how to install SQL Server SP4 if it failed on the replsys.sql script. I followed every single thread in Google and Microsoft knowledge base and nothing worked. So I knew I was on my own (as usual).
I knew what the issue was but it was difficult to prove since the setup.exe was a compiled program.
Method Starts Here:
The method is quite simple:
run \\x86\setup\setupsql k=dbg sp4 in debug mode, you must run in debug mode for it to work, since it prompts for each step Use windows or SQL authentication, When you get to the prompt to run replsys.sql script, stop
IMPORTANT OR it will bomb here
Prior to pressing Yes here at the replsys.sql, you must stop the MSSQL$Service if it is running and set the –m parameter in the startup parameters. Then start the MSSQL$Service (in single user mode as specified by –m parameter). As soon as it starts, delay 1-2 secs ONLY, and no more to allow the database to come up, and then press YES to run the REPLSYS.sql script
Press Yes to run all the scripts up to and including 80sp4-tools.sql as the last one,
Then when you are running the SP_vupgrade_replication script.sql script, stop and do the same below
IMPORTANT OR it will bomb here
Prior to pressing Yes before the SP_vupgrade_replication script, you must stop the MSSQL$Service if it is running and set the –m parameter.
In the startup parameters. Then start the MSSQL$Service (in single user mode as specified by –m parameter). As soon as it starts, delay 1-2 secs ONLY, and no more to allow the database to come up, and then press YES to run the SP_vupgrade_replication script
You can then continue, and the setup will complete normally.
You can now run the SQL Server 2162 patch since it does not require single user mode without any intervention or special DBA fixes above.
Method Stops Here
You can simulate the exact error in the replsys.out file that occurs when SP4 bombs, by simply bring up SQL Server in single user mode, open a session to grab the single session, and then try to run replsys.sql, in an existing query analyzer session, and it will bomb, and give the exact error message as seen when SP4 bombs.
Microsoft needs to create a fix for this ASAP for it is a major issue with no resolutions as evidenced by the internet search.
I had to spend a total of 15 hours analysis to get this to work and there appears to be similar bugs in the original SQL2000 RTM release, in that the messages.sql script was causing a single user mode race as well.
st1\:* {BEHAVIOR: url(#ieooui)}@font-face {font-family: Monotype Corsiva;}@font-face {font-family: Comic Sans MS;}@font-face {font-family: Georgia;}@font-face {font-family: MS Serif;}@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; }P.MsoNormal {FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"}LI.MsoNormal {FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"}DIV.MsoNormal {FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"}DIV.Section1 {page: Section1}