RE: SQL 2000 Upgrade REPLSYS.SQL error
From: mehul (mehul_at_discussions.microsoft.com)
Date: 01/22/05
- Next message: Bernie V: "database size"
- Previous message: Mandy: "Re: Login Setup..."
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 22 Jan 2005 04:49:02 -0800
I have a very similar problem. Server is Compaq ML570G1 with dual Processor
PIII 933 MHZ and 4GB RAM running windows 2000 advance server. i was upgrading
from sql 7 to 2000 and ran in to the same issue. After I changed the
replsys.msg as mentioned in this post, I still get the same error with
replsys.sql. The replsys.out says error "Insufficient System Memory" - I
didnt monitor the memory usage during the upgrade, but otherwise system with
4GB has always above 3GB avaliable memory.
Any help would be greatly appreciated.
Thanks in advance,
Mehul.
"Vikram Jayaram [MS]" wrote:
>
> Here's my analysis of the situation along with what could be a good
> resolution -
>
> Cause
> =====
> - You probably had SQL 7.0 and had earlier tried to upgrade to SQL 2000,
> which failed due to a different issue perhaps?
> - So now, when you try to run the SQL 2000 RTM setup again, it realises
> that the previous install was inscomplete and therefore offers to retry the
> upgrade again.
> - Now the setup is failing while executing the replsys.sql script file with
> the above errors.
> - This happening because when you try to setup SP3, it changes the
> xp_execresultset from being an extended procedure to a standard SQL
> procedure.
>
>
> Resolution
> =========
> - Modify the replsys.sql script file; search for "xp_execresultset"; change
> the following statement:
> if exists (select * from sysobjects
> where name = 'xp_execresultset')
> execute dbo.sp_dropextendedproc 'xp_execresultset'
> go
>
> - to the following :
> if exists (select * from sysobjects
> where type = 'P' and name = 'xp_execresultset')
> begin
> drop procedure dbo.xp_execresultset
> end
> go
>
> - Copy the CD to a local folder; replace the replsys.sql file with the
> above modified version.
> - Rerun the setup with the new file. You could also rerun the setup in
> debug mode from \x86\setup by executing the following from the command
> prompt as:-
> setupsql k=Dbg
>
> - When it comes to the message.sql script, start SQL from a Command prompt
> and then continue executing the messages.sql script from setup. (This will
> ensure that
> the issue mentioned in article # 300676
> (<http://support.microsoft.com/?id=300676>) is not seen and that the server
> is started before the messages.sql script is executed).
> - When the debug interrupt comes to the point where replsys.sql script is
> to be executed, go ahead and ensure that the modified file is in place, and
> then let the
> setup continue.
> - It should complete properly then.
>
> Also note, if the object doesn't exist in sysobjects, it won't try to do
> the sp_dropextendedproc in the replsys.sql script during setup.
>
> drop procedure master.dbo.xp_execresultset
>
> HTH!
>
>
> Vikram Jayaram
> Microsoft, SQL Server
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
>
>
- Next message: Bernie V: "database size"
- Previous message: Mandy: "Re: Login Setup..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
