Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SP4 Setup Failure Expand / Collapse
Author
Message
Posted Thursday, July 13, 2006 3:16 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 9:36 AM
Points: 140, Visits: 229

Hello All,

I'm trying to install SP4 on a multiple instance SQL Server 2000 server and I'm getting the following error:

 Error running script: replsys.sql(1)

When I check the replsys.out file, here's what I see:

[DBNETLIB]General network error. Check your network documentation.
[DBNETLIB]ConnectionRead (recv()).

Has anybody seen this error before?

I successfully install SP4 on another SQL instance running on that same server without any problems. Whatever the problem I'm having with the first instance is isolated to that instance.

Thanks in advance for any help!! It's really appreciated.

Ronnie

Post #294262
Posted Monday, July 17, 2006 8:00 AM
SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Friday, May 18, 2007 3:36 PM
Points: 10,039, Visits: 1
No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!
Post #294813
Posted Monday, July 17, 2006 8:31 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 11:01 PM
Points: 140, Visits: 124
Sounds like the service pack installer is having problems connecting to the instance via shared memory. The service pack attempts to connect via shared memory and places the sql server in single user mode, after it checks for connectivity problems (i.e. osql.exe -Slpc:InstanceName, where InstanceName is your SQL Server instance name). If it cannot connect via shared memory because of a Windows resource problem, a reboot is in order.

At what point in your sqlsp.log are you noticing the issues? Immediately, or after the initial checks have been performed? If it is after the the initial connectivity check, there may be something else going on that we have experienced in the past, but I would rather not type our problem/resolution if it is not relevant to what you are experiencing.



Post #294851
Posted Monday, July 17, 2006 1:43 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 9:36 AM
Points: 140, Visits: 229

Thanks for getting back to me on this.

The update is failing right after it trys to run the replsys.sql

Here are the last few lines of the sqlsp.log file:

16:46:52 Begin ServPriv (EPA)
16:46:52 End ServPriv()
16:46:53 Upgrading databases
16:46:54 Upgrading databases on instance 'EPA'
16:46:54 C:\DOCUME~1\RONNIE~1.ISO\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe  -Silent 1 -Action 6 -Service MSSQL$EPA 
16:46:54 Process Exit Code: (0)
16:46:54 C:\DOCUME~1\RONNIE~1.ISO\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe  -Silent 1 -Action 6 -Service MSSQL$EPA 
16:46:54 Process Exit Code: (0)
16:46:54 C:\DOCUME~1\RONNIE~1.ISO\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe  -Silent 1 -Action 1 -Service MSSQL$EPA   -StartupOptions \-T4022 \-T4010 \-m
16:47:05 Process Exit Code: (0)
16:47:05 D:\SQL2KSP4\x86\BINN\osql.exe  -Slpc:SQLSVRDEV\EPA -b -n -d master -o "C:\Program Files\Microsoft SQL Server\MSSQL$EPA\install\replsys.out" -i "C:\Program Files\Microsoft SQL Server\MSSQL$EPA\install\replsys.sql" -E
16:47:05 Process Exit Code: (1)
16:47:10 Error running script: replsys.sql (1)
16:47:10 C:\DOCUME~1\RONNIE~1.ISO\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe  -Silent 1 -Action 6 -Service MSSQL$EPA 
16:47:25 Process Exit Code: (0)
16:47:25 Action CleanUpInstall:
16:47:25 Installation Failed.

Thanks again.

Ronnie

Post #294965
Posted Monday, July 17, 2006 3:51 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, November 18, 2014 11:01 PM
Points: 140, Visits: 124
No problem.
Thanks for the log post. I am not sure if this will help or not, but there maybe another process that is logging onto your SQL Server prior to the service pack updating it. I would recommend stopping your instance and restarting it in single user mode, just like the script shows (or from the command-line sqlservr ... i.e. MSSQL\Binn\sqlservr -c -m -T4022 -T4010), and from another command line session logon to your instance as the script does i.e. osql -Slpc:SQLSVRDEV\EPA -d master (you can omit the -n and - b if you like). If this is the same problem that plagued us on a few systems, you should get something like the database is in use or only one connection is allowed while in single user mode.

For us, we had a Webservice running on the SQL Server (WSUS) that ran as the NT Authority/SYSTEM account, and reconnected to the database as soon as it became available. That was locking out the service pack from connecting and running the replsys.sql file. If something else is blocking you, I would recommend that if you have IIS or a Webserver running on your SQL Server machine, temporarily stop it or just the Web application that is running on it, until your update is complete. Otherwise, you may have hunt down and temporarily stop whatever application is connecting to your database while you update the system.

Hope that this helps ....



Post #295011
Posted Monday, July 24, 2006 4:06 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 18, 2014 2:36 PM
Points: 1, Visits: 46
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.
 

 

Pete DeShan

Oracle/SQL Server DBA, System Architect

petedeshan@bellsouth.net

Post #296910
Posted Wednesday, July 26, 2006 3:10 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 9:36 AM
Points: 140, Visits: 229

Pete - You are my hero!!

Thank you very much. Your instructions worked perfectly. One thing I relized I had to do for some reason is stop the default SQL instance from running. I'm running multiple instances on my SQL server and for some reason when I tried to start the instance in single user mode, I received several errors complaining about the ERRORLOG under the default server instance. Once I stopped that instance and followed your instructions, Everything worked like a charm.

I agree with you that MS should address this and either put out a new version of the SP4 and/or document how to resolve this problem. Finding a resolution is like finding buried treasure. Geezz!

Thanks again!

Ronnie

Post #297595
Posted Saturday, June 19, 2010 1:17 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, November 26, 2014 9:34 PM
Points: 284, Visits: 265

1. Check if distribution database exist though the Replication is dropped
2. If so drop the distribution database
3. To drop the distribution database by over - restoring of some user database
4. Perform the patching / SQL SP again.

It has worked fine for me


Sivaprasad S - [ SIVA ]http://sivasql.blogspot.com/
Post #939939
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse