Icon not displayed correctly for custom component

So i finally figured out how to create custom transform and add an icon to it. However - when i added the component to toolbox it appears as a file icon (when i didnt have icon it appeared as a blue box) - in the data flow designer it appears as the correct image.

From BOL wrote:

"The Data Flow toolbox uses the 16x16, 16-color image type, while

the design surface of the data flow tab uses the 32x32, 16-color image

type. Both are default image types for icons created using Microsoft

Visual Studio 2005."

I assume this has something to do with it - my ico is default 32x32 - however, what would be the way to fix it?

hi,

i think this this is

the same as my problem before.

Your Integration service is running on limited permission

close visual studion

run services.msc

change the logon with a more privelege user

and the restartn the services

regards,

joey

|||

Make sure you have both sized icons in the icon file, one is 64x64, and the other is 16x16, sounds like you're missing the 16x16 one.

|||

I have created a test icon with a range of sizes and color depths, which will help identify the requirements. You could use to test the issue, as different sized icons can clearly be identified. For example 16x6 will show green and 32x32 will be mauve. This way you can prove what sizes are required.

Icon Color Size Tester http://www.sqldts.com/redir.aspx?1304

Personally I use 16 and 32 sized frames in my icons, normally at 256 and 32bit color depths.

|||

KirkHaselden wrote:

Make sure you have both sized icons in the icon file, one is 64x64, and the other is 16x16, sounds like you're missing the 16x16 one.

Yup - i was missing the 16x16x - (actually it was created as default my VS) - so I had to Right click the icon in the layout window and go to "Current Icon Image Types".

Thankssql

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

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

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

I4 to I8 in Aggregation

I'm using an Aggregation task to summarize an input file by item and week before inserting it into a SQL table.

Two of the fields I'm summing, because their totals per record can occasionally exceed 32k, are defined as int (I4) instead of smallint (I2). However, the summarized total never exceeds the value an int can hold.

I ran into a problem on the insert, however, with SSIS telling me it couldn't insert an I8 value into an I4 table field. I discovered the metadata for the summed totals had automatically been set to bigint (I8), and the mapping was failing.

I didn't see a way to change that metadata within the Aggregation task itself, so I added a Data Conversion task to convert the totals to four-byte signed integers and enable the mapping. Was that the proper workaround?

Based on your problrem description, it is the workaround that I would have used, for what that's worth.

I/O error on backup or restore restart-checkpoint file

