Install security patch ms03-031 on sql2k sp3 server

Tried to install security patch ms03-031 on sql2k sp3
server, but got message said that there is no valid
instance for the patch. Anyone else had this problem?I would first run Select @.@.version from Query Analyzer to verify that the
version is 2000.8.00.760 (SP3)
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thanks for the response, Rand.
Yes, I did that and even tried to reapply sp3 but still
can't install that patch with same message. Any other
reasons?
>--Original Message--
>I would first run Select @.@.version from Query Analyzer to
verify that the
>version is 2000.8.00.760 (SP3)
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||Check the registry for the version number.
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion\CSDVersion.
Make sure it also say 8.00.760
Rand.
This posting is provided "as is" with no warranties and confers no rights.|||Thanks for the response, Rand. That was first thing I do
and it returned correct result. I even tried reapply sp3
but still got message said that can't find instance for
the patch. Any other reasons?
>--Original Message--
>I would first run Select @.@.version from Query Analyzer to
verify that the
>version is 2000.8.00.760 (SP3)
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>|||It says 8.00.534, I changed it to 8.00.760 but still
doesn't let me apply the patch.
>--Original Message--
>Check the registry for the version number.
>HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVer
sion\CSDVersion.
>Make sure it also say 8.00.760
>Rand.
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>

Install Second Instance Of SQL Server 2005

I'm trying to install a second instance of SQL Server 2005 to an existing
server where Service Pack 2 is installed. Nothing special - no clustering, I
just want an additional instance for QA purposes.
The problem that I'm experiencing is that I receive an error message during
the installation:
Error 1603 installing Microsoft SQL Server 2005 Setup Support Files
The log file doesn't provide any description of an error. My only guess at
this point is that my current instance has higher versions of files than the
ones on the original install disk.
Any suggestions on how to proceed? Should I wipe-out the server and start
over?
I would appreciate any assistance. THANKS!!!
Regards,
RayHi Ray,
You could try running sqlrun.msi (in the setup directory) directly,
instead of the setup.exe. That would forego the installation of the
Setup Support Files. Not sure if that works, though.
--
Regards,
Steve
www.foxville.ch
On Sep 13, 7:08 pm, raz0r9edge <raz0r9e...@.discussions.microsoft.com>
wrote:
> I'm trying to install a second instance of SQL Server 2005 to an existing
> server where Service Pack 2 is installed. Nothing special - no clustering, I
> just want an additional instance for QA purposes.
> The problem that I'm experiencing is that I receive an error message during
> the installation:
> Error 1603 installing Microsoft SQL Server 2005 Setup Support Files
> The log file doesn't provide any description of an error. My only guess at
> this point is that my current instance has higher versions of files than the
> ones on the original install disk.
> Any suggestions on how to proceed? Should I wipe-out the server and start
> over?
> I would appreciate any assistance. THANKS!!!
> Regards,
> Ray

Install RS - Separate DB from Web

I am trying to install reporting services on a web server, which will connect
to an existing instance of the RS Sql Server backend on another machine.
This backend server already has SP2 installed - so when I install RS on the
web server machine and try to point to the existing backend during
installation, it tells me that it is not compatible.
What would be the correct steps to take in order to install on a web server
and connect to an existing RS backend DB? Any relevant articles will help...
Enjoy!
mikeFirst, are you implementing a web farm?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Michael R" <MichaelR@.discussions.microsoft.com> wrote in message
news:9F638932-02F0-48DF-8EF9-A54EF42AF0FA@.microsoft.com...
>I am trying to install reporting services on a web server, which will
>connect
> to an existing instance of the RS Sql Server backend on another machine.
> This backend server already has SP2 installed - so when I install RS on
> the
> web server machine and try to point to the existing backend during
> installation, it tells me that it is not compatible.
> What would be the correct steps to take in order to install on a web
> server
> and connect to an existing RS backend DB? Any relevant articles will
> help...
> Enjoy!
> mike|||Not in the sense that I will have multiple ReportServer databases. I will
have a one to one relationship: 1 web server and 1 server with the
ReportServer database.
It was recommended that I do this by the server admins, in order to take the
load off of IIS.
"Bruce L-C [MVP]" wrote:
> First, are you implementing a web farm?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Michael R" <MichaelR@.discussions.microsoft.com> wrote in message
> news:9F638932-02F0-48DF-8EF9-A54EF42AF0FA@.microsoft.com...
> >I am trying to install reporting services on a web server, which will
> >connect
> > to an existing instance of the RS Sql Server backend on another machine.
> > This backend server already has SP2 installed - so when I install RS on
> > the
> > web server machine and try to point to the existing backend during
> > installation, it tells me that it is not compatible.
> >
> > What would be the correct steps to take in order to install on a web
> > server
> > and connect to an existing RS backend DB? Any relevant articles will
> > help...
> >
> > Enjoy!
> >
> > mike
>
>|||I would try this:
1) install SQL RS on the web server, and during the install, create new
SQL RS database(s) for it to point to / use (doesn't matter where you
put the DB, you'll end up dropping them soon). At the end of the
install, you'll have a new SQL RS web app, pointing to a new SQL RS db.
2) Apply SP1 to the SQL RS instance (web & new database).
3) Apply SP2 to the SQL RS instance (web & new database).
4) Now that you're web app is up to SP2, you can point it to your
original database using the 'rsconfig' command line utility (see SQL RS
Books Online for details of usage & syntax). After using 'rsconfig' to
point your app to the original database, you'll need to run the
'rskeymgmt' command line utility to initialize / activate your Report
Server for use with the original database (allows it to read the
original database) -- see Books Online for details of syntax and usage.
5) Drop the new SQL RS databases that were created in Step #1, since
you're not going to use them, now that your web app is pointing to the
'original' SP2 database.

install reporting services 2005

Do you or do you not need (have to have) an instance of sql server 2005
installed somewhere (the same machine, on the network, anywhere) in order to
install reporting services 2005?Yes, you DO need to have a SQL Server database engine available
somewhere, however it does not need to be 2005 (although, MS does not
recommend using 2000 db w/ RS 2005, because of limiting new feature
set).
The ReportServer piece uses (2) SQL Server databases, named
ReportServerDB and ReportServerTempDB, to store catalog information
(e.g., folders, report RDL, security info, settings, etc.).
Reporting Services, itself, is composed of 3 pieces: a windows
service, a web service application and a asp.net web application. All
of those must connect to a database somewhere so it can get the reports
you have stored, etc.
If you choose to use a remote database engine, you will need 2 licenses
of SQL Server:
- one for where you install the ReportingServices instance, and
- one for where the database engine is installed
You can also scale-out the Report Server to a web farm, so you would
have n number of IIS Web servers, each running their own license of SQL
Server, with only the Reporting Services installed, and configured in a
scale-out (web farm/files only) setup. You would then need a DB server
running its own license of SQL Server with the database engine.
I hope that answers your question and clears up any doubts.
Regards,
Thiago Silva|||One clarification. There is absolutely NO problem using a 2000 DB as the
metadata/cache for RS 2005. All features are available. This is both
supported and expected configuration. I am running that way. This is
separate from licensing. If you have everything on one box and you leave the
DB as 2000 and install/upgrade to RS 2005 then you need a SQL Server 2005
license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"tafs7" <tsilva7@.gmail.com> wrote in message
news:1145312024.732011.199790@.z34g2000cwc.googlegroups.com...
> Yes, you DO need to have a SQL Server database engine available
> somewhere, however it does not need to be 2005 (although, MS does not
> recommend using 2000 db w/ RS 2005, because of limiting new feature
> set).
> The ReportServer piece uses (2) SQL Server databases, named
> ReportServerDB and ReportServerTempDB, to store catalog information
> (e.g., folders, report RDL, security info, settings, etc.).
> Reporting Services, itself, is composed of 3 pieces: a windows
> service, a web service application and a asp.net web application. All
> of those must connect to a database somewhere so it can get the reports
> you have stored, etc.
> If you choose to use a remote database engine, you will need 2 licenses
> of SQL Server:
> - one for where you install the ReportingServices instance, and
> - one for where the database engine is installed
> You can also scale-out the Report Server to a web farm, so you would
> have n number of IIS Web servers, each running their own license of SQL
> Server, with only the Reporting Services installed, and configured in a
> scale-out (web farm/files only) setup. You would then need a DB server
> running its own license of SQL Server with the database engine.
> I hope that answers your question and clears up any doubts.
> Regards,
> Thiago Silva
>|||Bruce is absolutely correct. I hope I didn't confuse you.
I am running, in production at a client, a scale out deployment of 2 RS
2005 servers, which uses a separate SQL 2000 db for storing the
catalog.
There are no known issues, and this is definetely supported. However,
what I meant is that you will find more MS documentation using all 2005
servers, because they would prefer you to license it that way, in order
to get the new features and benefits of the SQL 2005 database engine.
Regards,
Thiago Silva

Install New Instance/ Store Data & Log Files in existing drive

Hello,
I need to install a new instance of SQL Server 2000 on a cluster.
Currently, we have three instances. Each instances stores program files on
the E:\ Drive. Each instance has its own drive for data and another for
logs. However, there is no more unallocated space on the array to create
another partitioned drive.
My question is: If I create the new instance, can I store the data and log
files on an existing drive? Are there any performance or overhead costs that
should be considered?
Thank you,
Caroline
Each instance must have separate disk resources from any other instances.
You will need new disks to create another instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Caroline" <Caroline@.community.nospam> wrote in message
news:4E870F35-33B9-4E92-91E6-1993FD8FE4C4@.microsoft.com...
> Hello,
> I need to install a new instance of SQL Server 2000 on a cluster.
> Currently, we have three instances. Each instances stores program files
> on
> the E:\ Drive. Each instance has its own drive for data and another for
> logs. However, there is no more unallocated space on the array to create
> another partitioned drive.
> My question is: If I create the new instance, can I store the data and
> log
> files on an existing drive? Are there any performance or overhead costs
> that
> should be considered?
> Thank you,
> Caroline
sql

Install new instance

Hi,
I just wanted to install a new instance of SQL Server. I came to the point
where I had to decide, where to install the program and datafiles. Am I
right in assuming, that these have to be different from my default
instance?
TIA
ThomasThomas
BOL says:
"
Each named instance of Microsoft SQL Server 2000 has a specific location
for its program files and another for its data files that is different from
that of the default instance of SQL Server.
"
"Thomas Wrobel" <twrobel@.waslos.de> wrote in message
news:Xns94B5963B2301Btwrobelwaslosde@.207
.46.248.16...
> Hi,
> I just wanted to install a new instance of SQL Server. I came to the point
> where I had to decide, where to install the program and datafiles. Am I
> right in assuming, that these have to be different from my default
> instance?
> TIA
> Thomas

Install multiple instance of database to one computer question

Dear all,
If i want to install multiple instance of database to one computer(XP) for a
developer edition. Do i need to buy two license of developer edition for two
instance to install to one computer? Moreover if i install two instance to
one computer, can the two instance of database can start together in
enterprise manager/ or just one instance can operate in one time? It is
because install two instance of database, one for on-going development and
one for use to backup the data from the production server(since it need to
test the backup data can restore)
I don't know about the license but you can run 2 instances ( 1 has to be
named) at the same time just register them both in enterprise Manager
http://sqlservercode.blogspot.com/
"Joe" wrote:

> Dear all,
> If i want to install multiple instance of database to one computer(XP) for a
> developer edition. Do i need to buy two license of developer edition for two
> instance to install to one computer? Moreover if i install two instance to
> one computer, can the two instance of database can start together in
> enterprise manager/ or just one instance can operate in one time? It is
> because install two instance of database, one for on-going development and
> one for use to backup the data from the production server(since it need to
> test the backup data can restore)
|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:4B562ABF-916B-4EDD-A145-E79D773C7B91@.microsoft.com...
> Dear all,
> If i want to install multiple instance of database to one computer(XP) for
> a
> developer edition. Do i need to buy two license of developer edition for
> two
> instance to install to one computer? Moreover if i install two instance to
> one computer, can the two instance of database can start together in
> enterprise manager/ or just one instance can operate in one time? It is
> because install two instance of database, one for on-going development and
> one for use to backup the data from the production server(since it need to
> test the backup data can restore)
My understanding is that you can install as many instances as you want on
the same machine. The licensing comes in to play either per processor or
per seat. With the developer edition, I don't think you need to purchase
CALs as you are not supposed to be using Dev edition for production. I
would double check that however.
There is no problem installing multiple instances on the same server and
both will be able to run concurrently. It will eat up more of your
resources however as each instance of SQL Server will have it's own services
executing and memory needs.
HTH
Rick Sawtell
MCT, MCSD, MCDBA
|||Yeah and the developer edition is only like $50 a copy.
See:
http://www.microsoft.com/sql/howtobuy/faq.mspx
and
http://www.microsoft.com/sql/howtobuy/default.mspx
and
http://www.microsoft.com/sql/howtobuy/development.mspx
HTH
Jerry
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:%23Dr8ldPxFHA.596@.TK2MSFTNGP12.phx.gbl...
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:4B562ABF-916B-4EDD-A145-E79D773C7B91@.microsoft.com...
> My understanding is that you can install as many instances as you want on
> the same machine. The licensing comes in to play either per processor or
> per seat. With the developer edition, I don't think you need to purchase
> CALs as you are not supposed to be using Dev edition for production. I
> would double check that however.
> There is no problem installing multiple instances on the same server and
> both will be able to run concurrently. It will eat up more of your
> resources however as each instance of SQL Server will have it's own
> services executing and memory needs.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

Install multiple instance of database to one computer question

Dear all,
If i want to install multiple instance of database to one computer(XP) for a
developer edition. Do i need to buy two license of developer edition for two
instance to install to one computer? Moreover if i install two instance to
one computer, can the two instance of database can start together in
enterprise manager/ or just one instance can operate in one time? It is
because install two instance of database, one for on-going development and
one for use to backup the data from the production server(since it need to
test the backup data can restore)I don't know about the license but you can run 2 instances ( 1 has to be
named) at the same time just register them both in enterprise Manager
http://sqlservercode.blogspot.com/
"Joe" wrote:

> Dear all,
> If i want to install multiple instance of database to one computer(XP) for
a
> developer edition. Do i need to buy two license of developer edition for t
wo
> instance to install to one computer? Moreover if i install two instance to
> one computer, can the two instance of database can start together in
> enterprise manager/ or just one instance can operate in one time? It is
> because install two instance of database, one for on-going development and
> one for use to backup the data from the production server(since it need to
> test the backup data can restore)|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:4B562ABF-916B-4EDD-A145-E79D773C7B91@.microsoft.com...
> Dear all,
> If i want to install multiple instance of database to one computer(XP) for
> a
> developer edition. Do i need to buy two license of developer edition for
> two
> instance to install to one computer? Moreover if i install two instance to
> one computer, can the two instance of database can start together in
> enterprise manager/ or just one instance can operate in one time? It is
> because install two instance of database, one for on-going development and
> one for use to backup the data from the production server(since it need to
> test the backup data can restore)
My understanding is that you can install as many instances as you want on
the same machine. The licensing comes in to play either per processor or
per seat. With the developer edition, I don't think you need to purchase
CALs as you are not supposed to be using Dev edition for production. I
would double check that however.
There is no problem installing multiple instances on the same server and
both will be able to run concurrently. It will eat up more of your
resources however as each instance of SQL Server will have it's own services
executing and memory needs.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Yeah and the developer edition is only like $50 a copy.
See:
http://www.microsoft.com/sql/howtobuy/faq.mspx
and
http://www.microsoft.com/sql/howtobuy/default.mspx
and
http://www.microsoft.com/sql/howtobuy/development.mspx
HTH
Jerry
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:%23Dr8ldPxFHA.596@.TK2MSFTNGP12.phx.gbl...
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:4B562ABF-916B-4EDD-A145-E79D773C7B91@.microsoft.com...
> My understanding is that you can install as many instances as you want on
> the same machine. The licensing comes in to play either per processor or
> per seat. With the developer edition, I don't think you need to purchase
> CALs as you are not supposed to be using Dev edition for production. I
> would double check that however.
> There is no problem installing multiple instances on the same server and
> both will be able to run concurrently. It will eat up more of your
> resources however as each instance of SQL Server will have it's own
> services executing and memory needs.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

Install multiple instance of database to one computer question

Dear all,
If i want to install multiple instance of database to one computer(XP) for a
developer edition. Do i need to buy two license of developer edition for two
instance to install to one computer? Moreover if i install two instance to
one computer, can the two instance of database can start together in
enterprise manager/ or just one instance can operate in one time? It is
because install two instance of database, one for on-going development and
one for use to backup the data from the production server(since it need to
test the backup data can restore)I don't know about the license but you can run 2 instances ( 1 has to be
named) at the same time just register them both in enterprise Manager
http://sqlservercode.blogspot.com/
"Joe" wrote:
> Dear all,
> If i want to install multiple instance of database to one computer(XP) for a
> developer edition. Do i need to buy two license of developer edition for two
> instance to install to one computer? Moreover if i install two instance to
> one computer, can the two instance of database can start together in
> enterprise manager/ or just one instance can operate in one time? It is
> because install two instance of database, one for on-going development and
> one for use to backup the data from the production server(since it need to
> test the backup data can restore)|||"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:4B562ABF-916B-4EDD-A145-E79D773C7B91@.microsoft.com...
> Dear all,
> If i want to install multiple instance of database to one computer(XP) for
> a
> developer edition. Do i need to buy two license of developer edition for
> two
> instance to install to one computer? Moreover if i install two instance to
> one computer, can the two instance of database can start together in
> enterprise manager/ or just one instance can operate in one time? It is
> because install two instance of database, one for on-going development and
> one for use to backup the data from the production server(since it need to
> test the backup data can restore)
My understanding is that you can install as many instances as you want on
the same machine. The licensing comes in to play either per processor or
per seat. With the developer edition, I don't think you need to purchase
CALs as you are not supposed to be using Dev edition for production. I
would double check that however.
There is no problem installing multiple instances on the same server and
both will be able to run concurrently. It will eat up more of your
resources however as each instance of SQL Server will have it's own services
executing and memory needs.
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Yeah and the developer edition is only like $50 a copy.
See:
http://www.microsoft.com/sql/howtobuy/faq.mspx
and
http://www.microsoft.com/sql/howtobuy/default.mspx
and
http://www.microsoft.com/sql/howtobuy/development.mspx
HTH
Jerry
"Rick Sawtell" <r_sawtell@.hotmail.com> wrote in message
news:%23Dr8ldPxFHA.596@.TK2MSFTNGP12.phx.gbl...
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:4B562ABF-916B-4EDD-A145-E79D773C7B91@.microsoft.com...
>> Dear all,
>> If i want to install multiple instance of database to one computer(XP)
>> for a
>> developer edition. Do i need to buy two license of developer edition for
>> two
>> instance to install to one computer? Moreover if i install two instance
>> to
>> one computer, can the two instance of database can start together in
>> enterprise manager/ or just one instance can operate in one time? It is
>> because install two instance of database, one for on-going development
>> and
>> one for use to backup the data from the production server(since it need
>> to
>> test the backup data can restore)
> My understanding is that you can install as many instances as you want on
> the same machine. The licensing comes in to play either per processor or
> per seat. With the developer edition, I don't think you need to purchase
> CALs as you are not supposed to be using Dev edition for production. I
> would double check that however.
> There is no problem installing multiple instances on the same server and
> both will be able to run concurrently. It will eat up more of your
> resources however as each instance of SQL Server will have it's own
> services executing and memory needs.
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>

