Instances of SQL

Hi,

Is it possible to install more than one instance of SQL on the same server?
I am thinking of the SQL that comes with Windows 2003 SBS (Small business)

--
Thank you
Please post onlyYes. Sql2k supports named instances.

http://msdn.microsoft.com/library/e...nstall_259u.asp

"!!bogus" <hello@.microb.com> wrote in message
news:Dwavc.95442$tb4.3789522@.news20.bellglobal.com ...
> Hi,
> Is it possible to install more than one instance of SQL on the same server?
> I am thinking of the SQL that comes with Windows 2003 SBS (Small business)
> --
> Thank you
> Please post only|||"!!bogus" <hello@.microb.com> wrote in message news:<Dwavc.95442$tb4.3789522@.news20.bellglobal.com>...
> Hi,
> Is it possible to install more than one instance of SQL on the same server?
> I am thinking of the SQL that comes with Windows 2003 SBS (Small business)

SQL2000 supports multiple instances (see Books Online), but you need
to consider the impact on the server resources - you will need to
manage CPU and memory carefully to give each instance enough to work
with, as well as leaving enough for the OS and other applications. I
don't know anything about SBS specifically, but my feeling would be
that since SBS already installs a bunch of different applications on
the same server, you probably don't want to add the complexity of
multiple MSSQL instances.

Depending on what you want to achieve, you might want to look at MSDE,
which is a free version of MSSQL with some limitations:

http://www.microsoft.com/sql/msde/

Simon

instance name

Hi,
my machine name is webdev5
when I run sql server, it asks for the server name, I enter 'webdev5'
and using windows authentication.
where can I find out about the instance name? on my machine? I am using
2005
thank you
kenInstance name is most commonly used when there are multiple installations of
SQL Server on the same computer. If you have only one SQL Server, and if you
did not deselect the "Use DEFAULT Instance" option when installing, then
your instance is named 'webdev5'.
Read about Instance and Instance Names in Books Online.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<SQLken@.gmail.com> wrote in message
news:1159221843.315654.187670@.m7g2000cwm.googlegroups.com...
> Hi,
> my machine name is webdev5
> when I run sql server, it asks for the server name, I enter 'webdev5'
> and using windows authentication.
> where can I find out about the instance name? on my machine? I am using
> 2005
> thank you
> ken
>|||Hi,
If you are logged into SQL Server Management studio then connect to SQL
server and open a Query window and execute
SELECT @.@.SERVERNAME
If its a default instance it just returns the machine name. This will be
trated as the SQL Server name. If you have Servername\Instancename;
then you have installed a named SQL Server instance.
You could also get this information from Errorlog of SQL Server. There you
have to look for Server name:.............
Thanks
Hari
SQL Server MVP
<SQLken@.gmail.com> wrote in message
news:1159221843.315654.187670@.m7g2000cwm.googlegroups.com...
> Hi,
> my machine name is webdev5
> when I run sql server, it asks for the server name, I enter 'webdev5'
> and using windows authentication.
> where can I find out about the instance name? on my machine? I am using
> 2005
> thank you
> ken
>sql

instance name

Hi,
my machine name is webdev5
when I run sql server, it asks for the server name, I enter 'webdev5'
and using windows authentication.
where can I find out about the instance name? on my machine? I am using
2005
thank you
ken
Instance name is most commonly used when there are multiple installations of
SQL Server on the same computer. If you have only one SQL Server, and if you
did not deselect the "Use DEFAULT Instance" option when installing, then
your instance is named 'webdev5'.
Read about Instance and Instance Names in Books Online.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<SQLken@.gmail.com> wrote in message
news:1159221843.315654.187670@.m7g2000cwm.googlegro ups.com...
> Hi,
> my machine name is webdev5
> when I run sql server, it asks for the server name, I enter 'webdev5'
> and using windows authentication.
> where can I find out about the instance name? on my machine? I am using
> 2005
> thank you
> ken
>
|||Hi,
If you are logged into SQL Server Management studio then connect to SQL
server and open a Query window and execute
SELECT @.@.SERVERNAME
If its a default instance it just returns the machine name. This will be
trated as the SQL Server name. If you have Servername\Instancename;
then you have installed a named SQL Server instance.
You could also get this information from Errorlog of SQL Server. There you
have to look for Server name:.............
Thanks
Hari
SQL Server MVP
<SQLken@.gmail.com> wrote in message
news:1159221843.315654.187670@.m7g2000cwm.googlegro ups.com...
> Hi,
> my machine name is webdev5
> when I run sql server, it asks for the server name, I enter 'webdev5'
> and using windows authentication.
> where can I find out about the instance name? on my machine? I am using
> 2005
> thank you
> ken
>

instance name

Hi,
my machine name is webdev5
when I run sql server, it asks for the server name, I enter 'webdev5'
and using windows authentication.
where can I find out about the instance name? on my machine? I am using
2005
thank you
kenInstance name is most commonly used when there are multiple installations of
SQL Server on the same computer. If you have only one SQL Server, and if you
did not deselect the "Use DEFAULT Instance" option when installing, then
your instance is named 'webdev5'.
Read about Instance and Instance Names in Books Online.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<SQLken@.gmail.com> wrote in message
news:1159221843.315654.187670@.m7g2000cwm.googlegroups.com...
> Hi,
> my machine name is webdev5
> when I run sql server, it asks for the server name, I enter 'webdev5'
> and using windows authentication.
> where can I find out about the instance name? on my machine? I am using
> 2005
> thank you
> ken
>|||Hi,
If you are logged into SQL Server Management studio then connect to SQL
server and open a Query window and execute
SELECT @.@.SERVERNAME
If its a default instance it just returns the machine name. This will be
trated as the SQL Server name. If you have Servername\Instancename;
then you have installed a named SQL Server instance.
You could also get this information from Errorlog of SQL Server. There you
have to look for Server name:.............
Thanks
Hari
SQL Server MVP
<SQLken@.gmail.com> wrote in message
news:1159221843.315654.187670@.m7g2000cwm.googlegroups.com...
> Hi,
> my machine name is webdev5
> when I run sql server, it asks for the server name, I enter 'webdev5'
> and using windows authentication.
> where can I find out about the instance name? on my machine? I am using
> 2005
> thank you
> ken
>sql

Installting sqlserver 2005 on the client machine for windows application

Hi
I developed a windows application in Visual studio 2005 and the database is sqlexpress.
I wanted my application to run on another system.For that i have installed sqlexpress 2005 on that machine.But that machine doesn't show me any enterprise manager or query manager for sqlserver.
Is there any solution for this.

Thanks

hi,

yes... you have to separately download and install SQL Server Management Studio Express... http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

regards

|||SQL Server Express does not come with EM or Query Analyzer. These two components have been merged into the SQL Server Managment Studio. The SQL Server Management Studio Express (which actually is a stripped of SQL Server Managment Studio (aka SSMS)) can be downloaded separately from Microsoft or is already included in the Express Advanced Edition (which actually includes some other cool features like Reporting Services for SQL Server Express).

http://msdn.microsoft.com/vstudio/express/sql/download/

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.desql

Installting SQL Server 2k5

I have SQL Server 2000 on Windows XP professional OS.
I want to install SQLServer 2K5?
Do I need to to uninstall SQLServer2K before installing SQLServer 2k5 ?
What steps should be taken before and after SQL Server 2K5 installation?
Thanks,Hi,
You should be able to install SQL Server 2005 and SQL Server 2000 side
by side.
I think you may need SP2 of XP Pro.
One important thing to watch out for is any old components left behind
by past builds of SQL Server 2005 or Visual Studio 2005. If they are
present you need to uninstall CAREFULLY and in the right order or you
can expect to hit problems.
Andrew Watt
MVP - InfoPath
On Wed, 12 Oct 2005 12:01:02 -0700, "UA" <usha.anumolu@.eds.com> wrote:

