Showing posts with label sp4. Show all posts
Showing posts with label sp4. Show all posts

Wednesday, March 28, 2012

IA64 SP4 Install Problem

I am having trouble installing SP4 on my IA64. Like the instructions said in
section 1.1 of the help file I have changed it to allow Unsigned drivers to
Silently Succeed. However I am still getting a failure.
On thing to note when I run the following command I get some different
results than the help file say I sould.
SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
SERVERPROPERTY('ProductVersion')
SP3
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
Windows NT 5.2 (Build 3790: )
8.00.818
About a year ago MS and Oracle were working with me to solve a memory leak
issue and I think that may be related to why SP4 wont install but I cant be
sure.
The only hint as to what the error is at the begining of the logfile (See
below).
05/18/2005 08:29:49.910
================================================== ==============================
05/18/2005 08:29:49.910 Hotfix package launched
05/18/2005 08:29:49.910 Local Computer:
05/18/2005 08:29:49.910 Target Details: SG1
05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:49.910 windir = C:\WINDOWS
05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
05/18/2005 08:29:49.910
05/18/2005 08:29:50.850 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 Product Details:
05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
05/18/2005 08:29:51.110 build = 2039
05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
SQL Server 2000 64-bit features including the relational database engine and
Analysis Services. If you have not done so already, back up the master and
msdb databases and stop all database programs and services before proceeding.
05/18/2005 08:29:51.110 kbarticle = KB884525
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 package = HotFix1
05/18/2005 08:29:51.110 productname = SQLOLAP64
05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
Pack 4
05/18/2005 08:29:51.110 splevel = RTM,4
05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:51.110 version = 8
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 File Group Details: MSP
05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress
05/18/2005 08:29:51.110 File Details: sqlrun.msp
05/18/2005 08:29:51.110 lockedfilecheck = 1
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 Instance Details: MSSQLServer
05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
05/18/2005 08:29:51.110 default = TRUE
05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
05/18/2005 08:29:51.110 id = MSSQLServer
05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL
05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 name = MSSQLServer
05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
05/18/2005 08:29:51.110 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.110 servicename = MSSQLServer
05/18/2005 08:29:51.110 sku = ENTERPRISE
05/18/2005 08:29:51.110 sp = RTM
05/18/2005 08:29:51.110 type = Liberty
05/18/2005 08:29:51.110 version = 8
Anybody?
"Jim" wrote:

> I am having trouble installing SP4 on my IA64. Like the instructions said in
> section 1.1 of the help file I have changed it to allow Unsigned drivers to
> Silently Succeed. However I am still getting a failure.
> On thing to note when I run the following command I get some different
> results than the help file say I sould.
> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
> SERVERPROPERTY('ProductVersion')
> SP3
> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
> Windows NT 5.2 (Build 3790: )
> 8.00.818
> About a year ago MS and Oracle were working with me to solve a memory leak
> issue and I think that may be related to why SP4 wont install but I cant be
> sure.
> The only hint as to what the error is at the begining of the logfile (See
> below).
> 05/18/2005 08:29:49.910
> ================================================== ==============================
> 05/18/2005 08:29:49.910 Hotfix package launched
> 05/18/2005 08:29:49.910 Local Computer:
> 05/18/2005 08:29:49.910 Target Details: SG1
> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
> 05/18/2005 08:29:49.910
> 05/18/2005 08:29:50.850 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 Product Details:
> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
> 05/18/2005 08:29:51.110 build = 2039
> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
> SQL Server 2000 64-bit features including the relational database engine and
> Analysis Services. If you have not done so already, back up the master and
> msdb databases and stop all database programs and services before proceeding.
> 05/18/2005 08:29:51.110 kbarticle = KB884525
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 package = HotFix1
> 05/18/2005 08:29:51.110 productname = SQLOLAP64
> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
> Pack 4
> 05/18/2005 08:29:51.110 splevel = RTM,4
> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:51.110 version = 8
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 File Group Details: MSP
> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress
> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
> 05/18/2005 08:29:51.110 lockedfilecheck = 1
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
> 05/18/2005 08:29:51.110 default = TRUE
> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
> 05/18/2005 08:29:51.110 id = MSSQLServer
> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
> SQL Server\MSSQL
> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
> Server\MSSQL
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 name = MSSQLServer
> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
> 05/18/2005 08:29:51.110 productcode =
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.110 servicename = MSSQLServer
> 05/18/2005 08:29:51.110 sku = ENTERPRISE
> 05/18/2005 08:29:51.110 sp = RTM
> 05/18/2005 08:29:51.110 type = Liberty
> 05/18/2005 08:29:51.110 version = 8
|||Sorry don't have an answer for you. If no one else pipes in you may want to
give MS PSS a call.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:D129328E-93E4-4E2A-BC6B-129B9D7341AE@.microsoft.com...[vbcol=seagreen]
> Anybody?
> "Jim" wrote:
|||I'm getting the same error as well. I'm thinking it has something to
do with a previous version of a hotfix that was applied:
SELECT @.@.Version
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003
15:32:45 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition (64-bit) on Windows NT 5.2 (Build 3790: )
05/26/2005 21:10:33.107
================================================== ==============================
05/26/2005 21:10:33.107 Hotfix package launched
05/26/2005 21:10:33.107 Local Computer:
05/26/2005 21:10:33.107 Target Details: OLYMPOS
05/26/2005 21:10:33.107 commonfilesdir = C:\Program Files\Common
Files
05/26/2005 21:10:33.107 programfilesdir = C:\Program Files
05/26/2005 21:10:33.107 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:33.107 windir = C:\WINDOWS
05/26/2005 21:10:33.107 winsysdir = C:\WINDOWS\system32
05/26/2005 21:10:33.107
05/26/2005 21:10:34.756 The following product instance was
disqualified because a parent product instance of the same product
code was found: {0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.959 The following product instance was
disqualified because a parent product instance of the same product
code was found: {FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.959 Product Details:
05/26/2005 21:10:34.959 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.959 build = 2039
05/26/2005 21:10:34.959 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.959 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.959 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.959 kbarticle = KB884525
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.959 package = HotFix1
05/26/2005 21:10:34.959 productname = SQLOLAP64
05/26/2005 21:10:34.959 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.959 splevel = RTM,4
05/26/2005 21:10:34.959 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.959 version = 8
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 File Group Details: MSP
05/26/2005 21:10:34.959 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.959 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.959 File Details: sqlrun.msp
05/26/2005 21:10:34.959 lockedfilecheck = 1
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 Instance Details: PRODUCTION
05/26/2005 21:10:34.959 = Software\Microsoft\Microsoft SQL
Server\PRODUCTION\Setup
05/26/2005 21:10:34.959 agentservicename = SQLAgent$PRODUCTION
05/26/2005 21:10:34.959 hiveregpath = Software\Microsoft\Microsoft
SQL Server\PRODUCTION
05/26/2005 21:10:34.959 id = PRODUCTION
05/26/2005 21:10:34.959 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.969 name = PRODUCTION
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 servicename = MSSQL$PRODUCTION
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\RMSWORK\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = OLAP
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: SQL Tools
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\80\Tools
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = SQL Tools
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: OLAPClient
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Common
Files\system\OLE DB
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = OLAPClient
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:51.286 Authenticating user using Windows
Authentication
05/26/2005 21:10:51.306 SQL Service MSSQL$PRODUCTION was previously
running, ready for authentication
05/26/2005 21:10:51.306 SQL Agent Service SQLAgent$PRODUCTION was
previously running
05/26/2005 21:10:51.489 User authentication was successful
05/26/2005 21:10:54.787 Attempting to install product: SQLOLAP64
|||Hi there:
i am also facing the same problem when i try installing SQL2k SP4 on IA serversWere you able ti fix it. Will appreciate any help.
Kind Regards,
Roshan
From http://www.developmentnow.com/g/118_2005_5_0_0_524275/IA64-SP4-Install-Problem.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
Posted by perplexingmqwo at 2:16 AM 0 comments
Labels: , , , , , , , , , , , , , , ,

IA64 SP4 Install Problem

I am having trouble installing SP4 on my IA64. Like the instructions said in
section 1.1 of the help file I have changed it to allow Unsigned drivers to
Silently Succeed. However I am still getting a failure.
On thing to note when I run the following command I get some different
results than the help file say I sould.
SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
SERVERPROPERTY('ProductVersion')
SP3
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) o
n
Windows NT 5.2 (Build 3790: )
8.00.818
About a year ago MS and Oracle were working with me to solve a memory leak
issue and I think that may be related to why SP4 wont install but I cant be
sure.
The only hint as to what the error is at the begining of the logfile (See
below).
05/18/2005 08:29:49.910
========================================
====================================
====
05/18/2005 08:29:49.910 Hotfix package launched
05/18/2005 08:29:49.910 Local Computer:
05/18/2005 08:29:49.910 Target Details: SG1
05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:49.910 windir = C:\WINDOWS
05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
05/18/2005 08:29:49.910
05/18/2005 08:29:50.850 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 Product Details:
05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
05/18/2005 08:29:51.110 build = 2039
05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
SQL Server 2000 64-bit features including the relational database engine and
Analysis Services. If you have not done so already, back up the master and
msdb databases and stop all database programs and services before proceeding
.
05/18/2005 08:29:51.110 kbarticle = KB884525
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 package = HotFix1
05/18/2005 08:29:51.110 productname = SQLOLAP64
05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
Pack 4
05/18/2005 08:29:51.110 splevel = RTM,4
05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:51.110 version = 8
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 File Group Details: MSP
05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress
05/18/2005 08:29:51.110 File Details: sqlrun.msp
05/18/2005 08:29:51.110 lockedfilecheck = 1
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 Instance Details: MSSQLServer
05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
05/18/2005 08:29:51.110 default = TRUE
05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
05/18/2005 08:29:51.110 id = MSSQLServer
05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL
05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 name = MSSQLServer
05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
05/18/2005 08:29:51.110 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.110 servicename = MSSQLServer
05/18/2005 08:29:51.110 sku = ENTERPRISE
05/18/2005 08:29:51.110 sp = RTM
05/18/2005 08:29:51.110 type = Liberty
05/18/2005 08:29:51.110 version = 8Anybody?
"Jim" wrote:

> I am having trouble installing SP4 on my IA64. Like the instructions said
in
> section 1.1 of the help file I have changed it to allow Unsigned drivers t
o
> Silently Succeed. However I am still getting a failure.
> On thing to note when I run the following command I get some different
> results than the help file say I sould.
> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
> SERVERPROPERTY('ProductVersion')
> SP3
> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit)
on
> Windows NT 5.2 (Build 3790: )
> 8.00.818
> About a year ago MS and Oracle were working with me to solve a memory leak
> issue and I think that may be related to why SP4 wont install but I cant b
e
> sure.
> The only hint as to what the error is at the begining of the logfile (See
> below).
> 05/18/2005 08:29:49.910
> ========================================
==================================
======
> 05/18/2005 08:29:49.910 Hotfix package launched
> 05/18/2005 08:29:49.910 Local Computer:
> 05/18/2005 08:29:49.910 Target Details: SG1
> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
> 05/18/2005 08:29:49.910
> 05/18/2005 08:29:50.850 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 Product Details:
> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
> 05/18/2005 08:29:51.110 build = 2039
> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on al
l
> SQL Server 2000 64-bit features including the relational database engine a
nd
> Analysis Services. If you have not done so already, back up the master an
d
> msdb databases and stop all database programs and services before proceedi
ng.
> 05/18/2005 08:29:51.110 kbarticle = KB884525
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 package = HotFix1
> 05/18/2005 08:29:51.110 productname = SQLOLAP64
> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Servi
ce
> Pack 4
> 05/18/2005 08:29:51.110 splevel = RTM,4
> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:51.110 version = 8
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 File Group Details: MSP
> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress
> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
> 05/18/2005 08:29:51.110 lockedfilecheck = 1
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
> 05/18/2005 08:29:51.110 default = TRUE
> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
> 05/18/2005 08:29:51.110 id = MSSQLServer
> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
> SQL Server\MSSQL
> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
> Server\MSSQL
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 name = MSSQLServer
> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
> 05/18/2005 08:29:51.110 productcode =
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.110 servicename = MSSQLServer
> 05/18/2005 08:29:51.110 sku = ENTERPRISE
> 05/18/2005 08:29:51.110 sp = RTM
> 05/18/2005 08:29:51.110 type = Liberty
> 05/18/2005 08:29:51.110 version = 8|||Sorry don't have an answer for you. If no one else pipes in you may want to
give MS PSS a call.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:D129328E-93E4-4E2A-BC6B-129B9D7341AE@.microsoft.com...[vbcol=seagreen]
> Anybody?
> "Jim" wrote:
>|||I'm getting the same error as well. I'm thinking it has something to
do with a previous version of a hotfix that was applied:
SELECT @.@.Version
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003
15:32:45 Copyright (c) 1988-2003 Microsoft Corporation Enterprise
Edition (64-bit) on Windows NT 5.2 (Build 3790: )
05/26/2005 21:10:33.107
========================================
====================================
====
05/26/2005 21:10:33.107 Hotfix package launched
05/26/2005 21:10:33.107 Local Computer:
05/26/2005 21:10:33.107 Target Details: OLYMPOS
05/26/2005 21:10:33.107 commonfilesdir = C:\Program Files\Common
Files
05/26/2005 21:10:33.107 programfilesdir = C:\Program Files
05/26/2005 21:10:33.107 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:33.107 windir = C:\WINDOWS
05/26/2005 21:10:33.107 winsysdir = C:\WINDOWS\system32
05/26/2005 21:10:33.107
05/26/2005 21:10:34.756 The following product instance was
disqualified because a parent product instance of the same product
code was found: {0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.959 The following product instance was
disqualified because a parent product instance of the same product
code was found: {FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.959 Product Details:
05/26/2005 21:10:34.959 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.959 build = 2039
05/26/2005 21:10:34.959 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.959 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.959 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.959 kbarticle = KB884525
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.959 package = HotFix1
05/26/2005 21:10:34.959 productname = SQLOLAP64
05/26/2005 21:10:34.959 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.959 splevel = RTM,4
05/26/2005 21:10:34.959 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.959 version = 8
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 File Group Details: MSP
05/26/2005 21:10:34.959 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.959 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.959 File Details: sqlrun.msp
05/26/2005 21:10:34.959 lockedfilecheck = 1
05/26/2005 21:10:34.959 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 Instance Details: PRODUCTION
05/26/2005 21:10:34.959 = Software\Microsoft\Microsoft SQL
Server\PRODUCTION\Setup
05/26/2005 21:10:34.959 agentservicename = SQLAgent$PRODUCTION
05/26/2005 21:10:34.959 hiveregpath = Software\Microsoft\Microsoft
SQL Server\PRODUCTION
05/26/2005 21:10:34.959 id = PRODUCTION
05/26/2005 21:10:34.959 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$PRODUCTION
05/26/2005 21:10:34.959 lcid = 1033
05/26/2005 21:10:34.969 name = PRODUCTION
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 servicename = MSSQL$PRODUCTION
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\RMSWORK\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = OLAP
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: SQL Tools
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\80\Tools
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = SQL Tools
05/26/2005 21:10:34.969 productcode =
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotF
ix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =
\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =
<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: OLAPClient
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Common
Files\system\OLE DB
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = OLAPClient
05/26/2005 21:10:34.969 productcode =
{FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:51.286 Authenticating user using Windows
Authentication
05/26/2005 21:10:51.306 SQL Service MSSQL$PRODUCTION was previously
running, ready for authentication
05/26/2005 21:10:51.306 SQL Agent Service SQLAgent$PRODUCTION was
previously running
05/26/2005 21:10:51.489 User authentication was successful
05/26/2005 21:10:54.787 Attempting to install product: SQLOLAP64|||Hi there:
i am also facing the same problem when i try installing SQL2k SP4 on IA serv
ersWere you able ti fix it. Will appreciate any help.
Kind Regards,
Roshan
From m.htm" target="_blank">http://www.developmentnow.com/g/118...le
m.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
Posted by perplexingmqwo at 2:15 AM 0 comments
Labels: , , , , , , , , , , , , , , ,

IA64 SP4 Install Problem

I am having trouble installing SP4 on my IA64. Like the instructions said in
section 1.1 of the help file I have changed it to allow Unsigned drivers to
Silently Succeed. However I am still getting a failure.
On thing to note when I run the following command I get some different
results than the help file say I sould.
SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
SERVERPROPERTY('ProductVersion')
SP3
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
Windows NT 5.2 (Build 3790: )
8.00.818
About a year ago MS and Oracle were working with me to solve a memory leak
issue and I think that may be related to why SP4 wont install but I cant be
sure.
The only hint as to what the error is at the begining of the logfile (See
below).
05/18/2005 08:29:49.910
================================================================================ 05/18/2005 08:29:49.910 Hotfix package launched
05/18/2005 08:29:49.910 Local Computer:
05/18/2005 08:29:49.910 Target Details: SG1
05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:49.910 windir = C:\WINDOWS
05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
05/18/2005 08:29:49.910
05/18/2005 08:29:50.850 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 The following product instance was disqualified
because a parent product instance of the same product code was found:
{0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.100 Product Details:
05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
05/18/2005 08:29:51.110 build = 2039
05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
SQL Server 2000 64-bit features including the relational database engine and
Analysis Services. If you have not done so already, back up the master and
msdb databases and stop all database programs and services before proceeding.
05/18/2005 08:29:51.110 kbarticle = KB884525
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 package = HotFix1
05/18/2005 08:29:51.110 productname = SQLOLAP64
05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
Pack 4
05/18/2005 08:29:51.110 splevel = RTM,4
05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
05/18/2005 08:29:51.110 version = 8
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 File Group Details: MSP
05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress
05/18/2005 08:29:51.110 File Details: sqlrun.msp
05/18/2005 08:29:51.110 lockedfilecheck = 1
05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/18/2005 08:29:51.110
05/18/2005 08:29:51.110 Instance Details: MSSQLServer
05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
05/18/2005 08:29:51.110 default = TRUE
05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
05/18/2005 08:29:51.110 id = MSSQLServer
05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
SQL Server\MSSQL
05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
Server\MSSQL
05/18/2005 08:29:51.110 lcid = 1033
05/18/2005 08:29:51.110 name = MSSQLServer
05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
05/18/2005 08:29:51.110 productcode = {0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/18/2005 08:29:51.110 servicename = MSSQLServer
05/18/2005 08:29:51.110 sku = ENTERPRISE
05/18/2005 08:29:51.110 sp = RTM
05/18/2005 08:29:51.110 type = Liberty
05/18/2005 08:29:51.110 version = 8Anybody?
"Jim" wrote:
> I am having trouble installing SP4 on my IA64. Like the instructions said in
> section 1.1 of the help file I have changed it to allow Unsigned drivers to
> Silently Succeed. However I am still getting a failure.
> On thing to note when I run the following command I get some different
> results than the help file say I sould.
> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
> SERVERPROPERTY('ProductVersion')
> SP3
> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition (64-bit) on
> Windows NT 5.2 (Build 3790: )
> 8.00.818
> About a year ago MS and Oracle were working with me to solve a memory leak
> issue and I think that may be related to why SP4 wont install but I cant be
> sure.
> The only hint as to what the error is at the begining of the logfile (See
> below).
> 05/18/2005 08:29:49.910
> ================================================================================> 05/18/2005 08:29:49.910 Hotfix package launched
> 05/18/2005 08:29:49.910 Local Computer:
> 05/18/2005 08:29:49.910 Target Details: SG1
> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
> 05/18/2005 08:29:49.910
> 05/18/2005 08:29:50.850 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 The following product instance was disqualified
> because a parent product instance of the same product code was found:
> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.100 Product Details:
> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
> 05/18/2005 08:29:51.110 build = 2039
> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on all
> SQL Server 2000 64-bit features including the relational database engine and
> Analysis Services. If you have not done so already, back up the master and
> msdb databases and stop all database programs and services before proceeding.
> 05/18/2005 08:29:51.110 kbarticle = KB884525
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 package = HotFix1
> 05/18/2005 08:29:51.110 productname = SQLOLAP64
> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit) Service
> Pack 4
> 05/18/2005 08:29:51.110 splevel = RTM,4
> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
> 05/18/2005 08:29:51.110 version = 8
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 File Group Details: MSP
> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress
> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
> 05/18/2005 08:29:51.110 lockedfilecheck = 1
> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039 KBNUMBER=KB884525
> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
> 05/18/2005 08:29:51.110
> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
> 05/18/2005 08:29:51.110 default = TRUE
> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
> 05/18/2005 08:29:51.110 id = MSSQLServer
> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program Files\Microsoft
> SQL Server\MSSQL
> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft SQL
> Server\MSSQL
> 05/18/2005 08:29:51.110 lcid = 1033
> 05/18/2005 08:29:51.110 name = MSSQLServer
> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
> 05/18/2005 08:29:51.110 productcode => {0F34966C-4EF4-45AE-B78E-486BEFB71698}
> 05/18/2005 08:29:51.110 servicename = MSSQLServer
> 05/18/2005 08:29:51.110 sku = ENTERPRISE
> 05/18/2005 08:29:51.110 sp = RTM
> 05/18/2005 08:29:51.110 type = Liberty
> 05/18/2005 08:29:51.110 version = 8|||Sorry don't have an answer for you. If no one else pipes in you may want to
give MS PSS a call.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"Jim" <Jim@.discussions.microsoft.com> wrote in message
news:D129328E-93E4-4E2A-BC6B-129B9D7341AE@.microsoft.com...
> Anybody?
> "Jim" wrote:
>> I am having trouble installing SP4 on my IA64. Like the instructions said
>> in
>> section 1.1 of the help file I have changed it to allow Unsigned drivers
>> to
>> Silently Succeed. However I am still getting a failure.
>> On thing to note when I run the following command I get some different
>> results than the help file say I sould.
>> SELECT SERVERPROPERTY('ProductLevel'), @.@.VERSION,
>> SERVERPROPERTY('ProductVersion')
>> SP3
>> Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 2003
>> 15:32:45
>> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition
>> (64-bit) on
>> Windows NT 5.2 (Build 3790: )
>> 8.00.818
>> About a year ago MS and Oracle were working with me to solve a memory
>> leak
>> issue and I think that may be related to why SP4 wont install but I cant
>> be
>> sure.
>> The only hint as to what the error is at the begining of the logfile (See
>> below).
>> 05/18/2005 08:29:49.910
>> ================================================================================>> 05/18/2005 08:29:49.910 Hotfix package launched
>> 05/18/2005 08:29:49.910 Local Computer:
>> 05/18/2005 08:29:49.910 Target Details: SG1
>> 05/18/2005 08:29:49.910 commonfilesdir = C:\Program Files\Common Files
>> 05/18/2005 08:29:49.910 programfilesdir = C:\Program Files
>> 05/18/2005 08:29:49.910 supportdir = C:\SQL2KSP4\IA64
>> 05/18/2005 08:29:49.910 windir = C:\WINDOWS
>> 05/18/2005 08:29:49.910 winsysdir = C:\WINDOWS\system32
>> 05/18/2005 08:29:49.910
>> 05/18/2005 08:29:50.850 The following product instance was disqualified
>> because a parent product instance of the same product code was found:
>> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
>> 05/18/2005 08:29:51.100 The following product instance was disqualified
>> because a parent product instance of the same product code was found:
>> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
>> 05/18/2005 08:29:51.100 Product Details:
>> 05/18/2005 08:29:51.110 INF File Name: C:\SQL2KSP4\IA64\HotFix1.inf
>> 05/18/2005 08:29:51.110 build = 2039
>> 05/18/2005 08:29:51.110 description = SQL Server 2000 (64-bit)
>> 05/18/2005 08:29:51.110 description2 = Analysis Services 2000 (64-bit)
>> 05/18/2005 08:29:51.110 details = This Service Pack can be applied on
>> all
>> SQL Server 2000 64-bit features including the relational database engine
>> and
>> Analysis Services. If you have not done so already, back up the master
>> and
>> msdb databases and stop all database programs and services before
>> proceeding.
>> 05/18/2005 08:29:51.110 kbarticle = KB884525
>> 05/18/2005 08:29:51.110 lcid = 1033
>> 05/18/2005 08:29:51.110 package = HotFix1
>> 05/18/2005 08:29:51.110 productname = SQLOLAP64
>> 05/18/2005 08:29:51.110 servicepackname = SQL Server 2000 (64-bit)
>> Service
>> Pack 4
>> 05/18/2005 08:29:51.110 splevel = RTM,4
>> 05/18/2005 08:29:51.110 supportdir = C:\SQL2KSP4\IA64
>> 05/18/2005 08:29:51.110 version = 8
>> 05/18/2005 08:29:51.110
>> 05/18/2005 08:29:51.110 File Group Details: MSP
>> 05/18/2005 08:29:51.110 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
>> 05/18/2005 08:29:51.110 File Details: OverridePreSP4QFE.msp
>> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039
>> KBNUMBER=KB884525
>> REBOOT=ReallySuppress
>> 05/18/2005 08:29:51.110 File Details: sqlrun.msp
>> 05/18/2005 08:29:51.110 lockedfilecheck = 1
>> 05/18/2005 08:29:51.110 parameters = SQLBUILD=2039
>> KBNUMBER=KB884525
>> REBOOT=ReallySuppress FORCEPATCH=DISTMDL SUPPORTFTPATCH=1
>> SUPPORTMSSEARCHPATCH=1 FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
>> MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
>> 05/18/2005 08:29:51.110
>> 05/18/2005 08:29:51.110 Instance Details: MSSQLServer
>> 05/18/2005 08:29:51.110 = Software\Microsoft\MSSQLServer\Setup
>> 05/18/2005 08:29:51.110 agentservicename = SQLSERVERAGENT
>> 05/18/2005 08:29:51.110 default = TRUE
>> 05/18/2005 08:29:51.110 hiveregpath = Software\Microsoft\MSSQLServer
>> 05/18/2005 08:29:51.110 id = MSSQLServer
>> 05/18/2005 08:29:51.110 installsqldatadir = C:\Program
>> Files\Microsoft
>> SQL Server\MSSQL
>> 05/18/2005 08:29:51.110 installsqldir = C:\Program Files\Microsoft
>> SQL
>> Server\MSSQL
>> 05/18/2005 08:29:51.110 lcid = 1033
>> 05/18/2005 08:29:51.110 name = MSSQLServer
>> 05/18/2005 08:29:51.110 olapservicename = MSSQLServerOLAPService
>> 05/18/2005 08:29:51.110 productcode =>> {0F34966C-4EF4-45AE-B78E-486BEFB71698}
>> 05/18/2005 08:29:51.110 servicename = MSSQLServer
>> 05/18/2005 08:29:51.110 sku = ENTERPRISE
>> 05/18/2005 08:29:51.110 sp = RTM
>> 05/18/2005 08:29:51.110 type = Liberty
>> 05/18/2005 08:29:51.110 version = 8|||I'm getting the same error as well. I'm thinking it has something t
do with a previous version of a hotfix that was applied
SELECT @.@.Versio
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64) Jun 1 200
15:32:45 Copyright (c) 1988-2003 Microsoft Corporation Enterpris
Edition (64-bit) on Windows NT 5.2 (Build 3790: )
05/26/2005 21:10:33.10
===============================================================================05/26/2005 21:10:33.107 Hotfix package launche
05/26/2005 21:10:33.107 Local Computer
05/26/2005 21:10:33.107 Target Details: OLYMPO
05/26/2005 21:10:33.107 commonfilesdir = C:\Program Files\Commo
File
05/26/2005 21:10:33.107 programfilesdir = C:\Program File
05/26/2005 21:10:33.107 supportdir
\\Pontos\IT\pontos\it\SQL2KSP4\IA6
05/26/2005 21:10:33.107 windir = C:\WINDOW
05/26/2005 21:10:33.107 winsysdir = C:\WINDOWS\system3
05/26/2005 21:10:33.107
05/26/2005 21:10:34.756 The following product instance wa
disqualified because a parent product instance of the same produc
code was found: {0F34966C-4EF4-45AE-B78E-486BEFB71698
05/26/2005 21:10:34.959 The following product instance wa
disqualified because a parent product instance of the same produc
code was found: {FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F
05/26/2005 21:10:34.959 Product Details
05/26/2005 21:10:34.959 INF File Name
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.in
05/26/2005 21:10:34.959 build = 203
05/26/2005 21:10:34.959 description = SQL Server 2000 (64-bit
05/26/2005 21:10:34.959 description2 = Analysis Services 200
(64-bit
05/26/2005 21:10:34.959 details = This Service Pack can be applie
on all SQL Server 2000 64-bit features including the relationa
database engine and Analysis Services. If you have not done s
already, back up the master and msdb databases and stop all databas
programs and services before proceeding
05/26/2005 21:10:34.959 kbarticle = KB88452
05/26/2005 21:10:34.959 lcid = 103
05/26/2005 21:10:34.959 package = HotFix
05/26/2005 21:10:34.959 productname = SQLOLAP6
05/26/2005 21:10:34.959 servicepackname = SQL Server 2000 (64-bit
Service Pack
05/26/2005 21:10:34.959 splevel = RTM,
05/26/2005 21:10:34.959 supportdir
\\Pontos\IT\pontos\it\SQL2KSP4\IA6
05/26/2005 21:10:34.959 version =05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 File Group Details: MS
05/26/2005 21:10:34.959 sourcepath
<SUPPORTDIR>\<PACKAGE>\File
05/26/2005 21:10:34.959 File Details: OverridePreSP4QFE.ms
05/26/2005 21:10:34.959 parameters = SQLBUILD=203
KBNUMBER=KB884525 REBOOT=ReallySuppres
05/26/2005 21:10:34.959 File Details: sqlrun.ms
05/26/2005 21:10:34.959 lockedfilecheck =05/26/2005 21:10:34.959 parameters = SQLBUILD=203
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMD
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.959
05/26/2005 21:10:34.959 Instance Details: PRODUCTIO
05/26/2005 21:10:34.959 = Software\Microsoft\Microsoft SQ
Server\PRODUCTION\Setu
05/26/2005 21:10:34.959 agentservicename = SQLAgent$PRODUCTIO
05/26/2005 21:10:34.959 hiveregpath = Software\Microsoft\Microsof
SQL Server\PRODUCTIO
05/26/2005 21:10:34.959 id = PRODUCTIO
05/26/2005 21:10:34.959 installsqldatadir = C:\Progra
Files\Microsoft SQL Server\MSSQL$PRODUCTIO
05/26/2005 21:10:34.959 installsqldir = C:\Program Files\Microsof
SQL Server\MSSQL$PRODUCTIO
05/26/2005 21:10:34.959 lcid = 103
05/26/2005 21:10:34.969 name = PRODUCTIO
05/26/2005 21:10:34.969 productcode
{0F34966C-4EF4-45AE-B78E-486BEFB71698
05/26/2005 21:10:34.969 servicename = MSSQL$PRODUCTIO
05/26/2005 21:10:34.969 sku = ENTERPRIS
05/26/2005 21:10:34.969 sp = RT
05/26/2005 21:10:34.969 type = Libert
05/26/2005 21:10:34.969 version =05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWOR
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQ
Server\RMSWORK\Setu
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWOR
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode ={FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = Liberty
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: RMSWORK
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 agentservicename = SQLAgent$RMSWORK
05/26/2005 21:10:34.969 hiveregpath = Software\Microsoft\Microsoft
SQL Server\RMSWORK
05/26/2005 21:10:34.969 id = RMSWORK
05/26/2005 21:10:34.969 installsqldatadir = C:\Program
Files\Microsoft SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\MSSQL$RMSWORK
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = RMSWORK
05/26/2005 21:10:34.969 olapservicename = MSSQLServerOLAPService
05/26/2005 21:10:34.969 productcode ={FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 servicename = MSSQL$RMSWORK
05/26/2005 21:10:34.969 sku = ENTERPRISE
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 type = OLAP
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = SQL Server 2000 (64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: SQL Tools
05/26/2005 21:10:34.969 = Software\Microsoft\Microsoft SQL
Server\80\Tools\ClientSetup\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Microsoft
SQL Server\80\Tools
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = SQL Tools
05/26/2005 21:10:34.969 productcode ={0F34966C-4EF4-45AE-B78E-486BEFB71698}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Product Details:
05/26/2005 21:10:34.969 INF File Name:
\\Pontos\IT\pontos\it\SQL2KSP4\IA64\HotFix1.inf
05/26/2005 21:10:34.969 build = 2039
05/26/2005 21:10:34.969 description = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 description2 = Analysis Services 2000
(64-bit)
05/26/2005 21:10:34.969 details = This Service Pack can be applied
on all SQL Server 2000 64-bit features including the relational
database engine and Analysis Services. If you have not done so
already, back up the master and msdb databases and stop all database
programs and services before proceeding.
05/26/2005 21:10:34.969 kbarticle = KB884525
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 package = HotFix1
05/26/2005 21:10:34.969 productname = SQLOLAP64
05/26/2005 21:10:34.969 servicepackname = SQL Server 2000 (64-bit)
Service Pack 4
05/26/2005 21:10:34.969 splevel = RTM,4
05/26/2005 21:10:34.969 supportdir =\\Pontos\IT\pontos\it\SQL2KSP4\IA64
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 File Group Details: MSP
05/26/2005 21:10:34.969 sourcepath =<SUPPORTDIR>\<PACKAGE>\Files
05/26/2005 21:10:34.969 File Details: OverridePreSP4QFE.msp
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress
05/26/2005 21:10:34.969 File Details: sqlrun.msp
05/26/2005 21:10:34.969 lockedfilecheck = 1
05/26/2005 21:10:34.969 parameters = SQLBUILD=2039
KBNUMBER=KB884525 REBOOT=ReallySuppress FORCEPATCH=DISTMDL
SUPPORTFTPATCH=1 SUPPORTMSSEARCHPATCH=1
FTPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
MSSEARCHPATCHPATH="<SUPPORTDIR>\<PACKAGE>\Files"
05/26/2005 21:10:34.969
05/26/2005 21:10:34.969 Instance Details: OLAPClient
05/26/2005 21:10:34.969 = Software\Microsoft\OLAP Server\Setup
05/26/2005 21:10:34.969 installsqldir = C:\Program Files\Common
Files\system\OLE DB
05/26/2005 21:10:34.969 lcid = 1033
05/26/2005 21:10:34.969 name = OLAPClient
05/26/2005 21:10:34.969 productcode ={FA0BA25D-6D7B-4E7F-8BD6-FC8C53B5D47F}
05/26/2005 21:10:34.969 sp = RTM
05/26/2005 21:10:34.969 version = 8
05/26/2005 21:10:34.969
05/26/2005 21:10:51.286 Authenticating user using Windows
Authentication
05/26/2005 21:10:51.306 SQL Service MSSQL$PRODUCTION was previously
running, ready for authentication
05/26/2005 21:10:51.306 SQL Agent Service SQLAgent$PRODUCTION was
previously running
05/26/2005 21:10:51.489 User authentication was successful
05/26/2005 21:10:54.787 Attempting to install product: SQLOLAP64|||Hi there:
i am also facing the same problem when i try installing SQL2k SP4 on IA serversWere you able ti fix it. Will appreciate any help.
Kind Regards,
Rosha
From http://www.developmentnow.com/g/118_2005_5_0_0_524275/IA64-SP4-Install-Problem.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
Posted by perplexingmqwo at 2:15 AM 0 comments
Labels: , , , , , , , , , , , , , , ,

I/O issues after SP4 upgrade

Hi,
We have upgraded 3 of our SQL Servers to SP4 in the past 2 weeks. We
monitor these servers with Veritas, and we have noticed that all 3 servers
have shown a marked increase (around 4x) in Disk Sec/Transfer, Disk
Sec/Write, and Disk Queue Length.
For example, on one server, Disk Writes and Disk Transfers were taking on
average 7 ms to complete (with SP3a). Post-SP4, they are taking
approximately 30 ms on average. The queue length has jumped from around 3
to about 15. [I know the avg disk queue length was a bit high to start
with - we are working with our SAN vendor to get this figured out]
Queries are still executing in about the same time, CPU utilization is about
the same, and we see no other negative effects. But we're wondering why the
I/O is so much worse than when we were running SP3a. We changed nothing
besides moving to SP4. And we did install the post-SP4 AWE patch as well.
Has anyone run into this before or know of any articles that touch on
possible causes?
--
Regards,
Jake Marx
www.longhead.com
[please keep replies in the newsgroup - email address unmonitored]Have the query plans changed? Is the increased I/O due to more table scans?
Did you run sp_updatestats?
--
Andrew J. Kelly SQL MVP
"Jake Marx" <msnews@.longhead.com> wrote in message
news:OM%23R2MCVGHA.4348@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We have upgraded 3 of our SQL Servers to SP4 in the past 2 weeks. We
> monitor these servers with Veritas, and we have noticed that all 3 servers
> have shown a marked increase (around 4x) in Disk Sec/Transfer, Disk
> Sec/Write, and Disk Queue Length.
> For example, on one server, Disk Writes and Disk Transfers were taking on
> average 7 ms to complete (with SP3a). Post-SP4, they are taking
> approximately 30 ms on average. The queue length has jumped from around 3
> to about 15. [I know the avg disk queue length was a bit high to start
> with - we are working with our SAN vendor to get this figured out]
> Queries are still executing in about the same time, CPU utilization is
> about the same, and we see no other negative effects. But we're wondering
> why the I/O is so much worse than when we were running SP3a. We changed
> nothing besides moving to SP4. And we did install the post-SP4 AWE patch
> as well. Has anyone run into this before or know of any articles that
> touch on possible causes?
> --
> Regards,
> Jake Marx
> www.longhead.com
>
> [please keep replies in the newsgroup - email address unmonitored]
>|||Hi Andrew,
Andrew J. Kelly wrote:
> Have the query plans changed? Is the increased I/O due to more table
> scans? Did you run sp_updatestats?
Thanks for the suggestions. I did not run sp_updatestats - I just did it on
one of the less-busy servers to see if it makes a difference. The query
plans are not different from what I have seen so far, but I will keep
looking. Table scans have come down a bit since upgrading to SP4.
The strange thing (to me) is that overall I/O activity is about the same;
reads/writes per sec is pretty constant. It's just the duration of each I/O
operation and the disk queue length that went up. And this happened only on
the data drive - the trans log and local (tempdb) drives' queue lengths
actually decreased.
--
Regards,
Jake Marx
www.longhead.com
[please keep replies in the newsgroup - email address unmonitored]
>> We have upgraded 3 of our SQL Servers to SP4 in the past 2 weeks. We
>> monitor these servers with Veritas, and we have noticed that all 3
>> servers have shown a marked increase (around 4x) in Disk
>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>> For example, on one server, Disk Writes and Disk Transfers were
>> taking on average 7 ms to complete (with SP3a). Post-SP4, they are
>> taking approximately 30 ms on average. The queue length has jumped
>> from around 3 to about 15. [I know the avg disk queue length was a
>> bit high to start with - we are working with our SAN vendor to get
>> this figured out] Queries are still executing in about the same time, CPU
>> utilization
>> is about the same, and we see no other negative effects. But we're
>> wondering why the I/O is so much worse than when we were running
>> SP3a. We changed nothing besides moving to SP4. And we did install
>> the post-SP4 AWE patch as well. Has anyone run into this before or
>> know of any articles that touch on possible causes?|||There should be very few table scans if they are optimized properly
regardless of the SP. I haven't seen anything yet that indicates SP4 itself
caused increased I/O times but anything is possible. Any chance you were
monitoring fn_virtualfilestats() before and after? If so do you notice
increased bytes read or written or just increased IOStallms?
--
Andrew J. Kelly SQL MVP
"Jake Marx" <msnews@.longhead.com> wrote in message
news:%23KCJtvNVGHA.4764@.TK2MSFTNGP10.phx.gbl...
> Hi Andrew,
> Andrew J. Kelly wrote:
>> Have the query plans changed? Is the increased I/O due to more table
>> scans? Did you run sp_updatestats?
> Thanks for the suggestions. I did not run sp_updatestats - I just did it
> on one of the less-busy servers to see if it makes a difference. The
> query plans are not different from what I have seen so far, but I will
> keep looking. Table scans have come down a bit since upgrading to SP4.
> The strange thing (to me) is that overall I/O activity is about the same;
> reads/writes per sec is pretty constant. It's just the duration of each
> I/O operation and the disk queue length that went up. And this happened
> only on the data drive - the trans log and local (tempdb) drives' queue
> lengths actually decreased.
> --
> Regards,
> Jake Marx
> www.longhead.com
>
> [please keep replies in the newsgroup - email address unmonitored]
>
>> We have upgraded 3 of our SQL Servers to SP4 in the past 2 weeks. We
>> monitor these servers with Veritas, and we have noticed that all 3
>> servers have shown a marked increase (around 4x) in Disk
>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>> For example, on one server, Disk Writes and Disk Transfers were
>> taking on average 7 ms to complete (with SP3a). Post-SP4, they are
>> taking approximately 30 ms on average. The queue length has jumped
>> from around 3 to about 15. [I know the avg disk queue length was a
>> bit high to start with - we are working with our SAN vendor to get
>> this figured out] Queries are still executing in about the same time,
>> CPU utilization
>> is about the same, and we see no other negative effects. But we're
>> wondering why the I/O is so much worse than when we were running
>> SP3a. We changed nothing besides moving to SP4. And we did install
>> the post-SP4 AWE patch as well. Has anyone run into this before or
>> know of any articles that touch on possible causes?
>|||Hi Andrew,
Andrew J. Kelly wrote:
> There should be very few table scans if they are optimized properly
> regardless of the SP. I haven't seen anything yet that indicates SP4
> itself caused increased I/O times but anything is possible. Any
> chance you were monitoring fn_virtualfilestats() before and after? If so
> do you notice increased bytes read or written or just increased
> IOStallms?
Most of the table/index scans are on very small tables (some of which are
heaps). There aren't any table scans on larger tables, and there are very
few index scans on larger tables (we're working on removing those as we
can). Full scans/sec seem to hover around 3. We have several hundred
concurrent users on this db.
No, I haven't used fn_virtualfilestats() before. Just ran it, and it seems
useful - thanks for the tip. IoStallMS / NumberReads + NumberWrites) is
less than 6 for all files, so that seems OK based on the documentation I've
seen.
--
Regards,
Jake Marx
www.longhead.com
[please keep replies in the newsgroup - email address unmonitored]
>> Andrew J. Kelly wrote:
>> Have the query plans changed? Is the increased I/O due to more
>> table scans? Did you run sp_updatestats?
>> Thanks for the suggestions. I did not run sp_updatestats - I just
>> did it on one of the less-busy servers to see if it makes a
>> difference. The query plans are not different from what I have seen
>> so far, but I will keep looking. Table scans have come down a bit
>> since upgrading to SP4. The strange thing (to me) is that overall I/O
>> activity is about the
>> same; reads/writes per sec is pretty constant. It's just the
>> duration of each I/O operation and the disk queue length that went
>> up. And this happened only on the data drive - the trans log and
>> local (tempdb) drives' queue lengths actually decreased.
>> --
>> Regards,
>> Jake Marx
>> www.longhead.com
>>
>> [please keep replies in the newsgroup - email address unmonitored]
>>
>> We have upgraded 3 of our SQL Servers to SP4 in the past 2 weeks. We
>> monitor these servers with Veritas, and we have noticed that
>> all 3 servers have shown a marked increase (around 4x) in Disk
>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>> For example, on one server, Disk Writes and Disk Transfers were
>> taking on average 7 ms to complete (with SP3a). Post-SP4, they are
>> taking approximately 30 ms on average. The queue length has jumped
>> from around 3 to about 15. [I know the avg disk queue length was a
>> bit high to start with - we are working with our SAN vendor to get
>> this figured out] Queries are still executing in about the same
>> time, CPU utilization
>> is about the same, and we see no other negative effects. But we're
>> wondering why the I/O is so much worse than when we were running
>> SP3a. We changed nothing besides moving to SP4. And we did
>> install the post-SP4 AWE patch as well. Has anyone run into this
>> before or know of any articles that touch on possible causes?|||The filestats will let you know if you are actually reading / writing more
data or simply getting increased access times with the same data.
--
Andrew J. Kelly SQL MVP
"Jake Marx" <msnews@.longhead.com> wrote in message
news:eTDfwOOVGHA.4864@.TK2MSFTNGP12.phx.gbl...
> Hi Andrew,
> Andrew J. Kelly wrote:
>> There should be very few table scans if they are optimized properly
>> regardless of the SP. I haven't seen anything yet that indicates SP4
>> itself caused increased I/O times but anything is possible. Any
>> chance you were monitoring fn_virtualfilestats() before and after? If so
>> do you notice increased bytes read or written or just increased
>> IOStallms?
> Most of the table/index scans are on very small tables (some of which are
> heaps). There aren't any table scans on larger tables, and there are very
> few index scans on larger tables (we're working on removing those as we
> can). Full scans/sec seem to hover around 3. We have several hundred
> concurrent users on this db.
> No, I haven't used fn_virtualfilestats() before. Just ran it, and it
> seems useful - thanks for the tip. IoStallMS / NumberReads +
> NumberWrites) is less than 6 for all files, so that seems OK based on the
> documentation I've seen.
> --
> Regards,
> Jake Marx
> www.longhead.com
>
> [please keep replies in the newsgroup - email address unmonitored]
>> Andrew J. Kelly wrote:
>> Have the query plans changed? Is the increased I/O due to more
>> table scans? Did you run sp_updatestats?
>> Thanks for the suggestions. I did not run sp_updatestats - I just
>> did it on one of the less-busy servers to see if it makes a
>> difference. The query plans are not different from what I have seen
>> so far, but I will keep looking. Table scans have come down a bit
>> since upgrading to SP4. The strange thing (to me) is that overall I/O
>> activity is about the
>> same; reads/writes per sec is pretty constant. It's just the
>> duration of each I/O operation and the disk queue length that went
>> up. And this happened only on the data drive - the trans log and
>> local (tempdb) drives' queue lengths actually decreased.
>> --
>> Regards,
>> Jake Marx
>> www.longhead.com
>>
>> [please keep replies in the newsgroup - email address unmonitored]
>>
>> We have upgraded 3 of our SQL Servers to SP4 in the past 2 weeks. We
>> monitor these servers with Veritas, and we have noticed that
>> all 3 servers have shown a marked increase (around 4x) in Disk
>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>> For example, on one server, Disk Writes and Disk Transfers were
>> taking on average 7 ms to complete (with SP3a). Post-SP4, they are
>> taking approximately 30 ms on average. The queue length has jumped
>> from around 3 to about 15. [I know the avg disk queue length was a
>> bit high to start with - we are working with our SAN vendor to get
>> this figured out] Queries are still executing in about the same
>> time, CPU utilization
>> is about the same, and we see no other negative effects. But we're
>> wondering why the I/O is so much worse than when we were running
>> SP3a. We changed nothing besides moving to SP4. And we did
>> install the post-SP4 AWE patch as well. Has anyone run into this
>> before or know of any articles that touch on possible causes?
>|||Hi Andrew,
Andrew J. Kelly wrote:
> The filestats will let you know if you are actually reading / writing
> more data or simply getting increased access times with the same data.
Thanks. According to perfmon before and after SP4 installation, the I/O
load is about the same now as it was then (approx the same # of writes/sec
and reads/sec) - it's just the sec/write and sec/transfer (along with the
disk queue length) that are higher.
I'm not sure what else to look at. I know that SP4 reports I/O
latching/locking differently than SP3a, but that shouldn't affect perfmon OS
stats, right? I'd imagine those are collected directly by the disk
subsystem and that SQL would have nothing to do with that collection...
Thanks again for your help. I'm going through all the query plans now to
make sure nothing has changed.
--
Regards,
Jake Marx
www.longhead.com
[please keep replies in the newsgroup - email address unmonitored]
>> Andrew J. Kelly wrote:
>> There should be very few table scans if they are optimized properly
>> regardless of the SP. I haven't seen anything yet that indicates
>> SP4 itself caused increased I/O times but anything is possible. Any
>> chance you were monitoring fn_virtualfilestats() before and after?
>> If so do you notice increased bytes read or written or just
>> increased IOStallms?
>> Most of the table/index scans are on very small tables (some of
>> which are heaps). There aren't any table scans on larger tables,
>> and there are very few index scans on larger tables (we're working
>> on removing those as we can). Full scans/sec seem to hover around
>> 3. We have several hundred concurrent users on this db.
>> No, I haven't used fn_virtualfilestats() before. Just ran it, and it
>> seems useful - thanks for the tip. IoStallMS / NumberReads +
>> NumberWrites) is less than 6 for all files, so that seems OK based
>> on the documentation I've seen.
>>
>> Andrew J. Kelly wrote:
>> Have the query plans changed? Is the increased I/O due to more
>> table scans? Did you run sp_updatestats?
>> Thanks for the suggestions. I did not run sp_updatestats - I just
>> did it on one of the less-busy servers to see if it makes a
>> difference. The query plans are not different from what I have
>> seen so far, but I will keep looking. Table scans have come down
>> a bit since upgrading to SP4. The strange thing (to me) is that
>> overall I/O activity is about the
>> same; reads/writes per sec is pretty constant. It's just the
>> duration of each I/O operation and the disk queue length that went
>> up. And this happened only on the data drive - the trans log and
>> local (tempdb) drives' queue lengths actually decreased.
>> We have upgraded 3 of our SQL Servers to SP4 in the past 2
>> weeks. We monitor these servers with Veritas, and we have
>> noticed that all 3 servers have shown a marked increase (around 4x)
>> in Disk
>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>> For example, on one server, Disk Writes and Disk Transfers were
>> taking on average 7 ms to complete (with SP3a). Post-SP4, they
>> are taking approximately 30 ms on average. The queue length has
>> jumped from around 3 to about 15. [I know the avg disk queue
>> length was a bit high to start with - we are working with our
>> SAN vendor to get this figured out] Queries are still executing
>> in about the same time, CPU utilization
>> is about the same, and we see no other negative effects. But
>> we're wondering why the I/O is so much worse than when we were
>> running SP3a. We changed nothing besides moving to SP4. And we
>> did install the post-SP4 AWE patch as well. Has anyone run into
>> this before or know of any articles that touch on possible
>> causes?|||The sp should not affect perfmon stats for I/O. Are you sure there wasn't
anything else done around that same timeframe that may have affected this?
Any changes to the SAN or the OS? I wish I could offer something better
than that but this is not something I have heard happening to others upon
adding SP4 (or any service pack for that matter).
--
Andrew J. Kelly SQL MVP
"Jake Marx" <msnews@.longhead.com> wrote in message
news:u7lZo02VGHA.4724@.TK2MSFTNGP09.phx.gbl...
> Hi Andrew,
> Andrew J. Kelly wrote:
>> The filestats will let you know if you are actually reading / writing
>> more data or simply getting increased access times with the same data.
> Thanks. According to perfmon before and after SP4 installation, the I/O
> load is about the same now as it was then (approx the same # of writes/sec
> and reads/sec) - it's just the sec/write and sec/transfer (along with the
> disk queue length) that are higher.
> I'm not sure what else to look at. I know that SP4 reports I/O
> latching/locking differently than SP3a, but that shouldn't affect perfmon
> OS stats, right? I'd imagine those are collected directly by the disk
> subsystem and that SQL would have nothing to do with that collection...
> Thanks again for your help. I'm going through all the query plans now to
> make sure nothing has changed.
> --
> Regards,
> Jake Marx
> www.longhead.com
>
> [please keep replies in the newsgroup - email address unmonitored]
>> Andrew J. Kelly wrote:
>> There should be very few table scans if they are optimized properly
>> regardless of the SP. I haven't seen anything yet that indicates
>> SP4 itself caused increased I/O times but anything is possible. Any
>> chance you were monitoring fn_virtualfilestats() before and after?
>> If so do you notice increased bytes read or written or just
>> increased IOStallms?
>> Most of the table/index scans are on very small tables (some of
>> which are heaps). There aren't any table scans on larger tables,
>> and there are very few index scans on larger tables (we're working
>> on removing those as we can). Full scans/sec seem to hover around
>> 3. We have several hundred concurrent users on this db.
>> No, I haven't used fn_virtualfilestats() before. Just ran it, and it
>> seems useful - thanks for the tip. IoStallMS / NumberReads +
>> NumberWrites) is less than 6 for all files, so that seems OK based
>> on the documentation I've seen.
>>
>> Andrew J. Kelly wrote:
>> Have the query plans changed? Is the increased I/O due to more
>> table scans? Did you run sp_updatestats?
>> Thanks for the suggestions. I did not run sp_updatestats - I just
>> did it on one of the less-busy servers to see if it makes a
>> difference. The query plans are not different from what I have
>> seen so far, but I will keep looking. Table scans have come down
>> a bit since upgrading to SP4. The strange thing (to me) is that
>> overall I/O activity is about the
>> same; reads/writes per sec is pretty constant. It's just the
>> duration of each I/O operation and the disk queue length that went
>> up. And this happened only on the data drive - the trans log and
>> local (tempdb) drives' queue lengths actually decreased.
>>> We have upgraded 3 of our SQL Servers to SP4 in the past 2
>>> weeks. We monitor these servers with Veritas, and we have
>>> noticed that all 3 servers have shown a marked increase (around 4x)
>>> in Disk
>>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>>>
>>> For example, on one server, Disk Writes and Disk Transfers were
>>> taking on average 7 ms to complete (with SP3a). Post-SP4, they
>>> are taking approximately 30 ms on average. The queue length has
>>> jumped from around 3 to about 15. [I know the avg disk queue
>>> length was a bit high to start with - we are working with our
>>> SAN vendor to get this figured out] Queries are still executing
>>> in about the same time, CPU utilization
>>> is about the same, and we see no other negative effects. But
>>> we're wondering why the I/O is so much worse than when we were
>>> running SP3a. We changed nothing besides moving to SP4. And we
>>> did install the post-SP4 AWE patch as well. Has anyone run into
>>> this before or know of any articles that touch on possible
>>> causes?
>|||Hi Andrew,
Andrew J. Kelly wrote:
> The sp should not affect perfmon stats for I/O. Are you sure there
> wasn't anything else done around that same timeframe that may have
> affected this? Any changes to the SAN or the OS? I wish I could
> offer something better than that but this is not something I have
> heard happening to others upon adding SP4 (or any service pack for
> that matter).
I know - that's why I find this so strange. I would think that maybe we had
done something else at the same time, but we have done the SP4 upgrade on
three separate servers at three separate times, and we see the increase in
perfmon I/O stats on each server beginning with the time we upgraded each
one. We are using an EMC Celerra over iSCSI for the data and log files on
all three servers, so maybe SP4 changed something in that respect? I
wouldn't think so. (?)
Thanks again for all of your help!
--
Regards,
Jake
>> Andrew J. Kelly wrote:
>> The filestats will let you know if you are actually reading /
>> writing more data or simply getting increased access times with the
>> same data.
>> Thanks. According to perfmon before and after SP4 installation, the
>> I/O load is about the same now as it was then (approx the same # of
>> writes/sec and reads/sec) - it's just the sec/write and sec/transfer
>> (along with the disk queue length) that are higher.
>> I'm not sure what else to look at. I know that SP4 reports I/O
>> latching/locking differently than SP3a, but that shouldn't affect
>> perfmon OS stats, right? I'd imagine those are collected directly
>> by the disk subsystem and that SQL would have nothing to do with
>> that collection... Thanks again for your help. I'm going through all
>> the query plans
>> now to make sure nothing has changed.
>> Andrew J. Kelly wrote:
>> There should be very few table scans if they are optimized
>> properly regardless of the SP. I haven't seen anything yet that
>> indicates SP4 itself caused increased I/O times but anything is
>> possible. Any chance you were monitoring fn_virtualfilestats()
>> before and after? If so do you notice increased bytes read or
>> written or just increased IOStallms?
>> Most of the table/index scans are on very small tables (some of
>> which are heaps). There aren't any table scans on larger tables,
>> and there are very few index scans on larger tables (we're working
>> on removing those as we can). Full scans/sec seem to hover around
>> 3. We have several hundred concurrent users on this db.
>> No, I haven't used fn_virtualfilestats() before. Just ran it, and
>> it seems useful - thanks for the tip. IoStallMS / NumberReads +
>> NumberWrites) is less than 6 for all files, so that seems OK based
>> on the documentation I've seen.
>>
>> Andrew J. Kelly wrote:
>>> Have the query plans changed? Is the increased I/O due to more
>>> table scans? Did you run sp_updatestats?
>> Thanks for the suggestions. I did not run sp_updatestats - I
>> just did it on one of the less-busy servers to see if it makes a
>> difference. The query plans are not different from what I have
>> seen so far, but I will keep looking. Table scans have come down
>> a bit since upgrading to SP4. The strange thing (to me) is that
>> overall I/O activity is about the
>> same; reads/writes per sec is pretty constant. It's just the
>> duration of each I/O operation and the disk queue length that
>> went up. And this happened only on the data drive - the trans
>> log and local (tempdb) drives' queue lengths actually decreased.
>>> We have upgraded 3 of our SQL Servers to SP4 in the past 2
>>> weeks. We monitor these servers with Veritas, and we have
>>> noticed that all 3 servers have shown a marked increase
>>> (around 4x) in Disk
>>> Sec/Transfer, Disk Sec/Write, and Disk Queue Length.
>>>
>>> For example, on one server, Disk Writes and Disk Transfers were
>>> taking on average 7 ms to complete (with SP3a). Post-SP4, they
>>> are taking approximately 30 ms on average. The queue length
>>> has jumped from around 3 to about 15. [I know the avg disk
>>> queue length was a bit high to start with - we are working
>>> with our SAN vendor to get this figured out] Queries are still
>>> executing
>>> in about the same time, CPU utilization
>>> is about the same, and we see no other negative effects. But
>>> we're wondering why the I/O is so much worse than when we were
>>> running SP3a. We changed nothing besides moving to SP4. And
>>> we did install the post-SP4 AWE patch as well. Has anyone run
>>> into this before or know of any articles that touch on possible
>>> causes?sql
Posted by perplexingmqwo at 2:02 AM 0 comments
Labels: , , , , , , , , , , ,
Subscribe to: Posts (Atom)