Install msde with instancename on a W2003 cluster

How can i install the SQL MSDE (sp3a) with a instance name
on a windows 2003 cluster server.
A custumer has a windows 2003 cluster server. When i run
our setup, with parameters like intsance=myprogram, the
software installs normaly on the server. Our client
software louks voor
%Server%\%InstanceName% across the network.
The software don't see the instance name.
Thanks.
Sounds like it is installing correctly. There is nothing special about
installing MSDE on a node of a cluster. Can you use OSQL on the server you
installed MSDE on to connect to the SQL Server? Have you used svrnetcn.exe
to enable the protocols for MSDE? Have you applied SP3 to the MSDE
installation? TCP/IP is not available on Windows 2003 until SP3 is
installed on any version of SQL Server 2000.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Yes, the software installs correctly. (I don't see event
in the logs)
We used msde 2000 with sp3.
Yes i have used the svrnetcn.exe to configure the tcp/ip
protocol, set port to 1433.
I haven't used Osql to test the connection.
I test with the sql enterprice manager, to connect the
msde on the 2003 server. This don't work.
When i install the same msde software on a nomal Windows
2003 server everything works fine.
What else can i do?
What can there be wrong?
Thanks for your reply.
sql

install integration service on existing instance

I need to install Integration Service on an existing SQL 2005 instance. Is
it possible add components to an existing instance or do I need to create a
new instance of SQL server?
When you install SSIS on a Server, the service is "stand alone", not bound to
a specific instance. You can install SSIS alone, running the setup and asking
for the installation of the Integration services without install the other
components
Gilberto Zampatti
"Mike" wrote:

> I need to install Integration Service on an existing SQL 2005 instance. Is
> it possible add components to an existing instance or do I need to create a
> new instance of SQL server?
>
>

install integration service on existing instance

I need to install Integration Service on an existing SQL 2005 instance. Is
it possible add components to an existing instance or do I need to create a
new instance of SQL server?When you install SSIS on a Server, the service is "stand alone", not bound t
o
a specific instance. You can install SSIS alone, running the setup and askin
g
for the installation of the Integration services without install the other
components
Gilberto Zampatti
"Mike" wrote:

> I need to install Integration Service on an existing SQL 2005 instance. Is
> it possible add components to an existing instance or do I need to create
a
> new instance of SQL server?
>
>

install integration service on existing instance

I need to install Integration Service on an existing SQL 2005 instance. Is
it possible add components to an existing instance or do I need to create a
new instance of SQL server?When you install SSIS on a Server, the service is "stand alone", not bound to
a specific instance. You can install SSIS alone, running the setup and asking
for the installation of the Integration services without install the other
components
Gilberto Zampatti
"Mike" wrote:
> I need to install Integration Service on an existing SQL 2005 instance. Is
> it possible add components to an existing instance or do I need to create a
> new instance of SQL server?
>
>sql

Install help

I have recently inherited a Windows 2003 server box that has both
SQLExpress installed along with a Named 2005 instance. The problem I'm
having is that on the named instance they didn't(or it failed) install
Integrated Services. I went into add/remove programs and tried to change the
install options(add SSIS). I choose the named Instance but it never allows
me choose Integrated Services to install.
How can I get SSIS installed?
I looked at the folder structure and the named instance doesn't have
reference to SSIS being there.
Thanks.
SSIS isn't instance aware. Or rather, you cannot have several instances in SSIS, and basically SSIS
isn't tied to a specific instance. I haven't done this myself, but I'd just run setup from the
install DVD and add SSIS from there.
There's is one connection for SSIS to an instance, and this is in which MSDB to store the packages,
and you configure this in below XML file (after installation):
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AHartman" <Hoosbruin@.Kconline.com> wrote in message news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.gbl...
> I have recently inherited a Windows 2003 server box that has both SQLExpress installed along with
> a Named 2005 instance. The problem I'm having is that on the named instance they didn't(or it
> failed) install Integrated Services. I went into add/remove programs and tried to change the
> install options(add SSIS). I choose the named Instance but it never allows me choose Integrated
> Services to install.
> How can I get SSIS installed?
> I looked at the folder structure and the named instance doesn't have reference to SSIS being
> there.
>
> Thanks.
|||This file exists "C:\Program Files\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvr.ini.xml" but I still don't have any service to
start?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3WL1hl2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> SSIS isn't instance aware. Or rather, you cannot have several instances in
> SSIS, and basically SSIS isn't tied to a specific instance. I haven't done
> this myself, but I'd just run setup from the install DVD and add SSIS from
> there.
> There's is one connection for SSIS to an instance, and this is in which
> MSDB to store the packages, and you configure this in below XML file
> (after installation):
> C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "AHartman" <Hoosbruin@.Kconline.com> wrote in message
> news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>
|||You need to modify that file so that it will point to your
named instance. Modify the section for the server:
<ServerName>.</ServerName>
to point to your named instance:
<ServerName>ServerName\InstanceName</ServerName>
There is a topic in books online that explains this. Look up
the topic:
Configuring the Integration Services Service
and check the section regarding configuring a named
instance.
-Sue
On Thu, 9 Aug 2007 05:44:05 -0400, "AHartman"
<Hoosbruin@.Kconline.com> wrote:
[vbcol=seagreen]
>This file exists "C:\Program Files\Microsoft SQL
>Server\90\DTS\Binn\MsDtsSrvr.ini.xml" but I still don't have any service to
>start?
>
>
>
>"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
>message news:e3WL1hl2HHA.3940@.TK2MSFTNGP05.phx.gbl...

