January 24, 2006 at 11:23 am
We've been able to successfully apply SP4 to all of our SQL Servers except one. Although the service pack went on to the default instance (which we don't use) without a problem, it consistently fails on the named instances with an error in the replcom script:
Creating procedure sp_MShelpobjectpublications
Msg 134, Level 16, State 2, Server SDEVDB02\DDB02, Procedure sp_MShelpobjectpublications, Line 80
The variable name '@object_name' has already been declared. Variable
names must be unique within a query batch or stored procedure.
All instances on the server were running SQL 2K with SP3 before the upgrade, and Windows Server 2003 Enterprise. I've tried numerous times (rebuilding the instance between each attempt), attempting various fixes such as stopping unnecessary services, allowing named pipes, etc., always with the same result. The only environmental difference between this server and those that upgraded without error is that it is outside of our firewall. Could this be the problem? Has anyone else had this trouble?
GG
January 24, 2006 at 5:01 pm
You may want to download sp4 again. The error is a sql syntax error during a create procedure statement. Perhaps the script got corrupted.
January 24, 2006 at 8:23 pm
Agreed. This error is definitely a SQL syntax error. Your network configuration is not an issue here at all.
K. Brian Kelley
@kbriankelley
January 25, 2006 at 5:45 am
A good thought, but I've already tried that. I also copied the same SP4 install package to another server and was able to use it to upgrade the instances on that server with no problem. Beyond that, the same script was used on the default instance of the failing server, and that went on with no problem. It's only on the named instances that have user databases that the script fails.
I copied the script for the sp_MShelpobjectpublications proc that keeps failing to QA on one of the failing instances and parsed it, and no errors come up. Seems like it has to be something outside of the script that either interferes or affects how it is interpreted, but I'm stumped as to what that could be.
GG
January 25, 2006 at 7:09 am
Does the named instances differ from the default instance in any way? Collation, Language settings, etc.?
K. Brian Kelley
@kbriankelley
January 25, 2006 at 8:01 am
No, those kinds of properties are the same on all instances, and pretty much the installation defaults.
GG
January 25, 2006 at 8:46 am
Are there any additional errors in your sqlsp.log ? This should be in the %SYSTEMROOT% directory on the server. This might give a clue as to if there is another issue that's being masked by the very obvious error.
K. Brian Kelley
@kbriankelley
January 25, 2006 at 9:57 am
Comparing the sqlsp.log from a failed attempt to that of another server that was successful, the first difference (other than instance name and locations) is when the script fails:
11:59:09 Process Exit Code: (1)
11:59:31 Error running script: replcom.sql (1)
GG
January 25, 2006 at 11:10 am
In this case you're going to probably want to call Microsoft support. The obvious points of failure aren't the cause.
K. Brian Kelley
@kbriankelley
January 25, 2006 at 1:22 pm
OK, I appreciate your time.
GG
January 25, 2006 at 2:10 pm
just a guess, are the entrys in the sysservers correct?
January 26, 2006 at 6:28 am
Those entries are correct, but I'm going to rummage around in the other system tables to look for anything amiss. Otherwise, I guess it'll just have to stay on SP3a. Thanks
GG
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply