Comparing dates

HI,

In my report there are two parameters,One is for StartDate and One is for enddate.Startdate must lessthan enddate.How to compare two dates in sqlserver report,and if send date is earlier than startdate how to display error message.

Thanks in advance

You can use the Parameters collection to reference the value of a parameter - Parameters!StartDate.Value. So you can compare the two dates like =IIF(Parameters!StartDate.Value > Parameters!EndDate.Value, "Error", "OK").|||

Hi,

where we have to write that iif condition.Please help me.

|||You can use the expression as the value of a textbox where you want to display the comparison result.

Comparing dates

HI,

In my report there are two parameters,One is for StartDate and One is for enddate.Startdate must lessthan enddate.How to compare two dates in sqlserver report,and if send date is earlier than startdate how to display error message.

Thanks in advance

Try this:

= IIF( CDate(First(Fields!EndDate.Value)) > CDate(First(Fields!StartDate.Value)), "ERROR!", "OK!")

compare two string in SQL Server

Hi,
I am writing a Store Procedure for Login, as following:
@.p_sUsername, @.p_sPassword are parameters
...
SELECT @.BName = B.username, @.BPW = Password FROM BENUTZER as B WHERE
username = @.p_sUsername AND Passwort = @.p_sPassword
...
but the SELECT Statement can not differ Uppercase and Lowercase, that means,
"Martin" = "martin"
Then I check explicitly:
if @.BName != @.p_sUsername
Login = 0
but this comparing works the same.
What can I do?
Thanks
Martinif you SQL Server database is not case sensitive you have to convert to to a
comparable format ,e.g. varbinary or specifiy a CASE Sensitive (CS) Collatio
n
for it:
Select 1 where 'test' = 'TEST'
GO
Select 1 where 'Test' COLLATE SQL_Latin1_General_CP1_CS_AS = 'TEST' COLLATE
SQL_Latin1_General_CP1_CS_AS
GO
Select 1 Where CAST('Test' as varbinary) = CAST('TEST' as varbinary)
Select 1 where 'test' = 'TEST'
GO
Select 1 where 'Test' COLLATE SQL_Latin1_General_CP1_CS_AS = 'TEST' COLLATE
SQL_Latin1_General_CP1_CS_AS
GO
Select 1 Where CAST('Test' as varbinary) = CAST('TEST' as varbinary)
--
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Martin" wrote:

> Hi,
> I am writing a Store Procedure for Login, as following:
> @.p_sUsername, @.p_sPassword are parameters
> ...
> SELECT @.BName = B.username, @.BPW = Password FROM BENUTZER as B WHERE
> username = @.p_sUsername AND Passwort = @.p_sPassword
> ...
> but the SELECT Statement can not differ Uppercase and Lowercase, that mean
s,
> "Martin" = "martin"
> Then I check explicitly:
> if @.BName != @.p_sUsername
> Login = 0
> but this comparing works the same.
> What can I do?
> Thanks
> Martin
>
>|||Case-sensitivity is determined by the column collation. So choose a
case-sensitive collation. For example:
ALTER TABLE benutzer
ALTER COLUMN username VARCHAR(128) COLLATE Latin1_General_CS_AS ;
David Portas
SQL Server MVP
--|||Thanks
Martin
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> schrieb im
Newsbeitrag news:1125571037.540712.199690@.g43g2000cwa.googlegroups.com...
> Case-sensitivity is determined by the column collation. So choose a
> case-sensitive collation. For example:
> ALTER TABLE benutzer
> ALTER COLUMN username VARCHAR(128) COLLATE Latin1_General_CS_AS ;
> --
> David Portas
> SQL Server MVP
> --
>|||thanks
Martin
"Jens Smeyer" <Jens@.[Remove_that][for contacting me]sqlserver2005.de>
schrieb im Newsbeitrag
news:877CE479-F0DF-4CDA-8720-A14908BFB207@.microsoft.com...
> if you SQL Server database is not case sensitive you have to convert to to
a
> comparable format ,e.g. varbinary or specifiy a CASE Sensitive (CS)
Collation
> for it:
> Select 1 where 'test' = 'TEST'
> GO
>
> Select 1 where 'Test' COLLATE SQL_Latin1_General_CP1_CS_AS = 'TEST'
COLLATE
> SQL_Latin1_General_CP1_CS_AS
> GO
> Select 1 Where CAST('Test' as varbinary) = CAST('TEST' as varbinary)
> Select 1 where 'test' = 'TEST'
> GO
>
> Select 1 where 'Test' COLLATE SQL_Latin1_General_CP1_CS_AS = 'TEST'
COLLATE
> SQL_Latin1_General_CP1_CS_AS
> GO
> Select 1 Where CAST('Test' as varbinary) = CAST('TEST' as varbinary)
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "Martin" wrote:
>
means,|||To add to the other responses, if you force a case-sensitive compare in your
SQL statement, consider also including the normal compare in your WHERE
clause. This will allow SQL Server to efficiently use indexes on those
columns and thereby improve performance.
SELECT
@.BName = B.username,
@.BPW = Password
FROM BENUTZER as B
WHERE
username COLLATE SQL_Latin1_General_CP1_CS_AS = @.p_sUsername AND
username = @.p_sUsername AND
password COLLATE SQL_Latin1_General_CP1_CS_AS = @.p_sPassword AND
Password = @.p_sPassword
Hope this helps.
Dan Guzman
SQL Server MVP
"Martin" <martinsm@.freenet.de> wrote in message
news:Okeml6trFHA.304@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I am writing a Store Procedure for Login, as following:
> @.p_sUsername, @.p_sPassword are parameters
> ...
> SELECT @.BName = B.username, @.BPW = Password FROM BENUTZER as B WHERE
> username = @.p_sUsername AND Passwort = @.p_sPassword
> ...
> but the SELECT Statement can not differ Uppercase and Lowercase, that
> means,
> "Martin" = "martin"
> Then I check explicitly:
> if @.BName != @.p_sUsername
> Login = 0
> but this comparing works the same.
> What can I do?
> Thanks
> Martin
>

Company Logo on the Parameters Bar

Hello all,
would like to know if its possible to have a company logo on the
parameters bar that appears above the report ?
Thx
BofoUnless you can figure out how to get this in the viewer CSS, not on the
built-in toolbar. You would need to build your own prompt area.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Win2003InstallIssues" <bofobofo@.yahoo.com> wrote in message
news:1107010875.797510.255770@.c13g2000cwb.googlegroups.com...
> Hello all,
> would like to know if its possible to have a company logo on the
> parameters bar that appears above the report ?
> Thx
> Bofo
>|||And how can somebody create its own prompt area?
I'm (and some others too) search since many hours for a clue on this
subject. The only things to find are that this should be done to solve
several problems. But not a piece of a hint where the information for this
can be found. - Realy incredible!!!
"Brian Welcker [MS]" wrote:
> Unless you can figure out how to get this in the viewer CSS, not on the
> built-in toolbar. You would need to build your own prompt area.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Win2003InstallIssues" <bofobofo@.yahoo.com> wrote in message
> news:1107010875.797510.255770@.c13g2000cwb.googlegroups.com...
> > Hello all,
> >
> > would like to know if its possible to have a company logo on the
> > parameters bar that appears above the report ?
> >
> > Thx
> > Bofo
> >
>
>|||So how would I be able to add company logo in the breadcrumb area?
"Brian Welcker [MS]" wrote:
> Unless you can figure out how to get this in the viewer CSS, not on the
> built-in toolbar. You would need to build your own prompt area.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Win2003InstallIssues" <bofobofo@.yahoo.com> wrote in message
> news:1107010875.797510.255770@.c13g2000cwb.googlegroups.com...
> > Hello all,
> >
> > would like to know if its possible to have a company logo on the
> > parameters bar that appears above the report ?
> >
> > Thx
> > Bofo
> >
>
>|||Dev Main wrote:
> And how can somebody create its own prompt area?
> I'm (and some others too) search since many hours for a clue on this
> subject. The only things to find are that this should be done to solve
> several problems. But not a piece of a hint where the information for
> this can be found. - Realy incredible!!!
Use a real name, go to www.codeproject.com and search for reporting
services.
I needed 3 hours to develop my own prompt area!
Maybe you have to switch back and create your reports with excel :-/
regards
Frank

CommandText

Dim MiSQL As String = "INSERT INTO tabla1(ID,Proveedor,Tipo) VALUES (@.IDCentro,@.Proveedor,@.Tipo)"
............
cm.Parameters.Add(New SqlParameter("@.IDCentro", SqlDbType.Int, 4)).Value = 15
cm.Parameters.Add(New SqlParameter("@.Proveedor", SqlDbType.NVarChar, 50)).Value = "IBM"
cm.Parameters.Add(New SqlParameter("@.Tipo", SqlDbType.TinyInt, 1)).Value = 35

Hi friens, its possible to get the string with the vaules of parameters changed?, i mean get this string in code:

INSERT INTO tabla1(ID,Proveedor,Tipo) VALUES (15,IBM,35);

I tried with CommandText but in this string are the variables and not the values...thx a lot.

No.

You can get something similiar if you you SQL Profiler, but it'll look something like:

sp_ExecuteSQL "INSERT INTO tabla1(ID,Proveedor,Tipo) VALUES (@.IDCentro,@.Proveedor,@.Tipo)",@.IDCentruo=N'15',@.Proveedor=N'IBM',@.Tipo=N'35'

Command line to pass parameters in SQL

Hi,
Do you know if any command I can use to pass parameters into reports,
generate PDF report format and drop it into a shared folder? Thanks.
ChuckYou can pass parameters ,and create PDF from a URL report request, but I do
not think you can specify a save directory
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:297FC292-95E4-408D-9E93-78C698A98AFC@.microsoft.com...
> Hi,
> Do you know if any command I can use to pass parameters into reports,
> generate PDF report format and drop it into a shared folder? Thanks.
>
> Chuck

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.

command line parameters are invalid in SQL server Agent

Hi

Microsoft confirmed that the error message "The command line parameters are invalid" issue mentioned above is a bug and has been resolved in the next "drop" of SQL Server 2005.

has this error been fixed by microsoft. Cos i still get this error!!!!!!!!!

I am also trying to run the package from command line and when i click on execute the package it runs half way and hangs. What could be the problem?.

But when i run it from my Studio and stored package it works fine!!!

Thanks,

Jas

Perhaps the command line is incorrect. You do appear to have some keys that stick on your keyboard, which could lead to typing invalid commands.

Seriously, we need some more information to help you. What command line parameters are you trying to set?

Your second issue probably needs another thread. We would need to know what the package does - what tasks execute and what it is doing when it hangs.

Donald

|||

I have created a job to execute a SSIS package located in the SSIS Package Store. When starting the job I receive an error. The history log reports:

Message
Executed as user: semaster\vagnel. The command line parameters are invalid. The step failed.

I did not write this command line it is auto generated through wizard.

This is the command line:

/SQL "\ArchiveMain" /SERVER "SE413695\AASQL2005" /WARNASERROR /MAXCONCURRENT " -1 " /CHECKPOINTING OFF

Thanks,

Jasmine

command line parameters are invalid

I have a package that let me to import data from a excel book to a Sql server data base. When I try to run this package like a step into a SQL server Job it show me the next error.

"The command line parameters are invalid. The step failed."

the "command line" looks like this

/FILE "C:\Project\Package.dtsx" /CONNECTION ConexionExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Da ta Source=;Extended Properties=""EXCEL 8.0;HDR=YES"";" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

and in my excel conexion is:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=;Extended Properties="EXCEL 8.0;HDR=YES";

When i run the "Command Line" in the "Command window" the error is more expecific

"EXCEL 8.0;HDR=YES;" is not valid

So I chanded the "Command Line" in order to run it in de command window(look the double quote in the excel properties)

/FILE "C:\Project\Package.dtsx" /CONNECTION ConexionExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Da ta Source=;Extended Properties="EXCEL 8.0;HDR=YES";" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI

then the package RUN, but when i tried to do the same thing in the

sql wizzard, it just dont work and it lost the threat from de package and the errors says this time:

Couldn't find the package

Some one who knows the answer or has any idea to helpme please?

thanks

Use in the Import/Export wizard in SQL.

Adamus

|||According to current Books Online, the double quote is the correct method to escape the quotes inside the parameter. Are you running SP1? I believe they made some changes to the parsing of command lines in SP1, so perhaps that may help.|||

I have a windows 2003 server and the SP1 is only for windows vista, I have installed this version but, i don't know if it has some thing to do with that

|||

I have found the soluction,

I you have seen the command line, the excel connection doesn't have a Data Source because it change in a bucle, I modified connection string parameter in the package in oder to recive a variable with all the connection string, then when i programming my step in the job i don't need to especified the excel connection string.

Thanks Cesar for the aswer

Command line installation of SQL Server 2005 Express with Advanced Features

Hi,

I'm trying to install SQL Express 2005 with Reporting Services using Install Shield 11.5. The command line parameters which i am using is:

/qn ADDLOCAL=SQL_Engine,SQL_Data_Files,RS_Server,RS_Web_Interface,Client_Components SECURITYMODE=SQL SAPWD=<password> DISABLENETWORKPROTOCOLS=0 RSCONFIGURATION=Default RSSQLLOCAL=1 AUTOSTART=1

It installs the SQL Server and Reporting Services. It configures (creates Virtual Directories for report server and database) but it is not initializing the Report Server.

Having done the installation when i check the Report Server Status it was running and everything seems to be OK except it wasn't initialized.

Any idea?

Thanks,

Moby.

It's been a long time since I've played around with this, but I think it is the RSCONFIGURATION command.

Here's the snippet from template.ini. It looks like the default is FilesOnly, which does not configure RS. Can you try it with the Default value and let us know if it works?

;--
; RSCONFIGURATION specifies the Reporting Services installation option.

; The installation options can be either “FilesOnly” or “Default”.
; The “FilesOnly” option will only install the files without configuring the Reporting Services.
; The “Default” option will install the files and configure the Reporting Services.
; If you specify RSCONFIGURATION=Default, you must set RSSQLLOCAL=1
; NOTE: If no option is specified the default is “FilesOnly”.
; For example:
; RSCONFIGURATION=Default
; RSCONFIGURATION=FilesOnly

Thanks,
Sam Lester (MSFT)

|||Hi,

Well i am using the Default configuration option as if you look at the parameters in my previous post. As i said before it does all configuration except initializing the server.

But now i have figured it out. Thanks for your efforts. Having installed it with the parameters used in my previous message, you need to restart the PC. Once it is restarted the server will be initialized.

Thanks,
Mubashir

Come on! Just apply the +@*?&%&? settings! :p

Hi,
No matter how many times I push the god damn "Apply" button in the report
manager (parameters section) it never Applies my changes. The page doesn't
even refresh.
Im getting quite frustrated with this problem and I can't seem to find an
hint on what could possibly be causing it.
Thx for any input on this.This is usually caused by an issues with ASP.Net not being configured
correctly. You could try running aspnet_regiis.exe -i to reinstall asp.net
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:52F48552-990B-4DC2-8A0D-487547221EBC@.microsoft.com...
> Hi,
> No matter how many times I push the god damn "Apply" button in the report
> manager (parameters section) it never Applies my changes. The page doesn't
> even refresh.
> Im getting quite frustrated with this problem and I can't seem to find an
> hint on what could possibly be causing it.
> Thx for any input on this.|||Well that is just not a risk im willing to take in a production environment
... we're due to change our servers in a few weeks so I'll just wait until
then and see if the problem disapears ... (fingers crossed :S )
"Daniel Reib (MSFT)" wrote:
> This is usually caused by an issues with ASP.Net not being configured
> correctly. You could try running aspnet_regiis.exe -i to reinstall asp.net
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Eric" <Eric@.discussions.microsoft.com> wrote in message
> news:52F48552-990B-4DC2-8A0D-487547221EBC@.microsoft.com...
> > Hi,
> >
> > No matter how many times I push the god damn "Apply" button in the report
> > manager (parameters section) it never Applies my changes. The page doesn't
> > even refresh.
> >
> > Im getting quite frustrated with this problem and I can't seem to find an
> > hint on what could possibly be causing it.
> >
> > Thx for any input on this.
>
>

