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 and Computer Name Change

Hi!
I know that the default instance of MSDE is the computer name. If the
computer's name is subsequently changed, will the default instance’s name
change to the new computer name as well.
Thanks for your thoughts.
Actually the default instance name is not the computer name. All instances
are addressed in connections strings as <computer name>\<instance name>. If
you leave off the instance name then SQL Server assumes you are talking
about the default instance. So yes, if you change the computer name, all
your connection strings will break, probably including some that you aren't
aware of so changing the computer name is a risky thing to do. At a minimum
you will nee to use sp_addserver and restart MSDE to change SQL Server's
local server name.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Gene" <Gene@.discussions.microsoft.com> wrote in message
news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
> Hi!
> I know that the default instance of MSDE is the computer name. If the
> computer's name is subsequently changed, will the default instance's name
> change to the new computer name as well.
> Thanks for your thoughts.
|||Thanks for the input Roger. I don't know much about SQL, but my guess would
have been pretty close to your response. I'm concerned about breaking
something I'm not aware of and not knowing where to go from there.
Regards,
Gene
"Roger Wolter[MSFT]" wrote:

> Actually the default instance name is not the computer name. All instances
> are addressed in connections strings as <computer name>\<instance name>. If
> you leave off the instance name then SQL Server assumes you are talking
> about the default instance. So yes, if you change the computer name, all
> your connection strings will break, probably including some that you aren't
> aware of so changing the computer name is a risky thing to do. At a minimum
> you will nee to use sp_addserver and restart MSDE to change SQL Server's
> local server name.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Gene" <Gene@.discussions.microsoft.com> wrote in message
> news:85740AA2-9F4B-4CF8-B304-E27782458703@.microsoft.com...
>
>
sql

MSDE Access via the Network

I'm having a terrible time accessing an MSDE instance over the network.
sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
installed the MSDE instance using setup.exe with the following command:
setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
instanceName="<my instance name>"
No luck. So I thought I'd use the svrnetcn.exe utility to enable network
protocols since MSDE seems to be ignoring the command line. When I try to run
svrnetcn.exe, the screen flickers but the program never opens.
This *was* working several weeks ago. It quit working about the time I
installed Service Pack 2 for Windows XP on the box that was hosting this
server. Does anyone have any idea why this is happening to me? Any help
would be GREATLY appreciated.
Rob Reagan
rob@.digitallabsinc.com
hi Rob,
"Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> I'm having a terrible time accessing an MSDE instance over the network.
> sqlDMO's listAvailableSQLServers doesn't see the installed instance. I
> installed the MSDE instance using setup.exe with the following command:
> setup.exe disablenetworkprotocols=0 sapwd="<pwd>" securityMode=SQL
> instanceName="<my instance name>"
> No luck. So I thought I'd use the svrnetcn.exe utility to enable network
> protocols since MSDE seems to be ignoring the command line. When I try to
run
> svrnetcn.exe, the screen flickers but the program never opens.
> This *was* working several weeks ago. It quit working about the time I
> installed Service Pack 2 for Windows XP on the box that was hosting this
> server. Does anyone have any idea why this is happening to me? Any help
> would be GREATLY appreciated.
> Rob Reagan
> rob@.digitallabsinc.com
>
SP service pack 2 changed a lot of things regarding SQL Server connections
too..
I've not installed sp2 yet, but it's worth reading
http://support.microsoft.com/default.aspx?kbid=841249 and related links...
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
|||Thank you so much! That's just the information I needed.
SP2 makes my PC so secure, not even my own applications can get through...
"Andrea Montanari" wrote:

> hi Rob,
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> ha scritto nel messaggio
> news:5B63E3CB-8307-49C8-ABC4-56B114893B1D@.microsoft.com...
> run
> SP service pack 2 changed a lot of things regarding SQL Server connections
> too..
> I've not installed sp2 yet, but it's worth reading
> http://support.microsoft.com/default.aspx?kbid=841249 and related links...
> --
> 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
>

msde 2000 verify instance

I'm trying to write logic that verifies whether or not a named instance
already exists on a PC using C#. Is there a way to do this?
hi,
"liz23" <liz23@.discussions.microsoft.com> ha scritto nel messaggio
news:5C36ED99-6FC3-4D66-9775-0E6958DEE554@.microsoft.com...
> I'm trying to write logic that verifies whether or not a named instance
> already exists on a PC using C#. Is there a way to do this?
you can try several methods... you can (locally) query the windows registry
for the
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\
InstalledInstances
which return a list of all locally installed instances, where "MSSQLSERVER"
is the default instance...
you can query the SQLDMO.Application .ListAvailableSQLServers method to
return all available instance of the lan or SQLDMO.SQLServer2
..ListInstalledInstances("ServerName") for all available instaces on the
specified server...
by the way, .ListAvailableServer uses ODBC function SQLBrowseConnect()
provided by ODBC libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are
conclusive and consistent, becouse results are influenced of various
servers's answer states, answer time, etc.
Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS
broadcast, on which SQL Servers respond (Default protocol for SQL Server
7.0), while in SQL Server 2000 the rules changed, because the default client
protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS
broadcast, listening on port 1434:
which is using a UDP broadcast on port 1434, if instance do not listen or
not respond on time they will not be part of the enumeration.
Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to
listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never
show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast.
There is a gray window of 15 minutes after shutdown, where a browse master
in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS
broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.
In SQL Server 2000 using MDAC 2.6 this changes a little, because now the
default protocol has been changed to be TCP/IP sockets and instead of a
NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic
still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts,
only machines within the same subnet show up.
Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have
..ListAvailableServer method to work properly, becouse precding release of
Sql-DMO Components of Sql Server 2000 present a bug in this area.
The Service Pack 3a introduced some new amenity in order to prevent MSDE
2000 to be hit by Internet worms like Slammer and Saphire virus and to
increase security, so that Microsoft decided to default for disabling
SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on
UDP port 1434 when they are configured to not listen on any network
protocols. This will stop enlisting these servers.
other way to locate end enum SQL Server on the lan are available at
http://www.sqldev.net/misc/EnumSQLSvr.htm
http://www.sqldev.net/misc/ListSQLSvr.htm
http://www.sqldev.net/misc/OleDbEnum.htm
or try connecting to a specified instance name via Ado.Net, if you geuss a
defined instance is available... but keep the connection time-out very low
=;-D
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

MSDE 2000 SP3a install failure

I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.

your help is appreciated.the instance name is "MSDE"

Why is this not in the setup documentation?

MSDE 2000 Set-up: Invalid instance name

Thanks in advance.

I installed SQL 2000 Client Portion in my local computer: No server functionality. I selected my computer name as an instance name. Installation went OK.

Now, I am trying to install MSDE in my computer. Error comes in early part of installation: It says, "The instance name specified is not valid"

Please, any advise and suggestion.

Try deinstalling the SQL Client (why did that ask for an instance name when you didn't install the server - are you sure about deselecting the server?)

Install MSDE after the SQL Client was deinstalled. MSDE 2000 comes with a readme which explains the command line options for the setup. Read it carefully.

--
SvenC

|||

Thanks.

By the way, I have SQL 2005 Server in my computer.

Maybe, this is why.

|||

Yes, presumably MSDE tries to use the same instance name already in use by SQL 2005. Why would you want both versions on one machine?

Well, you can do it, but check the MSDE readme how to configure a different instance name. In the connection string you will use servername\instancename to access the named instance.

--
SvenC

MSDE 2000 named instance with my application

I am writing an application and wish to distribute MSDE with it.
I was considering using a batch file to do the install using the line
setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
However, the next step would be to call osql to either script the schema or
sp_attach_db the database. Well this raises the issue of once installed
with a named instance how do I do osql -E -S MACHINENAME\InstanceName
without knowing it ahead of time? Is there perhaps 1. an easier way or 2. a
different syntax to achieving it? I am pretty sure I will run into more
grief when attempting to set up the ODBC connections also.
Maybe I'd just be better off rewriting this to use an Access database
instead
hi Bradley,
"Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> I am writing an application and wish to distribute MSDE with it.
> I was considering using a batch file to do the install using the line
> setup INSTANCENAME="InstanceName" SAPWD="AStrongSAPwd"
> However, the next step would be to call osql to either script the schema
or
> sp_attach_db the database. Well this raises the issue of once installed
> with a named instance how do I do osql -E -S MACHINENAME\InstanceName
> without knowing it ahead of time? Is there perhaps 1. an easier way or 2.
a
> different syntax to achieving it? I am pretty sure I will run into more
> grief when attempting to set up the ODBC connections also.
> Maybe I'd just be better off rewriting this to use an Access database
> instead
you don't actually need to reference the Machine name... just refer to it as
"(local)" or "."
so, the full instance name will be
(local)\InstanceName
stay this MSDE... you'll love it =;-D
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
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2npor3F3baroU1@.uni-berlin.de...
> hi Bradley,
> "Bradley M. Small" <BSmall@.XNOSPAMXmjsi.com> ha scritto nel messaggio
> news:ejW7scifEHA.1424@.tk2msftngp13.phx.gbl...
> you don't actually need to reference the Machine name... just refer to it
as
> "(local)" or "."
> so, the full instance name will be
> (local)\InstanceName
> stay this MSDE... you'll love it =;-D
> --
Great!!! Seemed like there had to be a better syntax
Now, all I need to figure out is how to add the odbc connection from a batch
file. Is that even possible?

MSDE 2000 Named instance in conjunction with SQL server 7

I have SQL server 7 running as a default instance and I'm trying to install
MSDE 2000. I was able to install it as a named instance by running the
following:
setup.exe SAPWD="password" INSTANCENAME="named_instance"
Now I can not connect to the named instance with OSQL. What do I need to do
to connect properly?
Hi,
Try to connect to the instance as servername\named_instance
Example: If your machine name is MyServer1 and your named instance is
Cyclops then you would refer to the server as MyServer1\Cyclops. If this
will not work for you in the long run, you can always set up an alias on
your client through the Client Network Utility to refer to it in a more
conventional manner.
-Jose Molina
"iranpessar@.hotmail.com" <iranpessarhotmailcom@.discussions.microsoft.com>
wrote in message news:1FB9C0FC-639B-4B6E-A4EC-6623B70F3F78@.microsoft.com...
>I have SQL server 7 running as a default instance and I'm trying to install
> MSDE 2000. I was able to install it as a named instance by running the
> following:
> setup.exe SAPWD="password" INSTANCENAME="named_instance"
> Now I can not connect to the named instance with OSQL. What do I need to
> do
> to connect properly?

MSDE 2000 Named instance in conjunction with SQL server 7

I have SQL server 7 running as a default instance and I'm trying to install
MSDE 2000. I was able to install it as a named instance by running the
following:
setup.exe SAPWD="password" INSTANCENAME="named_instance"
Now I can not connect to the named instance with OSQL. What do I need to do
to connect properly?Hi,
Try to connect to the instance as servername\named_instance
Example: If your machine name is MyServer1 and your named instance is
Cyclops then you would refer to the server as MyServer1\Cyclops. If this
will not work for you in the long run, you can always set up an alias on
your client through the Client Network Utility to refer to it in a more
conventional manner.
-Jose Molina
"iranpessar@.hotmail.com" <iranpessarhotmailcom@.discussions.microsoft.com>
wrote in message news:1FB9C0FC-639B-4B6E-A4EC-6623B70F3F78@.microsoft.com...
>I have SQL server 7 running as a default instance and I'm trying to install
> MSDE 2000. I was able to install it as a named instance by running the
> following:
> setup.exe SAPWD="password" INSTANCENAME="named_instance"
> Now I can not connect to the named instance with OSQL. What do I need to
> do
> to connect properly?sql

MSDE 2000 install on SQL 2000

Hello,
I have installed MSDE 2000 on Win Server 2003 with instance name brprof,
there SQL Server 2000 already installed as a local instance named SBGBHO.
Now, I registered my new MSDE 2000 on enterprise manager, registration done
successfully, but it display following error
LOGIN FAILED FOR USER SA : REASON NOT ASSOCIATED WITH TRUSTED SQL SERVER
CONNECTION
HARSHA.
hi Harsha,
Harsha Shah wrote:
> Hello,
> I have installed MSDE 2000 on Win Server 2003 with instance name
> brprof, there SQL Server 2000 already installed as a local instance
> named SBGBHO. Now, I registered my new MSDE 2000 on enterprise
> manager, registration done successfully, but it display following
> error
> LOGIN FAILED FOR USER SA : REASON NOT ASSOCIATED WITH TRUSTED SQL
> SERVER CONNECTION
MSDE installs by default only allowing trusted WinNT connections... you can
change this behavior, allowing standard SQL Server connection at install
time providing the
SECURITYMODE=SQL
parameter to the setup.exe boostrap installer, or later accessing the
windows registry, as described in
http://support.microsoft.com/default...b;en-us;285097
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE 2000

Hello!!
I have a application that creates an instance of MSDE 2000 called
MMSQL$EMMSDE. It uses its own login to pass inforamtion called embuser. This
company does not provide information on how to recover data from the
database. I have a client that had their motherboard crash and needed a new
computer and wanted to recover the data off the drive. I have the MDF and LDF
files all under the data folder. Everytime I copy these over to a new
installation says that it is no good and my aplication I use cannot connect
to it as well. Is there anyway that anybody knows of on how to reconnect the
MDF file to another computer that has a fresh install of this applciation and
instance so it can receover the data?
Any and all posts is appreciated.
Thanks,
Fred
After you copied the MDF and/or LDF files to the new computer, where an SQL
Server/MSDE is installed, did you attached the data file the the instance of
SQL Server/MSDE?
"Fred Boltz" <Fred Boltz@.discussions.microsoft.com> wrote in message
news:57576684-C93B-4BD3-AF85-6A03BB605A8D@.microsoft.com...
> Hello!!
> I have a application that creates an instance of MSDE 2000 called
> MMSQL$EMMSDE. It uses its own login to pass inforamtion called embuser.
> This
> company does not provide information on how to recover data from the
> database. I have a client that had their motherboard crash and needed a
> new
> computer and wanted to recover the data off the drive. I have the MDF and
> LDF
> files all under the data folder. Everytime I copy these over to a new
> installation says that it is no good and my aplication I use cannot
> connect
> to it as well. Is there anyway that anybody knows of on how to reconnect
> the
> MDF file to another computer that has a fresh install of this applciation
> and
> instance so it can receover the data?
> Any and all posts is appreciated.
> Thanks,
> Fred
|||I tried using a 3rd party software to attach the file but could not. Can you
tell me how to go about doing that?
"Norman Yuan" wrote:

> After you copied the MDF and/or LDF files to the new computer, where an SQL
> Server/MSDE is installed, did you attached the data file the the instance of
> SQL Server/MSDE?
>
> "Fred Boltz" <Fred Boltz@.discussions.microsoft.com> wrote in message
> news:57576684-C93B-4BD3-AF85-6A03BB605A8D@.microsoft.com...
>
>
|||hi Fred,
Fred Boltz wrote:
> I tried using a 3rd party software to attach the file but could not.
> Can you tell me how to go about doing that?
>
have you been reported with an exception? what is the message?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea,
I am not sure of your question. What do you mean by have I been reported
with an exception? Here was the original message I wrote:
Hello!!
I have a application that creates an instance of MSDE 2000 called
MMSQL$EMMSDE. It uses its own login to pass inforamtion called embuser. This
company does not provide information on how to recover data from the
database. I have a client that had their motherboard crash and needed a new
computer and wanted to recover the data off the drive. I have the MDF and LDF
files all under the data folder. Everytime I copy these over to a new
installation says that it is no good and my aplication I use cannot connect
to it as well. Is there anyway that anybody knows of on how to reconnect the
MDF file to another computer that has a fresh install of this applciation and
instance so it can receover the data?
Any and all posts is appreciated.
Thanks,
Fred
"Andrea Montanari" wrote:

> hi Fred,
> Fred Boltz wrote:
> have you been reported with an exception? what is the message?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||hi Fred,
Fred Boltz wrote:
> Andrea,
> I am not sure of your question. What do you mean by have I been
> reported with an exception? Here was the original message I wrote:
you answered to Norman:
>I tried using a 3rd party software to attach the file but could not. Can
>you
>tell me how to go about doing that?
did the tool you used to re-attach the database reported you an exception?
anyway, you can use oSql.exe, the command line tool provided with MSDE to
reattach the database..
you have to log in as a sysadmin member so to have admin permissions granted
in MSDE using a truste connection, or you have to provide credentials of a
standard SQL Server login member of the sysadmin SQL Server group (like
"sa")..
once you are connected, you have to execute the sp_attach_db
(http://msdn2.microsoft.com/en-us/library/aa259611(SQL.80).aspx) system
stored procedure like
1>EXECUTE master..sp_attach_db @.dbname = 'the_database_name',
2>@.filename1 = N'ful_path_to_the_mdf_file.Mdf',
3>@.filename2 = N'ful_path_to_the_ldf_file.Ldf'
4>GO
then you can quit oSql.exe.. see
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q325003 for further
info about oSql.ex and MSDE uses
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply

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 & SQL Server 2000

I have MSDE 2000 SP3a (default instance) installed and working on my XP Pro
machine, but I'd like to follow some development labs that use the SQL Server
2000 databases. Can I also install SQL Server 2000 3a and if so, what special
'things' must I do to install it?
Dale Cowan
hi Dale,
"Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
news:D5AC5D41-BAA8-4502-B847-06DD990929CF@.microsoft.com...
> I have MSDE 2000 SP3a (default instance) installed and working on my XP
Pro
> machine, but I'd like to follow some development labs that use the SQL
Server
> 2000 databases. Can I also install SQL Server 2000 3a and if so, what
special
> 'things' must I do to install it?
you can only install SQL Server 2000 Developer edition, Personal Edition and
MSDE, on Windows clients platforms... the Standard and Enterprise edition
are only for server platforms...
as long as you install a supported version, you only have to specify a named
instance installation, as your pc already hosts a default instance.
you can have different service pack levels (never tried different localized
versions, but may be =;-D), but the shared binaries in \Program
Files\Microsoft SQL Server\80 folders will be updated at the highes
installed service pack level.
at the moment there's no SQL Server service pack 3 installation, you have to
install the RTM and apply the desired service pack
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
|||RTM?
"Andrea Montanari" wrote:

> hi Dale,
> "Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
> news:D5AC5D41-BAA8-4502-B847-06DD990929CF@.microsoft.com...
> Pro
> Server
> special
> you can only install SQL Server 2000 Developer edition, Personal Edition and
> MSDE, on Windows clients platforms... the Standard and Enterprise edition
> are only for server platforms...
> as long as you install a supported version, you only have to specify a named
> instance installation, as your pc already hosts a default instance.
> you can have different service pack levels (never tried different localized
> versions, but may be =;-D), but the shared binaries in \Program
> Files\Microsoft SQL Server\80 folders will be updated at the highes
> installed service pack level.
> at the moment there's no SQL Server service pack 3 installation, you have to
> install the RTM and apply the desired service pack
> --
> 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
>
|||hi Dale,
"Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
news:610C1A77-A467-4BD9-92E5-BE5B5961AEC2@.microsoft.com...
> RTM?
Release To Manufacturer =;-D
the 1st at al retail version
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 help. Everything installed just fine - even MS03-031 security
update afterward. MBSA reports few problems.
"Andrea Montanari" wrote:

> hi Dale,
> "Dale" <Dale@.discussions.microsoft.com> ha scritto nel messaggio
> news:610C1A77-A467-4BD9-92E5-BE5B5961AEC2@.microsoft.com...
> Release To Manufacturer =;-D
> the 1st at al retail version
> --
> 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
>

MSDE & SQL 7 running, backups fail

I have a W2K Server with SQL Server 7 and an instance of MSDE 2000 installed.
SQL Server 7 and MSDE 2000 both run OK together (I can make ODBC connections
to their databases from other clients, Enterprise Manager and dbamgr2k work)
and the MSDE 2000 backup jobs run successfully.
However, the SQL Server 7 maintenance jobs do not run successfully. SQL
Agent is running.
The same jobs DO run if MSDE 2000 is not running.
SQL Server connection is NT authentication.
SQL Agent Service startup account is system account.
SQL Agent SQLServer connection is Windows NT authentication.
MSDE connection is trusted NT authentication.
The Event log shows:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan Test'' (0xA15AFA82EC43BD4FBA057E1ECA0E2E61) - Status: Failed
- Invoked on: 29/07/2005 15:22:23 - Message: The job failed. Unable to
determine if the owner (sa) of job DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan Test' has server access (reason: Unable to connect to server
- check SQL Server and SQL Server Agent errorlogs).
SQLAgent.OUT:
29/07/2005 15:21:32 - ! [298] SQLServer Error: 14, Invalid connection.
[SQLSTATE 08001]
29/07/2005 15:21:32 - ! [298] SQLServer Error: 14, ConnectionOpen (Invalid
Instance()). [SQLSTATE 01000]
29/07/2005 15:21:32 - ! [382] Logon to server '(local)' failed
(ConnCachePerfCounterValues)
29/07/2005 15:22:23 - ! [298] SQLServer Error: 14, Invalid connection.
[SQLSTATE 08001]
29/07/2005 15:22:23 - ! [298] SQLServer Error: 14, ConnectionOpen (Invalid
Instance()). [SQLSTATE 01000]
29/07/2005 15:22:23 - ! [382] Logon to server '(local)' failed
(ConnCachePerfCounterValues)
Interestingly, I have to start the services in a particular order - SQL
Server and SQL Server Agent start automatically with Windows. I then have to
manually start MSDE and MSDE Agent otherwise SQL Server Agent cannot start.
I have recreated the same problem on a second server.
Any ideas why my SQL Server 7 jobs will not run?
Has anyone else achieved this?
hi,
Swaffs wrote:
> I have a W2K Server with SQL Server 7 and an instance of MSDE 2000
> installed. SQL Server 7 and MSDE 2000 both run OK together (I can
> make ODBC connections to their databases from other clients,
> Enterprise Manager and dbamgr2k work) and the MSDE 2000 backup jobs
> run successfully.
> However, the SQL Server 7 maintenance jobs do not run successfully.
> SQL Agent is running.
> The same jobs DO run if MSDE 2000 is not running.
I've tried reproducing the problem as indicated, but it seems I'm more lucky
then you
on a virtual machine, where both SQL Server 7.0 Dev Edition sp4 and MSDE Rel
A (sp3a) and relative Agent are running under LocalSystem account...
searching fo your reported exceptions I only found problems related to the
account running the service, but this should not be the case as SQL Server
7.0 Agent runs ok when MSDE is not running...
but I'll keep searching..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea - after reading that you tried it with SP3a without any issues,
I installed the latest Service Pack for MSDE, rebooted and started the MSDE
services before the SQL Services and the SQL Agent jobs work fine now.
Amazing what a difference a weekend makes!

MSDE & SQL 2000 same server

Hi Andrea,
I was just wondering.. does the 16 instance number apply to total of msde and sql server on a machine or does it mean 16 each.
Thanks
same old newbie
Total.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"new bie" <anonymous@.discussions.microsoft.com> wrote in message
news:8E4A2EF4-1D3F-44A5-9350-AA8238BC73E2@.microsoft.com...
> Hi Andrea,
> I was just wondering.. does the 16 instance number apply to total of msde and sql server on a machine or
does it mean 16 each.
> Thanks
> same old newbie
|||Thanks Tibor

MSDE & Enterprise Manager

I seem to be having problems registering an MSDE instance with my Enterprise
Manager. I keep getting the 'access denied or server does not exist' error.
Is there something special that I need to do or some other version of
Enterprise Manager that I should be using?
thanks for all your help.
JD
Did you consider this article to set up the desired communication ?
http://www.codeproject.com/database/ConfigureMSDE.asp
HTH, jens Suessmeyer.
|||Jens,
Thank you much for this link. It looks very promising. A few years back,
I had some information on how to set this up but have since lost it.
Once again, Thanks,
Joe
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1129564389.827519.206390@.z14g2000cwz.googlegr oups.com...
> Did you consider this article to set up the desired communication ?
>
> http://www.codeproject.com/database/ConfigureMSDE.asp
>
> HTH, jens Suessmeyer.
>
|||Hello,
This is a general error and you can refer to the following article to
troubleshoot the issue:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/kb/328306/
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Sophie,
Thanks for the link. I'll check it out this morning.
Joe D
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:fI6TTq60FHA.3328@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> This is a general error and you can refer to the following article to
> troubleshoot the issue:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/kb/328306/
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ================================================== ===
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hello,
You are welcome. If anyting is unclear, feel free to post back.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE & Enterprise Manager

I seem to be having problems registering an MSDE instance with my Enterprise
Manager. I keep getting the 'access denied or server does not exist' error.
Is there something special that I need to do or some other version of
Enterprise Manager that I should be using?
thanks for all your help.
JDDid you consider this article to set up the desired communication ?
http://www.codeproject.com/database/ConfigureMSDE.asp
HTH, jens Suessmeyer.|||Jens,
Thank you much for this link. It looks very promising. A few years back,
I had some information on how to set this up but have since lost it.
Once again, Thanks,
Joe
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1129564389.827519.206390@.z14g2000cwz.googlegroups.com...
> Did you consider this article to set up the desired communication ?
>
> http://www.codeproject.com/database/ConfigureMSDE.asp
>
> HTH, jens Suessmeyer.
>|||Hello,
This is a general error and you can refer to the following article to
troubleshoot the issue:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/kb/328306/
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Sophie,
Thanks for the link. I'll check it out this morning.
Joe D
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:fI6TTq60FHA.3328@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> This is a general error and you can refer to the following article to
> troubleshoot the issue:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/kb/328306/
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello,
You are welcome. If anyting is unclear, feel free to post back.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE & Enterprise Manager

I seem to be having problems registering an MSDE instance with my Enterprise
Manager. I keep getting the 'access denied or server does not exist' error.
Is there something special that I need to do or some other version of
Enterprise Manager that I should be using?
thanks for all your help.
JDDid you consider this article to set up the desired communication ?
http://www.codeproject.com/database/ConfigureMSDE.asp
HTH, jens Suessmeyer.|||Jens,
Thank you much for this link. It looks very promising. A few years back,
I had some information on how to set this up but have since lost it.
Once again, Thanks,
Joe
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1129564389.827519.206390@.z14g2000cwz.googlegroups.com...
> Did you consider this article to set up the desired communication ?
>
> http://www.codeproject.com/database/ConfigureMSDE.asp
>
> HTH, jens Suessmeyer.
>|||Hello,
This is a general error and you can refer to the following article to
troubleshoot the issue:
Potential causes of the "SQL Server does not exist or access denied" error
message
http://support.microsoft.com/kb/328306/
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Sophie,
Thanks for the link. I'll check it out this morning.
Joe D
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:fI6TTq60FHA.3328@.TK2MSFTNGXA01.phx.gbl...
> Hello,
> This is a general error and you can refer to the following article to
> troubleshoot the issue:
> Potential causes of the "SQL Server does not exist or access denied" error
> message
> http://support.microsoft.com/kb/328306/
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ========================================
=============
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello,
You are welcome. If anyting is unclear, feel free to post back.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

MSDE & datadir

Is it possible that on the client's machine I install my MSDE instance in the default location (C:\Program Files\Microsoft SQL Server), i.e. do not specify any datadir or Targetdir location in the setup BUT still create my app's database (during installat
ion) in my app's folder, for e.g. in C:\Program Files\MyCompany\Data\ folder and then attach this database's .mdf file to my instance which I installed. Is it necessary that the database has to be in the data folder under the MSDE install location...
Please suggest.
I am asking because I want to have nothing but database in the my app's data folder.
>> still create my app's database (during installation) in my app's folder
Yes. This is possible. It is NOT mandated that the specific databases that
you create should also fall inside the default location. In event that you
create database without any specific paths then they are created in the
default location.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"qa" <anonymous@.discussions.microsoft.com> wrote in message
news:CC9D5500-4C13-45B6-9040-F4A908DAEB26@.microsoft.com...
> Is it possible that on the client's machine I install my MSDE instance in
the default location (C:\Program Files\Microsoft SQL Server), i.e. do not
specify any datadir or Targetdir location in the setup BUT still create my
app's database (during installation) in my app's folder, for e.g. in
C:\Program Files\MyCompany\Data\ folder and then attach this database's .mdf
file to my instance which I installed. Is it necessary that the database
has to be in the data folder under the MSDE install location...
> Please suggest.
> I am asking because I want to have nothing but database in the my app's
data folder.
|||Thanks Vinod for your reply. How can I specify path for the database (not the entire data folder) as C:\Program Files\MyCompany\Data\ while creating the database using scripts during the installation program. And is keeping the database away in myapp's
folder a recommended way of working..
qa
|||You have to specify the path to the database and log files in the CREATE
DATABASE statement of the script file. Example for a database called "HAS":
CREATE DATABASE [HAS] ON (NAME = N'HAS_Data', FILENAME = N'f:\Microsoft SQL
Server\MSSQL\data\HAS_Data.MDF' , SIZE = 2, FILEGROWTH = 10%) LOG ON (NAME =
N'HAS_Log', FILENAME = N'f:\Microsoft SQL Server\MSSQL\data\HAS_Log.LDF' ,
SIZE = 1, FILEGROWTH = 10%)
COLLATE Latin1_General_CI_AS
GO
Willem
"qa" <anonymous@.discussions.microsoft.com> schreef in bericht
news:A7253E41-0E31-4D5C-967F-E7483AE75304@.microsoft.com...
> Thanks Vinod for your reply. How can I specify path for the database (not
the entire data folder) as C:\Program Files\MyCompany\Data\ while creating
the database using scripts during the installation program. And is keeping
the database away in myapp's folder a recommended way of working..
> qa