Install help

I have recently inherited a Windows 2003 server box that has both
SQLExpress installed along with a Named 2005 instance. The problem I'm
having is that on the named instance they didn't(or it failed) install
Integrated Services. I went into add/remove programs and tried to change the
install options(add SSIS). I choose the named Instance but it never allows
me choose Integrated Services to install.
How can I get SSIS installed?
I looked at the folder structure and the named instance doesn't have
reference to SSIS being there.
Thanks.SSIS isn't instance aware. Or rather, you cannot have several instances in S
SIS, and basically SSIS
isn't tied to a specific instance. I haven't done this myself, but I'd just
run setup from the
install DVD and add SSIS from there.
There's is one connection for SSIS to an instance, and this is in which MSDB
to store the packages,
and you configure this in below XML file (after installation):
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AHartman" <Hoosbruin@.Kconline.com> wrote in message news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.
gbl...
> I have recently inherited a Windows 2003 server box that has both SQLExpre
ss installed along with
> a Named 2005 instance. The problem I'm having is that on the named instanc
e they didn't(or it
> failed) install Integrated Services. I went into add/remove programs and t
ried to change the
> install options(add SSIS). I choose the named Instance but it never allows
me choose Integrated
> Services to install.
> How can I get SSIS installed?
> I looked at the folder structure and the named instance doesn't have refe
rence to SSIS being
> there.
>
> Thanks.|||This file exists "C:\Program Files\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvr.ini.xml" but I still don't have any service to
start?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3WL1hl2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> SSIS isn't instance aware. Or rather, you cannot have several instances in
> SSIS, and basically SSIS isn't tied to a specific instance. I haven't done
> this myself, but I'd just run setup from the install DVD and add SSIS from
> there.
> There's is one connection for SSIS to an instance, and this is in which
> MSDB to store the packages, and you configure this in below XML file
> (after installation):
> C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "AHartman" <Hoosbruin@.Kconline.com> wrote in message
> news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>|||You need to modify that file so that it will point to your
named instance. Modify the section for the server:
<ServerName>.</ServerName>
to point to your named instance:
<ServerName>ServerName\InstanceName</ServerName>
There is a topic in books online that explains this. Look up
the topic:
Configuring the Integration Services Service
and check the section regarding configuring a named
instance.
-Sue
On Thu, 9 Aug 2007 05:44:05 -0400, "AHartman"
<Hoosbruin@.Kconline.com> wrote:
[vbcol=seagreen]
>This file exists "C:\Program Files\Microsoft SQL
>Server\90\DTS\Binn\MsDtsSrvr.ini.xml" but I still don't have any service to
>start?
>
>
>
>"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
>message news:e3WL1hl2HHA.3940@.TK2MSFTNGP05.phx.gbl...sql

Install help

I have recently inherited a Windows 2003 server box that has both
SQLExpress installed along with a Named 2005 instance. The problem I'm
having is that on the named instance they didn't(or it failed) install
Integrated Services. I went into add/remove programs and tried to change the
install options(add SSIS). I choose the named Instance but it never allows
me choose Integrated Services to install.
How can I get SSIS installed?
I looked at the folder structure and the named instance doesn't have
reference to SSIS being there.
Thanks.SSIS isn't instance aware. Or rather, you cannot have several instances in SSIS, and basically SSIS
isn't tied to a specific instance. I haven't done this myself, but I'd just run setup from the
install DVD and add SSIS from there.
There's is one connection for SSIS to an instance, and this is in which MSDB to store the packages,
and you configure this in below XML file (after installation):
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"AHartman" <Hoosbruin@.Kconline.com> wrote in message news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.gbl...
> I have recently inherited a Windows 2003 server box that has both SQLExpress installed along with
> a Named 2005 instance. The problem I'm having is that on the named instance they didn't(or it
> failed) install Integrated Services. I went into add/remove programs and tried to change the
> install options(add SSIS). I choose the named Instance but it never allows me choose Integrated
> Services to install.
> How can I get SSIS installed?
> I looked at the folder structure and the named instance doesn't have reference to SSIS being
> there.
>
> Thanks.|||This file exists "C:\Program Files\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvr.ini.xml" but I still don't have any service to
start?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e3WL1hl2HHA.3940@.TK2MSFTNGP05.phx.gbl...
> SSIS isn't instance aware. Or rather, you cannot have several instances in
> SSIS, and basically SSIS isn't tied to a specific instance. I haven't done
> this myself, but I'd just run setup from the install DVD and add SSIS from
> there.
> There's is one connection for SSIS to an instance, and this is in which
> MSDB to store the packages, and you configure this in below XML file
> (after installation):
> C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "AHartman" <Hoosbruin@.Kconline.com> wrote in message
> news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> I have recently inherited a Windows 2003 server box that has both
>> SQLExpress installed along with a Named 2005 instance. The problem I'm
>> having is that on the named instance they didn't(or it failed) install
>> Integrated Services. I went into add/remove programs and tried to change
>> the install options(add SSIS). I choose the named Instance but it never
>> allows me choose Integrated Services to install.
>> How can I get SSIS installed?
>> I looked at the folder structure and the named instance doesn't have
>> reference to SSIS being there.
>>
>> Thanks.
>|||You need to modify that file so that it will point to your
named instance. Modify the section for the server:
<ServerName>.</ServerName>
to point to your named instance:
<ServerName>ServerName\InstanceName</ServerName>
There is a topic in books online that explains this. Look up
the topic:
Configuring the Integration Services Service
and check the section regarding configuring a named
instance.
-Sue
On Thu, 9 Aug 2007 05:44:05 -0400, "AHartman"
<Hoosbruin@.Kconline.com> wrote:
>This file exists "C:\Program Files\Microsoft SQL
>Server\90\DTS\Binn\MsDtsSrvr.ini.xml" but I still don't have any service to
>start?
>
>
>
>"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
>message news:e3WL1hl2HHA.3940@.TK2MSFTNGP05.phx.gbl...
>> SSIS isn't instance aware. Or rather, you cannot have several instances in
>> SSIS, and basically SSIS isn't tied to a specific instance. I haven't done
>> this myself, but I'd just run setup from the install DVD and add SSIS from
>> there.
>> There's is one connection for SSIS to an instance, and this is in which
>> MSDB to store the packages, and you configure this in below XML file
>> (after installation):
>> C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "AHartman" <Hoosbruin@.Kconline.com> wrote in message
>> news:unCHtdj2HHA.3764@.TK2MSFTNGP04.phx.gbl...
>> I have recently inherited a Windows 2003 server box that has both
>> SQLExpress installed along with a Named 2005 instance. The problem I'm
>> having is that on the named instance they didn't(or it failed) install
>> Integrated Services. I went into add/remove programs and tried to change
>> the install options(add SSIS). I choose the named Instance but it never
>> allows me choose Integrated Services to install.
>> How can I get SSIS installed?
>> I looked at the folder structure and the named instance doesn't have
>> reference to SSIS being there.
>>
>> Thanks.

