Is it possible to recover from failed sp4 installation?

Hi All,
I have a client who last night attempted to install sql 2000 Enterprise
Edition SP4. When running the first time through it got past the Password
Validation and moved to the Analysing and Preparing stage of the
installation. At this point it completely hung - after an hour there was
still no activity.
Now when attempting to re-install SP3a it states that a later version is
already installed and when attempting to reinstall SP4 it hangs on password
validation everytime.
This is a production server, does anyone know if it is possible to recover
from the above scenario?
Thanks
LarryJosh
I have been istalling SP4 mamy times and have never got the situation. Hmmm,
try tirn off (from the network) the server and re-install SP4
"Josh Lawrence" <someone@.microsoft.com> wrote in message
news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> Hi All,
> I have a client who last night attempted to install sql 2000 Enterprise
> Edition SP4. When running the first time through it got past the Password
> Validation and moved to the Analysing and Preparing stage of the
> installation. At this point it completely hung - after an hour there was
> still no activity.
> Now when attempting to re-install SP3a it states that a later version is
> already installed and when attempting to reinstall SP4 it hangs on
> password validation everytime.
> This is a production server, does anyone know if it is possible to recover
> from the above scenario?
> Thanks
> Larry
>|||I have experienced this issue previously but can't recall the solution. I
have the awful feeling it may require a complete reinstallation of SQL2000
from the ground up.
Thanks
Josh
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> Josh
> I have been istalling SP4 mamy times and have never got the situation.
> Hmmm, try tirn off (from the network) the server and re-install SP4
>
>
> "Josh Lawrence" <someone@.microsoft.com> wrote in message
> news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
>|||Hi --
I have run into the exact same issue, where SP4 installation hangs on
password validation. It worked for me on number of other servers but it
doesn't work on this server.
I have tried using Windows and SQL Server authentication, sa without
password but it didn't make any difference.
Did anyone find a solution?
The funny thing is that @.@.version shows SP4, however it is Not SP4.
Thanks
Gurpreet
"Josh Lawrence" wrote:

> I have experienced this issue previously but can't recall the solution. I
> have the awful feeling it may require a complete reinstallation of SQL2000
> from the ground up.
> Thanks
> Josh
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
>
>

Is it possible to recover from failed sp4 installation?

Hi All,
I have a client who last night attempted to install sql 2000 Enterprise
Edition SP4. When running the first time through it got past the Password
Validation and moved to the Analysing and Preparing stage of the
installation. At this point it completely hung - after an hour there was
still no activity.
Now when attempting to re-install SP3a it states that a later version is
already installed and when attempting to reinstall SP4 it hangs on password
validation everytime.
This is a production server, does anyone know if it is possible to recover
from the above scenario?
Thanks
LarryJosh
I have been istalling SP4 mamy times and have never got the situation. Hmmm,
try tirn off (from the network) the server and re-install SP4
"Josh Lawrence" <someone@.microsoft.com> wrote in message
news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> Hi All,
> I have a client who last night attempted to install sql 2000 Enterprise
> Edition SP4. When running the first time through it got past the Password
> Validation and moved to the Analysing and Preparing stage of the
> installation. At this point it completely hung - after an hour there was
> still no activity.
> Now when attempting to re-install SP3a it states that a later version is
> already installed and when attempting to reinstall SP4 it hangs on
> password validation everytime.
> This is a production server, does anyone know if it is possible to recover
> from the above scenario?
> Thanks
> Larry
>|||I have experienced this issue previously but can't recall the solution. I
have the awful feeling it may require a complete reinstallation of SQL2000
from the ground up.
Thanks
Josh
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> Josh
> I have been istalling SP4 mamy times and have never got the situation.
> Hmmm, try tirn off (from the network) the server and re-install SP4
>
>
> "Josh Lawrence" <someone@.microsoft.com> wrote in message
> news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
>> Hi All,
>> I have a client who last night attempted to install sql 2000 Enterprise
>> Edition SP4. When running the first time through it got past the
>> Password Validation and moved to the Analysing and Preparing stage of the
>> installation. At this point it completely hung - after an hour there was
>> still no activity.
>> Now when attempting to re-install SP3a it states that a later version is
>> already installed and when attempting to reinstall SP4 it hangs on
>> password validation everytime.
>> This is a production server, does anyone know if it is possible to
>> recover from the above scenario?
>> Thanks
>> Larry
>|||Hi --
I have run into the exact same issue, where SP4 installation hangs on
password validation. It worked for me on number of other servers but it
doesn't work on this server.
I have tried using Windows and SQL Server authentication, sa without
password but it didn't make any difference.
Did anyone find a solution?
The funny thing is that @.@.version shows SP4, however it is Not SP4.
Thanks
Gurpreet
"Josh Lawrence" wrote:
> I have experienced this issue previously but can't recall the solution. I
> have the awful feeling it may require a complete reinstallation of SQL2000
> from the ground up.
> Thanks
> Josh
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> > Josh
> > I have been istalling SP4 mamy times and have never got the situation.
> > Hmmm, try tirn off (from the network) the server and re-install SP4
> >
> >
> >
> >
> >
> > "Josh Lawrence" <someone@.microsoft.com> wrote in message
> > news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> >> Hi All,
> >> I have a client who last night attempted to install sql 2000 Enterprise
> >> Edition SP4. When running the first time through it got past the
> >> Password Validation and moved to the Analysing and Preparing stage of the
> >> installation. At this point it completely hung - after an hour there was
> >> still no activity.
> >>
> >> Now when attempting to re-install SP3a it states that a later version is
> >> already installed and when attempting to reinstall SP4 it hangs on
> >> password validation everytime.
> >>
> >> This is a production server, does anyone know if it is possible to
> >> recover from the above scenario?
> >>
> >> Thanks
> >> Larry
> >>
> >
> >
>
>sql

