MSDE and Enterprise Manager?

I am a complete sql newbie! For the life of me I can't figure out how to get Enterprise Manager to connect with MSDE. Something about mixed mode or tcp/ip settings? But no one's ever really clear on how to do these things. I've uninstalled MSDE until I can get more info.

I just need a quick walk-through on how to install msde to work with EM. This is what I used when MSDE requested a strong password:

setup INSTANCENAME="InstanceName" SECURITYMODE=SQL SAPWD="AStrongSAPwd"

Is this correct? Any help would be appreciated.

Thanks.

You access it by address or servername + \ + Instance name:

Server\MSDEInstanceName

|||

What part are you having a problem with?

Tell EM to connect to the server\instancename using sql authentication login sa, password AStrongPWD.

|||If you have the full SQL Server installed then you install the MSDE as a named instance and right click at the top of the Enterprise manager of the full version to register the MSDE and you can manage it directly. If you have the MSDE installed then you install the full version as a named instance and repeat the above. I have registered 68 SQL Server 7/2000 in one XP box so if you have more questions post again. Hope this helps.|||

Thanks to everyone for their help.

I had the eval version of 2000 installed but it's expired. I would now like to use EM with MSDE to connect to the database on my website. I re-installed MSDE but it's only showing the local database.

When I try to register my online domain (ip address) it fails. Says sql may not be running. But it is running. I know it's something basic and silly I'm not doing, but I'm still very new to sql. Is there any other very basic step I may be missing?

Again, thanks for everyone's help...sorry for all the newbie questions.

|||

Which is probably correct because your SQL Server service maybe off, the developer edition is $40 in the link below but you could get it for less because when you are using hosting company you need Enterprise manager. Hope this helps.

http://www.provantage.com/buy-22053391-microsoft-backoffice-sql-server-2000-developer-edition-shopping.htm

MSDE and Enterprise Manager

If you have a machine running MSDE and you use Enterprise
Manager to connect to it, should you be able to set up
database maintenance plans that will delete expired
backups?
I'm seeing a situation where you can set up the
maintenance plan but the drop down box for the type of
period (days, weeks, etc) after which to delete expired
backups is blank.
My first thought is that there's an issue with using EM
to set up maintenance plans on MSDE.
Thanks for any assistance.
hi Charles,
"Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> If you have a machine running MSDE and you use Enterprise
> Manager to connect to it, should you be able to set up
> database maintenance plans that will delete expired
> backups?
> I'm seeing a situation where you can set up the
> maintenance plan but the drop down box for the type of
> period (days, weeks, etc) after which to delete expired
> backups is blank.
> My first thought is that there's an issue with using EM
> to set up maintenance plans on MSDE.
> Thanks for any assistance.
unfortunately, your first thought should be that you are not licensed to use
Enterprise Manager against MSDE instances, and you should rely on self based
solutions or third party tools
(http://www.microsoft.com/sql/msde/partners/default.asp or
http://www.aspfaq.com/show.asp?id=2442 , google for others)
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
|||Thanks for your message. My understanding of the licensing is you can use
Enterprise Manager IF you own a copy of SQL Server Standard or greater. If my
understanding is correct, then the issue goes back to functionality. Do you
agree?
In case you are wondering, you might use MSDE even if you have an installed
version of SQL Server if the application you are using is based on one or the
other. Great Plains, for example, knows which one you are using and has
specific licenses.
"Andrea Montanari" wrote:

> hi Charles,
> "Charles Allen" <callen@.bkd.com> ha scritto nel messaggio
> news:3d2c01c4c1ec$13e369d0$a301280a@.phx.gbl
> unfortunately, your first thought should be that you are not licensed to use
> Enterprise Manager against MSDE instances, and you should rely on self based
> solutions or third party tools
> (http://www.microsoft.com/sql/msde/partners/default.asp or
> http://www.aspfaq.com/show.asp?id=2442 , google for others)
> --
> 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
>
|||That's not quite correct. The Appropriate Uses of MSDE FAQ at
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp says the following:
Q. Can I use SQL Server tools and services in conjunction with MSDE?
A. You can only use SQL Server tools and services in conjunction with
MSDE if you acquired MSDE through SQL Server 2000 (Developer Edition,
Standard Edition, or Enterprise Edition), and if you are using MSDE in
conjunction with a properly licensed copy of SQL Server 2000. Visit the How
to Buy page for information on obtaining a valid SQL Server license.
Note: The tools and services included with SQL Server Developer
Edition may not be used to manage production server environments.
The following utilities are installed by the MSDE setup application
and are provided without restrictions for use with the copy of MSDE that is
installed by your application: bcp.exe, cnfgsvr.exe, dcomscm.exe, osql.exe,
sqlmaint.exe, sqlmangr.exe, scm.exe, sqladhlp.exe, and svrnetcn.exe. The
dtsrun.exe utility is also provided, but can only be used to run existing
Data Transformation Services (DTS) packages against the copy of MSDE
installed by your application; it cannot be used to develop new DTS
packages.
The key phrase here is "using MSDE in conjuntion with a properly licensed
copy of SQL Server 2000." Simply owning a copy of SQL Server Standard
Edition isn't enough, and you'll have to talk to your laywer to figure out
what that phrase means. All I've been told is that it doesn't apply in most
cases and requires a room full of lawyers and a white board to understand.
Rather than go through all that, you're probably better off putting Andrea's
suggestion to work and using a third-party tool.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"Charles Allen" <CharlesAllen@.discussions.microsoft.com> wrote in message
news:18142445-2FBB-43EC-9719-8751C5AC767D@.microsoft.com...[vbcol=seagreen]
> Thanks for your message. My understanding of the licensing is you can use
> Enterprise Manager IF you own a copy of SQL Server Standard or greater. If
> my
> understanding is correct, then the issue goes back to functionality. Do
> you
> agree?
> In case you are wondering, you might use MSDE even if you have an
> installed
> version of SQL Server if the application you are using is based on one or
> the
> other. Great Plains, for example, knows which one you are using and has
> specific licenses.
> "Andrea Montanari" wrote:
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end

MSDE 2000 with Access 2003: The First steps

Finally got to the point where I can connect to MSDE from Access. If you are setting up MSDE for the first time, you may find a couple useful points in the following.
MSDE 2000 with Access 2003: The First steps.
1) install MSDE from Office CD (need to locate in MSDE directory by browsing and start it manually. Read KB article 319930 first);
2) when installing, need to specify "sa" (system admin) password which is not (does not have to be anyway) the same as Windows Administrator's password. It is required in order not to leave sysadmin password blank which would leave a security hole;
3) if you are using all the correct switches with the 'setup' command, the mixed login mode will be allowed. The mixed login mode lets you login from non-admin account by using MSDE login. I did not use any switches so had to make the adjustments in the r
egistry. Very easy, but I still had to locate the required key which was not where it is supposed to be judging from KB article 319930, but quite near it.
4) restart and check that 2 new services are running: MSSQLSERVER and SQLSERVERAGENT.
5) restart the PC and log in under (Windows) administrator account (does not need to be THE "Administrator", just any account with admin privileges)
6) test the connection to MDSE by going to command line, typing "osql -E" (no " needed). You should see ">1" which means MDSE is running.
7) Now this is the $100 trick: type "sp_addlogin [BUILTIN\POWER USERS]", <ENTER>, "GO". wait for some reaction (something like 2 rows affected)
8) Here comes another $100 trick: type "grant all", <ENTER>, "to [BUILTIN\POWER USERS]", <ENTER>, "go".
Now you can go back to your every day Windows login (I assume you are using an account from Power Users group, aren't you?), start Access, create a new .adp file and connect your Access .adp file to MSDE using "Trusted Connection" or "Use Windows NT integ
rated security".
Oh by the way you can type "exit" from command line to stop your connection to MSDE when you feel like.
You can also submit commands and scripts via OSQL directly from the command
line. I thought from your previous post that you were trying to 'assign
(SQL) sysadmin permissions to a newly created (SQL) account.' I.e., your
SQL account was already created and you were trying to put it in the
sysadmin server role. By the way,
$50 Discount - GRANT grants database-specific permissions to users. So if
you have more than one Database, you need to use GRANT on all databases and
database objects you want the user to have access to.
$0.02 worth - sp_addrolemember and sp_addsrvrolemember adds users to
server-wide roles, like "sysadmin." GRANT is database object specific, so
it works only on individual databases and database objects (tables, etc.)
Cheers,
Michael C.
"Lolik" <Lolik@.discussions.microsoft.com> wrote in message
news:BDFB3614-78ED-4DB2-8468-7C78073A7906@.microsoft.com...
> Finally got to the point where I can connect to MSDE from Access. If you
are setting up MSDE for the first time, you may find a couple useful points
in the following.
> MSDE 2000 with Access 2003: The First steps.
> 1) install MSDE from Office CD (need to locate in MSDE directory by
browsing and start it manually. Read KB article 319930 first);
> 2) when installing, need to specify "sa" (system admin) password which is
not (does not have to be anyway) the same as Windows Administrator's
password. It is required in order not to leave sysadmin password blank which
would leave a security hole;
> 3) if you are using all the correct switches with the 'setup' command, the
mixed login mode will be allowed. The mixed login mode lets you login from
non-admin account by using MSDE login. I did not use any switches so had to
make the adjustments in the registry. Very easy, but I still had to locate
the required key which was not where it is supposed to be judging from KB
article 319930, but quite near it.
> 4) restart and check that 2 new services are running: MSSQLSERVER and
SQLSERVERAGENT.
> 5) restart the PC and log in under (Windows) administrator account (does
not need to be THE "Administrator", just any account with admin privileges)
> 6) test the connection to MDSE by going to command line, typing "osql -E"
(no " needed). You should see ">1" which means MDSE is running.
> 7) Now this is the $100 trick: type "sp_addlogin [BUILTIN\POWER USERS]",
<ENTER>, "GO". wait for some reaction (something like 2 rows affected)
> 8) Here comes another $100 trick: type "grant all", <ENTER>, "to
[BUILTIN\POWER USERS]", <ENTER>, "go".
> Now you can go back to your every day Windows login (I assume you are
using an account from Power Users group, aren't you?), start Access, create
a new .adp file and connect your Access .adp file to MSDE using "Trusted
Connection" or "Use Windows NT integrated security".
> Oh by the way you can type "exit" from command line to stop your
connection to MSDE when you feel like.
|||$0.02 worth - sp_addrolemember and sp_addsrvrolemember adds users to
server-wide roles, like "sysadmin." GRANT is database object specific, so
it works only on individual databases and database objects (tables, etc.)
__________________
Do not underestimate your input Michael!
Guess I should run sp_addsrvrolemember too. Still after having used GRANT as above I was able to create a new SQL database and connect to it, at the time a new Access .adp file was set up.
The $50 tag referred to using [BUILTIN\POWER USERS] as a login. Could not find it mentioned anywhere. Maybe it is obvious to everyone but me but figuring out what [Corporate\Bobj] is in XP language was not straightforward to me at all.
|||Yes, you can grant User Groups access rights to your SQL Server One of
the benefits of using Integrated Security for your SQL Server logins. The
built-in server roles, like sysadmin grant general permissions server-wide,
and include various other little niceties. Since your user created the 2nd
database, that user is the database owner (dbo) for that database, so that
user will have all the rights associated with that database. Server Roles
make it a little easier to admin multiple databases.
Cheers,
Michael C.

> Do not underestimate your input Michael!
> Guess I should run sp_addsrvrolemember too. Still after having used GRANT
as above I was able to create a new SQL database and connect to it, at the
time a new Access .adp file was set up.
sql

MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
MarkSorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.net.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>

msde 2000 on windows 2003 server

I "Managed" to install msde on windows 2003 server but the sql service manager does list an thing to connect to.
what am i doing wrong does mdse work on windows 2003 server and how do i fix it ?
Hi,
I have found the following KB article that describes a similar scenario.
http://support.microsoft.com/default...&Product=sql2k
#appliesto
================================================== ==========================
================================================== =========
BUG: The SQL Server 2000 Service Manager Utility Does Not List Instances
That Have Not Enabled Network Connections
View products that this article applies to.
BUG #: 363267 (SHILOH_BUGS)
SYMPTOMS
If you configure an instance of SQL Server 2000 or SQL Server 2000 Desktop
Engine (also known as MSDE 2000) to disallow network connections, that
instance will not appear in the SQL Server 2000 Service Manager utility.
CAUSE
The SQL Server ODBC driver does not return instance names to the SQL
Service Manager if the instance does not support network connections.
WORKAROUND
To work around this behavior, stop and then start the service for the
instance by following these steps:
Right-click My Computer, and then click Manage.
Double-click Services and Applications in the left-hand screen.
Double-click Services.
Right-click the service for the instance of SQL Server. The name of the
service for a default instance of SQL Server 2000 is MSSQLServer. The name
of the service for a named instance of SQL Server 2000 is
MSSQL$instancename.
Click the action that you want applied to the instance, such as stop or
start.
================================================== ==========================
================================================== =========
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE 2000 installation on Windows 98 SE

Hi,
I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
service is running.
I am not able to connect to the MSDE in WIndows Authentication mode
while using Login ( sa ) / password the connectivity is done.
My GUI uses the MSDE connection in "Windows Authentication Mode" which
is working fine with the 2K/XP but not with 98SE/ME.
The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
is "Windows Authentication" BUT its not working in that way.
I have tried SECURITYMODE=SQL as command line to setup.exe as well but
results are same.
Any clue to run it in WMA Mode on Win98SE/ME ?
thanks
kapil
Hi Kaps,
Win98 doesn't provide the infrastructure that MSDE needs to use Windows
Authentication. You will need to use SQL Server authentication and specify
an password for sa (SAPWD) while installing it.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"kaps" <kapilkj@.gmail.com> wrote in message
news:1103617693.026085.125330@.f14g2000cwb.googlegr oups.com...
> Hi,
> I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
> service is running.
> I am not able to connect to the MSDE in WIndows Authentication mode
> while using Login ( sa ) / password the connectivity is done.
> My GUI uses the MSDE connection in "Windows Authentication Mode" which
> is working fine with the 2K/XP but not with 98SE/ME.
> The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
> is "Windows Authentication" BUT its not working in that way.
> I have tried SECURITYMODE=SQL as command line to setup.exe as well but
> results are same.
> Any clue to run it in WMA Mode on Win98SE/ME ?
>
> thanks
> kapil
>

MSDE 2000 connectivity problem

Hi,
I have installed MSDE 2000 into my desktop machine.I can
connect from other machines to my desktop and accessing
databases using Query Analyser, Enterperise manager,
Profiler.but I didn't connect from ASP.NET application
using as "connectionstring".
Earlier it was worked.now its not working.
Send me your valuable reply ASAP.
Thanks and regards,
RafiqHow does your connection string look like?
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Rafiq" <anonymous@.discussions.microsoft.com> wrote in message
news:088801c3a9ab$02032c50$a401280a@.phx.gbl...
> Hi,
> I have installed MSDE 2000 into my desktop machine.I can
> connect from other machines to my desktop and accessing
> databases using Query Analyser, Enterperise manager,
> Profiler.but I didn't connect from ASP.NET application
> using as "connectionstring".
> Earlier it was worked.now its not working.
> Send me your valuable reply ASAP.
> Thanks and regards,
> Rafiq

MSDE 2000 and Windows 2003

I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my client PCs. I can connect locally from my Server. I have no firewalls or any other devices in between my clients and server.
Did you enable network connection on msde? Use svrnetcn.exe.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jiffy" <anonymous@.discussions.microsoft.com> wrote in message
news:94F601EF-E2C2-4777-BDB8-DDC76DFFE97A@.microsoft.com...
> I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my client PCs. I can connect locally
from my Server. I have no firewalls or any other devices in between my clients and server.
|||After you do this you will need to stop and restart MSDE.
Rand
This posting is provided "as is" with no warranties and confers no rights.

MSDE 2000 and Windows 2003

I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my cl
ient PCs. I can connect locally from my Server. I have no firewalls or any o
ther devices in between my clients and server.Did you enable network connection on msde? Use svrnetcn.exe.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jiffy" <anonymous@.discussions.microsoft.com> wrote in message
news:94F601EF-E2C2-4777-BDB8-DDC76DFFE97A@.microsoft.com...
> I am having trouble connecting to a Windows 2003 w/ MSDE 2000 from all my client P
Cs. I can connect locally
from my Server. I have no firewalls or any other devices in between my clien
ts and server.|||After you do this you will need to stop and restart MSDE.
Rand
This posting is provided "as is" with no warranties and confers no rights.

MSDE 2000 and ODBC (Connection failed)

Hi
I Installed MSDE 2000 and try to connect with it via ODBC.
I want the connection with SQL Server authentication using a login ID "sa" and blank password
But it is dispaly this message:
====================
Connection failed:
SQLState:'28000'
SQL Server Error:18456
[Microsoft][ODBC Sql Server Driver][SQL Server]Login failed for user 'sa'
====================check what authentication method your msde is using and make sure that standard security is available.|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Thanks ms_sql_dba

My MSDE use both WINDOWS/SQL Server authentication
I check "LoginMode" value in REGISTRY it's = Zero which mean both|||Up 4 Help|||I found the Solution in Archive which guide me to this link:
http://www.dbforums.com/showthread.php?threadid=711306

The Solution is very simple:
Change "SA" password

use this command line in DOS:
osql -Q"exec sp_password null,'newpassword','sa'" -E

MSDE 2000 and enterprise (enterprize) manager remotely

Hey all.
Can you use enterprise manager to connect to an MSDE 2000 version of
SQL Server across the internet? Ignoring firewalls (server was placed
outside firewall to see if thats where the connection problem was)
We get the 'SQL Server does not exist or access denied
ConnectionOpen(Connect())' error when trying to connect to a clients
database on their server over the internet. However, everything looks
ok and I can vpn into their machine and connect to the server using
enterprise manager on a terminal service session on their servers.
This in itself is a pain and we would rather have their server
registered in our enterprise manager.
Does the same answer apply if the server was an installation of SQL
Server standard edition?Licensing questions aside:
Yes. Note that MSDE doesn't by default listen to any netlibs. If you can
connect to the same MSDE after VPN, then this shouldn't be an issue. I
suggest you, on the client, make sure that TCP IP is at the top of the list
in Client Network Utility. Also try connecting using IP address. And as for
port numbers,
The IP netlib uses 1433 for a default instance.
The IP netlib uses 1434 for the port resolution query and whatever the
instance picked at the first startup for the actual data traffic.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Karl Rhodes" <karl.rhodes@.keywave.com> wrote in message
news:7cee27c2.0402110245.64167e99@.posting.google.com...
> Hey all.
> Can you use enterprise manager to connect to an MSDE 2000 version of
> SQL Server across the internet? Ignoring firewalls (server was placed
> outside firewall to see if thats where the connection problem was)
> We get the 'SQL Server does not exist or access denied
> ConnectionOpen(Connect())' error when trying to connect to a clients
> database on their server over the internet. However, everything looks
> ok and I can vpn into their machine and connect to the server using
> enterprise manager on a terminal service session on their servers.
> This in itself is a pain and we would rather have their server
> registered in our enterprise manager.
> Does the same answer apply if the server was an installation of SQL
> Server standard edition?|||I have tested my theory out by installing MSDE on my workstation and
tryng to connect from another machine across the internet, with little
success, thats why I asked.
Do you have any other ideas why we wouldnt be able to register their
server in enterprise manager?
I can only register it in enterprise manager on the terminal server box,
not on my local ent manager.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Is the terminal server the machine where MSDE is installed? Remember that
MSDE doesn't listen to any netlibs by default. Apart from that and the
things I mentioned in my first post, I don't know what it might be.
Firewalls is the most common reason for this.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Karl Rhodes" <karl.rhodes@.keywave.com> wrote in message
news:OZpfufJ8DHA.452@.TK2MSFTNGP11.phx.gbl...
> I have tested my theory out by installing MSDE on my workstation and
> tryng to connect from another machine across the internet, with little
> success, thats why I asked.
> Do you have any other ideas why we wouldnt be able to register their
> server in enterprise manager?
> I can only register it in enterprise manager on the terminal server box,
> not on my local ent manager.
>
>
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!|||As far as I I know, yes the MSDE is on the same server as the terminal
services. BUT, When I log on terminal services and have a look at the
properties of the server (terminal services enterprise manager) it says
tcpip is enabled. Does this mean that this library is available and
SHOULD work across the internet?
remove 'REMOVESPAM.' for email
Karl Rhodes
Internet Solutions Architect
The Learning Business & Keywave
www.thelearningbiz.com
www.keywave.com
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

MSDE 2000 and enterprise (enterprize) manager remotely

Hey all.
Can you use enterprise manager to connect to an MSDE 2000 version of
SQL Server across the internet? Ignoring firewalls (server was placed
outside firewall to see if thats where the connection problem was)
We get the 'SQL Server does not exist or access denied
ConnectionOpen(Connect())' error when trying to connect to a clients
database on their server over the internet. However, everything looks
ok and I can vpn into their machine and connect to the server using
enterprise manager on a terminal service session on their servers.
This in itself is a pain and we would rather have their server
registered in our enterprise manager.
Does the same answer apply if the server was an installation of SQL
Server standard edition?Licensing questions aside:
Yes. Note that MSDE doesn't by default listen to any netlibs. If you can
connect to the same MSDE after VPN, then this shouldn't be an issue. I
suggest you, on the client, make sure that TCP IP is at the top of the list
in Client Network Utility. Also try connecting using IP address. And as for
port numbers,
The IP netlib uses 1433 for a default instance.
The IP netlib uses 1434 for the port resolution query and whatever the
instance picked at the first startup for the actual data traffic.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Karl Rhodes" <karl.rhodes@.keywave.com> wrote in message
news:7cee27c2.0402110245.64167e99@.posting.google.com...
> Hey all.
> Can you use enterprise manager to connect to an MSDE 2000 version of
> SQL Server across the internet? Ignoring firewalls (server was placed
> outside firewall to see if thats where the connection problem was)
> We get the 'SQL Server does not exist or access denied
> ConnectionOpen(Connect())' error when trying to connect to a clients
> database on their server over the internet. However, everything looks
> ok and I can vpn into their machine and connect to the server using
> enterprise manager on a terminal service session on their servers.
> This in itself is a pain and we would rather have their server
> registered in our enterprise manager.
> Does the same answer apply if the server was an installation of SQL
> Server standard edition?

MSDE 1.0 --> MSDE 2000 DB Connection Failure

Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now when this software runs it cannot connect to the Database.
I believe the problem to come in a line wrote as so:
BSTR bstrOpen = gServerName.AllocSysString();
although I'm not 100%.
Just wondering if anyone might had the same problem with MSDE 2000 and what they did to fix it. Thanks!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
One of the things that's different about MSDE2000 is that by default, tcp is
not enabled. You might need to re-enable it. You can do this by running
svrnetcn.exe.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%234NbSXufEHA.2984@.tk2msftngp13.phx.gbl...
> Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now
when this software runs it cannot connect to the Database.
> I believe the problem to come in a line wrote as so:
> BSTR bstrOpen = gServerName.AllocSysString();
> although I'm not 100%.
> Just wondering if anyone might had the same problem with MSDE 2000 and
what they did to fix it. Thanks!
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

MSDE + JDBC SP3 - Run Together in WS

I have a java application running with JDK 1.3.1. I`d like connect this
application through the SQL DB ( MSDE + SQL Server 2000 Driver for JDBC
Service Pack 3, both are free ). Is it possible.
Txs in advance,
Jose R Castro / MCP W2K
| Thread-Topic: MSDE + JDBC SP3 - Run Together in WS
| thread-index: AcTXTYaW1R/kc6+DROSEIv2/byEYnw==
| X-WBNR-Posting-Host: 201.1.124.200
| From: "=?Utf-8?B?Sm9zZSBSIENhc3Rybw==?=" <Jose R
Castro@.discussions.microsoft.com>
| Subject: MSDE + JDBC SP3 - Run Together in WS
| Date: Tue, 30 Nov 2004 18:29:04 -0800
| Lines: 7
| Message-ID: <0EF992D0-735C-439E-B581-A6FA4464B99A@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.jdbcdriver
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.jdbcdriver:6519
| X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
|
| I have a java application running with JDK 1.3.1. I`d like connect this
| application through the SQL DB ( MSDE + SQL Server 2000 Driver for JDBC
| Service Pack 3, both are free ). Is it possible.
| Txs in advance,
|
| Jose R Castro / MCP W2K
|
|
Yes, you can connect to MSDE from JDBC in the same way that you connect to
a full-blown instance of SQL Server..
Carb Simien, MCSE MCDBA MCAD
Microsoft Developer Support - Web Data
Please reply only to the newsgroups.
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.

MSDE (SQL Server does not exist or access denied.)

Hi all,
I'm getting this error message when I try to connect my MSDE database from other machine using enterprise manager application. Both of the machines are WinXP SP2. I found some solution such as using 'SQLServer Network Utility' but didn't work out for me. I even can not connect my database on my computer using TCP/IP. When I connect with name, it worked fine. I already enable both TCP/IP and Named pipe protocol on the MSDE machine.
If someone has solution on that please let me know.

Thanks,
MyoDid you open the ports on the computers ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||If you have SQL Server 2005 installed on the same box as the MSDE, you need make sure SQL Browser is running. Make sure the ports (UDP/1434 and your TCP Port) are open if firewall exists. Also try file sharing between machines and make it work, otherwise NP won't work. When you use cliconfg.exe, make TCP and NP are on the client protocol lists.|||
Yes,
There is also SQL 2000 and 2005Express running together with MSDE. I already changed the port no and try to connect it. But, still didn't work out. I tried at the other machine and it works. I don't know why it still doesn't work at this machine. May be I miss some configuration. I'll try again. Thanks for the message.

Regards,
Myo|||

I have exactly the same issue. I have installed MSDE2000 on a PC with Windows XP Professional and SP2. I have tried everything to connect to another remote server and still get the same error message

I have added ports 135 and ports 445 to the firewall but again without much success. Does anyone out there have any ideas on how to get this working?

|||You will first have to determine the port that MSDE is using by starting the application Srvnetcn.exe naviagte to TCP and note that number down. After this you will have to create an exclude filter for the firewall for the application sqlservr.exe using this number and the 1434 UDP for incoming request. That should egt you started for SQL Server.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Hi Jens,

Many thanks for your prompt response. I have tried all your suggestions but still cannot gain access to a remote database. TCP/IP is running on port 1433, using Srvnetcn.exe to check, and I have added both the entries you have suggested to the firewall exclude lists. Any other ideas? Thanks in advance

msde & windows xp sp2 question

hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
Have you tried disabling the firewall & then attempting to connect? Does it
work?
Cheers,
James Goodman
"S Purkiss" <shel@.shel.com> wrote in message
news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can
> i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've
> attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on
> the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
>
|||Hi James
Yep, I've tried this. Disabling the firewall doesn't improve the situation.
I have two theories on this...
1. i've heard it said that sp2's firewall doesn't actually go all the way
down when turned off
2. perhaps some netoworking protocol for sql is turned off when sp2 is
installed?
Take care,
Sheldon
"James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
> Have you tried disabling the firewall & then attempting to connect? Does
> it work?
>
> --
> Cheers,
> James Goodman
> "S Purkiss" <shel@.shel.com> wrote in message
> news:MNqdnQgi5cqwVffcRVn-rw@.rogers.com...
>
|||If you added sqlsvr.exe to the exception list that should open up port 1433
or whatever port your using if it is a named instance and also udp 1434.
Make sure you have file and print sharing enabled as well.
"S Purkiss" wrote:

> Hi James
> Yep, I've tried this. Disabling the firewall doesn't improve the situation.
> I have two theories on this...
> 1. i've heard it said that sp2's firewall doesn't actually go all the way
> down when turned off
> 2. perhaps some netoworking protocol for sql is turned off when sp2 is
> installed?
> Take care,
> Sheldon
>
> "James Goodman" <jamesATnorton-associates.co.ukREMOVE> wrote in message
> news:ux8vBpGsEHA.3896@.TK2MSFTNGP15.phx.gbl...
>
>

msde & windows xp sp2 question

hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
take to ensure other workstations can connect? The msde instance was
created with merge modules, and I cannot update to sp3a without the
manufacturer providing an installation, which isn't going to happen
apparently. Currently, none of my workstations can connect; i've attempted
to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
host system, with no luck.
Any assistance would be greatly appreciated!
S. Purkiss.
S Purkiss wrote:
> hosting an msde 2000 sp1 instance on a windows xp sp 2 box, what steps can i
> take to ensure other workstations can connect? The msde instance was
> created with merge modules, and I cannot update to sp3a without the
> manufacturer providing an installation, which isn't going to happen
> apparently. Currently, none of my workstations can connect; i've attempted
> to add sqlsvr.exe to the exception list, and also open port 1433 tcp on the
> host system, with no luck.
> Any assistance would be greatly appreciated!
> S. Purkiss.
>
Hi Sheldon
For a default instance of MSDE you need to open TCP 1433.
For a named instance you need to open UDP 1434 and the TCP port that the
named instance is using. You can find this port from the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\YourNamedInstance\MSSQLServer\SuperSocketNe tLib\Tcp, key TcpPort.
Good luck!

MSDE & Web pages

Hello all,
I am trying to connect a web page to an Access database (using ADO), using
the MSDE engine as opposed to jet. What I have at the moment doesn't work,
could anyone help?
Thanks in advance,
Adonis.I'm confused by your posting. Are you using MSDE or Access -- two different
databases. And, what do you have as a connection string ?
Michael D.|||Sorry about that. Iam using MSDE. (I have upsized an Mdb file up to an
adp/mdf). The connection string is
strDBPath=server.MapPath("quaSAR.adp")
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "Provider=msdasql;Data Source=" &strDBPath & ";"
Any ideas?
Regards,
Adonis.
"Michael D" <anonymous@.discussions.microsoft.com> wrote in message
news:AC684267-206E-47B6-A607-9E9230771A91@.microsoft.com...
> I'm confused by your posting. Are you using MSDE or Access -- two
different databases. And, what do you have as a connection string ?
> Michael D.|||(1) What error message do you get when you are trying to connect ? Please cu
t an paste the entire message here.
(2) Can you connect to the MSDE instance via Query Analyser or an ODBC DSN c
onnection ?
Thanks,
Michael D.|||Have a look at this article...
http://support.microsoft.com/defaul...&product=adonet
Michael D.

MSDE & Web pages

Hello all,
I am trying to connect a web page to an Access database (using ADO), using
the MSDE engine as opposed to jet. What I have at the moment doesn't work,
could anyone help?
Thanks in advance,
Adonis.
I'm confused by your posting. Are you using MSDE or Access -- two different databases. And, what do you have as a connection string ?
Michael D.
|||Sorry about that. Iam using MSDE. (I have upsized an Mdb file up to an
adp/mdf). The connection string is
strDBPath=server.MapPath("quaSAR.adp")
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "Provider=msdasql;Data Source=" &strDBPath & ";"
Any ideas?
Regards,
Adonis.
"Michael D" <anonymous@.discussions.microsoft.com> wrote in message
news:AC684267-206E-47B6-A607-9E9230771A91@.microsoft.com...
> I'm confused by your posting. Are you using MSDE or Access -- two
different databases. And, what do you have as a connection string ?
> Michael D.
|||(1) What error message do you get when you are trying to connect ? Please cut an paste the entire message here.
(2) Can you connect to the MSDE instance via Query Analyser or an ODBC DSN connection ?
Thanks,
Michael D.
|||Have a look at this article...
http://support.microsoft.com/default...product=adonet
Michael D.

MSDE & Web pages

Hello all,
I am trying to connect a web page to an Access database (using ADO), using
the MSDE engine as opposed to jet. What I have at the moment doesn't work,
could anyone help?
Thanks in advance,
Adonis.Sorry about that. Iam using MSDE. (I have upsized an Mdb file up to an
adp/mdf). The connection string is
strDBPath=server.MapPath("quaSAR.adp")
Set Conn = Server.CreateObject("ADODB.Connection")
Conn.Open "Provider=msdasql;Data Source=" &strDBPath & ";"
Any ideas?
Regards,
Adonis.
"Michael D" <anonymous@.discussions.microsoft.com> wrote in message
news:AC684267-206E-47B6-A607-9E9230771A91@.microsoft.com...
> I'm confused by your posting. Are you using MSDE or Access -- two
different databases. And, what do you have as a connection string ?
> Michael D.|||(1) What error message do you get when you are trying to connect ? Please cut an paste the entire message here
(2) Can you connect to the MSDE instance via Query Analyser or an ODBC DSN connection
Thanks
Michael D.|||Have a look at this article..
http://support.microsoft.com/default.aspx?kbid=308656&product=adone
Michael D