>I have SQL Server 2000 on Windows XP professional OS.
>I want to install SQLServer 2K5?
>Do I need to to uninstall SQLServer2K before installing SQLServer 2k5 ?
>What steps should be taken before and after SQL Server 2K5 installation?
>
>Thanks,

Installting SQL Server 2k5

I have SQL Server 2000 on Windows XP professional OS.
I want to install SQLServer 2K5?
Do I need to to uninstall SQLServer2K before installing SQLServer 2k5 ?
What steps should be taken before and after SQL Server 2K5 installation?
Thanks,
Hi,
You should be able to install SQL Server 2005 and SQL Server 2000 side
by side.
I think you may need SP2 of XP Pro.
One important thing to watch out for is any old components left behind
by past builds of SQL Server 2005 or Visual Studio 2005. If they are
present you need to uninstall CAREFULLY and in the right order or you
can expect to hit problems.
Andrew Watt
MVP - InfoPath
On Wed, 12 Oct 2005 12:01:02 -0700, "UA" <usha.anumolu@.eds.com> wrote:

>I have SQL Server 2000 on Windows XP professional OS.
>I want to install SQLServer 2K5?
>Do I need to to uninstall SQLServer2K before installing SQLServer 2k5 ?
>What steps should be taken before and after SQL Server 2K5 installation?
>
>Thanks,

Installting SQL Server 2k5

I have SQL Server 2000 on Windows XP professional OS.
I want to install SQLServer 2K5?
Do I need to to uninstall SQLServer2K before installing SQLServer 2k5 ?
What steps should be taken before and after SQL Server 2K5 installation?
Thanks,Hi,
You should be able to install SQL Server 2005 and SQL Server 2000 side
by side.
I think you may need SP2 of XP Pro.
One important thing to watch out for is any old components left behind
by past builds of SQL Server 2005 or Visual Studio 2005. If they are
present you need to uninstall CAREFULLY and in the right order or you
can expect to hit problems.
Andrew Watt
MVP - InfoPath
On Wed, 12 Oct 2005 12:01:02 -0700, "UA" <usha.anumolu@.eds.com> wrote:
>I have SQL Server 2000 on Windows XP professional OS.
>I want to install SQLServer 2K5?
>Do I need to to uninstall SQLServer2K before installing SQLServer 2k5 ?
>What steps should be taken before and after SQL Server 2K5 installation?
>
>Thanks,

Installing/Deploying Windows App with SQL Server 2005 CE

I am a little bit confused about making an installer/deployer.

I have an application using SQL Server 2005 CE (I have just updated to the most recent version Jan 2007). It will run on a new desktop PC (windows XP) if I install the SQL CE runtime and then copy the .EXE and the .SDF database file. This is great but my client wants the whole thing to install as one operation. I thought click once could do this but it seems that is only for Pocket PC targets? Can anyone point me to a method to make an appropriate installer please?

Pete

I am using the following:
SQLServerCE31-EN.msi - installer for SQL CE server runtime
SSCE31VSTools-ENU.exe - installed over VS 2005 SP1.Have you tried publishing it? - I have no problem doing this for standard apps.

In Brian Noyes' book "Smart Client Deployment with ClickOnce' there are several small sections on how to deploy CE

P235 "An example is the SQL Server 2005 CE CTP that is available at the time of this writing. You can download the .msi file to do and install of SQL Compact and you can also download the Bootstrapper Manifest needed to add SQL Compact to your Bootstrapper. If you are provided the Bootstrapper files, all you need to do is place the files in the right location."

I can recommend this book - written in a logical straightforward manner. Also covered is Deploying a (sic CE) Client Database with your Application (starting P 167)

Here is the video link from Steve Lasker's blog on CE deployment http://blogs.msdn.com/stevelasker/archive/2006/07/06/SQLServerEverywhereDeploymentOptions.aspx|||If you use something like Inno Setup you can just have the installer copy the SQL Server Compact Edition dll files to the application's folder. Then you won't have to worry about using the MSI file. Check the SQL Server Compact Edition Books Online for more.

Or, (still using Inno Setup) add the MSI file to the setup project and run it with the necessary options to install it right before the installation ends.
|||Great responses guys! I'll try everything you suggest and feed back here.

Pete|||Ok, thanks for the references to Steve Laskers blog. The screencast of deployment options gave me the information I needed. I have ended up using the VS Setup project to install the SQL CE dlls into the app folder and the GAC. That is great for me (I didn't want publish/deploy). I am sure Inno would have done the same but I don't have time to learn another setup app now (I've used NCIS as well in the past). Anyway, kudos to all of you and Steve Lasker and the MS Virtual PC people without which I would need 2 PCs to test all this...

Pete|||I should mention that it looks like just copying SQL Server Compact Edition's DLLs is not a way to do it anymore. I remember seeing it in the SQL Server Everywhere Edition Books Online but it seems to have been removed from the SQL Server Compact Edition Books Online. Just thought I shouldd mention this for anyone else who reads this thread.

Installing with MSDE on XP

I would like to install MSDE in Windows XP Professional. When I tried
to install it gave me an error A strong SA password is required for
security reasons. Please use SAPWD switch
I do not know how it handle this error if you can please let me how to
install in XP.
Step by Step process.
Thanking You
Your's Truly
Raj
hi Raj,
Raj wrote:
> I would like to install MSDE in Windows XP Professional. When I tried
> to install it gave me an error A strong SA password is required for
> security reasons. Please use SAPWD switch
> I do not know how it handle this error if you can please let me how to
> install in XP.
> Step by Step process.
Setup.exe is a boostrap intaller for MSDE and accepts parameters you can
provide at the command line as long as in a companion .Ini file..
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
you can find the list of all supported parameters...
please open a DOS command window and navigate to the folder hosting the
setup.exe file...
there you can run setup.exe with all the parameters of your choice..
- usually you have to provide the SAPWD parameter to specify a strong
password for the "sa" builtin login in order to protect it from both
internal and external attacks..
specify then
SAPWD=your_strong_password
- additional parameters let you specify if you want a named instance or a
default instance... specify
INSTANCENAME=your_instance_name
if you want a named instance...
- another parameter let you specify if you want to allow remote connections
from other PCs in your lan to your MSDE instance.. specify
DISABLENETWORKPROTOCOLS=0
if you need this feature...
- by default, MSDE is installed allowing only WindowsNT authenticated
connections and preventing standard SQL Server authenticated ones.. more on
this at http://support.microsoft.com/default...b;en-us;325022
you can specify
SECURITYMODE=SQL
to allow mixed mode security, thus allowing both WInNT integrated security
and standard SQL Server authenticated connections..
- the final important parameter is
/L*v "c:\msdelog.txt"
where you will allow verbose logging of the installation process, resulting
in a text file of about 2mb for a successfull installation you can inspect,
in case of problems, for
RETURN VALUE 3
entries... about 10 lines before each entry some (sometime cryptic)
description of the problwm will be reported..
so, if you like to install a "named instace" named "Raj" with mixed security
and enabled network protocols for remote connections you can run setup.exe
boostrap installer providing all parameters as
c:\..\>setup.exe /qb INSTANCENAME=Raj SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD=your_strong_password /L*v "c:\msdelog.txt"
you can later manage your installed instance via the native character tool
oSql.exe as described at
http://support.microsoft.com/default...;EN-US;q325003 or use a
third party tool, both commercial or free, like the ones listed at
http://www.microsoft.com/sql/msde/partners/ or
http://www.aspfaq.com/show.asp?id=2442... google for further..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Installing Veritas on Windows 2003 server

I'm trying to install Veritas Back Exec 9.1 on my Windows 2003 server acting
as domain controller.
First event is:
MsiInstaller Event ID 1015
Failed to connect to server. Error: 0x800401F0
Then MsiInstaller Event ID 11707
1: 2: VERITAS Backup Exec for Windows Servers 3: 1: 1707
Then MsiInstaller Event ID 11708
Product: Microsoft SQL Server Desktop Engine -- Installation operation
failed.
What is the problem?
Could be the same prob that I have.
I have installede Backup Exec 9.1 to ′with MS SQL 2000 server
No I would like to add my dekstop and laptop option and this need to have the MSDE desktop , but my installation failes,
here is where I am comming to now
I need to find the Hotfix as stated in this artickel Knowledge Base-article - 829386
(You Cannot Install MSDE 2000 if the Server Service Is Not Running)
http://support.microsoft.com/default...b;en-us;829386
anyone know where to find it ?
|||My server is domain controller.I have a member server running Windows 2003
and on it i can install Veritas without problems.Hm.....?!
|||You sure can, I would recommend installing BE 9.1 SP1

Installing Standard Edition on server with 4Gb memory

Are there any problems associated with installing SQL
Server 2000 "Standard Edition" on Windows 2000 Server on a
server with 4Gb of memory? I believe that the standard
edition will only "support" 2Gb of memory, but does that
mean that it will only access 2Gb or that it is not
supported on a server with more than 2Gb? I cannot find
any documentation on this.It just means the relational server won't access more than 2GB of memory.
There is no problem running it on a 4GB server, or an 8GB server, or ...
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Ludwig" <lbdba@.yahoo.com> wrote in message
news:06f901c36c50$d665dfd0$a401280a@.phx.gbl...
> Are there any problems associated with installing SQL
> Server 2000 "Standard Edition" on Windows 2000 Server on a
> server with 4Gb of memory? I believe that the standard
> edition will only "support" 2Gb of memory, but does that
> mean that it will only access 2Gb or that it is not
> supported on a server with more than 2Gb? I cannot find
> any documentation on this.|||Is that documented anywhere in a KB article or in Books-
online?
>--Original Message--
>It just means the relational server won't access more
than 2GB of memory.
>There is no problem running it on a 4GB server, or an 8GB
server, or ...
>--
>Hal Berenson, SQL Server MVP
>True Mountain Group LLC
>
>"Ludwig" <lbdba@.yahoo.com> wrote in message
>news:06f901c36c50$d665dfd0$a401280a@.phx.gbl...
>> Are there any problems associated with installing SQL
>> Server 2000 "Standard Edition" on Windows 2000 Server
on a
>> server with 4Gb of memory? I believe that the standard
>> edition will only "support" 2Gb of memory, but does that
>> mean that it will only access 2Gb or that it is not
>> supported on a server with more than 2Gb? I cannot find
>> any documentation on this.
>
>.
>|||Books Online:
mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn
.htm
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Ludwig" <lbdba@.yahoo.com> wrote in message news:069e01c36c65$aa8e6020$a601280a@.phx.gbl...
> Is that documented anywhere in a KB article or in Books-
> online?
> >--Original Message--
> >It just means the relational server won't access more
> than 2GB of memory.
> >There is no problem running it on a 4GB server, or an 8GB
> server, or ...
> >
> >--
> >Hal Berenson, SQL Server MVP
> >True Mountain Group LLC
> >
> >
> >"Ludwig" <lbdba@.yahoo.com> wrote in message
> >news:06f901c36c50$d665dfd0$a401280a@.phx.gbl...
> >> Are there any problems associated with installing SQL
> >> Server 2000 "Standard Edition" on Windows 2000 Server
> on a
> >> server with 4Gb of memory? I believe that the standard
> >> edition will only "support" 2Gb of memory, but does that
> >> mean that it will only access 2Gb or that it is not
> >> supported on a server with more than 2Gb? I cannot find
> >> any documentation on this.
> >
> >
> >.
> >|||Thanks Tibor. This is a good summary page, but it only
states ambiguously:
"This table shows the maximum amount of physical memory,
or RAM, that the database engine in each SQL Server 2000
edition can support"
It does not state if the server can have more than 2Gb.
>--Original Message--
>Books Online:
>mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%
20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn
>..htm
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?oi=djq&as
ugroup=microsoft.public.sqlserver
>|||At some point it becomes silly to document things, and this one is over that
line.
Why would SQL Server care if there was more memory on the machine then it
will actually utilize? It doesn't, nor could it.
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Ludwig" <lbdba@.yahoo.com> wrote in message
news:0f1401c36cfd$a9cb6230$a001280a@.phx.gbl...
> Thanks Tibor. This is a good summary page, but it only
> states ambiguously:
> "This table shows the maximum amount of physical memory,
> or RAM, that the database engine in each SQL Server 2000
> edition can support"
> It does not state if the server can have more than 2Gb.
> >--Original Message--
> >Books Online:
> >mk:@.MSITStore:C:\Program%20Files\Microsoft%20SQL%
> 20Server\80\Tools\Books\architec.chm::/8_ar_ts_8dbn
> >..htm
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?oi=djq&as
> ugroup=microsoft.public.sqlserver
> >
>|||Hal
I disagree and I think you have missed the point. I don't
think I am alone in this as I have read other postings
along the same line - I was hoping this time maybe I'd
receive a reference to a Microsoft document that is a
little clearer about what "support" means.
If SQL Server is configured to handle the memory
dynamically - rather than be allocated a fixed amount of
RAM - I would imagine it would be very important for it to
know how much memory is available on the server for other
processes.
I try not to be cynical, but I'm wondering if perhaps
there is a reason for the ambiguous documentation of the
memory capability - "Well I'm not real sure and I better
not take a chance, let's get the Enterprise Edition".
Ludwig
>--Original Message--
>At some point it becomes silly to document things, and
this one is over that
>line.
>Why would SQL Server care if there was more memory on the
machine then it
>will actually utilize? It doesn't, nor could it.
>--
>Hal Berenson, SQL Server MVP
>True Mountain Group LLC
>

Installing SSRS 2005 on Windows XP Pro

Hi All,

I want to run SSRS 2K5 on a windows XP pro workstation. Is this possible as I have tried several times but no luck. Cannot connect to the website http://servername/reports from internet explorer 7.

Has anyone ever successfully done this?

Gappo

Make sure you have IIS and Sql Server Agent running and actually insert your server name into the address (eg http://localhost/reports).

Good luck...

Installing SS2K5 SP1 on Windows 2003 server R2

Has anyone run into the issue of installing SP1 on a 2003 R2 server?

I have seen a post or two on other sites but I cannot seem to find them again.

Install goes great up until it comes to the upgrading of SSIS (Integration Services).

At that point is fails with the error of:

A recently applied update, KB913090, failed to install.

This is a dialog box that I hit the "send error report" button. It then goes to the upgrading of the Client Components (CC) and fails with the same error message of:

A recently applied update, KB913090, failed to install.

The ugrade the continues after I hit the same "send error report"button.

ALL of the other steps complete with SUCESSFULLY. Only the SSIS and Client Components show a failed status in the Installation Prog

In the Installation Complete screen, I can highlight both the SSIS and CC and see an additional error of:

Unable to install Windows Installer MSP file

I then can hit the View Log button (which I have done for the SSIS step) and see the error log but I am having a tough time making heads or tails of it.

I have attached the output from the SSIS error log below.

I have a couple of questions:

1. Is the install of SP1 good for all the other steps that completed successfully

2. Has anyone had issues with installing SP1 on a Windows 2003 R2 server? I have installed SP1 on other Windows 2003 servers NOT running R2 and it ran like a champ.

Thanks ALL!

====== ERROR LOG FROM SSIS UPGRADE ============================================

01/07/2007 19:23:23.247 ================================================================================
01/07/2007 19:23:23.247 Hotfix package launched
01/07/2007 19:23:23.747 Product discovery successfully completed during the install process for DTS
01/07/2007 19:23:23.762 SP Level check successfully completed during the install process for DTS
01/07/2007 19:23:23.778 Product language check successfully completed during the install process for DTS
01/07/2007 19:23:23.793 Product version check successfully completed during the install process for DTS
01/07/2007 19:23:23.825 Command-line instance name check completed during the install process
01/07/2007 19:23:23.840 Baseline build check completed during the install process
01/07/2007 19:28:41.393 Attempting to install instance: DTS
01/07/2007 19:28:41.408 Attempting to install target: AUS02DB13
01/07/2007 19:28:41.440 Attempting to check for locked files: sqlrun_dts.msp
01/07/2007 19:28:41.502 Attempting to check for locked files: \\AUS02DB13\g$2fe15a257eaedfc36c121fc912\HotFixDTS\Files\sqlrun_dts.msp
01/07/2007 19:28:41.518 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\DTS9\Logs\DTS9_Hotfix_KB913090_sqlrun_dts.msp.out
01/07/2007 19:28:48.799 MSP returned 1602: The user cancels installation.
01/07/2007 19:28:49.017 Successfully checked file: \\AUS02DB13\g$2fe15a257eaedfc36c121fc912\HotFixDTS\Files\sqlrun_dts.msp
01/07/2007 19:28:49.033 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
01/07/2007 19:28:49.064 Successfully read registry key: PendingFileRenameOperations
01/07/2007 19:28:49.080 Multi-string values:
01/07/2007 19:28:49.096 \?\g:\a4be8c9b1bce3ffa869bbb5137
01/07/2007 19:28:49.111 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\Shared\9.0.2047.0
C:\Program Files\Microsoft SQL Server\Shared\dbghelp.dll
01/07/2007 19:28:49.127 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\SqlDumper.exe
01/07/2007 19:28:49.142 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\SqlDumper.exe
01/07/2007 19:28:49.158 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\SqlDumper.exe
01/07/2007 19:28:49.174 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsqm.exe
01/07/2007 19:28:49.205 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\dtsinstall.exe
01/07/2007 19:28:49.221 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Resources\msmdsrv.rll
01/07/2007 19:28:49.236 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Resources\msmdsrv.rll
01/07/2007 19:28:49.252 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Resources\msmdsrv.rll
01/07/2007 19:28:49.267 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\msmdlocal.dll
01/07/2007 19:28:49.283 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\msmdlocal.dll
01/07/2007 19:28:49.299 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\msmdlocal.dll
01/07/2007 19:28:49.314 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\9.0.2047.0
C:\Program Files\Microsoft SQL Server\Shared\msmdlo~1.dll
01/07/2007 19:28:49.330 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServerCe.Dts.Provider\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServerCe.Dts.Provider.dll
01/07/2007 19:28:49.361 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DataStorage\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.DataStorage.dll
01/07/2007 19:28:49.377 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.CustomControls\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.CustomControls.dll
01/07/2007 19:28:49.392 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.WizardFramework\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.WizardFramework.dll
01/07/2007 19:28:49.408 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices.Xmla\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.XMLA.dll
01/07/2007 19:28:49.424 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.OlapEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.OlapEnum.dll
01/07/2007 19:28:49.439 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.ActiveXScriptTask.xml
01/07/2007 19:28:49.455 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.ActiveXScriptTaskUtil\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.470 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.ActiveXScriptTaskUtil\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.486 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.ActiveXScriptTaskUtil\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.517 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ActiveXScriptTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ActiveXScriptTask.dll
01/07/2007 19:28:49.533 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.549 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.ActiveXScriptTask.dll
01/07/2007 19:28:49.580 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.DataTransformationServices.Controls\9.0.242.0__89845dcd8080cc91\Microsoft.DataTransformationServices.Controls.DLL
01/07/2007 19:28:49.595 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTSWizard.exe
01/07/2007 19:28:49.611 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\SDK\Assemblies\Microsoft.SqlServer.TxScript.dll
01/07/2007 19:28:49.627 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Microsoft.SqlServer.TxScript.dll
01/07/2007 19:28:49.642 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TxScript\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TxScript.dll
01/07/2007 19:28:49.674 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSampling.dll
01/07/2007 19:28:49.689 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSampling.dll
01/07/2007 19:28:49.705 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSampling.dll
01/07/2007 19:28:49.720 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxRowCount.dll
01/07/2007 19:28:49.752 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxRowCount.dll
01/07/2007 19:28:49.767 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxRowCount.dll
01/07/2007 19:28:49.783 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Dts.DtsClient\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.Dts.DtsClient.dll
01/07/2007 19:28:49.799 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DataReaderDest\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.DataReaderDest.dll
01/07/2007 19:28:49.814 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.Dts.DtsClient.dll
01/07/2007 19:28:49.830 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Microsoft.SqlServer.DataReaderDest.dll
01/07/2007 19:28:49.830 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.TransferSqlServerObjectsTask.xml
01/07/2007 19:28:49.845 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferSqlServerObjectsTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferSqlServerObjectsTask.dll
01/07/2007 19:28:49.877 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferSqlServerObjectsTask.dll
01/07/2007 19:28:49.892 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.TransferStoredProceduresTask.xml
01/07/2007 19:28:49.908 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.TransferLoginsTask.xml
01/07/2007 19:28:49.924 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.TransferJobsTask.xml
01/07/2007 19:28:49.939 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.TransferErrorMessagesTask.xml
01/07/2007 19:28:49.970 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.TransferDatabasesTask.xml
01/07/2007 19:28:49.986 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferStoredProceduresTask.dll
01/07/2007 19:28:50.002 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferLoginsTask.dll
01/07/2007 19:28:50.002 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferJobsTask.dll
01/07/2007 19:28:50.033 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferErrorMessagesTask.dll
01/07/2007 19:28:50.033 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferDatabasesTask.dll
01/07/2007 19:28:50.049 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TransferObjectsTask.dll
01/07/2007 19:28:50.064 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferStoredProceduresTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferStoredProceduresTask.dll
01/07/2007 19:28:50.080 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferLoginsTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferLoginsTask.dll
01/07/2007 19:28:50.095 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferJobsTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferJobsTask.dll
01/07/2007 19:28:50.111 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferErrorMessagesTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferErrorMessagesTask.dll
01/07/2007 19:28:50.111 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferDatabasesTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferDatabasesTask.dll
01/07/2007 19:28:50.127 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TransferObjectsTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TransferObjectsTask.dll
01/07/2007 19:28:50.142 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DtsTransferProvider\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.DtsTransferProvider.dll
01/07/2007 19:28:50.158 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.TableTransferGeneratorTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.TableTransferGeneratorTask.dll
01/07/2007 19:28:50.174 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.DtsTransferProvider.dll
01/07/2007 19:28:50.189 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.TableTransferGeneratorTask.dll
01/07/2007 19:28:50.189 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxTermExtraction.dll
01/07/2007 19:28:50.205 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxTermExtraction.dll
01/07/2007 19:28:50.220 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxTermExtraction.dll
01/07/2007 19:28:50.236 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxTermLookup.dll
01/07/2007 19:28:50.252 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxTermLookup.dll
01/07/2007 19:28:50.267 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxTermLookup.dll
01/07/2007 19:28:50.283 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dts.rll
01/07/2007 19:28:50.283 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dtsconn.rll
01/07/2007 19:28:50.299 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dtsconn.rll
01/07/2007 19:28:50.314 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dtsconn.rll
01/07/2007 19:28:50.330 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\en\Microsoft.SqlServer.ForEachAdoEnumerator.xml
01/07/2007 19:28:50.345 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\en\Microsoft.SqlServer.ForEachSMOEnumerator.xml
01/07/2007 19:28:50.377 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Connections\en\Microsoft.SqlServer.ManagedConnections.xml
01/07/2007 19:28:50.392 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTSPipelinePerf.dll
01/07/2007 19:28:50.408 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dtspipeline.rll
01/07/2007 19:28:50.408 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dtspipeline.rll
01/07/2007 19:28:50.424 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Resources\dtspipeline.rll
01/07/2007 19:28:50.439 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.FtpTask.xml
01/07/2007 19:28:50.455 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.FtpTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.FtpTask.dll
01/07/2007 19:28:50.470 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.FtpTask.dll
01/07/2007 19:28:50.486 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.ExecProcTask.xml
01/07/2007 19:28:50.517 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.SendMailTask.xml
01/07/2007 19:28:50.549 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.MSMQTask.xml
01/07/2007 19:28:50.580 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.MSMQUtil\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.595 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.MSMQUtil\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.595 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.MSMQUtil\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.611 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.MSMQTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.MSMQTask.dll
01/07/2007 19:28:50.627 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.642 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.658 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.674 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll
01/07/2007 19:28:50.689 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxMulticast.dll
01/07/2007 19:28:50.705 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxMulticast.dll
01/07/2007 19:28:50.705 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxMulticast.dll
01/07/2007 19:28:50.720 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\CommandDest.dll
01/07/2007 19:28:50.736 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\CommandDest.dll
01/07/2007 19:28:50.752 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\CommandDest.dll
01/07/2007 19:28:50.767 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxFileInserter.dll
01/07/2007 19:28:50.767 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxFileInserter.dll
01/07/2007 19:28:50.799 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxFileInserter.dll
01/07/2007 19:28:50.845 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxFileExtractor.dll
01/07/2007 19:28:50.845 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxFileExtractor.dll
01/07/2007 19:28:50.861 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxFileExtractor.dll
01/07/2007 19:28:50.877 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxLineage.dll
01/07/2007 19:28:50.892 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxLineage.dll
01/07/2007 19:28:50.908 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxLineage.dll
01/07/2007 19:28:50.924 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxUnPivot.dll
01/07/2007 19:28:50.924 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxUnPivot.dll
01/07/2007 19:28:50.955 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxUnPivot.dll
01/07/2007 19:28:50.955 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxPivot.dll
01/07/2007 19:28:50.970 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxMergeJoin.dll
01/07/2007 19:28:50.986 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxMergeJoin.dll
01/07/2007 19:28:51.002 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxMergeJoin.dll
01/07/2007 19:28:51.017 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxUnAll.dll
01/07/2007 19:28:51.033 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSort.dll
01/07/2007 19:28:51.033 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSort.dll
01/07/2007 19:28:51.049 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSort.dll
01/07/2007 19:28:51.064 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSplit.dll
01/07/2007 19:28:51.080 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSplit.dll
01/07/2007 19:28:51.080 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxSplit.dll
01/07/2007 19:28:51.095 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxLookup.dll
01/07/2007 19:28:51.111 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxLookup.dll
01/07/2007 19:28:51.127 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxLookup.dll
01/07/2007 19:28:51.142 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxGroupDups.dll
01/07/2007 19:28:51.158 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxGroupDups.dll
01/07/2007 19:28:51.158 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxGroupDups.dll
01/07/2007 19:28:51.174 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxDerived.dll
01/07/2007 19:28:51.189 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxDerived.dll
01/07/2007 19:28:51.205 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxDerived.dll
01/07/2007 19:28:51.220 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxDataConvert.dll
01/07/2007 19:28:51.236 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxDataConvert.dll
01/07/2007 19:28:51.252 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxDataConvert.dll
01/07/2007 19:28:51.267 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxCopyMap.dll
01/07/2007 19:28:51.267 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxCopyMap.dll
01/07/2007 19:28:51.283 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxCopyMap.dll
01/07/2007 19:28:51.299 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxCharMap.dll
01/07/2007 19:28:51.314 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxCharMap.dll
01/07/2007 19:28:51.330 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxCharMap.dll
01/07/2007 19:28:51.345 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxBestMatch.dll
01/07/2007 19:28:51.345 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxBestMatch.dll
01/07/2007 19:28:51.361 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxBestMatch.dll
01/07/2007 19:28:51.377 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxAgg.dll
01/07/2007 19:28:51.392 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxAgg.dll
01/07/2007 19:28:51.408 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\TxAgg.dll
01/07/2007 19:28:51.424 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.XmlTask.xml
01/07/2007 19:28:51.439 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\dts\Binn\batchparser90.dll
01/07/2007 19:28:51.455 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.SQLTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SQLTask.dll
01/07/2007 19:28:51.470 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\SQLTaskConnections.dll
01/07/2007 19:28:51.470 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\SQLTaskConnections.dll
01/07/2007 19:28:51.486 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\SQLTaskConnections.dll
01/07/2007 19:28:51.502 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.SQLTask.dll
01/07/2007 19:28:51.533 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\SqlDest.dll
01/07/2007 19:28:51.549 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\SqlDest.dll
01/07/2007 19:28:51.580 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\SqlDest.dll
01/07/2007 19:28:51.595 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\SDK\Assemblies\Microsoft.SqlServer.ScriptTask.dll
01/07/2007 19:28:51.595 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ScriptTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ScriptTask.dll
01/07/2007 19:28:51.611 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.ScriptTask.dll
01/07/2007 19:28:51.627 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RecordSetDest.dll
01/07/2007 19:28:51.642 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RecordSetDest.dll
01/07/2007 19:28:51.658 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RecordSetDest.dll
01/07/2007 19:28:51.674 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RawSource.dll
01/07/2007 19:28:51.674 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RawSource.dll
01/07/2007 19:28:51.705 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RawSource.dll
01/07/2007 19:28:51.705 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RawDest.dll
01/07/2007 19:28:51.720 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RawDest.dll
01/07/2007 19:28:51.736 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\RawDest.dll
01/07/2007 19:28:51.752 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.ASTasks.xml
01/07/2007 19:28:51.767 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ASTasks\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ASTasks.dll
01/07/2007 19:28:51.783 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.ASTasks.dll
01/07/2007 19:28:51.799 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\OleDbSrc.dll
01/07/2007 19:28:51.799 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\OleDbSrc.dll
01/07/2007 19:28:51.830 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\OleDbSrc.dll
01/07/2007 19:28:51.845 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\OleDbDest.dll
01/07/2007 19:28:51.845 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\OleDbDest.dll
01/07/2007 19:28:51.861 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\OleDbDest.dll
01/07/2007 19:28:51.892 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\FlatFileDest.dll
01/07/2007 19:28:51.908 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\FlatFileDest.dll
01/07/2007 19:28:51.908 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\FlatFileDest.dll
01/07/2007 19:28:51.924 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\FlatFileSrc.dll
01/07/2007 19:28:51.955 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\FlatFileSrc.dll
01/07/2007 19:28:51.955 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\FlatFileSrc.dll
01/07/2007 19:28:51.970 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.FileSystemTask.xml
01/07/2007 19:28:51.986 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.FileSystemTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.FileSystemTask.dll
01/07/2007 19:28:52.017 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.FileSystemTask.dll
01/07/2007 19:28:52.033 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\ExecPackageTask.dll
01/07/2007 19:28:52.049 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.DmQueryTask.xml
01/07/2007 19:28:52.064 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DMQueryTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.DmQueryTask.dll
01/07/2007 19:28:52.064 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.DmQueryTask.dll
01/07/2007 19:28:52.095 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.BulkInsertTask.xml
01/07/2007 19:28:52.111 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BulkInsertTaskConnections\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.127 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BulkInsertTaskConnections\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.142 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BulkInsertTaskConnections\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.158 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.BulkInsertTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.BulkInsertTask.dll
01/07/2007 19:28:52.174 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.189 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.BulkInsertTask.dll
01/07/2007 19:28:52.205 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.WMIEWTask.xml
01/07/2007 19:28:52.220 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.WMIDRTask.xml
01/07/2007 19:28:52.236 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\en\Microsoft.SqlServer.WebServiceTask.xml
01/07/2007 19:28:52.252 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.WebServiceTask\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.WebServiceTask.dll
01/07/2007 19:28:52.267 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.MaintenancePlanTasks\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.MaintenancePlanTasks.dll
01/07/2007 19:28:52.283 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.WebServiceTask.dll
01/07/2007 19:28:52.299 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Tasks\Microsoft.SqlServer.MaintenancePlanTasks.dll
01/07/2007 19:28:52.314 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Resources\dtspipeline.rll
01/07/2007 19:28:52.330 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Resources\dtspipeline.rll
01/07/2007 19:28:52.345 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Resources\dtspipeline.rll
01/07/2007 19:28:52.345 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\exceldest.dll
01/07/2007 19:28:52.377 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\exceldest.dll
01/07/2007 19:28:52.392 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\exceldest.dll
01/07/2007 19:28:52.392 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\excelsrc.dll
01/07/2007 19:28:52.408 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\excelsrc.dll
01/07/2007 19:28:52.439 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\excelsrc.dll
01/07/2007 19:28:52.439 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Microsoft.SqlServer.XMLSrc.dll
01/07/2007 19:28:52.455 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\PipelineComponents\Microsoft.SqlServer.ADONETSrc.dll
01/07/2007 19:28:52.470 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.XmlSrc\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.XMLSrc.dll
01/07/2007 19:28:52.486 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ADONETSrc\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ADONETSrc.dll
01/07/2007 19:28:52.502 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.PipelineHost\9.0.242.0__89845dcd8080cc91\Microsoft.SQLServer.PipelineHost.dll
01/07/2007 19:28:52.517 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTSPipeline.dll
01/07/2007 19:28:52.533 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ForEachNodeListEnumerator\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ForEachNodeListEnumerator.dll
01/07/2007 19:28:52.549 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ForEachSMOEnumerator\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ForEachSMOEnumerator.dll
01/07/2007 19:28:52.564 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\DTEParseMgd\9.0.242.0__89845dcd8080cc91\DTEParseMgd.dll
01/07/2007 19:28:52.580 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\DTEParseMgd\9.0.242.0__89845dcd8080cc91\DTEParseMgd.dll
01/07/2007 19:28:52.595 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\DTEParseMgd\9.0.242.0__89845dcd8080cc91\DTEParseMgd.dll
01/07/2007 19:28:52.595 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTSComEx.dll
01/07/2007 19:28:52.611 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\dtsmsg.dll
01/07/2007 19:28:52.642 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTSLog.dll
01/07/2007 19:28:52.642 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DtsUt.dll
01/07/2007 19:28:52.658 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTS.dll
01/07/2007 19:28:52.674 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\Binn\DTEParsM.dll
01/07/2007 19:28:52.705 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn.90.2047.0
E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\NodeList.dll
01/07/2007 19:28:52.705 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\ForEachFileEnumerator.dll
01/07/2007 19:28:52.720 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\ForEachFileEnumerator.dll
01/07/2007 19:28:52.736 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\ForEachFileEnumerator.dll
01/07/2007 19:28:52.752 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\ForEachEnumerators\Microsoft.SqlServer.ForEachSMOEnumerator.dll
01/07/2007 19:28:52.767 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\DTS\Binn\MsDtsSrvr.exe
01/07/2007 19:28:52.783 Failed to read version information for the following file: C:\Program Files\Microsoft.NET\ADOMD.NET\en\Microsoft.AnalysisServices.AdomdClient.xml
01/07/2007 19:28:52.799 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft.NET\ADOMD.NET\Microsoft.AnalysisServices.AdomdClient.dll
01/07/2007 19:28:52.814 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.AdomdClient.dll
01/07/2007 19:28:52.830 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\msasxpress.dll
01/07/2007 19:28:52.845 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\msasxpress.dll
01/07/2007 19:28:52.861 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\msasxpress.dll
01/07/2007 19:28:52.877 Failed to read version information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\Binn\Resources\
E:\MSSQL\MSSQL\SS2K5\Tools\Binn\Resources\sqlcm.xml
01/07/2007 19:28:52.877 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\Binn\Resources\SqlManager.rll
01/07/2007 19:28:52.908 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\Binn\Resources\SqlManager.rll
01/07/2007 19:28:52.924 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\Binn\Resources\SqlManager.rll
01/07/2007 19:28:52.939 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\binn\SqlManager.dll
01/07/2007 19:28:52.939 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\binn\SqlManager.dll
01/07/2007 19:28:52.970 Failed to read associated hotfix build information for the following file: E:\MSSQL\MSSQL\SS2K5\Tools\binn\SqlManager.dll
01/07/2007 19:28:52.986 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsvcsync.dll
01/07/2007 19:28:52.986 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsvcsync.dll
01/07/2007 19:28:53.002 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsvcsync.dll
01/07/2007 19:28:53.017 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsecacctchg.dll
01/07/2007 19:28:53.033 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsecacctchg.dll
01/07/2007 19:28:53.049 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlsecacctchg.dll
01/07/2007 19:28:53.064 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlftacct.dll
01/07/2007 19:28:53.064 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlftacct.dll
01/07/2007 19:28:53.095 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\sqlftacct.dll
01/07/2007 19:28:53.111 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\isacctchange.dll
01/07/2007 19:28:53.111 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\isacctchange.dll
01/07/2007 19:28:53.127 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\isacctchange.dll
01/07/2007 19:28:53.158 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\svrenumapi.dll
01/07/2007 19:28:53.174 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\svrenumapi.dll
01/07/2007 19:28:53.189 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\svrenumapi.dll
01/07/2007 19:28:53.189 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\Shared.90.2047.0
C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Rmo\9.0.242.0__89845dcd8080cc91\Rmo.dll
01/07/2007 19:28:53.205 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.DLL
01/07/2007 19:28:53.236 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.DataWarehouse.Interfaces\9.0.242.0__89845dcd8080cc91\Microsoft.DataWarehouse.Interfaces.DLL
01/07/2007 19:28:53.252 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.RegSvrEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.RegSvrEnum.dll
01/07/2007 19:28:53.252 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
01/07/2007 19:28:53.267 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
01/07/2007 19:28:53.299 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
01/07/2007 19:28:53.299 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ServiceBrokerEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ServiceBrokerEnum.dll
01/07/2007 19:28:53.314 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.WmiEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.WmiEnum.dll
01/07/2007 19:28:53.330 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SqlEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SqlEnum.dll
01/07/2007 19:28:53.345 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SmoEnum.dll
01/07/2007 19:28:53.361 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Smo\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.Smo.dll
01/07/2007 19:28:53.377 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\SqlSAC.exe
01/07/2007 19:28:53.392 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\Shared\Microsoft.SqlSac.Public.dll
01/07/2007 19:28:53.392 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.msxml6_interop\6.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.msxml6_interop.dll
01/07/2007 19:28:53.517 Attempting to install file: sqlrun_dts.msp
01/07/2007 19:28:53.548 Attempting to install file: \\AUS02DB13\g$2fe15a257eaedfc36c121fc912\HotFixDTS\Files\sqlrun_dts.msp
01/07/2007 19:28:53.564 Creating MSP install log file at: C:\WINDOWS\Hotfix\DTS9\Logs\DTS9_Hotfix_KB913090_sqlrun_dts.msp.log
01/07/2007 19:28:53.580 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
01/07/2007 19:28:53.580 Failed to read registry key: Debug
01/07/2007 19:29:48.375 MSP returned 1603: A fatal error occurred during installation.
01/07/2007 19:29:48.672 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
01/07/2007 19:29:48.687 Failed to read registry key: Debug
01/07/2007 19:29:48.687 Unable to install MSP file: \\AUS02DB13\g$2fe15a257eaedfc36c121fc912\HotFixDTS\Files\sqlrun_dts.msp
01/07/2007 19:29:48.703 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/07/2007 19:29:48.703 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
01/07/2007 19:29:48.750
01/07/2007 19:29:48.765 Product Status Summary:
01/07/2007 19:29:48.781 Product: SQL Server Native Client
01/07/2007 19:29:48.797 SQL Server Native Client (RTM ) - Success
01/07/2007 19:29:48.812
01/07/2007 19:29:48.828 Product: Setup Support Files
01/07/2007 19:29:48.844 Setup Support Files (RTM ) - Success
01/07/2007 19:29:48.844
01/07/2007 19:29:48.859 Product: Database Services
01/07/2007 19:29:48.875 Database Services (SP1 2047 ENU) - Success
01/07/2007 19:29:48.890
01/07/2007 19:29:48.906 Product: Integration Services
01/07/2007 19:29:48.922 Integration Services (SP1 ENU) - Failure
01/07/2007 19:29:48.937 Details: Unable to install Windows Installer MSP file
01/07/2007 19:29:48.953
01/07/2007 19:29:48.969 Product: Client Components
01/07/2007 19:29:48.969 Client Components (SP1 2047 ENU) - Not Applied
01/07/2007 19:29:48.984
01/07/2007 19:29:49.015 Product: MSXML 6.0 Parser
01/07/2007 19:29:49.062 MSXML 6.0 Parser (RTM ) - Not Applied
01/07/2007 19:29:49.078
01/07/2007 19:29:49.094 Product: SQLXML4
01/07/2007 19:29:49.109 SQLXML4 (RTM ) - Not Applied
01/07/2007 19:29:49.109
01/07/2007 19:29:49.140 Product: Backward Compatibility
01/07/2007 19:29:49.156 Backward Compatibility (RTM ) - Not Applied
01/07/2007 19:29:49.156
01/07/2007 19:29:49.172 Product: Microsoft SQL Server VSS Writer
01/07/2007 19:29:49.187 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
01/07/2007 19:29:49.203

Can you provide the DTS msp log (I don't remember the actual name) so we can investigate? It should be in the %windir%\Hotfix\DTS9\Logs folder?

Thanks,

Peter Saddow

|||

Sorry for the delay.

Your reply was about an hour too late - lol.

I uninstalled SS2K5 and ran into another issue. SSIS run great now BUT the SQL Server service is hanging with a "change pending state" and is impossible to kill.

I have opened a case with Microsoft.

Thanks for the help!

J Kusch

sql

Installing SQL205 in a cluster with mount points

I am struggling with an installation of SQL2005 on Windows Server 2003 SP1. I
am trying to set up a 2 node cluster with a single instance of sql2005. I
need to use mount points so I create a shared disk for the mount points and 2
disks which are mounted in there. The shared disk is called M: and the other
disks have names (DB and Logs). There will be more in due course but I
thought I would start with 2.
The install proceeds okay until it gets to the point where I have to choose
a cluster group to put it in. I have created one with M: in it plus the two
mounted disks. However, when I select that one it insists in making M: the
destination for the data files and, of course there is not enough space there
for them. It seems to be completed incapable of using the mount points. In
fact ir doesn't see them at all.
Does anyone know how to fix this or is it just not possible to use mount
points with SQL2005 in a cluster despite what the documentation says
Hi Colin,
This link has information about special mount point considerations
http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
Regards
Antonio Soto
Solid Quality Leaning
http://www.solidqualitylearning.com
DISCLAIMER:
Anything written in this message represents solely the point of view of the
sender. This message does not imply endorsement from Solid Quality Learning,
and it does not represent the point of view of Solid Quality Learning or any
other person, company or institution mentioned in this message
"Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribi en el mensaje
news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>I am struggling with an installation of SQL2005 on Windows Server 2003 SP1.
>I
> am trying to set up a 2 node cluster with a single instance of sql2005. I
> need to use mount points so I create a shared disk for the mount points
> and 2
> disks which are mounted in there. The shared disk is called M: and the
> other
> disks have names (DB and Logs). There will be more in due course but I
> thought I would start with 2.
> The install proceeds okay until it gets to the point where I have to
> choose
> a cluster group to put it in. I have created one with M: in it plus the
> two
> mounted disks. However, when I select that one it insists in making M: the
> destination for the data files and, of course there is not enough space
> there
> for them. It seems to be completed incapable of using the mount points. In
> fact ir doesn't see them at all.
> Does anyone know how to fix this or is it just not possible to use mount
> points with SQL2005 in a cluster despite what the documentation says
|||Dear Antonio,
Thanks for the info. The bit that is mssing from that document - at least I
cannot find it is how big the base drive has to be. As far as I can see what
is not mentioned is that the SQL 2005 installation will put some files in the
base drive. Most of the installation goes somewhere such as C:\Program
Files\... but some files are put in the shared drive which is acting as the
base drive. I have tried creating the base drive with about 50 GB and SQL
2005 then installs. I don't know how much will go in there for different
installation choices but I am now trying a 30GB base drive to see if that is
big enough.
Anyway, to summarise, the base drive isn't just for mount points as the
document suggests but also holds quite a few installation files which I guess
need to be shared between the cluster nodes.
Best wishes...
Colin
"Antonio Soto" wrote:

> Hi Colin,
> This link has information about special mount point considerations
> http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
> Regards
> Antonio Soto
> Solid Quality Leaning
> http://www.solidqualitylearning.com
> DISCLAIMER:
> Anything written in this message represents solely the point of view of the
> sender. This message does not imply endorsement from Solid Quality Learning,
> and it does not represent the point of view of Solid Quality Learning or any
> other person, company or institution mentioned in this message
>
> "Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribió en el mensaje
> news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>
>

Installing SQL server2000 / windows 2003 server

I am going to start installing sql server soon, do I have to have IIS installed? Is it a requirement?
Thanks.Not at all...................U can proceed without IIS.........but need to install SP3a to run sql server 2000 on windows 2003 OS|||Oh, ok. Thanks so much.

-Laura

Installing SQL Server Reporting Services

Current machine Windows XP Pro with sp2. Successfully installed all portions
of Reporting Services with exception to Report Designer to SQL Server 2000.
The message which appears at almost the conclusion of installation states
"There is a problem with this Windows Installer package. A program run as
part of the setup did not finish as expected. Contact your support personnel
or package vendor.". Then it rolls back the installation.
Looking through the Event Logs it shows there was an error registered due to
the msvcr71.dll. The error value is:
Error value: C0000013
Disk type: 5
This file is on the CD for the Reporting Services and it should not be
damaged, in use, etc. by any other process other than that of the installer.
After installing all but the designer, I even installed service pack 1 for
Reporting Services and still have the same result.
Ideas?
Your thoughts on this matter will be appreciated.Just wanted to post the resolution to the situation below.
From the event log it showed that it had a problem with the msvcr71.dll.
Comparing the datetime of the file on the CD to that of the system, they were
different.
So I copied the contents of the CD to the hard drive to point to the older
file to see if it would help. The result, it did not help so I put the
original file from the CD back into the Reportin Services install directory
of my hard drive.
In reading other posts regarding installs, there was a file mentioned in the
01SEP2004 post by Daniel Reib [MSFT] to an 'install problem' (original
subject for posting), which was RSRun.msi.
I installed this file with Visual Studio .NET open and within a project. It
seemed to be having a problem without VS.NET being open, at least on 2
machines. In the past attempts the event log showed that it was having a
problem starting up the VS.NET and that is why I opened the application and
project while installing. The install was successful and the Report Designer
is working.
Hope this helps some other people that experienced a similar issue.
-Guy
"Guy G" wrote:
> Current machine Windows XP Pro with sp2. Successfully installed all portions
> of Reporting Services with exception to Report Designer to SQL Server 2000.
> The message which appears at almost the conclusion of installation states
> "There is a problem with this Windows Installer package. A program run as
> part of the setup did not finish as expected. Contact your support personnel
> or package vendor.". Then it rolls back the installation.
> Looking through the Event Logs it shows there was an error registered due to
> the msvcr71.dll. The error value is:
> Error value: C0000013
> Disk type: 5
> This file is on the CD for the Reporting Services and it should not be
> damaged, in use, etc. by any other process other than that of the installer.
> After installing all but the designer, I even installed service pack 1 for
> Reporting Services and still have the same result.
> Ideas?
> Your thoughts on this matter will be appreciated.
>

Installing SQL Server on Windows 2003 Server

When I try to install SQL Server 2000 on Windows 2003, I get the message
that SQL Server 2000 SP2 and below are not supported.
How do I install SQL Server 2000 on Windows 2003?
You just install it (the dialog is a warning, not a halt), and then install
SP3a immediately afterward.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"David F" <davef@.nksj.ru> wrote in message
news:eyvESFcREHA.3452@.TK2MSFTNGP10.phx.gbl...
> When I try to install SQL Server 2000 on Windows 2003, I get the message
> that SQL Server 2000 SP2 and below are not supported.
> How do I install SQL Server 2000 on Windows 2003?
>
|||That's what I thought but when I tried doing so the installation proceeded
and then displayed an error that the Full Text service failed to install.
This was the only error I received.
I rebooted the machine and saw that the SQL Server folders had been
installed but the services had not been created. I tried to uninstall SQL
Server from the Add/Remove programs but SQL Server was not in the list. I
then inserted the SQL Server CD and tried to uninstall. There was no option
to uninstall. There was however, an option to install a new instance of SQL
Server.
Thus I appear to be in the worst situation: 1) I cannot uninstall because
neither CP or the SQL Server CD recognizes the failed installation and 2) I
cannot reinstall because the SQL Server CD thinks the default installation
already exists. (I cannot installed a named instance of SQL Server for use
with MS CRM)
BTW, I installed the standard edition of SQL Server with Mixed Mode
authentication to run under a specific domain administrator account.
Does anyone have any idea how I can clean up this failed installation?
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:uqVBYbcREHA.628@.TK2MSFTNGP11.phx.gbl...
> You just install it (the dialog is a warning, not a halt), and then
install
> SP3a immediately afterward.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
> "David F" <davef@.nksj.ru> wrote in message
> news:eyvESFcREHA.3452@.TK2MSFTNGP10.phx.gbl...
>
|||David,
[vbcol=seagreen]
Did you check sqlstp.log for the any hints/messages for this error?
[vbcol=seagreen]
'HOW TO: Manually Remove SQL Srv. 2000 Default, Named or Virtual'
http://support.microsoft.com/?id=290991
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"David F" <davef@.nksj.ru> wrote in message
news:uyzijvcREHA.3300@.tk2msftngp13.phx.gbl...
> That's what I thought but when I tried doing so the installation proceeded
> and then displayed an error that the Full Text service failed to install.
> This was the only error I received.
> I rebooted the machine and saw that the SQL Server folders had been
> installed but the services had not been created. I tried to uninstall SQL
> Server from the Add/Remove programs but SQL Server was not in the list. I
> then inserted the SQL Server CD and tried to uninstall. There was no
option
> to uninstall. There was however, an option to install a new instance of
SQL
> Server.
> Thus I appear to be in the worst situation: 1) I cannot uninstall because
> neither CP or the SQL Server CD recognizes the failed installation and 2)
I[vbcol=seagreen]
> cannot reinstall because the SQL Server CD thinks the default installation
> already exists. (I cannot installed a named instance of SQL Server for use
> with MS CRM)
> BTW, I installed the standard edition of SQL Server with Mixed Mode
> authentication to run under a specific domain administrator account.
> Does anyone have any idea how I can clean up this failed installation?
>
>
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:uqVBYbcREHA.628@.TK2MSFTNGP11.phx.gbl...
> install
message
>

Installing SQL Server on Windows 2003 Server

When I try to install SQL Server 2000 on Windows 2003, I get the message
that SQL Server 2000 SP2 and below are not supported.
How do I install SQL Server 2000 on Windows 2003?You just install it (the dialog is a warning, not a halt), and then install
SP3a immediately afterward.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"David F" <davef@.nksj.ru> wrote in message
news:eyvESFcREHA.3452@.TK2MSFTNGP10.phx.gbl...
> When I try to install SQL Server 2000 on Windows 2003, I get the message
> that SQL Server 2000 SP2 and below are not supported.
> How do I install SQL Server 2000 on Windows 2003?
>|||That's what I thought but when I tried doing so the installation proceeded
and then displayed an error that the Full Text service failed to install.
This was the only error I received.
I rebooted the machine and saw that the SQL Server folders had been
installed but the services had not been created. I tried to uninstall SQL
Server from the Add/Remove programs but SQL Server was not in the list. I
then inserted the SQL Server CD and tried to uninstall. There was no option
to uninstall. There was however, an option to install a new instance of SQL
Server.
Thus I appear to be in the worst situation: 1) I cannot uninstall because
neither CP or the SQL Server CD recognizes the failed installation and 2) I
cannot reinstall because the SQL Server CD thinks the default installation
already exists. (I cannot installed a named instance of SQL Server for use
with MS CRM)
BTW, I installed the standard edition of SQL Server with Mixed Mode
authentication to run under a specific domain administrator account.
Does anyone have any idea how I can clean up this failed installation?
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:uqVBYbcREHA.628@.TK2MSFTNGP11.phx.gbl...
> You just install it (the dialog is a warning, not a halt), and then
install
> SP3a immediately afterward.
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
> "David F" <davef@.nksj.ru> wrote in message
> news:eyvESFcREHA.3452@.TK2MSFTNGP10.phx.gbl...
> > When I try to install SQL Server 2000 on Windows 2003, I get the message
> > that SQL Server 2000 SP2 and below are not supported.
> >
> > How do I install SQL Server 2000 on Windows 2003?
> >
> >
>|||David,
>>displayed an error that the Full Text service failed to install.
Did you check sqlstp.log for the any hints/messages for this error?
>> Does anyone have any idea how I can clean up this failed installation?
'HOW TO: Manually Remove SQL Srv. 2000 Default, Named or Virtual'
http://support.microsoft.com/?id=290991
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"David F" <davef@.nksj.ru> wrote in message
news:uyzijvcREHA.3300@.tk2msftngp13.phx.gbl...
> That's what I thought but when I tried doing so the installation proceeded
> and then displayed an error that the Full Text service failed to install.
> This was the only error I received.
> I rebooted the machine and saw that the SQL Server folders had been
> installed but the services had not been created. I tried to uninstall SQL
> Server from the Add/Remove programs but SQL Server was not in the list. I
> then inserted the SQL Server CD and tried to uninstall. There was no
option
> to uninstall. There was however, an option to install a new instance of
SQL
> Server.
> Thus I appear to be in the worst situation: 1) I cannot uninstall because
> neither CP or the SQL Server CD recognizes the failed installation and 2)
I
> cannot reinstall because the SQL Server CD thinks the default installation
> already exists. (I cannot installed a named instance of SQL Server for use
> with MS CRM)
> BTW, I installed the standard edition of SQL Server with Mixed Mode
> authentication to run under a specific domain administrator account.
> Does anyone have any idea how I can clean up this failed installation?
>
>
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:uqVBYbcREHA.628@.TK2MSFTNGP11.phx.gbl...
> > You just install it (the dialog is a warning, not a halt), and then
> install
> > SP3a immediately afterward.
> >
> > --
> > Aaron Bertrand
> > SQL Server MVP
> > http://www.aspfaq.com/
> >
> >
> > "David F" <davef@.nksj.ru> wrote in message
> > news:eyvESFcREHA.3452@.TK2MSFTNGP10.phx.gbl...
> > > When I try to install SQL Server 2000 on Windows 2003, I get the
message
> > > that SQL Server 2000 SP2 and below are not supported.
> > >
> > > How do I install SQL Server 2000 on Windows 2003?
> > >
> > >
> >
> >
>