Is it possible to install the third instance?

Hi everyone,
I have active-passive two node cluster server, it's already installed two
instances with associated two network names and IP addresses. Is there
possible to install the third instance in this cluster server, if give the
specific network name and IP address but no physical node 3?
Regards,
-Chen
Yes. The Active-Passive, Active-Active nomenclature is left over from SQL
7.0 and no longer accurately represents the clustering capabilities of SQL
Server 2000. The short version is you can have up to 16 instances on a
cluster, regardless of the number of nodes. You can choose which instances
should be on which nodes during normal operating conditions. You do have to
have a unique network name, IP address, and disk resource for each instance.
You also need to make sure you have enough physical resources (memory, CPU,
IO capacity) on each node to handle the work load, even during a failover
condition.
The correct current terms are single-instance and multiple-instance
clusters.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:430C357E-407A-4F73-8764-DDAFD3203DC2@.microsoft.com...
> Hi everyone,
> I have active-passive two node cluster server, it's already installed two
> instances with associated two network names and IP addresses. Is there
> possible to install the third instance in this cluster server, if give the
> specific network name and IP address but no physical node 3?
> Regards,
> -Chen
>
sql

Is it possible to install SQL Sever 2005 Developer on Vista Home Premium?

During the install, I receive this message:

"Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online."

So, I went to the following and did everything documented about installing IIS 7.0.

http://msdn2.microsoft.com/en-us/library/aa964620.aspx

After installing IIS and verifying that it is serving pages just fine, when I try to install again, I still get the quoted error message above.

I am beginning to think that I cannot install SQL Server Developer on Vista Home Premium.

Does anyone know?

Thanks

Here's a link that should help: http://support.microsoft.com/kb/920201

I was experiencing the same problem. In my case, I did not have Windows Authentication selected when I installed IIS. When I added it, the warning went away.

|||Thanks. I'll try it with Windows Authentication selected.

Is it possible to install SQL Express with SQL standard Edition

Hi,

I have installed SQL standard Edition in my computer for one project. We want to kick off a new project, and intend to use SQL Express, Will anybody advise me whether I can install SQL express when SQL Standard Edition is there? or I need to remove SQL standard Edition first and install SQL express?

Thanks a lot

Haihong

Yes absolutely you can install them side-by-side. You are limited in the number and flavors of SQL Server installs really only by your hardware capabilities. The one caveat is that each beyond the first will have to be named uniquely as you can only have one default instance running. I have SQL Server 2000, SQL Server 2005 Express, and SQL Server 2005 Developer on the same machine and haven't had any problems.|||

Hi,

yes you sure can do this. The new SQL Express instance will have a different port number′, so if you want to connect to this instance you either have to name the port number after the instance name by using the syntax Machinename\InstanceName,Portnumber or start the SQL Browser service which wil redirect the client automatically to the appropiate port number during connection time.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Is it possible to install server and client in one PC

This maybe a dumb question, looks not possibe to me.
But if it is possible, then it would be very nice for development.Yes it's easy. Just follow the default (single server) installation
instructions and make sure you have VS.NET already installed.
--
Jeff Lynch
"A BizTalk Enthusiast"
http://dotnetjunkies.com/WebLog/jlynch/
"Frank RS" <FrankRS@.discussions.microsoft.com> wrote in message
news:41E0CAE4-2AFE-4EC6-B262-C96C942D9EB4@.microsoft.com...
> This maybe a dumb question, looks not possibe to me.
> But if it is possible, then it would be very nice for development.
>

is it possible to install MSDE after SQL2000?

i installed MSDE _AFTER_ i installed sql2000. i finally got the install to work by specifying the instance name, but i can't connect to my msde instance via enterprise manager. i tried \mycomputer\vsdotnet (the instance name) but it says it's not there. any ideas?nevermind, the instance was netsdk, not vsdotnet.

is it possible to install msde 2000 in win98

I am developing a project in Vb.net
using MSDE 2000 as backend.
I want to deployment my project in win98 OS PCs.
is it possible to install msde 2000 in win98
bye
S.MuhilanOriginally posted by S_Muhilan
I am developing a project in Vb.net
using MSDE 2000 as backend.
I want to deployment my project in win98 OS PCs.
is it possible to install msde 2000 in win98

bye
S.Muhilan

Yes You Can! It is possbile!

MSDE 2000 is a royalty-free, redistributable database engine that is fully compatible with SQL Server. MSDE 2000 is designed to run on Microsoft Windows 98, Windows Millennium Edition (Windows Me), Microsoft Windows NT Workstation version 4.0 (with Service Pack 5 or later), and Windows 2000 Professional as an embedded database for custom applications that require a local database engine.|||Be aware restrictions like database max size is 2GB only and restricted usage of memory and not all the features are available like SQL Server.

http://www.microsoft.com/sql/techinfo/development/2000/MSDEintegration.asp for further information.

Is it possible to install MS SQL 6.5 on Windows 2003?

Is it possible to install MS SQL 6.5 on Windows 2003?
Can you give some information if it is possible by some Patches or MDAC
?
or any spesific SP?
Thanks
SuhasHi ,
Officially SQL 6.5 is not supported on Windows 2003. But you can still
install SQL 6.5 in Windows 2003.
Thanks
Hari
SQL Server MVP
"suhas" <suhasvpatil@.gmail.com> wrote in message
news:1154430945.301135.302420@.b28g2000cwb.googlegroups.com...
> Is it possible to install MS SQL 6.5 on Windows 2003?
> Can you give some information if it is possible by some Patches or MDAC
> ?
> or any spesific SP?
> Thanks
> Suhas
>

Is it possible to install MS SQL 6.5 on Windows 2003?

Is it possible to install MS SQL 6.5 on Windows 2003?
Can you give some information if it is possible by some Patches or MDAC
?
or any spesific SP?
Thanks
SuhasHi ,
Officially SQL 6.5 is not supported on Windows 2003. But you can still
install SQL 6.5 in Windows 2003.
Thanks
Hari
SQL Server MVP
"suhas" <suhasvpatil@.gmail.com> wrote in message
news:1154430945.301135.302420@.b28g2000cwb.googlegroups.com...

> Is it possible to install MS SQL 6.5 on Windows 2003?
> Can you give some information if it is possible by some Patches or MDAC
> ?
> or any spesific SP?
> Thanks
> Suhas
>

Is it possible to install Enterprise from a Standard Edition CD?

There is only on one CD in my environment and it contains SQL Svr Standard;
however, some installs show as Enterprise Editions - is this possible?No, someone had another CD at some point.
--
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"NeverQuit" <NeverQuit@.discussions.microsoft.com> wrote in message
news:BBBDBE3A-0DB9-4F9D-8D4F-582F69EEA963@.microsoft.com...
> There is only on one CD in my environment and it contains SQL Svr
Standard;
> however, some installs show as Enterprise Editions - is this possible?

Is it possible to install Enterprise from a Standard Edition CD?

There is only on one CD in my environment and it contains SQL Svr Standard;
however, some installs show as Enterprise Editions - is this possible?
No, someone had another CD at some point.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"NeverQuit" <NeverQuit@.discussions.microsoft.com> wrote in message
news:BBBDBE3A-0DB9-4F9D-8D4F-582F69EEA963@.microsoft.com...
> There is only on one CD in my environment and it contains SQL Svr
Standard;
> however, some installs show as Enterprise Editions - is this possible?
sql

Is it possible to install Enterprise from a Standard Edition CD?

There is only on one CD in my environment and it contains SQL Svr Standard;
however, some installs show as Enterprise Editions - is this possible?No, someone had another CD at some point.
Please post DDL, sample data and desired results.
See http://www.aspfaq.com/5006 for info.
"NeverQuit" <NeverQuit@.discussions.microsoft.com> wrote in message
news:BBBDBE3A-0DB9-4F9D-8D4F-582F69EEA963@.microsoft.com...
> There is only on one CD in my environment and it contains SQL Svr
Standard;
> however, some installs show as Enterprise Editions - is this possible?

Is it necessary to install Intergration Service for different instance ?

We have to install another instance to an existing SQL Server 2005 Server.
We would like to know whether it is necessary for us to select Integration
Service ? Besides, we would like to know besides Database Engine, is there
any other service we have to select ?
Moreover, we find that Reporting Services is shown as an instance when we
view "Installed Instance", we would like to know why it behaves as an
instance ?
In addition, it seems that even though we have installed default instance,
SQL Server 2005 still gives us a choice of installing Default Instance.
What will happen if we choose "Default Instance" if there is already have
one ? In SQL Server 2000, the choice of Default Instance is disabled.
Thanks
Peter> We would like to know whether it is necessary for us to select Integration Service ?
You can only have one instance of SSIS (which will serve all database engine instance that need to
use it). So, if SSIS is already installed and you select to install it again, setup will tell you
that it is already installed.
> Besides, we would like to know besides Database Engine, is there any other service we have to
> select ?
Not really. But only you know if you after installing this instance need also, say SSAS.
> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
> Instance", we would like to know why it behaves as an instance ?
Because you can have several instances of RS, just the same way as you can have several instances of
the database engine.
> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
> gives us a choice of installing Default Instance. What will happen if we choose "Default Instance"
> if there is already have one ?
Setup will tell you that it already is installed and won't do anything.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:e9v0AnyCIHA.4956@.TK2MSFTNGP06.phx.gbl...
> We have to install another instance to an existing SQL Server 2005 Server. We would like to know
> whether it is necessary for us to select Integration Service ? Besides, we would like to know
> besides Database Engine, is there any other service we have to select ?
> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
> Instance", we would like to know why it behaves as an instance ?
> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
> gives us a choice of installing Default Instance. What will happen if we choose "Default Instance"
> if there is already have one ? In SQL Server 2000, the choice of Default Instance is disabled.
> Thanks
> Peter
>|||Dear Tibor,
From your mail, my understanding is that for SSIS, only 1 instance can be
installed.
On the other hand, for others - like RS, AS, Database Engine, we can install
more than 1 instance.
Is there any other services that only installed once - Like Notification
Services ... ?
Peter
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uZ9QyvzCIHA.5328@.TK2MSFTNGP05.phx.gbl...
>> We would like to know whether it is necessary for us to select
>> Integration Service ?
> You can only have one instance of SSIS (which will serve all database
> engine instance that need to use it). So, if SSIS is already installed and
> you select to install it again, setup will tell you that it is already
> installed.
>> Besides, we would like to know besides Database Engine, is there any
>> other service we have to select ?
> Not really. But only you know if you after installing this instance need
> also, say SSAS.
>> Moreover, we find that Reporting Services is shown as an instance when we
>> view "Installed Instance", we would like to know why it behaves as an
>> instance ?
> Because you can have several instances of RS, just the same way as you can
> have several instances of the database engine.
>
>> In addition, it seems that even though we have installed default
>> instance, SQL Server 2005 still gives us a choice of installing Default
>> Instance. What will happen if we choose "Default Instance" if there is
>> already have one ?
> Setup will tell you that it already is installed and won't do anything.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Peter" <Peter@.discussions.microsoft.com> wrote in message
> news:e9v0AnyCIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> We have to install another instance to an existing SQL Server 2005
>> Server. We would like to know whether it is necessary for us to select
>> Integration Service ? Besides, we would like to know besides Database
>> Engine, is there any other service we have to select ?
>> Moreover, we find that Reporting Services is shown as an instance when we
>> view "Installed Instance", we would like to know why it behaves as an
>> instance ?
>> In addition, it seems that even though we have installed default
>> instance, SQL Server 2005 still gives us a choice of installing Default
>> Instance. What will happen if we choose "Default Instance" if there is
>> already have one ? In SQL Server 2000, the choice of Default Instance is
>> disabled.
>> Thanks
>> Peter
>>
>|||Peter,
> From your mail, my understanding is that for SSIS, only 1 instance can be installed.
Correct.
> On the other hand, for others - like RS, AS, Database Engine, we can install more than 1 instance.
Also correct.
> Is there any other services that only installed once - Like Notification Services ... ?
Actually RS, AS and Db Engine are the only services for which you can install several instances.
You can only have one SQL Server browser - it doesn't make sense to have several.
You can only have one SQL Server VSS Writer - it doesn't make sense to have several.
You can only have one SSIS service
As for Notification Services (NS), you can only install it once. But you need to read about NS to
understand what that means. Installation of NS only installs some binary files (essentially). When
you develop an NS solution, you (among other things) run a program (NSCONTROL.EXE) to create the
Windows service. You can have several of these services, but that part is something you do *after*
you have installed the binary files. Also, NS will not ship with 2008, so it is essentially a dead
component which you probably don't want to build new solutions on.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Peter" <Peter@.discussions.microsoft.com> wrote in message
news:ez0wn7%23CIHA.4308@.TK2MSFTNGP06.phx.gbl...
> Dear Tibor,
> From your mail, my understanding is that for SSIS, only 1 instance can be installed.
> On the other hand, for others - like RS, AS, Database Engine, we can install more than 1 instance.
> Is there any other services that only installed once - Like Notification Services ... ?
> Peter
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uZ9QyvzCIHA.5328@.TK2MSFTNGP05.phx.gbl...
>> We would like to know whether it is necessary for us to select Integration Service ?
>> You can only have one instance of SSIS (which will serve all database engine instance that need
>> to use it). So, if SSIS is already installed and you select to install it again, setup will tell
>> you that it is already installed.
>> Besides, we would like to know besides Database Engine, is there any other service we have to
>> select ?
>> Not really. But only you know if you after installing this instance need also, say SSAS.
>> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
>> Instance", we would like to know why it behaves as an instance ?
>> Because you can have several instances of RS, just the same way as you can have several instances
>> of the database engine.
>>
>> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
>> gives us a choice of installing Default Instance. What will happen if we choose "Default
>> Instance" if there is already have one ?
>> Setup will tell you that it already is installed and won't do anything.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Peter" <Peter@.discussions.microsoft.com> wrote in message
>> news:e9v0AnyCIHA.4956@.TK2MSFTNGP06.phx.gbl...
>> We have to install another instance to an existing SQL Server 2005 Server. We would like to know
>> whether it is necessary for us to select Integration Service ? Besides, we would like to know
>> besides Database Engine, is there any other service we have to select ?
>> Moreover, we find that Reporting Services is shown as an instance when we view "Installed
>> Instance", we would like to know why it behaves as an instance ?
>> In addition, it seems that even though we have installed default instance, SQL Server 2005 still
>> gives us a choice of installing Default Instance. What will happen if we choose "Default
>> Instance" if there is already have one ? In SQL Server 2000, the choice of Default Instance is
>> disabled.
>> Thanks
>> Peter
>>
>>
>

Is it mandatory to install "SQL server client" to connect to server that has "SQL

Hello,

My database is on the server. I have a vb.net application installed on a client's machine. The problem is I am not able to connect to server from my application.

I have figured out that "SQL server client" is not installed on client's machine.

So is there any settings/utility available using which without installing SQL client I can connect to Server.

Any views/help would be apprecciated.

You do not need to install anything on the client to connect to RS. What error are you recieving?|||

The server machine contains the database and the vb.net application is installed on the client's machine. So my question is in order to connect to the database that resiedes on the server, should client's machine also need "sql server client" or is there any way in which the application can connect to database without "sql client" on client machine.

This has nothing to do with reporting services.

Thanks

|||

I would suggest posting your question here http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=158&SiteID=1

This is a report server forum, so I assumed the question was about RS. Assuming you are using .Net, the answer would still be no, client tools are not required on the client for an application.

Is it mandatory to install "SQL server client" to connect to server that has "

Hello,

My database is on the server. I have a vb.net application installed on a client's machine. The problem is I am not able to connect to server from my application.

I have figured out that "SQL server client" is not installed on client's machine.

So is there any settings/utility available using which without installing SQL client I can connect to Server.

Any views/help would be apprecciated.

You do not need to install anything on the client to connect to RS. What error are you recieving?|||

The server machine contains the database and the vb.net application is installed on the client's machine. So my question is in order to connect to the database that resiedes on the server, should client's machine also need "sql server client" or is there any way in which the application can connect to database without "sql client" on client machine.

This has nothing to do with reporting services.

Thanks

|||

I would suggest posting your question here http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=158&SiteID=1

This is a report server forum, so I assumed the question was about RS. Assuming you are using .Net, the answer would still be no, client tools are not required on the client for an application.

Is installing MS Outlook a security risk?

I just took over a new project and trying to setup the environment up to bes
t
practicing standards. I wanted to install MS Outlook to setup MAPI. My
manager thinks installing outlook on production server is really nuts. He
thinks it's a security risk and overall having MS Outlook on a production
server doesn't seem right. I have never heard of any kind of security risk o
r
any other internal problems MS Outlook can create in a production box with
SQL Server installed on it. Can one of the MVPs please confirm it for me and
if possible give any suggestions or arguments that I can use to convince him
?
Thanks in advance for your support ...
BobBob wrote:
> I just took over a new project and trying to setup the environment up to b
est
> practicing standards. I wanted to install MS Outlook to setup MAPI. My
> manager thinks installing outlook on production server is really nuts. He
> thinks it's a security risk and overall having MS Outlook on a production
> server doesn't seem right. I have never heard of any kind of security risk
or
> any other internal problems MS Outlook can create in a production box with
> SQL Server installed on it. Can one of the MVPs please confirm it for me a
nd
> if possible give any suggestions or arguments that I can use to convince h
im?
> Thanks in advance for your support ...
> Bob
I assume this is a SQL 2000 server? I agree, Outlook has no place on a
server, but if you want to use SQL Mail, you have no choice. You do
have alternatives to SQL Mail, however. I've used a command-line mailer
called "BLAT" for years with great success. There is also an extended
stored procedure available for download called xp_smtp_sendmail, that is
nearly a drop-in replacement for xp_sendmail.
Of course, if you're on SQL 2005, this is all moot...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I don't find Outlook to be a security risk, I find it to be a stability
risk. Outlook is a lot of things, but a stable MAPI service provider isn't
on that list. I prefer to use xp_smtpmail from www.sqldev.net. It isn't a
drop-in replacement for SQLMail or SQLAgentMail, but you can make it do most
of the tasks that xp_sendmail supports. I usually add extra steps for
failure and success notification to my agent jobs, but there are several
ways to implement this code. It is a very stable add-in and has caused me
zero problems, even on large cluster installations.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bob" <Bob@.discussions.microsoft.com> wrote in message
news:3A2B8DAB-9424-4E86-9C53-C8BD6E0B1206@.microsoft.com...
>I just took over a new project and trying to setup the environment up to
>best
> practicing standards. I wanted to install MS Outlook to setup MAPI. My
> manager thinks installing outlook on production server is really nuts. He
> thinks it's a security risk and overall having MS Outlook on a production
> server doesn't seem right. I have never heard of any kind of security risk
> or
> any other internal problems MS Outlook can create in a production box with
> SQL Server installed on it. Can one of the MVPs please confirm it for me
> and
> if possible give any suggestions or arguments that I can use to convince
> him?
> Thanks in advance for your support ...
> Bob|||Sorry, I forgot to put SQL Server version .. yes it is SQL Server 2000 (SP4)
on Windows 2003 server
That's the confusion .. MS Outlook is also a Microsoft product then why
can't we have that on the server where SQL Server resides?
"Tracy McKibben" wrote:

> Bob wrote:
> I assume this is a SQL 2000 server? I agree, Outlook has no place on a
> server, but if you want to use SQL Mail, you have no choice. You do
> have alternatives to SQL Mail, however. I've used a command-line mailer
> called "BLAT" for years with great success. There is also an extended
> stored procedure available for download called xp_smtp_sendmail, that is
> nearly a drop-in replacement for xp_sendmail.
> Of course, if you're on SQL 2005, this is all moot...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Bob wrote:
> Sorry, I forgot to put SQL Server version .. yes it is SQL Server 2000 (SP
4)
> on Windows 2003 server
> That's the confusion .. MS Outlook is also a Microsoft product then why
> can't we have that on the server where SQL Server resides?
>
My personal reasons:
1. It's absurd to require a full blown mail client in order to send
SMTP messages from a database server. In the *nix world, there are
hundreds of tiny, dedicated SMTP components available if you need to
send an email message. Why couldn't Microsoft provide something so
simple without requiring their mail client?
2. Outlook is not a stable application, and I don't like having
unstable applications running on my servers, especially when they have
hooks into my database server.
3. Internet Explorer is also a Microsoft product, but I don't trust it,
even on a Microsoft operating system, therefore I don't use it. IE has
some serious flaws, as does Outlook. If something (virus/worm,
whatever) gets loose on my network, I don't want to have to worry about
my databases getting nailed by it.
4. There are simply better options available...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Bob wrote:
> I just took over a new project and trying to setup the environment up to b
est
> practicing standards. I wanted to install MS Outlook to setup MAPI. My
> manager thinks installing outlook on production server is really nuts. He
> thinks it's a security risk and overall having MS Outlook on a production
> server doesn't seem right. I have never heard of any kind of security risk
or
> any other internal problems MS Outlook can create in a production box with
> SQL Server installed on it. Can one of the MVPs please confirm it for me a
nd
> if possible give any suggestions or arguments that I can use to convince h
im?
> Thanks in advance for your support ...
> Bob
MAPI mail support is gone from SQL Server 2005. That's one more reason
why NOT to use it (the main reason has always been "It sucks!"). Think
xp_smtp_sendmailk, Notification Services or some other mail component.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||my confusion has come to an end after reading all these replies ... Thanks s
o
much all for your help
"David Portas" wrote:

> Bob wrote:
> MAPI mail support is gone from SQL Server 2005. That's one more reason
> why NOT to use it (the main reason has always been "It sucks!"). Think
> xp_smtp_sendmailk, Notification Services or some other mail component.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:ekTxHeFpGHA.4424@.TK2MSFTNGP05.phx.gbl...
> Bob wrote:
best[vbcol=seagreen]
He[vbcol=seagreen]
production[vbcol=seagreen]
risk or[vbcol=seagreen]
with[vbcol=seagreen]
and[vbcol=seagreen]
him?[vbcol=seagreen]
> I assume this is a SQL 2000 server? I agree, Outlook has no place on a
> server, but if you want to use SQL Mail, you have no choice. You do
> have alternatives to SQL Mail, however. I've used a command-line mailer
> called "BLAT" for years with great success. There is also an extended
> stored procedure available for download called xp_smtp_sendmail, that is
> nearly a drop-in replacement for xp_sendmail.
Except they don't replace the best reason (in my opinion) to use outlook
which is to allow SQL Agent to send alerts, etc.
(I also have used blat btw, decent product.)
I don't think there's a problem with outlook on a SQL Server. Just make sure
it's only sending email and not receiving.
Generally I install the SMTP server that comes with IIS and have my Outlook
install send to this and have it relay to my "real" SMTP server.
This eliminates a lot of issues with Outlook locking up if it can't reach
the mail server.
I don't think the security risk is that large if you understand your goals
and what you're doing.

> Of course, if you're on SQL 2005, this is all moot...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OH33MhFpGHA.1796@.TK2MSFTNGP03.phx.gbl...
> I don't find Outlook to be a security risk, I find it to be a stability
> risk. Outlook is a lot of things, but a stable MAPI service provider
isn't
> on that list.
Just for the record, while I tend to agree, see my other email.
The BEST thing I ever did for Outlook was to put a local SMTP server on the
SQL box and set it up to relay only from that box to my main SMTP server.
This has GREATLY increased my stability. (to the point I really don't have
to think about SQL Mail at all. It pretty much just works.)

> I prefer to use xp_smtpmail from www.sqldev.net. It isn't a
> drop-in replacement for SQLMail or SQLAgentMail, but you can make it do
most
> of the tasks that xp_sendmail supports. I usually add extra steps for
> failure and success notification to my agent jobs, but there are several
> ways to implement this code. It is a very stable add-in and has caused me
> zero problems, even on large cluster installations.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Bob" <Bob@.discussions.microsoft.com> wrote in message
> news:3A2B8DAB-9424-4E86-9C53-C8BD6E0B1206@.microsoft.com...
He[vbcol=seagreen]
production[vbcol=seagreen]
risk[vbcol=seagreen]
with[vbcol=seagreen]
>

Is installing MS Outlook a security risk?

I just took over a new project and trying to setup the environment up to best
practicing standards. I wanted to install MS Outlook to setup MAPI. My
manager thinks installing outlook on production server is really nuts. He
thinks it's a security risk and overall having MS Outlook on a production
server doesn't seem right. I have never heard of any kind of security risk or
any other internal problems MS Outlook can create in a production box with
SQL Server installed on it. Can one of the MVPs please confirm it for me and
if possible give any suggestions or arguments that I can use to convince him?
Thanks in advance for your support ...
BobBob wrote:
> I just took over a new project and trying to setup the environment up to best
> practicing standards. I wanted to install MS Outlook to setup MAPI. My
> manager thinks installing outlook on production server is really nuts. He
> thinks it's a security risk and overall having MS Outlook on a production
> server doesn't seem right. I have never heard of any kind of security risk or
> any other internal problems MS Outlook can create in a production box with
> SQL Server installed on it. Can one of the MVPs please confirm it for me and
> if possible give any suggestions or arguments that I can use to convince him?
> Thanks in advance for your support ...
> Bob
I assume this is a SQL 2000 server? I agree, Outlook has no place on a
server, but if you want to use SQL Mail, you have no choice. You do
have alternatives to SQL Mail, however. I've used a command-line mailer
called "BLAT" for years with great success. There is also an extended
stored procedure available for download called xp_smtp_sendmail, that is
nearly a drop-in replacement for xp_sendmail.
Of course, if you're on SQL 2005, this is all moot...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I don't find Outlook to be a security risk, I find it to be a stability
risk. Outlook is a lot of things, but a stable MAPI service provider isn't
on that list. I prefer to use xp_smtpmail from www.sqldev.net. It isn't a
drop-in replacement for SQLMail or SQLAgentMail, but you can make it do most
of the tasks that xp_sendmail supports. I usually add extra steps for
failure and success notification to my agent jobs, but there are several
ways to implement this code. It is a very stable add-in and has caused me
zero problems, even on large cluster installations.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bob" <Bob@.discussions.microsoft.com> wrote in message
news:3A2B8DAB-9424-4E86-9C53-C8BD6E0B1206@.microsoft.com...
>I just took over a new project and trying to setup the environment up to
>best
> practicing standards. I wanted to install MS Outlook to setup MAPI. My
> manager thinks installing outlook on production server is really nuts. He
> thinks it's a security risk and overall having MS Outlook on a production
> server doesn't seem right. I have never heard of any kind of security risk
> or
> any other internal problems MS Outlook can create in a production box with
> SQL Server installed on it. Can one of the MVPs please confirm it for me
> and
> if possible give any suggestions or arguments that I can use to convince
> him?
> Thanks in advance for your support ...
> Bob|||Sorry, I forgot to put SQL Server version .. yes it is SQL Server 2000 (SP4)
on Windows 2003 server
That's the confusion .. MS Outlook is also a Microsoft product then why
can't we have that on the server where SQL Server resides?
"Tracy McKibben" wrote:
> Bob wrote:
> > I just took over a new project and trying to setup the environment up to best
> > practicing standards. I wanted to install MS Outlook to setup MAPI. My
> > manager thinks installing outlook on production server is really nuts. He
> > thinks it's a security risk and overall having MS Outlook on a production
> > server doesn't seem right. I have never heard of any kind of security risk or
> > any other internal problems MS Outlook can create in a production box with
> > SQL Server installed on it. Can one of the MVPs please confirm it for me and
> > if possible give any suggestions or arguments that I can use to convince him?
> > Thanks in advance for your support ...
> >
> > Bob
> I assume this is a SQL 2000 server? I agree, Outlook has no place on a
> server, but if you want to use SQL Mail, you have no choice. You do
> have alternatives to SQL Mail, however. I've used a command-line mailer
> called "BLAT" for years with great success. There is also an extended
> stored procedure available for download called xp_smtp_sendmail, that is
> nearly a drop-in replacement for xp_sendmail.
> Of course, if you're on SQL 2005, this is all moot...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Bob wrote:
> Sorry, I forgot to put SQL Server version .. yes it is SQL Server 2000 (SP4)
> on Windows 2003 server
> That's the confusion .. MS Outlook is also a Microsoft product then why
> can't we have that on the server where SQL Server resides?
>
My personal reasons:
1. It's absurd to require a full blown mail client in order to send
SMTP messages from a database server. In the *nix world, there are
hundreds of tiny, dedicated SMTP components available if you need to
send an email message. Why couldn't Microsoft provide something so
simple without requiring their mail client?
2. Outlook is not a stable application, and I don't like having
unstable applications running on my servers, especially when they have
hooks into my database server.
3. Internet Explorer is also a Microsoft product, but I don't trust it,
even on a Microsoft operating system, therefore I don't use it. IE has
some serious flaws, as does Outlook. If something (virus/worm,
whatever) gets loose on my network, I don't want to have to worry about
my databases getting nailed by it.
4. There are simply better options available...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Bob wrote:
> I just took over a new project and trying to setup the environment up to best
> practicing standards. I wanted to install MS Outlook to setup MAPI. My
> manager thinks installing outlook on production server is really nuts. He
> thinks it's a security risk and overall having MS Outlook on a production
> server doesn't seem right. I have never heard of any kind of security risk or
> any other internal problems MS Outlook can create in a production box with
> SQL Server installed on it. Can one of the MVPs please confirm it for me and
> if possible give any suggestions or arguments that I can use to convince him?
> Thanks in advance for your support ...
> Bob
MAPI mail support is gone from SQL Server 2005. That's one more reason
why NOT to use it (the main reason has always been "It sucks!"). Think
xp_smtp_sendmailk, Notification Services or some other mail component.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||my confusion has come to an end after reading all these replies ... Thanks so
much all for your help
"David Portas" wrote:
> Bob wrote:
> > I just took over a new project and trying to setup the environment up to best
> > practicing standards. I wanted to install MS Outlook to setup MAPI. My
> > manager thinks installing outlook on production server is really nuts. He
> > thinks it's a security risk and overall having MS Outlook on a production
> > server doesn't seem right. I have never heard of any kind of security risk or
> > any other internal problems MS Outlook can create in a production box with
> > SQL Server installed on it. Can one of the MVPs please confirm it for me and
> > if possible give any suggestions or arguments that I can use to convince him?
> > Thanks in advance for your support ...
> >
> > Bob
> MAPI mail support is gone from SQL Server 2005. That's one more reason
> why NOT to use it (the main reason has always been "It sucks!"). Think
> xp_smtp_sendmailk, Notification Services or some other mail component.
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:ekTxHeFpGHA.4424@.TK2MSFTNGP05.phx.gbl...
> Bob wrote:
> > I just took over a new project and trying to setup the environment up to
best
> > practicing standards. I wanted to install MS Outlook to setup MAPI. My
> > manager thinks installing outlook on production server is really nuts.
He
> > thinks it's a security risk and overall having MS Outlook on a
production
> > server doesn't seem right. I have never heard of any kind of security
risk or
> > any other internal problems MS Outlook can create in a production box
with
> > SQL Server installed on it. Can one of the MVPs please confirm it for me
and
> > if possible give any suggestions or arguments that I can use to convince
him?
> > Thanks in advance for your support ...
> >
> > Bob
> I assume this is a SQL 2000 server? I agree, Outlook has no place on a
> server, but if you want to use SQL Mail, you have no choice. You do
> have alternatives to SQL Mail, however. I've used a command-line mailer
> called "BLAT" for years with great success. There is also an extended
> stored procedure available for download called xp_smtp_sendmail, that is
> nearly a drop-in replacement for xp_sendmail.
Except they don't replace the best reason (in my opinion) to use outlook
which is to allow SQL Agent to send alerts, etc.
(I also have used blat btw, decent product.)
I don't think there's a problem with outlook on a SQL Server. Just make sure
it's only sending email and not receiving.
Generally I install the SMTP server that comes with IIS and have my Outlook
install send to this and have it relay to my "real" SMTP server.
This eliminates a lot of issues with Outlook locking up if it can't reach
the mail server.
I don't think the security risk is that large if you understand your goals
and what you're doing.
> Of course, if you're on SQL 2005, this is all moot...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OH33MhFpGHA.1796@.TK2MSFTNGP03.phx.gbl...
> I don't find Outlook to be a security risk, I find it to be a stability
> risk. Outlook is a lot of things, but a stable MAPI service provider
isn't
> on that list.
Just for the record, while I tend to agree, see my other email.
The BEST thing I ever did for Outlook was to put a local SMTP server on the
SQL box and set it up to relay only from that box to my main SMTP server.
This has GREATLY increased my stability. (to the point I really don't have
to think about SQL Mail at all. It pretty much just works.)
> I prefer to use xp_smtpmail from www.sqldev.net. It isn't a
> drop-in replacement for SQLMail or SQLAgentMail, but you can make it do
most
> of the tasks that xp_sendmail supports. I usually add extra steps for
> failure and success notification to my agent jobs, but there are several
> ways to implement this code. It is a very stable add-in and has caused me
> zero problems, even on large cluster installations.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Bob" <Bob@.discussions.microsoft.com> wrote in message
> news:3A2B8DAB-9424-4E86-9C53-C8BD6E0B1206@.microsoft.com...
> >I just took over a new project and trying to setup the environment up to
> >best
> > practicing standards. I wanted to install MS Outlook to setup MAPI. My
> > manager thinks installing outlook on production server is really nuts.
He
> > thinks it's a security risk and overall having MS Outlook on a
production
> > server doesn't seem right. I have never heard of any kind of security
risk
> > or
> > any other internal problems MS Outlook can create in a production box
with
> > SQL Server installed on it. Can one of the MVPs please confirm it for me
> > and
> > if possible give any suggestions or arguments that I can use to convince
> > him?
> > Thanks in advance for your support ...
> >
> > Bob
>

IS install after SP1 fails

Subject says it all; I need to install IS, but the installer says v.2047 of IS is already installed; it it NOT installed. When I go to add/remove programs, under the Sql Server 2005, it allows me to try to install IS, but that also fails, as no components are found for installation. This is SS dev edition, W2003.

I can uninstall SS2005 and start over, but is there a quicker way to fix this?

I don't think this is a known issue. If time to solution is your top priority, probably uninstall/reinstall is the way to go. Otherwise, post links to both the RTM Setup logfiles (%Program Files%\Microsoft SQL Server\90\Setup Bootstrap\Files) and the SP1 Setup logfiles (%Windir%\Hotfix) and we'll see if we can't help you figure out what's going on here.

Paul

|||

I'm kind of curious; I'm not sure which log files you need (and they are too large to post?). The hotfix.log is from April (sp1), and here is a snip:

04/25/2006 08:10:44.168 Found Report Server 2005 product definition
04/25/2006 08:10:45.371 Found DTS 2005 product definition
04/25/2006 08:10:46.871 Determining QFE level for product instance
04/25/2006 08:10:46.917 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\DTS\\Binn\DTSPipeline.dll
04/25/2006 08:10:46.933 Found following QFE level for product instance : 1399
04/25/2006 08:10:46.933 Determining GDR branching Hotfix for product instance
04/25/2006 08:10:46.949 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\DTS\\Binn\DTSPipeline.dll
04/25/2006 08:10:46.964 No GDR branch Hotfix found for product instance
04/25/2006 08:10:46.996 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
04/25/2006 08:10:47.011 Successfully read registry key: CommonFilesDir, string value = C:\Program Files\Common Files
04/25/2006 08:10:47.027 Successfully opened registry key: SOFTWARE\Microsoft\Windows\CurrentVersion
04/25/2006 08:10:47.042 Successfully read registry key: ProgramFilesDir, string value = C:\Program Files
04/25/2006 08:10:47.105 Attempting to check IA 64 platform
04/25/2006 08:10:47.121 Result of IA64 check: 0
04/25/2006 08:10:47.136 Last error: 0

And there is a good logn sqlsetyp0006_qsqlca1_support.log, note the line that says:

MSI (s) (0C:60) [07:14:04:228]: File: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Microsoft.SqlServer.DTS.UpgradeAdvisor.dll; Won't Overwrite; Won't patch; Existing file is of an equal version

logging stopped: 6/16/2006 7:14:06 ===

|||

Yes, the logs will be too big to post here. Instead, you'll need to post a link to the files.

I think this is your scenario; please correct me if I'm wrong:

1. You installed RTM, but didn't include IS in the install. [Log files for the original install will be in the %Program Files%\Microsoft SQL Server\... location]

2. You installed SP1 [Log files will be in the %Windir%\Hotfix location]

3. You attempted to add IS to the product by going to Add/Remove Programs (ARP) and selecting "Change" for the SQL Server 2005 entry. [Log files will also be in the %Program Files%\Microsoft SQL Server\... location]

Does this make sense?

|||

1. yes

2. yes

3. yes, after install of IS from media failed.

'post a link'....sorry, I don't get how to allow you to securely access an internal server?