comboboxes input parameter

Is it possible to configure combo box with values depending on another
combobox selection in Reporting Parameters
e.g.
Input1: a combobox with country
Input2: should dynamically display states in the selected country, which
user can select.
appreciate any pointers . thxOn Apr 19, 12:06 pm, "nkg" <x...@.yahoo.com> wrote:
> Is it possible to configure combo box with values depending on another
> combobox selection in Reporting Parameters
> e.g.
> Input1: a combobox with country
> Input2: should dynamically display states in the selected country, which
> user can select.
> appreciate any pointers . thx
Sure. What you want to do is create a dataset to use for the second
report parameter (in the Data tab, select the <New Dataset...> option
from the drop-down list to the right of Dataset) and include the usual
query as well as the place holder parameter (i.e., select States from
StateTable where Country = @.Country). Then select the 'Edit Selected
Dataset' button [...] and on the Parameters tab enter in the Name of
the parameter (in this case, @.Country) [it is case sensitive by the
way] and select the Parameter that @.Country should be dependent on
(most likely, something like: Parameters!Country.Value). hope this
helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||thx. a lot that worked.
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1177009678.611966.300310@.b58g2000hsg.googlegroups.com...
> On Apr 19, 12:06 pm, "nkg" <x...@.yahoo.com> wrote:
>> Is it possible to configure combo box with values depending on another
>> combobox selection in Reporting Parameters
>> e.g.
>> Input1: a combobox with country
>> Input2: should dynamically display states in the selected country, which
>> user can select.
>> appreciate any pointers . thx
>
> Sure. What you want to do is create a dataset to use for the second
> report parameter (in the Data tab, select the <New Dataset...> option
> from the drop-down list to the right of Dataset) and include the usual
> query as well as the place holder parameter (i.e., select States from
> StateTable where Country = @.Country). Then select the 'Edit Selected
> Dataset' button [...] and on the Parameters tab enter in the Name of
> the parameter (in this case, @.Country) [it is case sensitive by the
> way] and select the Parameter that @.Country should be dependent on
> (most likely, something like: Parameters!Country.Value). hope this
> helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Apr 20, 2:45 pm, "nkg" <x...@.yahoo.com> wrote:
> thx. a lot that worked."EMartinez" <emartinez...@.gmail.com> wrote in message
> news:1177009678.611966.300310@.b58g2000hsg.googlegroups.com...
> > On Apr 19, 12:06 pm, "nkg" <x...@.yahoo.com> wrote:
> >> Is it possible to configure combo box with values depending on another
> >> combobox selection in Reporting Parameters
> >> e.g.
> >> Input1: a combobox with country
> >> Input2: should dynamically display states in the selected country, which
> >> user can select.
> >> appreciate any pointers . thx
> > Sure. What you want to do is create a dataset to use for the second
> > report parameter (in the Data tab, select the <New Dataset...> option
> > from the drop-down list to the right of Dataset) and include the usual
> > query as well as the place holder parameter (i.e., select States from
> > StateTable where Country = @.Country). Then select the 'Edit Selected
> > Dataset' button [...] and on the Parameters tab enter in the Name of
> > the parameter (in this case, @.Country) [it is case sensitive by the
> > way] and select the Parameter that @.Country should be dependent on
> > (most likely, something like: Parameters!Country.Value). hope this
> > helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
You're welcome. Glad I could be of assistance.
Regards,
Enrique Martinez
Sr. Software Consultant