Install Full-Text on Existing SQL Server 2005 Cluster

I need to install the full-text engine on an existing SQL Server 2005
cluster virtual instance but can't seem to figure out how. Any ideas?
Start | Programs | Add/Remove Programs
Click the modify link underneath SQL Server.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adam Weigert" <adam.weigert@.wegmans.com> wrote in message
news:uKpmBzkPGHA.2624@.TK2MSFTNGP12.phx.gbl...
>I need to install the full-text engine on an existing SQL Server 2005
>cluster virtual instance but can't seem to figure out how. Any ideas?
>
|||Unfortunately, the only change operation I can do from Add/Remove programs
for the cluster instance is either add or remove a node from the cluster.
There are no options to change what is installed.
I've looked at some of the command line maintenance features, but haven't
been able to figure out the correct command to issue.
Any other ideas or info?
|||In case anyone else runs into this, I did open a support case with Microsoft
and they concluded that this option was "left out" of the cluster change
options. They are going to place a feature enhancement request with the
product team. I'll update the thread if any new information arises in the
near future.
|||Thanks for the info.
*mike hodgson*
http://sqlnerd.blogspot.com
Adam Weigert wrote:

>In case anyone else runs into this, I did open a support case with Microsoft
>and they concluded that this option was "left out" of the cluster change
>options. They are going to place a feature enhancement request with the
>product team. I'll update the thread if any new information arises in the
>near future.
>
>

Install failure: "Error 29550. Cannot connect to the SQL server instance

