I have been looking at SC.exe from the resource kit to query sql server
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.
Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.
Showing posts with label exe. Show all posts
Showing posts with label exe. Show all posts
Sunday, February 12, 2012
Command line qeury of service
I have been looking at SC.exe from the resource kit to query sql server
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.
Command line qeury of service
I have been looking at SC.exe from the resource kit to query sql server
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.
services from command line. Anyone have any recommendations other than this
to do so.
I was looking to query all my sql servers to check services and output to a
file.Russ,
How about VBScript and WMI? Or VBScript and SQL-DMO?
HTH
Jerry
"RussN" <RussN@.discussions.microsoft.com> wrote in message
news:EEA1A919-672C-441F-8F4D-9838F67650FE@.microsoft.com...
>I have been looking at SC.exe from the resource kit to query sql server
> services from command line. Anyone have any recommendations other than
> this
> to do so.
> I was looking to query all my sql servers to check services and output to
> a
> file.
Command Line Parameters to msiexec
I am trying to pass command line parameters to msiexec for installing
msde2000.
Line is :
"c:\windows\system32\msiexec.exe" /settings "D:\develop\servis\setup.ini" /i
"e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /L*v
"D:\develop\servis\MSDE_setup.log"
It does not accept /settings "D:\develop\servis\setup.ini" part.
Any idea?
Hi,
The /Settings is the parameter of MSDE's setup and not msiexec.
From the syntax that you have sent, it seems as you are providing /settings
as the syntax for msiexec instead of the msde's setup.
Try to run the MSDE setup using the following syntax
"e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
"D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
Below is the msde's parameter list with its description.
================================================== ==========================
==========================================
Syntax
setup [/?]
[
[ /i package_file
[ /settings ini_file ]
| [ [ ALLOWXDBCHAINING=1 ]
[ BLANKSAPWD=1 ]
[ CALLBACK=Dllname!CallbackFunctionName ]
[ COLLATION="collation_name" ]
[ DATADIR="data_folder_path" ]
[ DISABLENETWORKPROTOCOLS=n ]
[ INSTANCENAME="instance_name" ]
[ SAPWD="sa_password" ]
[ SECURITYMODE=SQL ]
[ TARGETDIR="executable_folder_path" ]
[ UPGRADE=1 ]
[ UPGRADEUSER=admin_login ]
[ UPGRADEPWD=admin_password ]
]
]
[ /L*v [filename] ]
[ /upgradesp { SQLRUN
| <MSIPath>SQLRunnn.msi }
]
[ /qn | /qb ]
[ /x package_name ]
]
Arguments
/?
Displays a syntax summary of the setup options.
Important Because setup displays more options than it accepts, use only
the options documented in this topic.
/i package_file
Specifies the name of the Windows Installer installation package file (an
.msi file) to be used to install an instance of the Microsoft SQL Server
2000 Desktop Engine (MSDE 2000). The package file specified must be one of
the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
\MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe. If
/i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
folder on the SQL Server 2000 compact disc to the folder in which Setup.exe
is located.
For SP3 or later, the preferred approach is to specify the INSTANCENAME
parameter instead of the /i option. If all of the .msi package files are
present, then Setup will dynamically select which package file to use for
the installation. If neither /i nor INSTANCENAME are specified, Setup will
dynamically select the package file and install a default instance.
Caution It is possible to overwrite an instance by mistake. You must check
for instances that are already present, including instances installed by
other vendors' software.
/settings ini_file_name
Specifies the name of an .ini file containing settings for the Setup
parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified, these
parameters should be set in the .ini file, not on the command prompt. Place
the .ini file in the folder where Setup.exe is located.
ALLOWXDBCHAINING=1
In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
behavior of the Installer and enables cross database ownership chains for
the instance. For more information about cross database chaining, see Cross
DB Ownership Chaining. You should not use this parameter unless you are
running an application that requires cross database ownership chains.
BLANKSAPWD=1
Overrides the Installer's default behavior, which is to require that you
specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
assigns a null password to the sa login
Security Note Assigning a null, blank, simple, or well-known password to
the sa login can allow unauthorized people access to your data.
CALLBACK=Dllname!CallbackFunctionName
Specifies the name of the DLL containing the Desktop Engine Windows
Installer callback function, and the name of the callback function. For
more information, see Windows Installer Callback Functions for Desktop
Engine.
COLLATION="collation_name"
Specifies the SQL Server collation that will be used as the default
collation for this instance of the Desktop Engine. For information about
collation names, see Windows Collation Name and SQL Collation Name.
DATADIR="data_folder_path"
Specifies the folder where the SQL Server system databases are built.
Assuming that the system default for program files is C:\Program Files:
The default value for default instances is: C:\Program Files\Microsoft SQL
Server\MSSQL\Data\.
The default value for named instances is C:\Program Files\Microsoft SQL
Server\MSSQL$<instance_name>\Data\, where instance_name is the name
specified in the INSTANCENAME option.
The file path for this parameter must end with a backslash (\). When
installing a default instance, setup appends mssql\data to the end of the
path specified in DATADIR. When installing a named instance, setup appends
mssql$<instance_name>\data, where instance_name is the value specified in
the INSTANCENAME option.
Setup builds two other folders at the same location as the Data folder, a
Log folder for the database engine error logs, and an Install folder
containing installation scripts.
Note Settings that contain spaces should be enclosed with quotation marks.
DISABLENETWORKPROTOCOLS=n
In SQL Server 2000 SP3 or later, specifies how the Installer configures the
network protocol support for the instance of the Desktop Engine being
installed or upgraded. n is an integer number, and should be set to either
0 or 1.
These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
Value Specified for n Upgrading Existing Instance Installing New Instance
1 Instance is configured with all server Net-Libraries disabled. Instance
is configured with all server Net-Libraries disabled.
0 The existing server Net-Library configuration is retained. Instance is
configured with default server Net-Libraries and addresses enabled.
Parameter not specified, or is any value other than 0 or 1 The existing
server Net-Library configuration is retained. Instance is configured with
all server Net-Libraries disabled.
In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared to
SP3a:
When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
either not specified or set to a value other than 0 or 1, then the instance
is installed with the default Net-Libraries and addresses enabled. In SP3a,
the Net-Libraries are disabled.
Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
the instance will still use User Datagram Protocol (UDP) port 1434. In
SP3a, the instance will not use UDP port 1434 in that configuration. For
more information, see Controlling Net-Libraries and Communications
Addresses.
INSTANCENAME="instance_name"
Specifies the name for the instance. If no instance name is specified, the
instance is installed as a default instance.
SAPWD="sa_password"
Specifies the password to be assigned to the sa login when installing a new
instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
instance of MSDE 2000, so you should ensure the sa login has a strong
password before upgrading. You should always specify a strong sa password,
even when using Windows Authentication Mode. While the SAPWD parameter is
not written to the installation log file when running Setup.exe, it is if
you install using merge modules.
SECURITYMODE=SQL
Specifies that the instance be configured in Mixed Mode, where the instance
supports both SQL Server Authentication and Windows Authentication
connections.
In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
specified, the instance will be configured in Windows Authentication Mode.
The instance will only support Windows Authentication connections, and the
Windows local administrator's group will be added to the SQL Server
sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
instance in Mixed Mode.
Security Note When possible, use Windows Authentication.
In Microsoft Windows 98 or Windows ME, the instance is always configured to
use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
these operating systems, MSDE 2000 can only support SQL Server
Authentication connections.
TARGETDIR="executable_folder_path"
Specifies the folder where the Desktop Engine executable files are to be
installed. Assuming that your system default for program files is
C:\Program Files:
The default value for default instances is: C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\.
The default value for named instances is: C:\Program Files\Microsoft SQL
Server\MSSQL$<instance_name>\Binn\ for named instances, where instance_name
is the name specified in the INSTANCENAME option.
The file path for this parameter must end with a backslash (\). When
installing a default instance, setup appends mssql\binn to the end of the
path specified in TARGETDIR. When installing a named instance, setup
appends mssql$<instance_name>\binn.
Note Settings that contain spaces should be enclosed with quotation marks.
UPGRADE=1
Specifies that Desktop Engine Setup or Windows Installer is upgrading an
instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
same fashion as a default instance of MSDE 2000, and is always upgraded to
a default instance of MSDE 2000.
UPGRADEUSER=admin_login
Specifies the login to be used when you upgrade an instance of either MSDE
1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
member of the sysadmin fixed server role. This parameter is only used when
you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
UPGRADEPWD=admin_password
Specifies the password for the login specified in UPGRADEUSER when you
upgrade Desktop Engine using SQL Server Authentication.
/L*v [filename]
Specifies that a verbose log be created. If filename is specified, the log
is stored in the file specified.
/upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
Specifies that Setup will upgrade an existing instance of MSDE 2000. For
SP3 and later, this option replaces the /p option supported by earlier
versions of Setup. Do not use the /p option with SP3 or later. When
upgrading to SP3 or later, you are no longer required to specify the .msi
file used to install the existing instance of MSDE 2000.
Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
setup utility determines which .msi file to use. When you specify SQLRUN
without specifying an INSTANCENAME, Setup will upgrade the default instance
of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
upgrade the instance you specified using the INSTANCENAME parameter.
When you specify the name of an MSDE 2000 .msi installation package file,
Setup will upgrade whichever instance on the computer was originally
installed with a merge module of the same name. For example, if you specify
SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
originally installed using SqlRun01.msi. MSIPath is the path to the folder
holding the .msi file. MSIPath defaults to Setup\.
/qn
Specifies that Setup run with no user interface.
/qb
Specifies that Setup show only the basic user interface. Only dialog boxes
displaying progress information are displayed. Other dialog boxes, such as
the dialog box that asks users whether they want to restart at the end of
the setup process, are not displayed.
If neither /qn nor /qb is specified, Setup displays all user interface
dialog boxes.
/x package_name
Specifies the name of the Windows Installer installation package file (an
.msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
Engine. You must specify the name of the same installation package file
that was used to install the instance of the Desktop Engine. Place the .msi
file in the same folder as Setup.exe.
================================================== ==========================
==========================================
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||In windows 98 it says : invalid command or file name
In windows 2003 it says : invalid command line parameters.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:lXiEhehZEHA.2804@.cpmsftngxa06.phx.gbl...
> Hi,
> The /Settings is the parameter of MSDE's setup and not msiexec.
> From the syntax that you have sent, it seems as you are providing
/settings
> as the syntax for msiexec instead of the msde's setup.
> Try to run the MSDE setup using the following syntax
>
> "e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
> "D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
>
> Below is the msde's parameter list with its description.
>
================================================== ==========================
> ==========================================
> Syntax
> setup [/?]
> [
> [ /i package_file
> [ /settings ini_file ]
> | [ [ ALLOWXDBCHAINING=1 ]
> [ BLANKSAPWD=1 ]
> [ CALLBACK=Dllname!CallbackFunctionName ]
> [ COLLATION="collation_name" ]
> [ DATADIR="data_folder_path" ]
> [ DISABLENETWORKPROTOCOLS=n ]
> [ INSTANCENAME="instance_name" ]
> [ SAPWD="sa_password" ]
> [ SECURITYMODE=SQL ]
> [ TARGETDIR="executable_folder_path" ]
> [ UPGRADE=1 ]
> [ UPGRADEUSER=admin_login ]
> [ UPGRADEPWD=admin_password ]
> ]
> ]
> [ /L*v [filename] ]
> [ /upgradesp { SQLRUN
> | <MSIPath>SQLRunnn.msi }
> ]
> [ /qn | /qb ]
> [ /x package_name ]
> ]
> Arguments
> /?
> Displays a syntax summary of the setup options.
>
> Important Because setup displays more options than it accepts, use only
> the options documented in this topic.
>
> /i package_file
> Specifies the name of the Windows Installer installation package file (an
> msi file) to be used to install an instance of the Microsoft SQL ServerT
> 2000 Desktop Engine (MSDE 2000). The package file specified must be one of
> the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
> \MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe.
If
> /i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
> folder on the SQL Server 2000 compact disc to the folder in which
Setup.exe
> is located.
> For SP3 or later, the preferred approach is to specify the INSTANCENAME
> parameter instead of the /i option. If all of the .msi package files are
> present, then Setup will dynamically select which package file to use for
> the installation. If neither /i nor INSTANCENAME are specified, Setup will
> dynamically select the package file and install a default instance.
>
> Caution It is possible to overwrite an instance by mistake. You must
check
> for instances that are already present, including instances installed by
> other vendors' software.
>
> /settings ini_file_name
> Specifies the name of an .ini file containing settings for the Setup
> parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
> INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified,
these
> parameters should be set in the .ini file, not on the command prompt.
Place
> the .ini file in the folder where Setup.exe is located.
> ALLOWXDBCHAINING=1
> In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
> behavior of the Installer and enables cross database ownership chains for
> the instance. For more information about cross database chaining, see
Cross
> DB Ownership Chaining. You should not use this parameter unless you are
> running an application that requires cross database ownership chains.
> BLANKSAPWD=1
> Overrides the Installer's default behavior, which is to require that you
> specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
> assigns a null password to the sa login
>
> Security Note Assigning a null, blank, simple, or well-known password to
> the sa login can allow unauthorized people access to your data.
>
> CALLBACK=Dllname!CallbackFunctionName
> Specifies the name of the DLL containing the Desktop Engine Windows
> Installer callback function, and the name of the callback function. For
> more information, see Windows Installer Callback Functions for Desktop
> Engine.
> COLLATION="collation_name"
> Specifies the SQL Server collation that will be used as the default
> collation for this instance of the Desktop Engine. For information about
> collation names, see Windows Collation Name and SQL Collation Name.
> DATADIR="data_folder_path"
> Specifies the folder where the SQL Server system databases are built.
> Assuming that the system default for program files is C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data\.
>
> The default value for named instances is C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Data\, where instance_name is the name
> specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\data to the end of the
> path specified in DATADIR. When installing a named instance, setup appends
> mssql$<instance_name>\data, where instance_name is the value specified in
> the INSTANCENAME option.
> Setup builds two other folders at the same location as the Data folder, a
> Log folder for the database engine error logs, and an Install folder
> containing installation scripts.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> DISABLENETWORKPROTOCOLS=n
> In SQL Server 2000 SP3 or later, specifies how the Installer configures
the
> network protocol support for the instance of the Desktop Engine being
> installed or upgraded. n is an integer number, and should be set to either
> 0 or 1.
> These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
> Value Specified for n Upgrading Existing Instance Installing New Instance
> 1 Instance is configured with all server Net-Libraries disabled. Instance
> is configured with all server Net-Libraries disabled.
> 0 The existing server Net-Library configuration is retained. Instance is
> configured with default server Net-Libraries and addresses enabled.
> Parameter not specified, or is any value other than 0 or 1 The existing
> server Net-Library configuration is retained. Instance is configured with
> all server Net-Libraries disabled.
>
> In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared
to
> SP3a:
> When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
> either not specified or set to a value other than 0 or 1, then the
instance
> is installed with the default Net-Libraries and addresses enabled. In
SP3a,
> the Net-Libraries are disabled.
>
> Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
> the instance will still use User Datagram Protocol (UDP) port 1434. In
> SP3a, the instance will not use UDP port 1434 in that configuration. For
> more information, see Controlling Net-Libraries and Communications
> Addresses.
> INSTANCENAME="instance_name"
> Specifies the name for the instance. If no instance name is specified, the
> instance is installed as a default instance.
> SAPWD="sa_password"
> Specifies the password to be assigned to the sa login when installing a
new
> instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
> instance of MSDE 2000, so you should ensure the sa login has a strong
> password before upgrading. You should always specify a strong sa password,
> even when using Windows Authentication Mode. While the SAPWD parameter is
> not written to the installation log file when running Setup.exe, it is if
> you install using merge modules.
> SECURITYMODE=SQL
> Specifies that the instance be configured in Mixed Mode, where the
instance
> supports both SQL Server Authentication and Windows Authentication
> connections.
> In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
> specified, the instance will be configured in Windows Authentication Mode.
> The instance will only support Windows Authentication connections, and the
> Windows local administrator's group will be added to the SQL Server
> sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
> instance in Mixed Mode.
>
> Security Note When possible, use Windows Authentication.
>
> In Microsoft Windows 98 or Windows ME, the instance is always configured
to
> use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
> these operating systems, MSDE 2000 can only support SQL Server
> Authentication connections.
> TARGETDIR="executable_folder_path"
> Specifies the folder where the Desktop Engine executable files are to be
> installed. Assuming that your system default for program files is
> C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\.
>
> The default value for named instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Binn\ for named instances, where
instance_name
> is the name specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\binn to the end of the
> path specified in TARGETDIR. When installing a named instance, setup
> appends mssql$<instance_name>\binn.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> UPGRADE=1
> Specifies that Desktop Engine Setup or Windows Installer is upgrading an
> instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
> Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
> same fashion as a default instance of MSDE 2000, and is always upgraded to
> a default instance of MSDE 2000.
> UPGRADEUSER=admin_login
> Specifies the login to be used when you upgrade an instance of either MSDE
> 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
> member of the sysadmin fixed server role. This parameter is only used when
> you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
> UPGRADEPWD=admin_password
> Specifies the password for the login specified in UPGRADEUSER when you
> upgrade Desktop Engine using SQL Server Authentication.
> /L*v [filename]
> Specifies that a verbose log be created. If filename is specified, the log
> is stored in the file specified.
> /upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
> Specifies that Setup will upgrade an existing instance of MSDE 2000. For
> SP3 and later, this option replaces the /p option supported by earlier
> versions of Setup. Do not use the /p option with SP3 or later. When
> upgrading to SP3 or later, you are no longer required to specify the .msi
> file used to install the existing instance of MSDE 2000.
> Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
> setup utility determines which .msi file to use. When you specify SQLRUN
> without specifying an INSTANCENAME, Setup will upgrade the default
instance
> of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
> upgrade the instance you specified using the INSTANCENAME parameter.
> When you specify the name of an MSDE 2000 .msi installation package file,
> Setup will upgrade whichever instance on the computer was originally
> installed with a merge module of the same name. For example, if you
specify
> SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
> originally installed using SqlRun01.msi. MSIPath is the path to the folder
> holding the .msi file. MSIPath defaults to Setup\.
> /qn
> Specifies that Setup run with no user interface.
> /qb
> Specifies that Setup show only the basic user interface. Only dialog boxes
> displaying progress information are displayed. Other dialog boxes, such as
> the dialog box that asks users whether they want to restart at the end of
> the setup process, are not displayed.
> If neither /qn nor /qb is specified, Setup displays all user interface
> dialog boxes.
> /x package_name
> Specifies the name of the Windows Installer installation package file (an
> msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
> Engine. You must specify the name of the same installation package file
> that was used to install the instance of the Desktop Engine. Place the
..msi
> file in the same folder as Setup.exe.
>
>
================================================== ==========================
> ==========================================
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||"F:\mcd\msde2000\setup.exe" /settings "D:\develop\Servis\setup.ini" /i
"F:\mcd\msde2000\SETUP\SQLRUN01.MSI" /L*v "D:\develop\Servis\MSDE_setup.log"
/wait
But above line reallt works fine.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:lXiEhehZEHA.2804@.cpmsftngxa06.phx.gbl...
> Hi,
> The /Settings is the parameter of MSDE's setup and not msiexec.
> From the syntax that you have sent, it seems as you are providing
/settings
> as the syntax for msiexec instead of the msde's setup.
> Try to run the MSDE setup using the following syntax
>
> "e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
> "D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
>
> Below is the msde's parameter list with its description.
>
================================================== ==========================
> ==========================================
> Syntax
> setup [/?]
> [
> [ /i package_file
> [ /settings ini_file ]
> | [ [ ALLOWXDBCHAINING=1 ]
> [ BLANKSAPWD=1 ]
> [ CALLBACK=Dllname!CallbackFunctionName ]
> [ COLLATION="collation_name" ]
> [ DATADIR="data_folder_path" ]
> [ DISABLENETWORKPROTOCOLS=n ]
> [ INSTANCENAME="instance_name" ]
> [ SAPWD="sa_password" ]
> [ SECURITYMODE=SQL ]
> [ TARGETDIR="executable_folder_path" ]
> [ UPGRADE=1 ]
> [ UPGRADEUSER=admin_login ]
> [ UPGRADEPWD=admin_password ]
> ]
> ]
> [ /L*v [filename] ]
> [ /upgradesp { SQLRUN
> | <MSIPath>SQLRunnn.msi }
> ]
> [ /qn | /qb ]
> [ /x package_name ]
> ]
> Arguments
> /?
> Displays a syntax summary of the setup options.
>
> Important Because setup displays more options than it accepts, use only
> the options documented in this topic.
>
> /i package_file
> Specifies the name of the Windows Installer installation package file (an
> msi file) to be used to install an instance of the Microsoft SQL ServerT
> 2000 Desktop Engine (MSDE 2000). The package file specified must be one of
> the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
> \MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe.
If
> /i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
> folder on the SQL Server 2000 compact disc to the folder in which
Setup.exe
> is located.
> For SP3 or later, the preferred approach is to specify the INSTANCENAME
> parameter instead of the /i option. If all of the .msi package files are
> present, then Setup will dynamically select which package file to use for
> the installation. If neither /i nor INSTANCENAME are specified, Setup will
> dynamically select the package file and install a default instance.
>
> Caution It is possible to overwrite an instance by mistake. You must
check
> for instances that are already present, including instances installed by
> other vendors' software.
>
> /settings ini_file_name
> Specifies the name of an .ini file containing settings for the Setup
> parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
> INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified,
these
> parameters should be set in the .ini file, not on the command prompt.
Place
> the .ini file in the folder where Setup.exe is located.
> ALLOWXDBCHAINING=1
> In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
> behavior of the Installer and enables cross database ownership chains for
> the instance. For more information about cross database chaining, see
Cross
> DB Ownership Chaining. You should not use this parameter unless you are
> running an application that requires cross database ownership chains.
> BLANKSAPWD=1
> Overrides the Installer's default behavior, which is to require that you
> specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
> assigns a null password to the sa login
>
> Security Note Assigning a null, blank, simple, or well-known password to
> the sa login can allow unauthorized people access to your data.
>
> CALLBACK=Dllname!CallbackFunctionName
> Specifies the name of the DLL containing the Desktop Engine Windows
> Installer callback function, and the name of the callback function. For
> more information, see Windows Installer Callback Functions for Desktop
> Engine.
> COLLATION="collation_name"
> Specifies the SQL Server collation that will be used as the default
> collation for this instance of the Desktop Engine. For information about
> collation names, see Windows Collation Name and SQL Collation Name.
> DATADIR="data_folder_path"
> Specifies the folder where the SQL Server system databases are built.
> Assuming that the system default for program files is C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data\.
>
> The default value for named instances is C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Data\, where instance_name is the name
> specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\data to the end of the
> path specified in DATADIR. When installing a named instance, setup appends
> mssql$<instance_name>\data, where instance_name is the value specified in
> the INSTANCENAME option.
> Setup builds two other folders at the same location as the Data folder, a
> Log folder for the database engine error logs, and an Install folder
> containing installation scripts.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> DISABLENETWORKPROTOCOLS=n
> In SQL Server 2000 SP3 or later, specifies how the Installer configures
the
> network protocol support for the instance of the Desktop Engine being
> installed or upgraded. n is an integer number, and should be set to either
> 0 or 1.
> These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
> Value Specified for n Upgrading Existing Instance Installing New Instance
> 1 Instance is configured with all server Net-Libraries disabled. Instance
> is configured with all server Net-Libraries disabled.
> 0 The existing server Net-Library configuration is retained. Instance is
> configured with default server Net-Libraries and addresses enabled.
> Parameter not specified, or is any value other than 0 or 1 The existing
> server Net-Library configuration is retained. Instance is configured with
> all server Net-Libraries disabled.
>
> In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared
to
> SP3a:
> When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
> either not specified or set to a value other than 0 or 1, then the
instance
> is installed with the default Net-Libraries and addresses enabled. In
SP3a,
> the Net-Libraries are disabled.
>
> Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
> the instance will still use User Datagram Protocol (UDP) port 1434. In
> SP3a, the instance will not use UDP port 1434 in that configuration. For
> more information, see Controlling Net-Libraries and Communications
> Addresses.
> INSTANCENAME="instance_name"
> Specifies the name for the instance. If no instance name is specified, the
> instance is installed as a default instance.
> SAPWD="sa_password"
> Specifies the password to be assigned to the sa login when installing a
new
> instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
> instance of MSDE 2000, so you should ensure the sa login has a strong
> password before upgrading. You should always specify a strong sa password,
> even when using Windows Authentication Mode. While the SAPWD parameter is
> not written to the installation log file when running Setup.exe, it is if
> you install using merge modules.
> SECURITYMODE=SQL
> Specifies that the instance be configured in Mixed Mode, where the
instance
> supports both SQL Server Authentication and Windows Authentication
> connections.
> In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
> specified, the instance will be configured in Windows Authentication Mode.
> The instance will only support Windows Authentication connections, and the
> Windows local administrator's group will be added to the SQL Server
> sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
> instance in Mixed Mode.
>
> Security Note When possible, use Windows Authentication.
>
> In Microsoft Windows 98 or Windows ME, the instance is always configured
to
> use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
> these operating systems, MSDE 2000 can only support SQL Server
> Authentication connections.
> TARGETDIR="executable_folder_path"
> Specifies the folder where the Desktop Engine executable files are to be
> installed. Assuming that your system default for program files is
> C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\.
>
> The default value for named instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Binn\ for named instances, where
instance_name
> is the name specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\binn to the end of the
> path specified in TARGETDIR. When installing a named instance, setup
> appends mssql$<instance_name>\binn.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> UPGRADE=1
> Specifies that Desktop Engine Setup or Windows Installer is upgrading an
> instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
> Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
> same fashion as a default instance of MSDE 2000, and is always upgraded to
> a default instance of MSDE 2000.
> UPGRADEUSER=admin_login
> Specifies the login to be used when you upgrade an instance of either MSDE
> 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
> member of the sysadmin fixed server role. This parameter is only used when
> you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
> UPGRADEPWD=admin_password
> Specifies the password for the login specified in UPGRADEUSER when you
> upgrade Desktop Engine using SQL Server Authentication.
> /L*v [filename]
> Specifies that a verbose log be created. If filename is specified, the log
> is stored in the file specified.
> /upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
> Specifies that Setup will upgrade an existing instance of MSDE 2000. For
> SP3 and later, this option replaces the /p option supported by earlier
> versions of Setup. Do not use the /p option with SP3 or later. When
> upgrading to SP3 or later, you are no longer required to specify the .msi
> file used to install the existing instance of MSDE 2000.
> Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
> setup utility determines which .msi file to use. When you specify SQLRUN
> without specifying an INSTANCENAME, Setup will upgrade the default
instance
> of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
> upgrade the instance you specified using the INSTANCENAME parameter.
> When you specify the name of an MSDE 2000 .msi installation package file,
> Setup will upgrade whichever instance on the computer was originally
> installed with a merge module of the same name. For example, if you
specify
> SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
> originally installed using SqlRun01.msi. MSIPath is the path to the folder
> holding the .msi file. MSIPath defaults to Setup\.
> /qn
> Specifies that Setup run with no user interface.
> /qb
> Specifies that Setup show only the basic user interface. Only dialog boxes
> displaying progress information are displayed. Other dialog boxes, such as
> the dialog box that asks users whether they want to restart at the end of
> the setup process, are not displayed.
> If neither /qn nor /qb is specified, Setup displays all user interface
> dialog boxes.
> /x package_name
> Specifies the name of the Windows Installer installation package file (an
> msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
> Engine. You must specify the name of the same installation package file
> that was used to install the instance of the Desktop Engine. Place the
..msi
> file in the same folder as Setup.exe.
>
>
================================================== ==========================
> ==========================================
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||Hi,
"F:\mcd\msde2000\setup.exe" /settings "D:\develop\Servis\setup.ini" /i
"F:\mcd\msde2000\SETUP\SQLRUN01.MSI" /L*v "D:\develop\Servis\MSDE_setup.log"
/wait
These lines work, because you are providing parameters to the setup and not
to the MSIEXEC file.
MSIEXEC and setup.exe are two independent softwares.
The /Settings is a parameter of Setup.exe
For parameter information on MSIEXEC please visit,
http://msdn.microsoft.com/library/de...us/msi/setup/c
ommand_line_options.asp
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
msde2000.
Line is :
"c:\windows\system32\msiexec.exe" /settings "D:\develop\servis\setup.ini" /i
"e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /L*v
"D:\develop\servis\MSDE_setup.log"
It does not accept /settings "D:\develop\servis\setup.ini" part.
Any idea?
Hi,
The /Settings is the parameter of MSDE's setup and not msiexec.
From the syntax that you have sent, it seems as you are providing /settings
as the syntax for msiexec instead of the msde's setup.
Try to run the MSDE setup using the following syntax
"e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
"D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
Below is the msde's parameter list with its description.
================================================== ==========================
==========================================
Syntax
setup [/?]
[
[ /i package_file
[ /settings ini_file ]
| [ [ ALLOWXDBCHAINING=1 ]
[ BLANKSAPWD=1 ]
[ CALLBACK=Dllname!CallbackFunctionName ]
[ COLLATION="collation_name" ]
[ DATADIR="data_folder_path" ]
[ DISABLENETWORKPROTOCOLS=n ]
[ INSTANCENAME="instance_name" ]
[ SAPWD="sa_password" ]
[ SECURITYMODE=SQL ]
[ TARGETDIR="executable_folder_path" ]
[ UPGRADE=1 ]
[ UPGRADEUSER=admin_login ]
[ UPGRADEPWD=admin_password ]
]
]
[ /L*v [filename] ]
[ /upgradesp { SQLRUN
| <MSIPath>SQLRunnn.msi }
]
[ /qn | /qb ]
[ /x package_name ]
]
Arguments
/?
Displays a syntax summary of the setup options.
Important Because setup displays more options than it accepts, use only
the options documented in this topic.
/i package_file
Specifies the name of the Windows Installer installation package file (an
.msi file) to be used to install an instance of the Microsoft SQL Server
2000 Desktop Engine (MSDE 2000). The package file specified must be one of
the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
\MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe. If
/i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
folder on the SQL Server 2000 compact disc to the folder in which Setup.exe
is located.
For SP3 or later, the preferred approach is to specify the INSTANCENAME
parameter instead of the /i option. If all of the .msi package files are
present, then Setup will dynamically select which package file to use for
the installation. If neither /i nor INSTANCENAME are specified, Setup will
dynamically select the package file and install a default instance.
Caution It is possible to overwrite an instance by mistake. You must check
for instances that are already present, including instances installed by
other vendors' software.
/settings ini_file_name
Specifies the name of an .ini file containing settings for the Setup
parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified, these
parameters should be set in the .ini file, not on the command prompt. Place
the .ini file in the folder where Setup.exe is located.
ALLOWXDBCHAINING=1
In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
behavior of the Installer and enables cross database ownership chains for
the instance. For more information about cross database chaining, see Cross
DB Ownership Chaining. You should not use this parameter unless you are
running an application that requires cross database ownership chains.
BLANKSAPWD=1
Overrides the Installer's default behavior, which is to require that you
specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
assigns a null password to the sa login
Security Note Assigning a null, blank, simple, or well-known password to
the sa login can allow unauthorized people access to your data.
CALLBACK=Dllname!CallbackFunctionName
Specifies the name of the DLL containing the Desktop Engine Windows
Installer callback function, and the name of the callback function. For
more information, see Windows Installer Callback Functions for Desktop
Engine.
COLLATION="collation_name"
Specifies the SQL Server collation that will be used as the default
collation for this instance of the Desktop Engine. For information about
collation names, see Windows Collation Name and SQL Collation Name.
DATADIR="data_folder_path"
Specifies the folder where the SQL Server system databases are built.
Assuming that the system default for program files is C:\Program Files:
The default value for default instances is: C:\Program Files\Microsoft SQL
Server\MSSQL\Data\.
The default value for named instances is C:\Program Files\Microsoft SQL
Server\MSSQL$<instance_name>\Data\, where instance_name is the name
specified in the INSTANCENAME option.
The file path for this parameter must end with a backslash (\). When
installing a default instance, setup appends mssql\data to the end of the
path specified in DATADIR. When installing a named instance, setup appends
mssql$<instance_name>\data, where instance_name is the value specified in
the INSTANCENAME option.
Setup builds two other folders at the same location as the Data folder, a
Log folder for the database engine error logs, and an Install folder
containing installation scripts.
Note Settings that contain spaces should be enclosed with quotation marks.
DISABLENETWORKPROTOCOLS=n
In SQL Server 2000 SP3 or later, specifies how the Installer configures the
network protocol support for the instance of the Desktop Engine being
installed or upgraded. n is an integer number, and should be set to either
0 or 1.
These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
Value Specified for n Upgrading Existing Instance Installing New Instance
1 Instance is configured with all server Net-Libraries disabled. Instance
is configured with all server Net-Libraries disabled.
0 The existing server Net-Library configuration is retained. Instance is
configured with default server Net-Libraries and addresses enabled.
Parameter not specified, or is any value other than 0 or 1 The existing
server Net-Library configuration is retained. Instance is configured with
all server Net-Libraries disabled.
In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared to
SP3a:
When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
either not specified or set to a value other than 0 or 1, then the instance
is installed with the default Net-Libraries and addresses enabled. In SP3a,
the Net-Libraries are disabled.
Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
the instance will still use User Datagram Protocol (UDP) port 1434. In
SP3a, the instance will not use UDP port 1434 in that configuration. For
more information, see Controlling Net-Libraries and Communications
Addresses.
INSTANCENAME="instance_name"
Specifies the name for the instance. If no instance name is specified, the
instance is installed as a default instance.
SAPWD="sa_password"
Specifies the password to be assigned to the sa login when installing a new
instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
instance of MSDE 2000, so you should ensure the sa login has a strong
password before upgrading. You should always specify a strong sa password,
even when using Windows Authentication Mode. While the SAPWD parameter is
not written to the installation log file when running Setup.exe, it is if
you install using merge modules.
SECURITYMODE=SQL
Specifies that the instance be configured in Mixed Mode, where the instance
supports both SQL Server Authentication and Windows Authentication
connections.
In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
specified, the instance will be configured in Windows Authentication Mode.
The instance will only support Windows Authentication connections, and the
Windows local administrator's group will be added to the SQL Server
sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
instance in Mixed Mode.
Security Note When possible, use Windows Authentication.
In Microsoft Windows 98 or Windows ME, the instance is always configured to
use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
these operating systems, MSDE 2000 can only support SQL Server
Authentication connections.
TARGETDIR="executable_folder_path"
Specifies the folder where the Desktop Engine executable files are to be
installed. Assuming that your system default for program files is
C:\Program Files:
The default value for default instances is: C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\.
The default value for named instances is: C:\Program Files\Microsoft SQL
Server\MSSQL$<instance_name>\Binn\ for named instances, where instance_name
is the name specified in the INSTANCENAME option.
The file path for this parameter must end with a backslash (\). When
installing a default instance, setup appends mssql\binn to the end of the
path specified in TARGETDIR. When installing a named instance, setup
appends mssql$<instance_name>\binn.
Note Settings that contain spaces should be enclosed with quotation marks.
UPGRADE=1
Specifies that Desktop Engine Setup or Windows Installer is upgrading an
instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
same fashion as a default instance of MSDE 2000, and is always upgraded to
a default instance of MSDE 2000.
UPGRADEUSER=admin_login
Specifies the login to be used when you upgrade an instance of either MSDE
1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
member of the sysadmin fixed server role. This parameter is only used when
you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
UPGRADEPWD=admin_password
Specifies the password for the login specified in UPGRADEUSER when you
upgrade Desktop Engine using SQL Server Authentication.
/L*v [filename]
Specifies that a verbose log be created. If filename is specified, the log
is stored in the file specified.
/upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
Specifies that Setup will upgrade an existing instance of MSDE 2000. For
SP3 and later, this option replaces the /p option supported by earlier
versions of Setup. Do not use the /p option with SP3 or later. When
upgrading to SP3 or later, you are no longer required to specify the .msi
file used to install the existing instance of MSDE 2000.
Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
setup utility determines which .msi file to use. When you specify SQLRUN
without specifying an INSTANCENAME, Setup will upgrade the default instance
of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
upgrade the instance you specified using the INSTANCENAME parameter.
When you specify the name of an MSDE 2000 .msi installation package file,
Setup will upgrade whichever instance on the computer was originally
installed with a merge module of the same name. For example, if you specify
SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
originally installed using SqlRun01.msi. MSIPath is the path to the folder
holding the .msi file. MSIPath defaults to Setup\.
/qn
Specifies that Setup run with no user interface.
/qb
Specifies that Setup show only the basic user interface. Only dialog boxes
displaying progress information are displayed. Other dialog boxes, such as
the dialog box that asks users whether they want to restart at the end of
the setup process, are not displayed.
If neither /qn nor /qb is specified, Setup displays all user interface
dialog boxes.
/x package_name
Specifies the name of the Windows Installer installation package file (an
.msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
Engine. You must specify the name of the same installation package file
that was used to install the instance of the Desktop Engine. Place the .msi
file in the same folder as Setup.exe.
================================================== ==========================
==========================================
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
|||In windows 98 it says : invalid command or file name
In windows 2003 it says : invalid command line parameters.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:lXiEhehZEHA.2804@.cpmsftngxa06.phx.gbl...
> Hi,
> The /Settings is the parameter of MSDE's setup and not msiexec.
> From the syntax that you have sent, it seems as you are providing
/settings
> as the syntax for msiexec instead of the msde's setup.
> Try to run the MSDE setup using the following syntax
>
> "e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
> "D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
>
> Below is the msde's parameter list with its description.
>
================================================== ==========================
> ==========================================
> Syntax
> setup [/?]
> [
> [ /i package_file
> [ /settings ini_file ]
> | [ [ ALLOWXDBCHAINING=1 ]
> [ BLANKSAPWD=1 ]
> [ CALLBACK=Dllname!CallbackFunctionName ]
> [ COLLATION="collation_name" ]
> [ DATADIR="data_folder_path" ]
> [ DISABLENETWORKPROTOCOLS=n ]
> [ INSTANCENAME="instance_name" ]
> [ SAPWD="sa_password" ]
> [ SECURITYMODE=SQL ]
> [ TARGETDIR="executable_folder_path" ]
> [ UPGRADE=1 ]
> [ UPGRADEUSER=admin_login ]
> [ UPGRADEPWD=admin_password ]
> ]
> ]
> [ /L*v [filename] ]
> [ /upgradesp { SQLRUN
> | <MSIPath>SQLRunnn.msi }
> ]
> [ /qn | /qb ]
> [ /x package_name ]
> ]
> Arguments
> /?
> Displays a syntax summary of the setup options.
>
> Important Because setup displays more options than it accepts, use only
> the options documented in this topic.
>
> /i package_file
> Specifies the name of the Windows Installer installation package file (an
> msi file) to be used to install an instance of the Microsoft SQL ServerT
> 2000 Desktop Engine (MSDE 2000). The package file specified must be one of
> the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
> \MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe.
If
> /i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
> folder on the SQL Server 2000 compact disc to the folder in which
Setup.exe
> is located.
> For SP3 or later, the preferred approach is to specify the INSTANCENAME
> parameter instead of the /i option. If all of the .msi package files are
> present, then Setup will dynamically select which package file to use for
> the installation. If neither /i nor INSTANCENAME are specified, Setup will
> dynamically select the package file and install a default instance.
>
> Caution It is possible to overwrite an instance by mistake. You must
check
> for instances that are already present, including instances installed by
> other vendors' software.
>
> /settings ini_file_name
> Specifies the name of an .ini file containing settings for the Setup
> parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
> INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified,
these
> parameters should be set in the .ini file, not on the command prompt.
Place
> the .ini file in the folder where Setup.exe is located.
> ALLOWXDBCHAINING=1
> In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
> behavior of the Installer and enables cross database ownership chains for
> the instance. For more information about cross database chaining, see
Cross
> DB Ownership Chaining. You should not use this parameter unless you are
> running an application that requires cross database ownership chains.
> BLANKSAPWD=1
> Overrides the Installer's default behavior, which is to require that you
> specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
> assigns a null password to the sa login
>
> Security Note Assigning a null, blank, simple, or well-known password to
> the sa login can allow unauthorized people access to your data.
>
> CALLBACK=Dllname!CallbackFunctionName
> Specifies the name of the DLL containing the Desktop Engine Windows
> Installer callback function, and the name of the callback function. For
> more information, see Windows Installer Callback Functions for Desktop
> Engine.
> COLLATION="collation_name"
> Specifies the SQL Server collation that will be used as the default
> collation for this instance of the Desktop Engine. For information about
> collation names, see Windows Collation Name and SQL Collation Name.
> DATADIR="data_folder_path"
> Specifies the folder where the SQL Server system databases are built.
> Assuming that the system default for program files is C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data\.
>
> The default value for named instances is C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Data\, where instance_name is the name
> specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\data to the end of the
> path specified in DATADIR. When installing a named instance, setup appends
> mssql$<instance_name>\data, where instance_name is the value specified in
> the INSTANCENAME option.
> Setup builds two other folders at the same location as the Data folder, a
> Log folder for the database engine error logs, and an Install folder
> containing installation scripts.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> DISABLENETWORKPROTOCOLS=n
> In SQL Server 2000 SP3 or later, specifies how the Installer configures
the
> network protocol support for the instance of the Desktop Engine being
> installed or upgraded. n is an integer number, and should be set to either
> 0 or 1.
> These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
> Value Specified for n Upgrading Existing Instance Installing New Instance
> 1 Instance is configured with all server Net-Libraries disabled. Instance
> is configured with all server Net-Libraries disabled.
> 0 The existing server Net-Library configuration is retained. Instance is
> configured with default server Net-Libraries and addresses enabled.
> Parameter not specified, or is any value other than 0 or 1 The existing
> server Net-Library configuration is retained. Instance is configured with
> all server Net-Libraries disabled.
>
> In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared
to
> SP3a:
> When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
> either not specified or set to a value other than 0 or 1, then the
instance
> is installed with the default Net-Libraries and addresses enabled. In
SP3a,
> the Net-Libraries are disabled.
>
> Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
> the instance will still use User Datagram Protocol (UDP) port 1434. In
> SP3a, the instance will not use UDP port 1434 in that configuration. For
> more information, see Controlling Net-Libraries and Communications
> Addresses.
> INSTANCENAME="instance_name"
> Specifies the name for the instance. If no instance name is specified, the
> instance is installed as a default instance.
> SAPWD="sa_password"
> Specifies the password to be assigned to the sa login when installing a
new
> instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
> instance of MSDE 2000, so you should ensure the sa login has a strong
> password before upgrading. You should always specify a strong sa password,
> even when using Windows Authentication Mode. While the SAPWD parameter is
> not written to the installation log file when running Setup.exe, it is if
> you install using merge modules.
> SECURITYMODE=SQL
> Specifies that the instance be configured in Mixed Mode, where the
instance
> supports both SQL Server Authentication and Windows Authentication
> connections.
> In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
> specified, the instance will be configured in Windows Authentication Mode.
> The instance will only support Windows Authentication connections, and the
> Windows local administrator's group will be added to the SQL Server
> sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
> instance in Mixed Mode.
>
> Security Note When possible, use Windows Authentication.
>
> In Microsoft Windows 98 or Windows ME, the instance is always configured
to
> use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
> these operating systems, MSDE 2000 can only support SQL Server
> Authentication connections.
> TARGETDIR="executable_folder_path"
> Specifies the folder where the Desktop Engine executable files are to be
> installed. Assuming that your system default for program files is
> C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\.
>
> The default value for named instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Binn\ for named instances, where
instance_name
> is the name specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\binn to the end of the
> path specified in TARGETDIR. When installing a named instance, setup
> appends mssql$<instance_name>\binn.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> UPGRADE=1
> Specifies that Desktop Engine Setup or Windows Installer is upgrading an
> instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
> Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
> same fashion as a default instance of MSDE 2000, and is always upgraded to
> a default instance of MSDE 2000.
> UPGRADEUSER=admin_login
> Specifies the login to be used when you upgrade an instance of either MSDE
> 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
> member of the sysadmin fixed server role. This parameter is only used when
> you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
> UPGRADEPWD=admin_password
> Specifies the password for the login specified in UPGRADEUSER when you
> upgrade Desktop Engine using SQL Server Authentication.
> /L*v [filename]
> Specifies that a verbose log be created. If filename is specified, the log
> is stored in the file specified.
> /upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
> Specifies that Setup will upgrade an existing instance of MSDE 2000. For
> SP3 and later, this option replaces the /p option supported by earlier
> versions of Setup. Do not use the /p option with SP3 or later. When
> upgrading to SP3 or later, you are no longer required to specify the .msi
> file used to install the existing instance of MSDE 2000.
> Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
> setup utility determines which .msi file to use. When you specify SQLRUN
> without specifying an INSTANCENAME, Setup will upgrade the default
instance
> of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
> upgrade the instance you specified using the INSTANCENAME parameter.
> When you specify the name of an MSDE 2000 .msi installation package file,
> Setup will upgrade whichever instance on the computer was originally
> installed with a merge module of the same name. For example, if you
specify
> SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
> originally installed using SqlRun01.msi. MSIPath is the path to the folder
> holding the .msi file. MSIPath defaults to Setup\.
> /qn
> Specifies that Setup run with no user interface.
> /qb
> Specifies that Setup show only the basic user interface. Only dialog boxes
> displaying progress information are displayed. Other dialog boxes, such as
> the dialog box that asks users whether they want to restart at the end of
> the setup process, are not displayed.
> If neither /qn nor /qb is specified, Setup displays all user interface
> dialog boxes.
> /x package_name
> Specifies the name of the Windows Installer installation package file (an
> msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
> Engine. You must specify the name of the same installation package file
> that was used to install the instance of the Desktop Engine. Place the
..msi
> file in the same folder as Setup.exe.
>
>
================================================== ==========================
> ==========================================
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||"F:\mcd\msde2000\setup.exe" /settings "D:\develop\Servis\setup.ini" /i
"F:\mcd\msde2000\SETUP\SQLRUN01.MSI" /L*v "D:\develop\Servis\MSDE_setup.log"
/wait
But above line reallt works fine.
"Ashish Ruparel [MSFT]" <v-ashrup@.online.microsoft.com> wrote in message
news:lXiEhehZEHA.2804@.cpmsftngxa06.phx.gbl...
> Hi,
> The /Settings is the parameter of MSDE's setup and not msiexec.
> From the syntax that you have sent, it seems as you are providing
/settings
> as the syntax for msiexec instead of the msde's setup.
> Try to run the MSDE setup using the following syntax
>
> "e:\msde2000setup\installdir\SETUP\SQLRUN01.MS I" /settings
> "D:\develop\servis\setup.ini" /i /L*v "D:\develop\servis\MSDE_setup.log"
>
> Below is the msde's parameter list with its description.
>
================================================== ==========================
> ==========================================
> Syntax
> setup [/?]
> [
> [ /i package_file
> [ /settings ini_file ]
> | [ [ ALLOWXDBCHAINING=1 ]
> [ BLANKSAPWD=1 ]
> [ CALLBACK=Dllname!CallbackFunctionName ]
> [ COLLATION="collation_name" ]
> [ DATADIR="data_folder_path" ]
> [ DISABLENETWORKPROTOCOLS=n ]
> [ INSTANCENAME="instance_name" ]
> [ SAPWD="sa_password" ]
> [ SECURITYMODE=SQL ]
> [ TARGETDIR="executable_folder_path" ]
> [ UPGRADE=1 ]
> [ UPGRADEUSER=admin_login ]
> [ UPGRADEPWD=admin_password ]
> ]
> ]
> [ /L*v [filename] ]
> [ /upgradesp { SQLRUN
> | <MSIPath>SQLRunnn.msi }
> ]
> [ /qn | /qb ]
> [ /x package_name ]
> ]
> Arguments
> /?
> Displays a syntax summary of the setup options.
>
> Important Because setup displays more options than it accepts, use only
> the options documented in this topic.
>
> /i package_file
> Specifies the name of the Windows Installer installation package file (an
> msi file) to be used to install an instance of the Microsoft SQL ServerT
> 2000 Desktop Engine (MSDE 2000). The package file specified must be one of
> the .msi files (Sqlrun01.msi through Sqlrun16.msi) distributed in the
> \MSDE\Setup folder. Place the .msi file in the same folder as Setup.exe.
If
> /i is not specified, copy all 16 of the .msi files from the \MSDE\Setup
> folder on the SQL Server 2000 compact disc to the folder in which
Setup.exe
> is located.
> For SP3 or later, the preferred approach is to specify the INSTANCENAME
> parameter instead of the /i option. If all of the .msi package files are
> present, then Setup will dynamically select which package file to use for
> the installation. If neither /i nor INSTANCENAME are specified, Setup will
> dynamically select the package file and install a default instance.
>
> Caution It is possible to overwrite an instance by mistake. You must
check
> for instances that are already present, including instances installed by
> other vendors' software.
>
> /settings ini_file_name
> Specifies the name of an .ini file containing settings for the Setup
> parameters ALLOWXDBCHAINING, DISABLENETWORKPROTOCOLS, TARGETDIR, DATADIR,
> INSTANCENAME, COLLATION, and SECURITYMODE. If /settings is specified,
these
> parameters should be set in the .ini file, not on the command prompt.
Place
> the .ini file in the folder where Setup.exe is located.
> ALLOWXDBCHAINING=1
> In SQL Server 2000 Service Pack 3 (SP3) or later, overrides the default
> behavior of the Installer and enables cross database ownership chains for
> the instance. For more information about cross database chaining, see
Cross
> DB Ownership Chaining. You should not use this parameter unless you are
> running an application that requires cross database ownership chains.
> BLANKSAPWD=1
> Overrides the Installer's default behavior, which is to require that you
> specify a strong sa password. If you specify BLANKSAPWD=1, the Installer
> assigns a null password to the sa login
>
> Security Note Assigning a null, blank, simple, or well-known password to
> the sa login can allow unauthorized people access to your data.
>
> CALLBACK=Dllname!CallbackFunctionName
> Specifies the name of the DLL containing the Desktop Engine Windows
> Installer callback function, and the name of the callback function. For
> more information, see Windows Installer Callback Functions for Desktop
> Engine.
> COLLATION="collation_name"
> Specifies the SQL Server collation that will be used as the default
> collation for this instance of the Desktop Engine. For information about
> collation names, see Windows Collation Name and SQL Collation Name.
> DATADIR="data_folder_path"
> Specifies the folder where the SQL Server system databases are built.
> Assuming that the system default for program files is C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Data\.
>
> The default value for named instances is C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Data\, where instance_name is the name
> specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\data to the end of the
> path specified in DATADIR. When installing a named instance, setup appends
> mssql$<instance_name>\data, where instance_name is the value specified in
> the INSTANCENAME option.
> Setup builds two other folders at the same location as the Data folder, a
> Log folder for the database engine error logs, and an Install folder
> containing installation scripts.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> DISABLENETWORKPROTOCOLS=n
> In SQL Server 2000 SP3 or later, specifies how the Installer configures
the
> network protocol support for the instance of the Desktop Engine being
> installed or upgraded. n is an integer number, and should be set to either
> 0 or 1.
> These are the behaviors of DISABLNETWORKPROTOCOLS in SP3a or later:
> Value Specified for n Upgrading Existing Instance Installing New Instance
> 1 Instance is configured with all server Net-Libraries disabled. Instance
> is configured with all server Net-Libraries disabled.
> 0 The existing server Net-Library configuration is retained. Instance is
> configured with default server Net-Libraries and addresses enabled.
> Parameter not specified, or is any value other than 0 or 1 The existing
> server Net-Library configuration is retained. Instance is configured with
> all server Net-Libraries disabled.
>
> In SP3, DISABLENETWORKPROTOCOLS has two differences in behavior compared
to
> SP3a:
> When installing a new instance using SP3, and DISABLENETWORKPROTOCOLS is
> either not specified or set to a value other than 0 or 1, then the
instance
> is installed with the default Net-Libraries and addresses enabled. In
SP3a,
> the Net-Libraries are disabled.
>
> Whenever all Net-Libraries are disabled for an instance of MSDE 2000 SP3,
> the instance will still use User Datagram Protocol (UDP) port 1434. In
> SP3a, the instance will not use UDP port 1434 in that configuration. For
> more information, see Controlling Net-Libraries and Communications
> Addresses.
> INSTANCENAME="instance_name"
> Specifies the name for the instance. If no instance name is specified, the
> instance is installed as a default instance.
> SAPWD="sa_password"
> Specifies the password to be assigned to the sa login when installing a
new
> instance of MSDE 2000. SAPWD is ignored when you upgrade an existing
> instance of MSDE 2000, so you should ensure the sa login has a strong
> password before upgrading. You should always specify a strong sa password,
> even when using Windows Authentication Mode. While the SAPWD parameter is
> not written to the installation log file when running Setup.exe, it is if
> you install using merge modules.
> SECURITYMODE=SQL
> Specifies that the instance be configured in Mixed Mode, where the
instance
> supports both SQL Server Authentication and Windows Authentication
> connections.
> In Microsoft Windows NT 4.0 or Windows 2000, if SECURITYMODE=SQL is not
> specified, the instance will be configured in Windows Authentication Mode.
> The instance will only support Windows Authentication connections, and the
> Windows local administrator's group will be added to the SQL Server
> sysadmin role. If SECURITYMODE=SQL is specified, Setup configures the
> instance in Mixed Mode.
>
> Security Note When possible, use Windows Authentication.
>
> In Microsoft Windows 98 or Windows ME, the instance is always configured
to
> use Mixed Mode, regardless of whether SECURITYMODE=SQL is specified. On
> these operating systems, MSDE 2000 can only support SQL Server
> Authentication connections.
> TARGETDIR="executable_folder_path"
> Specifies the folder where the Desktop Engine executable files are to be
> installed. Assuming that your system default for program files is
> C:\Program Files:
> The default value for default instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL\Binn\.
>
> The default value for named instances is: C:\Program Files\Microsoft SQL
> Server\MSSQL$<instance_name>\Binn\ for named instances, where
instance_name
> is the name specified in the INSTANCENAME option.
> The file path for this parameter must end with a backslash (\). When
> installing a default instance, setup appends mssql\binn to the end of the
> path specified in TARGETDIR. When installing a named instance, setup
> appends mssql$<instance_name>\binn.
>
> Note Settings that contain spaces should be enclosed with quotation
marks.
>
> UPGRADE=1
> Specifies that Desktop Engine Setup or Windows Installer is upgrading an
> instance of Microsoft Desktop Engine (MSDE) version 1.0 to SQL Server 2000
> Desktop Engine. The only value supported is 1. MSDE 1.0 operates in the
> same fashion as a default instance of MSDE 2000, and is always upgraded to
> a default instance of MSDE 2000.
> UPGRADEUSER=admin_login
> Specifies the login to be used when you upgrade an instance of either MSDE
> 1.0 or MSDE 2000 using SQL Server Authentication. The login must be a
> member of the sysadmin fixed server role. This parameter is only used when
> you specify SECURITYMODE=SQL when upgrading an instance of MSDE.
> UPGRADEPWD=admin_password
> Specifies the password for the login specified in UPGRADEUSER when you
> upgrade Desktop Engine using SQL Server Authentication.
> /L*v [filename]
> Specifies that a verbose log be created. If filename is specified, the log
> is stored in the file specified.
> /upgradesp { SQLRUN | <MSIPath>SQLRunnn.msi }
> Specifies that Setup will upgrade an existing instance of MSDE 2000. For
> SP3 and later, this option replaces the /p option supported by earlier
> versions of Setup. Do not use the /p option with SP3 or later. When
> upgrading to SP3 or later, you are no longer required to specify the .msi
> file used to install the existing instance of MSDE 2000.
> Many users simply specify SQLRUN, in which case the MSDE 2000 SP3 or later
> setup utility determines which .msi file to use. When you specify SQLRUN
> without specifying an INSTANCENAME, Setup will upgrade the default
instance
> of MSDE 2000. If you specify both SQLRUN and an INSTANCENAME, Setup will
> upgrade the instance you specified using the INSTANCENAME parameter.
> When you specify the name of an MSDE 2000 .msi installation package file,
> Setup will upgrade whichever instance on the computer was originally
> installed with a merge module of the same name. For example, if you
specify
> SqlRun01.msi, Setup will upgrade whichever instance of MSDE 2000 was
> originally installed using SqlRun01.msi. MSIPath is the path to the folder
> holding the .msi file. MSIPath defaults to Setup\.
> /qn
> Specifies that Setup run with no user interface.
> /qb
> Specifies that Setup show only the basic user interface. Only dialog boxes
> displaying progress information are displayed. Other dialog boxes, such as
> the dialog box that asks users whether they want to restart at the end of
> the setup process, are not displayed.
> If neither /qn nor /qb is specified, Setup displays all user interface
> dialog boxes.
> /x package_name
> Specifies the name of the Windows Installer installation package file (an
> msi file) to use when uninstalling an instance of SQL Server 2000 Desktop
> Engine. You must specify the name of the same installation package file
> that was used to install the instance of the Desktop Engine. Place the
..msi
> file in the same folder as Setup.exe.
>
>
================================================== ==========================
> ==========================================
>
> HTH
> Ashish
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
|||Hi,
"F:\mcd\msde2000\setup.exe" /settings "D:\develop\Servis\setup.ini" /i
"F:\mcd\msde2000\SETUP\SQLRUN01.MSI" /L*v "D:\develop\Servis\MSDE_setup.log"
/wait
These lines work, because you are providing parameters to the setup and not
to the MSIEXEC file.
MSIEXEC and setup.exe are two independent softwares.
The /Settings is a parameter of Setup.exe
For parameter information on MSIEXEC please visit,
http://msdn.microsoft.com/library/de...us/msi/setup/c
ommand_line_options.asp
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, February 10, 2012
Comclust.exe Windows 2003 Server
From what I have read you do have to apply COMCLUST.exe to
a Windows 2003 Server on a cluster server with SQL Server
2000 Enterprise?
If this is not correct, I have already loaded Windows 2003
Server on a cluster with SQL Server 2000 Enterprise.
How would I correct this problem?
Thanks,
Mark P.
Hi
Look at
http://www.microsoft.com/technet/pro.../newclust.mspx
"
MSDTC Configuration
The Microsoft Distributed Transaction Coordinator (MSDTC) can now be
configured once, and then be replicated to all nodes.
Benefits
? Easier Administration In previous versions, the COMCLUST.EXE utility had
to be run on each node in order to cluster the MSDTC. It is now possible to
configure MSDTC as a resource type, assign it to a resource group, and have
it automatically configured on all cluster nodes.
"
Regards
Mike
"Mark P." wrote:
> From what I have read you do have to apply COMCLUST.exe to
> a Windows 2003 Server on a cluster server with SQL Server
> 2000 Enterprise?
> If this is not correct, I have already loaded Windows 2003
> Server on a cluster with SQL Server 2000 Enterprise.
> How would I correct this problem?
> Thanks,
> Mark P.
>
|||Hi Mark,
You wrote " From what I have read you do have to apply COMCLUST.exe to a Windows 2003 Server on a cluster server with SQL Server 2000 Enterprise?"
I would be curious to know where it was written that we need to run comclust.exe on Win2003 cluster. It is true for Windows 2000 cluster and not for 2003.
Here are some Microsoft KB articles that has information for MSDTC on Windows 2003
How to Configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 Cluster
http://support.microsoft.com/?id=301600
How to enable Network DTC access in Windows Server 2003
http://support.microsoft.com/?kbid=817064
You wrote "If this is not correct, I have already loaded Windows 2003 Server on a cluster with SQL Server 2000 Enterprise. How would I correct this problem?"
You DO NOT need to configure MSDTC as a clustered resource for SQL Server 2000 cluster to work. You need MSDTC only if you are doing distributed transactions.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
a Windows 2003 Server on a cluster server with SQL Server
2000 Enterprise?
If this is not correct, I have already loaded Windows 2003
Server on a cluster with SQL Server 2000 Enterprise.
How would I correct this problem?
Thanks,
Mark P.
Hi
Look at
http://www.microsoft.com/technet/pro.../newclust.mspx
"
MSDTC Configuration
The Microsoft Distributed Transaction Coordinator (MSDTC) can now be
configured once, and then be replicated to all nodes.
Benefits
? Easier Administration In previous versions, the COMCLUST.EXE utility had
to be run on each node in order to cluster the MSDTC. It is now possible to
configure MSDTC as a resource type, assign it to a resource group, and have
it automatically configured on all cluster nodes.
"
Regards
Mike
"Mark P." wrote:
> From what I have read you do have to apply COMCLUST.exe to
> a Windows 2003 Server on a cluster server with SQL Server
> 2000 Enterprise?
> If this is not correct, I have already loaded Windows 2003
> Server on a cluster with SQL Server 2000 Enterprise.
> How would I correct this problem?
> Thanks,
> Mark P.
>
|||Hi Mark,
You wrote " From what I have read you do have to apply COMCLUST.exe to a Windows 2003 Server on a cluster server with SQL Server 2000 Enterprise?"
I would be curious to know where it was written that we need to run comclust.exe on Win2003 cluster. It is true for Windows 2000 cluster and not for 2003.
Here are some Microsoft KB articles that has information for MSDTC on Windows 2003
How to Configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 Cluster
http://support.microsoft.com/?id=301600
How to enable Network DTC access in Windows Server 2003
http://support.microsoft.com/?kbid=817064
You wrote "If this is not correct, I have already loaded Windows 2003 Server on a cluster with SQL Server 2000 Enterprise. How would I correct this problem?"
You DO NOT need to configure MSDTC as a clustered resource for SQL Server 2000 cluster to work. You need MSDTC only if you are doing distributed transactions.
HTH,
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
Subscribe to:
Posts (Atom)