MSDE and Enterprise Manager Trouble

I have installed an MSDE instance on my PC. I have used both the setup.exe program and installed MSDE with the merge modules. Everything works fine - I am able to programmatically connect to the database and execute all of my statements. However, when I t
ry to register the database with Enterprise Manager, Enterprise Manager doesn't see the instance. Similarly, my program that uses SQLDMO.DLL to enumerate all servers does not see the MSDE instance. Both the database, my program, and Enterprise Manager are
running locally on the same machine.
This is a development box, and I have had to uninstall MSDE by hand several times by removing registry keys manually. I suspect that my problem is that I have deleted a key that I needed. Does anyone have any clues? Thanks in advance.
Rob Reagan
MSDE with Sp3a or MSDE Release A installs by default without network
connections enabled and will not advertise itself on the network. You can
still register the instance in Enterprise Manager by typing the name in the
textbox during registration.
You can install MSDE with network connections, see the "Customizing Desktop
Engine Setup.exe" topic in Books Online for details. You can also enable
network connections after installation with (I think) svrnetcn.exe in the
Tools\Bin directory, but I have no MSDe instance to check that at the
moment.
Jacco Schalkwijk
SQL Server MVP
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:AEC24187-ADA9-48D1-ADC3-837FEE031CEB@.microsoft.com...
> I have installed an MSDE instance on my PC. I have used both the setup.exe
program and installed MSDE with the merge modules. Everything works fine - I
am able to programmatically connect to the database and execute all of my
statements. However, when I try to register the database with Enterprise
Manager, Enterprise Manager doesn't see the instance. Similarly, my program
that uses SQLDMO.DLL to enumerate all servers does not see the MSDE
instance. Both the database, my program, and Enterprise Manager are running
locally on the same machine.
> This is a development box, and I have had to uninstall MSDE by hand
several times by removing registry keys manually. I suspect that my problem
is that I have deleted a key that I needed. Does anyone have any clues?
Thanks in advance.
> Rob Reagan

MSDE 2000 Install - setup.ini

I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS

My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.

The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'

Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?

Being new to installing MSDE, are there any other parameters I have missed?

Ian

p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set upSolved the problem myself.
With Service Pack 3, msde has added a new parameter to the install = DISABLENETWORKPROTOCOLS. This parameter is defaulted to 1 which blocks remote access to the database. By adding the parameter with a value of 0 to the setup.ini file I can now connect from remote.
Ian

Originally posted by Ian Grant
I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS

My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.

The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'

Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?

Being new to installing MSDE, are there any other parameters I have missed?

Ian

p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set up

msde 2000 and sql server

Hi group!
I am developing an application using MSDE 2000.
I made a Setup.exe by using Installshield tool.
in Installshield I add the msde2000.msm with named
instance. so msde2000 will be installed to the end client
machine.
my question is if the end client machine has SQL server
(for example version 2000, 7.5, 6.0), after my installtion
the sql server in end client machine is still OK?
I found the msde installtion will install dll file to
C:\Program Files\Microsoft SQL Server\80,if end client
machine has SQL server, the msde installtion will rewrite
C:\Program Files\Microsoft SQL Server\80.
thank?
yan
Hi Yan,
I'd strongly suggest you:
1. Modify the setup.ini file to have the settings you want for MSDE and to
install it with an instance name that is unique to you. (That will avoid any
clash with an existing installation)
2. Get the end-customer to run the ms-supplied setup for the MSDE before
installing your app.
Unfortunately, there are just way too many problems with auto-installing it
at present. These will be rectified with SQL Express in the future.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"ycjj" <yan@.mcr-sol.pic.melco.co.jp> wrote in message
news:061a01c49b8f$74866590$a301280a@.phx.gbl...
> Hi group!
> I am developing an application using MSDE 2000.
> I made a Setup.exe by using Installshield tool.
> in Installshield I add the msde2000.msm with named
> instance. so msde2000 will be installed to the end client
> machine.
> my question is if the end client machine has SQL server
> (for example version 2000, 7.5, 6.0), after my installtion
> the sql server in end client machine is still OK?
> I found the msde installtion will install dll file to
> C:\Program Files\Microsoft SQL Server\80,if end client
> machine has SQL server, the msde installtion will rewrite
> C:\Program Files\Microsoft SQL Server\80.
> thank?
> yan

MSDE 2000 Analysis Services

Hi,
Is it possible to use SQL Analysis Services with MSDE 2000? I've
MSDE 2000 installed in mt m/c. When i try to install sql2kasp3.exe
after unpacking the exe, i'm getting the error "an error occurred
during the move data process:-145".
Thanks & Regards,
Kumar.MSDE doesn't come with Analysis Services. You need SQL Server Standard,
Enterprise, Evaluation or Developer Edition for Analysis Services
--
Jacco Schalkwijk
SQL Server MVP
"Senthil" <kumar.senthil@.gmail.com> wrote in message
news:4dce1b6a.0410010556.6822d11@.posting.google.com...
> Hi,
> Is it possible to use SQL Analysis Services with MSDE 2000? I've
> MSDE 2000 installed in mt m/c. When i try to install sql2kasp3.exe
> after unpacking the exe, i'm getting the error "an error occurred
> during the move data process:-145".
> Thanks & Regards,
> Kumar.|||Thanks a lot Jacco.
Regards,
Kumar.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid> wrote in message news:<#TjGPO8pEHA.3300@.TK2MSFTNGP12.phx.gbl>...
> MSDE doesn't come with Analysis Services. You need SQL Server Standard,
> Enterprise, Evaluation or Developer Edition for Analysis Services
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Senthil" <kumar.senthil@.gmail.com> wrote in message
> news:4dce1b6a.0410010556.6822d11@.posting.google.com...
> > Hi,
> > Is it possible to use SQL Analysis Services with MSDE 2000? I've
> > MSDE 2000 installed in mt m/c. When i try to install sql2kasp3.exe
> > after unpacking the exe, i'm getting the error "an error occurred
> > during the move data process:-145".
> >
> > Thanks & Regards,
> > Kumar.sql

Msde 2000

Hi folks!

Ive got here a Windows 2000 Professional PC and want to install the MSDE 2000 (incl. SP3) Desktop Server.

But when i execute the setup.exe the following Error Message will return:

http://www.dorst.de/sql.jpg

Here is the setup.ini

[Options]
TARGETDIR="C:\Programme\MSDE2000"
DATADIR="C:\Programme\MSDE2000\Daten"
SAPWD="*****"
SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0

Can anyone help?

THX !!!!!

Bye
CdRNoone knows why i cant install?|||Where did you get the the MDSE CD from? In seems that it may be corrupt.

I don't recall any internet calls during any installation I have performed. The fact that the website called s in Germany makes me wonder about the validity of the installation CD.

Be careful that it isn't corrupting your system.

Is there a reason that you are installing the German version?
("C:\Programme" as opposed to "C:\Program Files")|||The MSDE is included in a Program CD of Microsoft, but i tried to download it and install the MSDE... nothing change.

"C:\Programme" <- Thats the Standard-Programm-Dir :)

thx 4 help!

Bye

MSDE 2000

I downloaded MSDE from microsoft. When I click on Setup.exe I get this message:-

A SA password is required for security reasons. Use SAPWD switch to supply the same.

What does this mean and how can I sort it out?

Many thanks

Jim::I downloaded MSDE from microsoft. When I click on Setup.exe I get this message:-

lets see.

::A SA password is required for security reasons.

You need to provide a password for the user SA in the database. The SA user is the Administrator of the database server.

::Use SAPWD switch to supply the same.

You need to speficy this password using - a command line parameter, called a switch.|||How do I do that?

Cheers

Jim|||Look at the bottom of this page...

http://www.asp.net/msde/default.aspx?tabindex=0&tabid=1|||just run setup.exe SAPWD="passwd" in the cmd line

MSDE -> Express Upgrade problem.

Hello!

I'm trying to upgrade old MSDE instances to SQL Server 2005 Express SP1.

The following command fails:
SQLEXPR.EXE /qb UPGRADE=SQL_Engine INSTANCENAME=XXX ADDLOCAL=Client_Components,Connectivity

because the domain\x user cannot login. We have disabled Windows authentication. Is there a way to supply the SA login instead of a domain user?

Problem no #2:
After upgrading with Windows Authentication turned on, current SQL users cannot login (sa). Is Mixed authentication mode turned off during upgrade? Or what else could be the problem?

Our application is distributed around Europe. We have no control over our customers security settings/logins.
Also, the database contains sensitive data. Giving Windows Administrators access to the database is out of the question.

Kind regards

A

Check in the template.ini file that's in the high-level directory of the install media; the options are explained pretty well in there but in brief you can specify accounts, passwords, and security mode.