MSDE installation problem

During installation of MSDE I get the message
"The instance name specified is invalid"
Any ideas?
Thanks
Yannis
[option]
INSTANCENAME=new_instance_name
and check out the MSSQL$new_instance_name service is started.
personal point, don't to use the MSDE if you won't get trouble in the
released time.
"Yannis Makarounis" <Yannis.Makarounis@.ace-hellas.gr> wrote in message
news:egtqiw50EHA.1740@.TK2MSFTNGP15.phx.gbl...
> During installation of MSDE I get the message
> "The instance name specified is invalid"
> Any ideas?
> Thanks
> Yannis
>
|||False alarm.
After customer interrogation it was revealed that SQLServer 7 was already
installed on the machine
"Yannis Makarounis" wrote:

> During installation of MSDE I get the message
> "The instance name specified is invalid"
> Any ideas?
> Thanks
> Yannis
>
>
|||Hello guys,
I'm using MSDE for several months now and I did not meet any problem. But
reading some posts, it seems that I'm a lucky guy.
Can you develop your point of view because I'm deploying now the appliaction
and I begin to worry ... :-(
Thanks
"leighsword" <leighsword@.163.net> a crit dans le message de news:
eEEmx750EHA.2620@.TK2MSFTNGP10.phx.gbl...
> [option]
> INSTANCENAME=new_instance_name
> and check out the MSSQL$new_instance_name service is started.
> personal point, don't to use the MSDE if you won't get trouble in the
> released time.
> "Yannis Makarounis" <Yannis.Makarounis@.ace-hellas.gr> wrote in message
> news:egtqiw50EHA.1740@.TK2MSFTNGP15.phx.gbl...
>
|||you should spent your time to learning how to deploying the MSDN when you
have choose on it.
nobody can always be lucky just like nobody can always be 21 years old.
Don't waste your time to worry ,did it,then waitting for the result(china
proveb told us,the road of success is depend on person,but the result of
success is only depend on God).
i just want to tell the MS, their Toys(MSDE) is not good enough.
"Serge Fournier" <safournier@.free.fr> wrote in message
news:#hNE0KU1EHA.1404@.TK2MSFTNGP11.phx.gbl...
> Hello guys,
> I'm using MSDE for several months now and I did not meet any problem. But
> reading some posts, it seems that I'm a lucky guy.
> Can you develop your point of view because I'm deploying now the
appliaction
> and I begin to worry ... :-(
> Thanks
> "leighsword" <leighsword@.163.net> a crit dans le message de news:
> eEEmx750EHA.2620@.TK2MSFTNGP10.phx.gbl...
>
|||hi leighsword,
"leighsword" <leighsword@.163.net> ha scritto nel messaggio
news:eWhjqZb1EHA.1264@.TK2MSFTNGP12.phx.gbl
> you should spent your time to learning how to deploying the MSDN when
> you have choose on it.
> nobody can always be lucky just like nobody can always be 21 years
> old. Don't waste your time to worry ,did it,then waitting for the
> result(china proveb told us,the road of success is depend on
> person,but the result of success is only depend on God).
> i just want to tell the MS, their Toys(MSDE) is not good enough.
I actually had no pain (till now :D, and hope to continue that way)
distributing MSDE using just the standard setup.exe philosophy... I just
added a visual wrapper to that command line tool in order to gather all
required information, such as log file, sapwd, instance name, security mode,
target dir and so on, shelling then to the real installer, setup.exe, and
providing all parameters and had no problem at all... perhaps I was that
lucky becouse all machines I installed on meet the SQL Server requirements,
the OSs were updated, the OS's configuration was in order (File ad Printer
sharing was set, the Server service was running) and so on... personally I
never install MSDE as part of my own applications... a separate setup is
provided as, IMHO, the Server must be the very first thing to be installed
(where and if, depending on the machine nautre, client or server machine),
then the database must be installed and, finally, the application, again,
only if it must reside on the server as well...
so 2 separate setups are provided...
1) the MSDE installer
2) the application and the database installer
you have to run the MSDE installer on the machine hosting the server...
the application installer will install the application as long as a
companion tool that takes care of installing/patching the database... and
that's all :D:D
I succesfully use this solution since MSDE 1.0 :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||we used to the separate setup method too in client.
use the Director MX of MciroMedia to makes a great animation UI, like
following step.
__________________________________
/ \
| big title in here |
| 1.Install runtime library(.net framewok) |
| (icon)2.install the database enginee(MSDE). |
| (...) 3.install an application. |
\__________________________________/
we will check the MSDE is installed when install the application or install
the MSDE(3 step need the 2 step was done) using a MsdePatch.exe of our Setup
Tool.
note that i call this as Patch.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:310vodF356dhaU1@.uni-berlin.de...
> hi leighsword,
> "leighsword" <leighsword@.163.net> ha scritto nel messaggio
> news:eWhjqZb1EHA.1264@.TK2MSFTNGP12.phx.gbl
> I actually had no pain (till now :D, and hope to continue that way)
> distributing MSDE using just the standard setup.exe philosophy... I just
> added a visual wrapper to that command line tool in order to gather all
> required information, such as log file, sapwd, instance name, security
mode,
> target dir and so on, shelling then to the real installer, setup.exe, and
> providing all parameters and had no problem at all... perhaps I was that
> lucky becouse all machines I installed on meet the SQL Server
requirements,
> the OSs were updated, the OS's configuration was in order (File ad Printer
> sharing was set, the Server service was running) and so on... personally I
> never install MSDE as part of my own applications... a separate setup is
> provided as, IMHO, the Server must be the very first thing to be installed
> (where and if, depending on the machine nautre, client or server machine),
> then the database must be installed and, finally, the application, again,
> only if it must reside on the server as well...
> so 2 separate setups are provided...
> 1) the MSDE installer
> 2) the application and the database installer
> you have to run the MSDE installer on the machine hosting the server...
> the application installer will install the application as long as a
> companion tool that takes care of installing/patching the database... and
> that's all :D:D
> I succesfully use this solution since MSDE 1.0 :D
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>