Does any of you know what this is about:
"I/O error on backup or restore restart-checkpoint
file 'E:\Program Files\Microsoft SQL
Server\MSSQL\backup\Domain1.ckp'. Operating system error 3
(error not found). The statement is proceeding but is non-
restartable."
I get an error code 18272 (cant find it in BOL).
Note: Domain1 is the name of a specific database on my
server.
The directory 'E:\Program Files\Microsoft SQL
Server\MSSQL\backup' have been deleted so it is no wonder
that it can't either find nor create a file in that
directory.
The error was raised during a restore of the Domain1
database (the restore completed successfuly). I have a job
that kills every connection to the Domain1 database
(except it's own connection) for the database to be
restorable.
What setting must be set for SQL Server not to use this
directory for this purpose?
Note: backups (both data og log) are written just fine to
another directory.
Yours truly
Jakob Pedersen"Jakob Pedersen" <anonymous@.discussions.microsoft.com> wrote in message
news:171201c3e051$27d725d0$a301280a@.phx.gbl...

quote:

---

> Does any of you know what this is about :
> "I/O error on backup or restore restart-checkpoint
> file 'E:\Program Files\Microsoft SQL
> Server\MSSQL\backup\Domain1.ckp'. Operating system error 3
> (error not found). The statement is proceeding but is non-
> restartable."
> I get an error code 18272 (cant find it in BOL).
> Note: Domain1 is the name of a specific database on my
> server.
> The directory 'E:\Program Files\Microsoft SQL
> Server\MSSQL\backup' have been deleted so it is no wonder
> that it can't either find nor create a file in that
> directory.
> The error was raised during a restore of the Domain1
> database (the restore completed successfuly). I have a job
> that kills every connection to the Domain1 database
> (except it's own connection) for the database to be
> restorable.

---

Are you sure the restore was successful? It sounds like something did not
work quite right... do you still have the syntax you used for the restore?

quote:

---

> What setting must be set for SQL Server not to use this
> directory for this purpose?

---

It really depends on how you performed the restore here...

quote:

---

> Note: backups (both data og log) are written just fine to
> another directory.

---

During the restore? I'm not sure what you mean here.
Steve|||> "Jakob Pedersen" <anonymous@.discussions.microsoft.com> wrote in message

quote:

---

> news:171201c3e051$27d725d0$a301280a@.phx.gbl...
>

---

Are you sure the restore was successful? It sounds like something did not
work quite right... do you still have the syntax you used for the restore?

quote:

---

>
It really depends on how you performed the restore here...
[QUOTE]
During the restore? I'm not sure what you mean here.
Steve
[QUOTE]
>

---

I/O error 38(Reached the end of the file.)

We received this error last night:
Error: 823, Severity: 24, State: 2
I/O error 38(Reached the end of the file.) detected during read at offset
0x000000dfbce000 in file
'D:\FocalPoint\Databases\001_001\pdi_sta
ge_001_001.mdf'..
It occured during cube and dimision updates on analytical services. The D
drive resides on a SAN. Our network administrator is saying there are no
drive issues. Everything I have read on Error 823 is hardware related.
Any suggestions. Thanks.Take a look at http://support.microsoft.com/kb/313702
Linchi
"brymer28303" wrote:

> We received this error last night:
> Error: 823, Severity: 24, State: 2
> I/O error 38(Reached the end of the file.) detected during read at offset
> 0x000000dfbce000 in file
> 'D:\FocalPoint\Databases\001_001\pdi_sta
ge_001_001.mdf'..
> It occured during cube and dimision updates on analytical services. The D
> drive resides on a SAN. Our network administrator is saying there are no
> drive issues. Everything I have read on Error 823 is hardware related.
> Any suggestions. Thanks.
>

I/O error 38(Reached the end of the file.)

We received this error last night:
Error: 823, Severity: 24, State: 2
I/O error 38(Reached the end of the file.) detected during read at offset
0x000000dfbce000 in file
'D:\FocalPoint\Databases\001_001\pdi_stage_001_001 .mdf'..
It occured during cube and dimision updates on analytical services. The D
drive resides on a SAN. Our network administrator is saying there are no
drive issues. Everything I have read on Error 823 is hardware related.
Any suggestions. Thanks.
Take a look at http://support.microsoft.com/kb/313702
Linchi
"brymer28303" wrote:

> We received this error last night:
> Error: 823, Severity: 24, State: 2
> I/O error 38(Reached the end of the file.) detected during read at offset
> 0x000000dfbce000 in file
> 'D:\FocalPoint\Databases\001_001\pdi_stage_001_001 .mdf'..
> It occured during cube and dimision updates on analytical services. The D
> drive resides on a SAN. Our network administrator is saying there are no
> drive issues. Everything I have read on Error 823 is hardware related.
> Any suggestions. Thanks.
>

I/O error 38(Reached the end of the file.)

We received this error last night:
Error: 823, Severity: 24, State: 2
I/O error 38(Reached the end of the file.) detected during read at offset
0x000000dfbce000 in file
'D:\FocalPoint\Databases\001_001\pdi_stage_001_001.mdf'..
It occured during cube and dimision updates on analytical services. The D
drive resides on a SAN. Our network administrator is saying there are no
drive issues. Everything I have read on Error 823 is hardware related.
Any suggestions. Thanks.Take a look at http://support.microsoft.com/kb/313702
Linchi
"brymer28303" wrote:
> We received this error last night:
> Error: 823, Severity: 24, State: 2
> I/O error 38(Reached the end of the file.) detected during read at offset
> 0x000000dfbce000 in file
> 'D:\FocalPoint\Databases\001_001\pdi_stage_001_001.mdf'..
> It occured during cube and dimision updates on analytical services. The D
> drive resides on a SAN. Our network administrator is saying there are no
> drive issues. Everything I have read on Error 823 is hardware related.
> Any suggestions. Thanks.
>

I/O error (bad page id)

We can't get the database restored. It won't reattach
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
>

I/O error (bad page id)

We can't get the database restored. It won't reattach
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...
If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>
|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
>

I/O error (bad page id)

We can't get the database restored. It won't reattach
(sp_attach_db) and it won't restore from a backup file.
So we have the Mdf and Ldf files and a backup file but
since we detached, we can't seem to get the data on-line
again to do anything.
Any attempts to repair the database with CHECKDB results
in consistency errors. The database can be backed up but
not restored from a recent database backup. We tried to
recreate the database by using Copy Database Wizard and
DTS both with no success because of an I/O error. Trying
to query tables sometimes worked and other times didn't.
Finally, the database was detached and ended any attempts
to re-attach thus far.
Server: Msg 7995, Level 16, State 1, Line 1
Database 'woodsch0304' consistency errors in sysobjects,
sysindexes, syscolumns, or systypes prevent further
CHECKDB processing.
Not giving up yet...If the database has any value to you, it is time to open a call to MS PSS. I
think the cost is still $249.
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> We can't get the database restored. It won't reattach
> (sp_attach_db) and it won't restore from a backup file.
> So we have the Mdf and Ldf files and a backup file but
> since we detached, we can't seem to get the data on-line
> again to do anything.
> Any attempts to repair the database with CHECKDB results
> in consistency errors. The database can be backed up but
> not restored from a recent database backup. We tried to
> recreate the database by using Copy Database Wizard and
> DTS both with no success because of an I/O error. Trying
> to query tables sometimes worked and other times didn't.
> Finally, the database was detached and ended any attempts
> to re-attach thus far.
> Server: Msg 7995, Level 16, State 1, Line 1
> Database 'woodsch0304' consistency errors in sysobjects,
> sysindexes, syscolumns, or systypes prevent further
> CHECKDB processing.
>
> Not giving up yet...
>|||You've lost a page in one of the critical (for CHECKDB and database use)
system tables so you're in danger of losing your database. I concur with
Wayne's suggestion - PSS is your best bet.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:eGoGOWkJEHA.624@.TK2MSFTNGP11.phx.gbl...
> If the database has any value to you, it is time to open a call to MS PSS.
I
> think the cost is still $249.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Computer Education Services Corporation (CESC), Charlotte, NC
> www.computeredservices.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
>
> "Bob Pearson" <anonymous@.discussions.microsoft.com> wrote in message
> news:120d01c4263f$ffce93e0$a501280a@.phx.gbl...
> > We can't get the database restored. It won't reattach
> > (sp_attach_db) and it won't restore from a backup file.
> >
> > So we have the Mdf and Ldf files and a backup file but
> > since we detached, we can't seem to get the data on-line
> > again to do anything.
> >
> > Any attempts to repair the database with CHECKDB results
> > in consistency errors. The database can be backed up but
> > not restored from a recent database backup. We tried to
> > recreate the database by using Copy Database Wizard and
> > DTS both with no success because of an I/O error. Trying
> > to query tables sometimes worked and other times didn't.
> >
> > Finally, the database was detached and ended any attempts
> > to re-attach thus far.
> >
> > Server: Msg 7995, Level 16, State 1, Line 1
> >
> > Database 'woodsch0304' consistency errors in sysobjects,
> > sysindexes, syscolumns, or systypes prevent further
> > CHECKDB processing.
> >
> >
> > Not giving up yet...
> >
>

I want to run .sql file in MSDE

I want to run .sql file without using query analyzer in sql server
how to do thatBoth osql.exe and isql.exe are command prompt utilities from which you can run .sql files or sql-commands.

I want separate data sources for 1 RDL file

Hello all,
Here's my situation:
I have a single RDL file that describes a certain report.
I have different databases on different computers with the same tables
but different data in each table.
I need people to go to each computer, run the same RDL file, but have
it show the data that is specific to their database.
For instance, there is a single .rdl file which describes a personnel
report, and i want people at site A to only see info about site A's
personnel, and people at site B to only see info about site B's
personnel.
Is this possible? If so, is there any advice you can give me to help do
this? Thank you.
Kevin Green
Software Engineer
Pragmatech SoftwareOn each computer have an rds file specifying the connection properties for
that computer.
"KevinGreen24@.gmail.com" wrote:
> Hello all,
> Here's my situation:
> I have a single RDL file that describes a certain report.
> I have different databases on different computers with the same tables
> but different data in each table.
> I need people to go to each computer, run the same RDL file, but have
> it show the data that is specific to their database.
> For instance, there is a single .rdl file which describes a personnel
> report, and i want people at site A to only see info about site A's
> personnel, and people at site B to only see info about site B's
> personnel.
> Is this possible? If so, is there any advice you can give me to help do
> this? Thank you.
> Kevin Green
> Software Engineer
> Pragmatech Software
>|||Well we're working of a SaaS model, so every end user is running a thin
client, so we're not installing anything on the end user's computer.
magendo_man wrote:
> On each computer have an rds file specifying the connection properties for
> that computer.
> "KevinGreen24@.gmail.com" wrote:
> > Hello all,
> >
> > Here's my situation:
> >
> > I have a single RDL file that describes a certain report.
> >
> > I have different databases on different computers with the same tables
> > but different data in each table.
> >
> > I need people to go to each computer, run the same RDL file, but have
> > it show the data that is specific to their database.
> >
> > For instance, there is a single .rdl file which describes a personnel
> > report, and i want people at site A to only see info about site A's
> > personnel, and people at site B to only see info about site B's
> > personnel.
> >
> > Is this possible? If so, is there any advice you can give me to help do
> > this? Thank you.
> >
> > Kevin Green
> > Software Engineer
> > Pragmatech Software
> >
> >|||Are the databases on two different SQL servers? How do the users run the
report? From Report Manager, or embedded in a web page?
If they are running the reports from Report Manager on different servers
then you need to set up data sources (i.e. rds files) on each, with the same
name, but pointing to the site-specific database.
"KevinGreen24@.gmail.com" wrote:
> Well we're working of a SaaS model, so every end user is running a thin
> client, so we're not installing anything on the end user's computer.
> magendo_man wrote:
> > On each computer have an rds file specifying the connection properties for
> > that computer.
> >
> > "KevinGreen24@.gmail.com" wrote:
> >
> > > Hello all,
> > >
> > > Here's my situation:
> > >
> > > I have a single RDL file that describes a certain report.
> > >
> > > I have different databases on different computers with the same tables
> > > but different data in each table.
> > >
> > > I need people to go to each computer, run the same RDL file, but have
> > > it show the data that is specific to their database.
> > >
> > > For instance, there is a single .rdl file which describes a personnel
> > > report, and i want people at site A to only see info about site A's
> > > personnel, and people at site B to only see info about site B's
> > > personnel.
> > >
> > > Is this possible? If so, is there any advice you can give me to help do
> > > this? Thank you.
> > >
> > > Kevin Green
> > > Software Engineer
> > > Pragmatech Software
> > >
> > >
>|||Also in RS 2005 you can dynamically change the datasource based on the user.
I haven't done this but it is one of the capabilities.
Bruce Loehle-Conger
"magendo_man" <magendoman@.discussions.microsoft.com> wrote in message
news:BCD91F31-A84B-40D2-8B00-2FB36C53CD52@.microsoft.com...
> Are the databases on two different SQL servers? How do the users run the
> report? From Report Manager, or embedded in a web page?
> If they are running the reports from Report Manager on different servers
> then you need to set up data sources (i.e. rds files) on each, with the
> same
> name, but pointing to the site-specific database.
> "KevinGreen24@.gmail.com" wrote:
>> Well we're working of a SaaS model, so every end user is running a thin
>> client, so we're not installing anything on the end user's computer.
>> magendo_man wrote:
>> > On each computer have an rds file specifying the connection properties
>> > for
>> > that computer.
>> >
>> > "KevinGreen24@.gmail.com" wrote:
>> >
>> > > Hello all,
>> > >
>> > > Here's my situation:
>> > >
>> > > I have a single RDL file that describes a certain report.
>> > >
>> > > I have different databases on different computers with the same
>> > > tables
>> > > but different data in each table.
>> > >
>> > > I need people to go to each computer, run the same RDL file, but have
>> > > it show the data that is specific to their database.
>> > >
>> > > For instance, there is a single .rdl file which describes a personnel
>> > > report, and i want people at site A to only see info about site A's
>> > > personnel, and people at site B to only see info about site B's
>> > > personnel.
>> > >
>> > > Is this possible? If so, is there any advice you can give me to help
>> > > do
>> > > this? Thank you.
>> > >
>> > > Kevin Green
>> > > Software Engineer
>> > > Pragmatech Software
>> > >
>> > >
>>|||We host 1 report server which each client browser will access. We host
1 database server which has databases which hold the information for
each company that uses our product. So basically we host the data for
each company and we host the report server.
Each client browser will connect to the report server, and at that time
the appropriate company database will be accessed and the information
retrieved, along with the common .rdl file, and the appropriate report
rendered.
So there's 1 .rdl file which describes the form of the report, and
there are N databases for the N companies that use the product, which
hold the data. I need the 1 .rdl file to be able to display information
from any of the N databases that we have, based on the company that's
trying to access the report.
Does this make sense?
magendo_man wrote:
> Are the databases on two different SQL servers? How do the users run the
> report? From Report Manager, or embedded in a web page?
> If they are running the reports from Report Manager on different servers
> then you need to set up data sources (i.e. rds files) on each, with the same
> name, but pointing to the site-specific database.
> "KevinGreen24@.gmail.com" wrote:
> > Well we're working of a SaaS model, so every end user is running a thin
> > client, so we're not installing anything on the end user's computer.
> >
> > magendo_man wrote:
> > > On each computer have an rds file specifying the connection properties for
> > > that computer.
> > >
> > > "KevinGreen24@.gmail.com" wrote:
> > >
> > > > Hello all,
> > > >
> > > > Here's my situation:
> > > >
> > > > I have a single RDL file that describes a certain report.
> > > >
> > > > I have different databases on different computers with the same tables
> > > > but different data in each table.
> > > >
> > > > I need people to go to each computer, run the same RDL file, but have
> > > > it show the data that is specific to their database.
> > > >
> > > > For instance, there is a single .rdl file which describes a personnel
> > > > report, and i want people at site A to only see info about site A's
> > > > personnel, and people at site B to only see info about site B's
> > > > personnel.
> > > >
> > > > Is this possible? If so, is there any advice you can give me to help do
> > > > this? Thank you.
> > > >
> > > > Kevin Green
> > > > Software Engineer
> > > > Pragmatech Software
> > > >
> > > >
> >
> >|||That's exactly what i need, but i can't figure out how!
It also has to be secure of course.
Bruce L-C [MVP] wrote:
> Also in RS 2005 you can dynamically change the datasource based on the user.
> I haven't done this but it is one of the capabilities.
> Bruce Loehle-Conger
> "magendo_man" <magendoman@.discussions.microsoft.com> wrote in message
> news:BCD91F31-A84B-40D2-8B00-2FB36C53CD52@.microsoft.com...
> > Are the databases on two different SQL servers? How do the users run the
> > report? From Report Manager, or embedded in a web page?
> >
> > If they are running the reports from Report Manager on different servers
> > then you need to set up data sources (i.e. rds files) on each, with the
> > same
> > name, but pointing to the site-specific database.
> >
> > "KevinGreen24@.gmail.com" wrote:
> >
> >> Well we're working of a SaaS model, so every end user is running a thin
> >> client, so we're not installing anything on the end user's computer.
> >>
> >> magendo_man wrote:
> >> > On each computer have an rds file specifying the connection properties
> >> > for
> >> > that computer.
> >> >
> >> > "KevinGreen24@.gmail.com" wrote:
> >> >
> >> > > Hello all,
> >> > >
> >> > > Here's my situation:
> >> > >
> >> > > I have a single RDL file that describes a certain report.
> >> > >
> >> > > I have different databases on different computers with the same
> >> > > tables
> >> > > but different data in each table.
> >> > >
> >> > > I need people to go to each computer, run the same RDL file, but have
> >> > > it show the data that is specific to their database.
> >> > >
> >> > > For instance, there is a single .rdl file which describes a personnel
> >> > > report, and i want people at site A to only see info about site A's
> >> > > personnel, and people at site B to only see info about site B's
> >> > > personnel.
> >> > >
> >> > > Is this possible? If so, is there any advice you can give me to help
> >> > > do
> >> > > this? Thank you.
> >> > >
> >> > > Kevin Green
> >> > > Software Engineer
> >> > > Pragmatech Software
> >> > >
> >> > >
> >>
> >>|||The below is from help. Note that they show using a parameter but you could
also use the result of a query that uses the global variable for user (I
believe it is User!Username). Have a table that provides the mapping from
user to database.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
>>>>>>>>
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/4d8f0ae1-102b-4b3d-9155-fa584c962c9e.htm
Data Source Expressions
Data source expressions are processed at run time or when a report is
previewed. The expression must be written in Visual Basic. Use the following
guidelines when defining a data source expression:
a.. Design the report using a static connection string. A static
connection string refers to a connection string that is not set through an
expression (for example, when you follow the steps for creating a
report-specific or shared data source, you are defining a static connection
string). Using a static connection string allows you to connect to the data
source in Report Designer so that you can get the query results you need to
create the report.
b.. When defining the data source connection, do not use a shared data
source. You cannot use a data source expression in a shared data source. You
must define a report-specific data source for the report.
c.. Specify credentials separately from the connection string. You can use
stored credentials, prompted credentials, or integrated security.
d.. Add a report parameter to specify a data source. For parameter values,
you can either provide a static list of available values (in this case, the
available values should be data sources you can use with the report) or
define a query that retrieves a list of data sources at run time.
e.. Be sure that the list of data sources share the same database schema.
All report design begins with schema information. If there is a mismatch
between the schema used to define the report and the actual schema used by
the report at run time, the report might not run.
f.. Before publishing the report, replace the static connection string
with an expression. Wait until you are finished designing the report before
you replace the static connection string with an expression. Once you use an
expression, you cannot execute the query in Report Designer. Furthermore,
the field list in the Datasets window and the Parameters list will not
update automatically.
>>>>>>>>>
<KevinGreen24@.gmail.com> wrote in message
news:1153261522.566759.269720@.h48g2000cwc.googlegroups.com...
> That's exactly what i need, but i can't figure out how!
> It also has to be secure of course.
> Bruce L-C [MVP] wrote:
>> Also in RS 2005 you can dynamically change the datasource based on the
>> user.
>> I haven't done this but it is one of the capabilities.
>> Bruce Loehle-Conger
>> "magendo_man" <magendoman@.discussions.microsoft.com> wrote in message
>> news:BCD91F31-A84B-40D2-8B00-2FB36C53CD52@.microsoft.com...
>> > Are the databases on two different SQL servers? How do the users run
>> > the
>> > report? From Report Manager, or embedded in a web page?
>> >
>> > If they are running the reports from Report Manager on different
>> > servers
>> > then you need to set up data sources (i.e. rds files) on each, with the
>> > same
>> > name, but pointing to the site-specific database.
>> >
>> > "KevinGreen24@.gmail.com" wrote:
>> >
>> >> Well we're working of a SaaS model, so every end user is running a
>> >> thin
>> >> client, so we're not installing anything on the end user's computer.
>> >>
>> >> magendo_man wrote:
>> >> > On each computer have an rds file specifying the connection
>> >> > properties
>> >> > for
>> >> > that computer.
>> >> >
>> >> > "KevinGreen24@.gmail.com" wrote:
>> >> >
>> >> > > Hello all,
>> >> > >
>> >> > > Here's my situation:
>> >> > >
>> >> > > I have a single RDL file that describes a certain report.
>> >> > >
>> >> > > I have different databases on different computers with the same
>> >> > > tables
>> >> > > but different data in each table.
>> >> > >
>> >> > > I need people to go to each computer, run the same RDL file, but
>> >> > > have
>> >> > > it show the data that is specific to their database.
>> >> > >
>> >> > > For instance, there is a single .rdl file which describes a
>> >> > > personnel
>> >> > > report, and i want people at site A to only see info about site
>> >> > > A's
>> >> > > personnel, and people at site B to only see info about site B's
>> >> > > personnel.
>> >> > >
>> >> > > Is this possible? If so, is there any advice you can give me to
>> >> > > help
>> >> > > do
>> >> > > this? Thank you.
>> >> > >
>> >> > > Kevin Green
>> >> > > Software Engineer
>> >> > > Pragmatech Software
>> >> > >
>> >> > >
>> >>
>> >>
>|||Right. That's similar what I did to solve the problem this morning:
1. Create the master .rdl file that has a hidden parameter called
"DbName"
2. Make the connection string in the data source dynamic:
="Data Source=(local);Initial Catalog=" & Parameters!DbName.Value
3. Create a linked report(s)
4. Using the report manager, set the default value of DbName according
to the company that will own each linked report.
This way, the parameter can be set for the report based on the company
it belongs to, and it's also secure because role-based security can be
set up at the linked report level.
Bruce L-C [MVP] wrote:
> The below is from help. Note that they show using a parameter but you could
> also use the result of a query that uses the global variable for user (I
> believe it is User!Username). Have a table that provides the mapping from
> user to database.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> >>>>>>>>
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/4d8f0ae1-102b-4b3d-9155-fa584c962c9e.htm
> Data Source Expressions
> Data source expressions are processed at run time or when a report is
> previewed. The expression must be written in Visual Basic. Use the following
> guidelines when defining a data source expression:
> a.. Design the report using a static connection string. A static
> connection string refers to a connection string that is not set through an
> expression (for example, when you follow the steps for creating a
> report-specific or shared data source, you are defining a static connection
> string). Using a static connection string allows you to connect to the data
> source in Report Designer so that you can get the query results you need to
> create the report.
>
> b.. When defining the data source connection, do not use a shared data
> source. You cannot use a data source expression in a shared data source. You
> must define a report-specific data source for the report.
>
> c.. Specify credentials separately from the connection string. You can use
> stored credentials, prompted credentials, or integrated security.
>
> d.. Add a report parameter to specify a data source. For parameter values,
> you can either provide a static list of available values (in this case, the
> available values should be data sources you can use with the report) or
> define a query that retrieves a list of data sources at run time.
>
> e.. Be sure that the list of data sources share the same database schema.
> All report design begins with schema information. If there is a mismatch
> between the schema used to define the report and the actual schema used by
> the report at run time, the report might not run.
>
> f.. Before publishing the report, replace the static connection string
> with an expression. Wait until you are finished designing the report before
> you replace the static connection string with an expression. Once you use an
> expression, you cannot execute the query in Report Designer. Furthermore,
> the field list in the Datasets window and the Parameters list will not
> update automatically.
> >>>>>>>>>
> <KevinGreen24@.gmail.com> wrote in message
> news:1153261522.566759.269720@.h48g2000cwc.googlegroups.com...
> > That's exactly what i need, but i can't figure out how!
> >
> > It also has to be secure of course.
> >
> > Bruce L-C [MVP] wrote:
> >> Also in RS 2005 you can dynamically change the datasource based on the
> >> user.
> >>
> >> I haven't done this but it is one of the capabilities.
> >>
> >> Bruce Loehle-Conger
> >>
> >> "magendo_man" <magendoman@.discussions.microsoft.com> wrote in message
> >> news:BCD91F31-A84B-40D2-8B00-2FB36C53CD52@.microsoft.com...
> >> > Are the databases on two different SQL servers? How do the users run
> >> > the
> >> > report? From Report Manager, or embedded in a web page?
> >> >
> >> > If they are running the reports from Report Manager on different
> >> > servers
> >> > then you need to set up data sources (i.e. rds files) on each, with the
> >> > same
> >> > name, but pointing to the site-specific database.
> >> >
> >> > "KevinGreen24@.gmail.com" wrote:
> >> >
> >> >> Well we're working of a SaaS model, so every end user is running a
> >> >> thin
> >> >> client, so we're not installing anything on the end user's computer.
> >> >>
> >> >> magendo_man wrote:
> >> >> > On each computer have an rds file specifying the connection
> >> >> > properties
> >> >> > for
> >> >> > that computer.
> >> >> >
> >> >> > "KevinGreen24@.gmail.com" wrote:
> >> >> >
> >> >> > > Hello all,
> >> >> > >
> >> >> > > Here's my situation:
> >> >> > >
> >> >> > > I have a single RDL file that describes a certain report.
> >> >> > >
> >> >> > > I have different databases on different computers with the same
> >> >> > > tables
> >> >> > > but different data in each table.
> >> >> > >
> >> >> > > I need people to go to each computer, run the same RDL file, but
> >> >> > > have
> >> >> > > it show the data that is specific to their database.
> >> >> > >
> >> >> > > For instance, there is a single .rdl file which describes a
> >> >> > > personnel
> >> >> > > report, and i want people at site A to only see info about site
> >> >> > > A's
> >> >> > > personnel, and people at site B to only see info about site B's
> >> >> > > personnel.
> >> >> > >
> >> >> > > Is this possible? If so, is there any advice you can give me to
> >> >> > > help
> >> >> > > do
> >> >> > > this? Thank you.
> >> >> > >
> >> >> > > Kevin Green
> >> >> > > Software Engineer
> >> >> > > Pragmatech Software
> >> >> > >
> >> >> > >
> >> >>
> >> >>
> >