I'm trying to install the Dev version of Reporting Services (RS) on one
box and have it use an Sql Server 2000 (w/SP3) instance on another box.
Both the RS and SqlServer boxes are Windows 2000 Servers. Neither are
part of a "windows domain"--neither will they ever be. We only connect
to SqlServer via a user/pwd pair. Additionally, there are 2 instances of
SqlServer running on the box and both of them listen on custom ports. (I
have confirmed that I can successfully connect to the desired SqlServer
instance from the RS box.)
The error I got was the "Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.". The installer
attempts a domain login when I explicitly told it *not* to. I found no
way to get the installer to successfully connect to the database. The
solutions I've found on the web/Usenet have not worked either.
Since I couldn't get it to install through the GUI, I switched to using
an .ini file. Of course, it's not working either. The (500KB!) log file
the installer produces has only one useful line in it: "Error 29550.
Cannot connect to the SQL server instance ." That meant that the problem
was the RSDATABASESERVER variable. The instructions tell me to specify
an "SQL Server 2000 instance in format MACHINE\INSTANCENAME". I played
around with that value a lot; I wondered how it could figure out what
port to connect to for one thing. While doing so, I tried sniffing the
network to see if that would help me at all--it just got me more
frustrated: no attempt is made to contact the server! Ever.
First off: WHY choose this uncommon, inadequate format for specifying a
server? Why not just use an alias from "cliconfg" like everything else?
Second: why doesn't the installer even *try* to login to the server? If
there's a reason it can't access the network, wouldn't you think that
500KB log file is a good place to mention it?
What do I do? (Hint: don't suggest making either box part of a windows
domain)
GrangerTo have setup use sql auth during setup you must pass in command line
parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
so run this command
setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
This will allow you to use the setup GUI still but all communication with
the backend server will use sql auth. Note that the setup user needs to be
a dbo. You can safely use the sa account as it is only used during setup.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Granger Godbold" <granger.godbold@.FILLER.prometric.com> wrote in message
news:e4VCZaIEFHA.3888@.TK2MSFTNGP10.phx.gbl...
> I'm trying to install the Dev version of Reporting Services (RS) on one
> box and have it use an Sql Server 2000 (w/SP3) instance on another box.
> Both the RS and SqlServer boxes are Windows 2000 Servers. Neither are part
> of a "windows domain"--neither will they ever be. We only connect to
> SqlServer via a user/pwd pair. Additionally, there are 2 instances of
> SqlServer running on the box and both of them listen on custom ports. (I
> have confirmed that I can successfully connect to the desired SqlServer
> instance from the RS box.)
> The error I got was the "Login failed for user '(null)'. Reason: Not
> associated with a trusted SQL Server connection.". The installer attempts
> a domain login when I explicitly told it *not* to. I found no way to get
> the installer to successfully connect to the database. The solutions I've
> found on the web/Usenet have not worked either.
> Since I couldn't get it to install through the GUI, I switched to using an
> .ini file. Of course, it's not working either. The (500KB!) log file the
> installer produces has only one useful line in it: "Error 29550. Cannot
> connect to the SQL server instance ." That meant that the problem was the
> RSDATABASESERVER variable. The instructions tell me to specify an "SQL
> Server 2000 instance in format MACHINE\INSTANCENAME". I played around with
> that value a lot; I wondered how it could figure out what port to connect
> to for one thing. While doing so, I tried sniffing the network to see if
> that would help me at all--it just got me more frustrated: no attempt is
> made to contact the server! Ever.
> First off: WHY choose this uncommon, inadequate format for specifying a
> server? Why not just use an alias from "cliconfg" like everything else?
> Second: why doesn't the installer even *try* to login to the server? If
> there's a reason it can't access the network, wouldn't you think that
> 500KB log file is a good place to mention it?
> What do I do? (Hint: don't suggest making either box part of a windows
> domain)
> Granger|||Thanks for trying, but no, that doesn't work; I was already doing that. I was
trying to use the "sa" account from the beginning because the instructions say
the "setup" account is only used during setup.
My problem is still that the installer doesn't even *try* to connect to the
database server. Once I can get around that, my problem will be that it will
want to use Windows Authentication because the connection information only
consists of "server\instance"; that's why it has to login: to figure out the
port the instance lives at.
If anyone knows the person responsible for the decision to use this connection
method, please smack them upside the head for me.
Other ideas?
Granger
Daniel Reib [MSFT] wrote:
> To have setup use sql auth during setup you must pass in command line
> parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
> so run this command
> setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
> This will allow you to use the setup GUI still but all communication with
> the backend server will use sql auth. Note that the setup user needs to be
> a dbo. You can safely use the sa account as it is only used during setup.
>|||Well first of all, if you want it to connect, what does your client
configuration say?
I take it that on the general tab you have TCP/IP listed at the top - click
the properties tab and is the port set correctly for your particular
instance?
I am running reporting services stand-alone - with SQL Server NOT IN A
DOMAIN - and it runs just fine.
You can also create an ALIAS name to the server instance in the SQL Server
Client Network utility.
Finally, just to be sure we are "connecting the dots" here - fire up the SQL
Server Network utility and verify that the TCP/IP properties are also
listening on the correct port. (I bet they are since you are using the
system successfully)
Last but not least, even if you are using SQL Server authentication, you
should be able to use windows authentication only when doing the setup -
since as you said you have full control over the dev box - then you have
local admin rights - therefore you should be able to logon unless you have
modifed the BUILTIN\Administrators security for that machine. (I assume that
this is not the case).
Please let me know if you are still having an issue, I'll be happy to help
you out.
Of course, this may come as a dumb question, but I assume nothing: Did you
install SP3a for SQL Server? (I assume yes), did you install the SQL Server
hotfix 859 ?
=-Chris
"Granger Godbold" <granger.godbold@.invalid.prometric.com> wrote in message
news:ucLN4gZEFHA.3256@.tk2msftngp13.phx.gbl...
> Thanks for trying, but no, that doesn't work; I was already doing that. I
> was trying to use the "sa" account from the beginning because the
> instructions say the "setup" account is only used during setup.
> My problem is still that the installer doesn't even *try* to connect to
> the database server. Once I can get around that, my problem will be that
> it will want to use Windows Authentication because the connection
> information only consists of "server\instance"; that's why it has to
> login: to figure out the port the instance lives at.
> If anyone knows the person responsible for the decision to use this
> connection method, please smack them upside the head for me.
> Other ideas?
> Granger
>
> Daniel Reib [MSFT] wrote:
>> To have setup use sql auth during setup you must pass in command line
>> parameters. The params are RSSETUPACCOUNT and RSSETUPPASSWORD
>> so run this command
>> setup.exe RSSETUPACCOUNT=foo RSSETUPPASSWORD=bar
>> This will allow you to use the setup GUI still but all communication with
>> the backend server will use sql auth. Note that the setup user needs to
>> be a dbo. You can safely use the sa account as it is only used during
>> setup.|||Thanks Chris.
The connectivity is all OK. It appears I'm just going to have to go
sync the administrators on each of the boxes during the install.
However, that won't be for a while; I just gave up and installed
everything on my own box for now. When I've had a chance to play with it
for a while, I'll do another install attempt in a more "proper" DEV
environment.
As far as the updates on the database go, my DBA says he's only done
security bulletin stuff. I looked it over and it seems the DEV box has
SP3 not SP3a (I checked the Ssnetlib.dll; we have 2000.80.760 not
2000.80.766
(http://support.microsoft.com/default.aspx?scid=kb;en-us;819334)). Also,
since Enterprise Manager reports 8.00.760, I gather he's not done any
hotfixes. This KnowledgeBase article
(http://support.microsoft.com/default.aspx?scid=kb;en-us;888007) implies
we should be at least at .977. I'll go tease him for being a slacker. ;)
I wouldn't guess the hotfixes would have anything to do with my
problem, however, since my local database only has SP3 installed on it
and ReportingServices installed fine.
Again, thanks Chris =)
Granger
Christopher Conner wrote:
<snip>
> Last but not least, even if you are using SQL Server authentication, you
> should be able to use windows authentication only when doing the setup -
> since as you said you have full control over the dev box - then you have
> local admin rights - therefore you should be able to logon unless you have
> modifed the BUILTIN\Administrators security for that machine. (I assume that
> this is not the case).
> Please let me know if you are still having an issue, I'll be happy to help
> you out.
> Of course, this may come as a dumb question, but I assume nothing: Did you
> install SP3a for SQL Server? (I assume yes), did you install the SQL Server
> hotfix 859 ?
> =-Chris
>sql

Install Error - SQL 2000 Std/ NT4SP6a

I get an error, saying a previous instance of setup did not complete, select
continue or cancel to end.
Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
for MSSQLSERVER, service entries etc., but setup keeps coming back with the
above message. Have not removed any files from \winnt or system32. Server
rest several times.
Is there some registry key in CurrentControlSet I need to delete'
Thought I knew SQL !!!
--
Thanks for any help!
Neil MillingtonCan you post the exact error message?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Belmann" <SQLServer@.belmann.co.uk> wrote in message
news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> I get an error, saying a previous instance of setup did not complete, select
> continue or cancel to end.
> Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> above message. Have not removed any files from \winnt or system32. Server
> rest several times.
> Is there some registry key in CurrentControlSet I need to delete'
> Thought I knew SQL !!!
> --
> Thanks for any help!
> Neil Millington|||Tibor... will post tonight as server is in ISP and I need to get behing
firewall!
Much appreciated.
"Tibor Karaszi" wrote:
> Can you post the exact error message?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> > I get an error, saying a previous instance of setup did not complete, select
> > continue or cancel to end.
> >
> > Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> > for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> > above message. Have not removed any files from \winnt or system32. Server
> > rest several times.
> >
> > Is there some registry key in CurrentControlSet I need to delete'
> >
> > Thought I knew SQL !!!
> > --
> > Thanks for any help!
> > Neil Millington
>
>|||I suspect the error is that you have another setup (doesn't have to be a SQL Server setup) which is
in "pending" state. If so, search KB for a suitable part of the error message and you will find the
KB which describes the registry modification you need to perform...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Belmann" <SQLServer@.belmann.co.uk> wrote in message
news:CDC4EFFD-BCDA-4C08-9DA5-E938DDA4DB72@.microsoft.com...
> Tibor... will post tonight as server is in ISP and I need to get behing
> firewall!
> Much appreciated.
> "Tibor Karaszi" wrote:
> > Can you post the exact error message?
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> > news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> > > I get an error, saying a previous instance of setup did not complete, select
> > > continue or cancel to end.
> > >
> > > Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> > > for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> > > above message. Have not removed any files from \winnt or system32. Server
> > > rest several times.
> > >
> > > Is there some registry key in CurrentControlSet I need to delete'
> > >
> > > Thought I knew SQL !!!
> > > --
> > > Thanks for any help!
> > > Neil Millington
> >
> >
> >|||This was not the error message I was thinking of, I'm afraid. I suggest you start searching Google,
the newsgroup archives and KB. If you don't find anything there, consider posting this to the .setup
group. And be prepared to include the sqlstp.log file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Belmann" <SQLServer@.belmann.co.uk> wrote in message
news:A8921334-D3E0-4AE1-9225-31E8FCAE562F@.microsoft.com...
> Tibor,
> Thanks for the reply, here is the message:
> <<
> setup has detected that the previous install attempt was not completed.
> Retry to continue installation or cancel to exit setup
> >>
> ...when selecting 'Retry' setup starts to file copy into \program
> files\microsoft sql server but fails when trying to run script 1 (as
> everything has been removed from drive/registry).
> Neil.
> "Tibor Karaszi" wrote:
> > Can you post the exact error message?
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> > news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> > > I get an error, saying a previous instance of setup did not complete, select
> > > continue or cancel to end.
> > >
> > > Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> > > for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> > > above message. Have not removed any files from \winnt or system32. Server
> > > rest several times.
> > >
> > > Is there some registry key in CurrentControlSet I need to delete'
> > >
> > > Thought I knew SQL !!!
> > > --
> > > Thanks for any help!
> > > Neil Millington
> >
> >
> >|||Thanks Tibor...will post tonight, as server is in remote ISP and I need to
get behing the firewall.
Much appreciated,
Neil.
"Tibor Karaszi" wrote:
> Can you post the exact error message?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> > I get an error, saying a previous instance of setup did not complete, select
> > continue or cancel to end.
> >
> > Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> > for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> > above message. Have not removed any files from \winnt or system32. Server
> > rest several times.
> >
> > Is there some registry key in CurrentControlSet I need to delete'
> >
> > Thought I knew SQL !!!
> > --
> > Thanks for any help!
> > Neil Millington
>
>|||Tibor,
Thanks for the reply, here is the message:
<<
setup has detected that the previous install attempt was not completed.
Retry to continue installation or cancel to exit setup
...when selecting 'Retry' setup starts to file copy into \program
files\microsoft sql server but fails when trying to run script 1 (as
everything has been removed from drive/registry).
Neil.
"Tibor Karaszi" wrote:
> Can you post the exact error message?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> > I get an error, saying a previous instance of setup did not complete, select
> > continue or cancel to end.
> >
> > Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> > for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> > above message. Have not removed any files from \winnt or system32. Server
> > rest several times.
> >
> > Is there some registry key in CurrentControlSet I need to delete'
> >
> > Thought I knew SQL !!!
> > --
> > Thanks for any help!
> > Neil Millington
>
>

Install Error - SQL 2000 Std/ NT4SP6a

I get an error, saying a previous instance of setup did not complete, select
continue or cancel to end.
Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
for MSSQLSERVER, service entries etc., but setup keeps coming back with the
above message. Have not removed any files from \winnt or system32. Server
rest several times.
Is there some registry key in CurrentControlSet I need to delete?
Thought I knew SQL !!!
Thanks for any help!
Neil Millington
Can you post the exact error message?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Belmann" <SQLServer@.belmann.co.uk> wrote in message
news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
> I get an error, saying a previous instance of setup did not complete, select
> continue or cancel to end.
> Have removed the SQL foldersfrom \Program Files\xxx and the registry keys
> for MSSQLSERVER, service entries etc., but setup keeps coming back with the
> above message. Have not removed any files from \winnt or system32. Server
> rest several times.
> Is there some registry key in CurrentControlSet I need to delete?
> Thought I knew SQL !!!
> --
> Thanks for any help!
> Neil Millington
|||Thanks Tibor...will post tonight, as server is in remote ISP and I need to
get behing the firewall.
Much appreciated,
Neil.
"Tibor Karaszi" wrote:

> Can you post the exact error message?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
>
>
|||Tibor... will post tonight as server is in ISP and I need to get behing
firewall!
Much appreciated.
"Tibor Karaszi" wrote:

> Can you post the exact error message?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
>
>
|||I suspect the error is that you have another setup (doesn't have to be a SQL Server setup) which is
in "pending" state. If so, search KB for a suitable part of the error message and you will find the
KB which describes the registry modification you need to perform...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Belmann" <SQLServer@.belmann.co.uk> wrote in message
news:CDC4EFFD-BCDA-4C08-9DA5-E938DDA4DB72@.microsoft.com...[vbcol=seagreen]
> Tibor... will post tonight as server is in ISP and I need to get behing
> firewall!
> Much appreciated.
> "Tibor Karaszi" wrote:
|||Tibor,
Thanks for the reply, here is the message:
<<
setup has detected that the previous install attempt was not completed.
Retry to continue installation or cancel to exit setup[vbcol=seagreen]
...when selecting 'Retry' setup starts to file copy into \program
files\microsoft sql server but fails when trying to run script 1 (as
everything has been removed from drive/registry).
Neil.
"Tibor Karaszi" wrote:

> Can you post the exact error message?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Belmann" <SQLServer@.belmann.co.uk> wrote in message
> news:17D3E6B5-4465-4927-85F1-B73B5ADD70E7@.microsoft.com...
>
>
|||This was not the error message I was thinking of, I'm afraid. I suggest you start searching Google,
the newsgroup archives and KB. If you don't find anything there, consider posting this to the .setup
group. And be prepared to include the sqlstp.log file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Belmann" <SQLServer@.belmann.co.uk> wrote in message
news:A8921334-D3E0-4AE1-9225-31E8FCAE562F@.microsoft.com...[vbcol=seagreen]
> Tibor,
> Thanks for the reply, here is the message:
> <<
> setup has detected that the previous install attempt was not completed.
> Retry to continue installation or cancel to exit setup
> ...when selecting 'Retry' setup starts to file copy into \program
> files\microsoft sql server but fails when trying to run script 1 (as
> everything has been removed from drive/registry).
> Neil.
> "Tibor Karaszi" wrote: