MSDE Reinstall

Have reinstalled MSDE using Command Prompt Installation and received Errors.
Then I proceeded with a Batch.file installation and that seemed to work for the most part.

This is what I used for the Batch.file

setup.exe SAPWD=somename INSTANCENAME=somename SECURITYMODE=SQL

The Problem I ran into is - I can't seem to get the (SQL SERVER SERVICE MANAGER) to connect. I've entered the server name & instancename but so far no luck.

Ive checked - Control Panel/Administive Tools/Services - to make sure that it was installed & Yes it is there. So I Proceeded to start it up. Next I tried to Connect Via SERVER MANGER with no luck.
Then I did a c:\>osql -E check with the Command Line Prompt which returned the following message:

[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen <Connect<>>.

Tried again with c:\>osql -E -S
returned the same message.

[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen <Connect<>>.

Not sure what to do at this point any help/advice. Thx/TIA

(MSDE Version: sql2kdesksp3)
OS = XP ProUpdate:

Finally Managed to Connect to (SERVICE MANAGER) So now I have Connection with my server. I had to Specify ServerName\Instancename - and finally managed to connect.

But I can't seem to make a Database Connection In webMatrix. I entered The (USERName & Password Name) with no luck, even tried different combinations but still no luck!! USERNAME:Someusername**** (and) PASSWORD:SomePassword****

Is there a way I can create a New USERNAME & PASSWORD, with the command Line Prompt?
Anyone know how to do this? THX /TIS

Tristen|||view post 446484|||Thank you for Link/replying Bill,

Problem corrected. Reinstalled MSDE & Made a New SQL Authentication Password.|||Did "setup /upgradesp" help you?

MSDE install common sense issues?

MSDE installs via a batch file using Microsoft's setup.
Once installed does it really make sense to uninstall it?
What if Visio is already installed before my install, or some other product
that uses MSDE, what happens to that install when my install runs?
Would I need the sa password of the prior install?
If I install my database into the default instance? And then someone
uninstalls the original app (prior to my install) that installed MSDE. Does
the installation uninstall MSDE even though my app uses it too?
Is it safer always to make my database run in its own instance?
Regards...
j
hi Jeff,
"Jeff" <joedirt@.datahook.com> ha scritto nel messaggio
news:%23nD5tx8XEHA.3520@.TK2MSFTNGP10.phx.gbl...
> MSDE installs via a batch file using Microsoft's setup.
> Once installed does it really make sense to uninstall it?
I don't understand this question... if you install an application, does it
make sense uninstalling it?...
if you need that MSDE instance, don't uninstall it..

> What if Visio is already installed before my install, or some other
product
> that uses MSDE, what happens to that install when my install runs?
I don't know if Visio install a separate MSDE instance (my Visio
installation did not) .. but you can install up to 16 different instances of
MSDE.. ok that number is quite prohibitive as regard resources, as you never
will have or desire 16 running instances of MSDE on the same box..
but if you have a "particular" instance you don't want to share with other
applications, than you can install a private instance for that app and using
a "common" instance for all other databases...

> Would I need the sa password of the prior install?
as long as that instance is up, you need it...

> If I install my database into the default instance? And then someone
> uninstalls the original app (prior to my install) that installed MSDE.
Does
> the installation uninstall MSDE even though my app uses it too?
this must be asked to the ISV providing that MSDE instance... as per MSDE
original EULA it shoul'd be that way, but now MSDE is free, and each
instance can be a shared one, as long as the ISV providing it does not
specify it's reserved for his/her app(s)

> Is it safer always to make my database run in its own instance?
it really depends... personally I do not, I only have separate instances for
test under different service pack levels, but on production servers I always
ask the end user before installing if he/se needs a separate named instance
when an existing MSDE/SQL Server instance is detected..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply