Hello,
My 1st attempt to install .Net framework, MSDE, my application and the databases during setup (using the MSDE deployment toolkit RC) works fine on windows xp. Now when I try to do the same for windows 98 SE machine, I am able to install .Net framweork an
d MSDE, but after that during the installation I get the following error message:
"An exception occured in the OnAfterInstall event handler of DBInstaller.CustomInstaller --> Unable to access service: Operating system does not support controlling a Windows service. A service can only be controlled on Windows NT, Windows 2000, or lat
er."
It's clear that when the setup tries to start the service to create the database etc it fails. Is this a known issue. I researched on web but couldn't find anything. Any ideas.
Thanks
dev
Any ideas..
Showing posts with label net. Show all posts
Showing posts with label net. Show all posts
Friday, March 30, 2012
MSDE to SQL Server Express
Hi - I have an MSDE database running on my server - I'd like to port my asp.net 1.1 app to asp.net2, and make use of SQL 2005 Express.
How do I transfer my data from an MSDE database to SQL Server Express, keeping intact all of my unique ID fields, indexes, and SPs (I don't have any functions or views)
Thanks for any help,
Mark
Your best bet is either to "detach" it on the MSDE side, and "attach" it or "restore from backup" on the SQL 2005 side, or use DTS (data transformation services).
|||Hi - it's just SQL Server 2005 Express I have available, so no management tools are there to allow me to 'restore from backup' - I'm not sure it supports DTS either.
Has anyone else been able to do this?
Thanks, Mark|||
Even with SQL Express you should have the ability to detach the database. You need the Management studio installed to work with the Express server engine though. You can download it here.
http://www.microsoft.com/downloads/details.aspx?familyid=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&displaylang=en
|||You don't have to detach from SQL Express if you are using a file based database (You are if you use the AttachDB attribute in your connect string). Just stop whatever application that uses it, and copy the mdb/ldb files to SQL Sever 2005 and attach.MSDE sql express on laptop, error 26
hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
installed during the installation, finally trying to get an sql database to
work, i am a newbie to both Visual studio and SQL, anyway i can see the
database inside server explorer and all its talbles, but when i try to run
the application i get an error has occured while establishing a connection
the the server, When connecting to SQL server 2005, this failure may be
caused by the fact that under the default settings SQL server does not allow
remote connections, (provider SQL network interfaces, error:26 error
locatiang server/instance Specified
i read similar posts in this forum and tried the following
enabled TCP/Ip on the server and client, do i need any of the other
protocols enabled: shared memory is enabled, named pipes is disabled, tcp/ip
is enablaed and VIA is disabled, this is for the server, for the client
shared memory, tcp/ip, named pipes are all enabled while via is disabled
i ran the SQL server surface area configuration and choose the Surface area
configuration for servcies and connections, under there, the radio buttion
for local and remote connection/Using TCP/IP only are selected. so i think
that is ok
i copi8ed a SQL database to a folder in the database and set the connection
using the wizard, i tested the connection and it is ok.
are there other things to do are other places to check,
Possibility 1:
Start the SQL Server Browser Service. SQL Server 2005 Express installs as a
named instance called sqlexpress. The SQL Server Browser Service resolves a
connection attempt of <computer_name>\sqlexpress to a port number. Without
SQL Server Browser, when connecting to a named instance you need to specify
the port number when you connect. And all named instances like SQL Server
2005 listen on dynamic ports, so the port may change when SQL Server is
started.
Possibility 2:
If you are running on a laptop, you may be running on Windows XP, service
pack 2 which automatically turns on the Windows firewall. If you are
connecting from the same server, you should be connecting using Shared
Memory so that won't matter. If you are connecting from another computer,
you may need to open a TCP port, or allow sqlservr.exe to communicate
through the firewall.
If this information is helpful, more information is available at
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Frank Bruhn" <FrankBruhn@.discussions.microsoft.com> wrote in message
news:E96EEA76-4277-4D80-8B75-79D945744E95@.microsoft.com...
> hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
> installed during the installation, finally trying to get an sql database
> to
> work, i am a newbie to both Visual studio and SQL, anyway i can see the
> database inside server explorer and all its talbles, but when i try to run
> the application i get an error has occured while establishing a connection
> the the server, When connecting to SQL server 2005, this failure may be
> caused by the fact that under the default settings SQL server does not
> allow
> remote connections, (provider SQL network interfaces, error:26 error
> locatiang server/instance Specified
> i read similar posts in this forum and tried the following
> enabled TCP/Ip on the server and client, do i need any of the other
> protocols enabled: shared memory is enabled, named pipes is disabled,
> tcp/ip
> is enablaed and VIA is disabled, this is for the server, for the client
> shared memory, tcp/ip, named pipes are all enabled while via is disabled
> i ran the SQL server surface area configuration and choose the Surface
> area
> configuration for servcies and connections, under there, the radio buttion
> for local and remote connection/Using TCP/IP only are selected. so i think
> that is ok
> i copi8ed a SQL database to a folder in the database and set the
> connection
> using the wizard, i tested the connection and it is ok.
> are there other things to do are other places to check,
>
>
installed during the installation, finally trying to get an sql database to
work, i am a newbie to both Visual studio and SQL, anyway i can see the
database inside server explorer and all its talbles, but when i try to run
the application i get an error has occured while establishing a connection
the the server, When connecting to SQL server 2005, this failure may be
caused by the fact that under the default settings SQL server does not allow
remote connections, (provider SQL network interfaces, error:26 error
locatiang server/instance Specified
i read similar posts in this forum and tried the following
enabled TCP/Ip on the server and client, do i need any of the other
protocols enabled: shared memory is enabled, named pipes is disabled, tcp/ip
is enablaed and VIA is disabled, this is for the server, for the client
shared memory, tcp/ip, named pipes are all enabled while via is disabled
i ran the SQL server surface area configuration and choose the Surface area
configuration for servcies and connections, under there, the radio buttion
for local and remote connection/Using TCP/IP only are selected. so i think
that is ok
i copi8ed a SQL database to a folder in the database and set the connection
using the wizard, i tested the connection and it is ok.
are there other things to do are other places to check,
Possibility 1:
Start the SQL Server Browser Service. SQL Server 2005 Express installs as a
named instance called sqlexpress. The SQL Server Browser Service resolves a
connection attempt of <computer_name>\sqlexpress to a port number. Without
SQL Server Browser, when connecting to a named instance you need to specify
the port number when you connect. And all named instances like SQL Server
2005 listen on dynamic ports, so the port may change when SQL Server is
started.
Possibility 2:
If you are running on a laptop, you may be running on Windows XP, service
pack 2 which automatically turns on the Windows firewall. If you are
connecting from the same server, you should be connecting using Shared
Memory so that won't matter. If you are connecting from another computer,
you may need to open a TCP port, or allow sqlservr.exe to communicate
through the firewall.
If this information is helpful, more information is available at
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Frank Bruhn" <FrankBruhn@.discussions.microsoft.com> wrote in message
news:E96EEA76-4277-4D80-8B75-79D945744E95@.microsoft.com...
> hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
> installed during the installation, finally trying to get an sql database
> to
> work, i am a newbie to both Visual studio and SQL, anyway i can see the
> database inside server explorer and all its talbles, but when i try to run
> the application i get an error has occured while establishing a connection
> the the server, When connecting to SQL server 2005, this failure may be
> caused by the fact that under the default settings SQL server does not
> allow
> remote connections, (provider SQL network interfaces, error:26 error
> locatiang server/instance Specified
> i read similar posts in this forum and tried the following
> enabled TCP/Ip on the server and client, do i need any of the other
> protocols enabled: shared memory is enabled, named pipes is disabled,
> tcp/ip
> is enablaed and VIA is disabled, this is for the server, for the client
> shared memory, tcp/ip, named pipes are all enabled while via is disabled
> i ran the SQL server surface area configuration and choose the Surface
> area
> configuration for servcies and connections, under there, the radio buttion
> for local and remote connection/Using TCP/IP only are selected. so i think
> that is ok
> i copi8ed a SQL database to a folder in the database and set the
> connection
> using the wizard, i tested the connection and it is ok.
> are there other things to do are other places to check,
>
>
MSDE sql express on laptop, error 26
hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
installed during the installation, finally trying to get an sql database to
work, i am a newbie to both Visual studio and SQL, anyway i can see the
database inside server explorer and all its talbles, but when i try to run
the application i get an error has occured while establishing a connection
the the server, When connecting to SQL server 2005, this failure may be
caused by the fact that under the default settings SQL server does not allow
remote connections, (provider SQL network interfaces, error:26 error
locatiang server/instance Specified
i read similar posts in this forum and tried the following
enabled TCP/Ip on the server and client, do i need any of the other
protocols enabled: shared memory is enabled, named pipes is disabled, tcp/i
p
is enablaed and VIA is disabled, this is for the server, for the client
shared memory, tcp/ip, named pipes are all enabled while via is disabled
i ran the SQL server surface area configuration and choose the Surface area
configuration for servcies and connections, under there, the radio buttion
for local and remote connection/Using TCP/IP only are selected. so i think
that is ok
i copi8ed a SQL database to a folder in the database and set the connection
using the wizard, i tested the connection and it is ok.
are there other things to do are other places to check,Possibility 1:
Start the SQL Server Browser Service. SQL Server 2005 Express installs as a
named instance called sqlexpress. The SQL Server Browser Service resolves a
connection attempt of <computer_name>\sqlexpress to a port number. Without
SQL Server Browser, when connecting to a named instance you need to specify
the port number when you connect. And all named instances like SQL Server
2005 listen on dynamic ports, so the port may change when SQL Server is
started.
Possibility 2:
If you are running on a laptop, you may be running on Windows XP, service
pack 2 which automatically turns on the Windows firewall. If you are
connecting from the same server, you should be connecting using Shared
Memory so that won't matter. If you are connecting from another computer,
you may need to open a TCP port, or allow sqlservr.exe to communicate
through the firewall.
If this information is helpful, more information is available at
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Frank Bruhn" <FrankBruhn@.discussions.microsoft.com> wrote in message
news:E96EEA76-4277-4D80-8B75-79D945744E95@.microsoft.com...
> hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
> installed during the installation, finally trying to get an sql database
> to
> work, i am a newbie to both Visual studio and SQL, anyway i can see the
> database inside server explorer and all its talbles, but when i try to run
> the application i get an error has occured while establishing a connection
> the the server, When connecting to SQL server 2005, this failure may be
> caused by the fact that under the default settings SQL server does not
> allow
> remote connections, (provider SQL network interfaces, error:26 error
> locatiang server/instance Specified
> i read similar posts in this forum and tried the following
> enabled TCP/Ip on the server and client, do i need any of the other
> protocols enabled: shared memory is enabled, named pipes is disabled,
> tcp/ip
> is enablaed and VIA is disabled, this is for the server, for the client
> shared memory, tcp/ip, named pipes are all enabled while via is disabled
> i ran the SQL server surface area configuration and choose the Surface
> area
> configuration for servcies and connections, under there, the radio buttion
> for local and remote connection/Using TCP/IP only are selected. so i think
> that is ok
> i copi8ed a SQL database to a folder in the database and set the
> connection
> using the wizard, i tested the connection and it is ok.
> are there other things to do are other places to check,
>
>
installed during the installation, finally trying to get an sql database to
work, i am a newbie to both Visual studio and SQL, anyway i can see the
database inside server explorer and all its talbles, but when i try to run
the application i get an error has occured while establishing a connection
the the server, When connecting to SQL server 2005, this failure may be
caused by the fact that under the default settings SQL server does not allow
remote connections, (provider SQL network interfaces, error:26 error
locatiang server/instance Specified
i read similar posts in this forum and tried the following
enabled TCP/Ip on the server and client, do i need any of the other
protocols enabled: shared memory is enabled, named pipes is disabled, tcp/i
p
is enablaed and VIA is disabled, this is for the server, for the client
shared memory, tcp/ip, named pipes are all enabled while via is disabled
i ran the SQL server surface area configuration and choose the Surface area
configuration for servcies and connections, under there, the radio buttion
for local and remote connection/Using TCP/IP only are selected. so i think
that is ok
i copi8ed a SQL database to a folder in the database and set the connection
using the wizard, i tested the connection and it is ok.
are there other things to do are other places to check,Possibility 1:
Start the SQL Server Browser Service. SQL Server 2005 Express installs as a
named instance called sqlexpress. The SQL Server Browser Service resolves a
connection attempt of <computer_name>\sqlexpress to a port number. Without
SQL Server Browser, when connecting to a named instance you need to specify
the port number when you connect. And all named instances like SQL Server
2005 listen on dynamic ports, so the port may change when SQL Server is
started.
Possibility 2:
If you are running on a laptop, you may be running on Windows XP, service
pack 2 which automatically turns on the Windows firewall. If you are
connecting from the same server, you should be connecting using Shared
Memory so that won't matter. If you are connecting from another computer,
you may need to open a TCP port, or allow sqlservr.exe to communicate
through the firewall.
If this information is helpful, more information is available at
http://msdn2.microsoft.com/en-us/library/ms345318(en-US,SQL.90).aspx
--
Rick Byham
MCDBA, MCSE, MCSA
Lead Technical Writer,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Frank Bruhn" <FrankBruhn@.discussions.microsoft.com> wrote in message
news:E96EEA76-4277-4D80-8B75-79D945744E95@.microsoft.com...
> hi, I am running Visual Studio.net 2005 on my laptop, MSDE sql express was
> installed during the installation, finally trying to get an sql database
> to
> work, i am a newbie to both Visual studio and SQL, anyway i can see the
> database inside server explorer and all its talbles, but when i try to run
> the application i get an error has occured while establishing a connection
> the the server, When connecting to SQL server 2005, this failure may be
> caused by the fact that under the default settings SQL server does not
> allow
> remote connections, (provider SQL network interfaces, error:26 error
> locatiang server/instance Specified
> i read similar posts in this forum and tried the following
> enabled TCP/Ip on the server and client, do i need any of the other
> protocols enabled: shared memory is enabled, named pipes is disabled,
> tcp/ip
> is enablaed and VIA is disabled, this is for the server, for the client
> shared memory, tcp/ip, named pipes are all enabled while via is disabled
> i ran the SQL server surface area configuration and choose the Surface
> area
> configuration for servcies and connections, under there, the radio buttion
> for local and remote connection/Using TCP/IP only are selected. so i think
> that is ok
> i copi8ed a SQL database to a folder in the database and set the
> connection
> using the wizard, i tested the connection and it is ok.
> are there other things to do are other places to check,
>
>
Wednesday, March 28, 2012
MSDE Setup and first database
I'm deploying MSDE with a desktop app (windows forms .net).
after installing MSDE, how do I create the database for the application?
I cannot provide a createdb.sql script to the user because there is no
queryanalyzer or similar tools.
How can I run the create query from the setup? or what is the recommended
method for doing this?
Thank You!
Hi,
Give a batch file to create the database. All you have to do is double click
the batch file. batch file should contain:-
OSQL -Usa -Ppassword -S servername -Q'Create database
dbname' -o'c:\createdb.log'
Save the command inside a .BAT file and send to client side to create the
database. Instad of giving the -Q parameter you
can also input a .SQL file which contans sequence of TSQL commands.
Thanks
Hari
SQL Server MVP
"Harley" <harleyobrienAThotmailDOTcom> wrote in message
news:E3273FC0-ADE4-47B1-9F3D-8DEC479E3341@.microsoft.com...
> I'm deploying MSDE with a desktop app (windows forms .net).
> after installing MSDE, how do I create the database for the application?
> I cannot provide a createdb.sql script to the user because there is no
> queryanalyzer or similar tools.
> How can I run the create query from the setup? or what is the recommended
> method for doing this?
> Thank You!
after installing MSDE, how do I create the database for the application?
I cannot provide a createdb.sql script to the user because there is no
queryanalyzer or similar tools.
How can I run the create query from the setup? or what is the recommended
method for doing this?
Thank You!
Hi,
Give a batch file to create the database. All you have to do is double click
the batch file. batch file should contain:-
OSQL -Usa -Ppassword -S servername -Q'Create database
dbname' -o'c:\createdb.log'
Save the command inside a .BAT file and send to client side to create the
database. Instad of giving the -Q parameter you
can also input a .SQL file which contans sequence of TSQL commands.
Thanks
Hari
SQL Server MVP
"Harley" <harleyobrienAThotmailDOTcom> wrote in message
news:E3273FC0-ADE4-47B1-9F3D-8DEC479E3341@.microsoft.com...
> I'm deploying MSDE with a desktop app (windows forms .net).
> after installing MSDE, how do I create the database for the application?
> I cannot provide a createdb.sql script to the user because there is no
> queryanalyzer or similar tools.
> How can I run the create query from the setup? or what is the recommended
> method for doing this?
> Thank You!
MSDE Setup -- Wheres the Server?
I am using VB.net to build ASP.net pages. I finally decided it was time to start using SQL server based code. So, I installed MSDE...or so I thought.
I have the server Icon in the bottom systray and it's green and seems to be running.
I have been able to use Microsoft Access' Database Upgrade Wizard to create BB.adp file.
An in VB.net I see a master.dbo connection in Server Explorer.
But I can't figure out how to access the database via the SQL server. When I right click on Server Explorer...the Create a New SQL database menu item is greyed out.
My concern is that my installation is not complete and/or I don't know how to locate and verify the server.
Any help would be appreciated. ThanksMSDN link http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde/html/msderoadmap.asp to run thru the details.
I have the server Icon in the bottom systray and it's green and seems to be running.
I have been able to use Microsoft Access' Database Upgrade Wizard to create BB.adp file.
An in VB.net I see a master.dbo connection in Server Explorer.
But I can't figure out how to access the database via the SQL server. When I right click on Server Explorer...the Create a New SQL database menu item is greyed out.
My concern is that my installation is not complete and/or I don't know how to locate and verify the server.
Any help would be appreciated. ThanksMSDN link http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde/html/msderoadmap.asp to run thru the details.
Monday, March 26, 2012
msde security...........................
I have a business directory software done in vb.net and sqlserver .We are
using msde for distribution purpose .The problem we are facing is about the
security of the data . The cd goes to common man and we are concerned about
the security of the data.Is there any option where we can ensure that the
database cannot be opened by the user . please help
..Urgent.........................
If by "common man" you mean that the database is installed on each
person's computer in their own MSDE instance, then the answer is no,
you can't prevent them from getting at the data because they are a
system administrator on that instance. If the database is located on a
server, then it is possible to implement a more robust security scheme
since users can be prevented from accessing the physical files and
from connecting as system administrators.
--Mary
On Thu, 8 Sep 2005 13:33:01 -0700, "techiebose"
<techiebose@.discussions.microsoft.com> wrote:
>I have a business directory software done in vb.net and sqlserver .We are
>using msde for distribution purpose .The problem we are facing is about the
>security of the data . The cd goes to common man and we are concerned about
>the security of the data.Is there any option where we can ensure that the
>database cannot be opened by the user . please help
>.Urgent.........................
sql
using msde for distribution purpose .The problem we are facing is about the
security of the data . The cd goes to common man and we are concerned about
the security of the data.Is there any option where we can ensure that the
database cannot be opened by the user . please help
..Urgent.........................
If by "common man" you mean that the database is installed on each
person's computer in their own MSDE instance, then the answer is no,
you can't prevent them from getting at the data because they are a
system administrator on that instance. If the database is located on a
server, then it is possible to implement a more robust security scheme
since users can be prevented from accessing the physical files and
from connecting as system administrators.
--Mary
On Thu, 8 Sep 2005 13:33:01 -0700, "techiebose"
<techiebose@.discussions.microsoft.com> wrote:
>I have a business directory software done in vb.net and sqlserver .We are
>using msde for distribution purpose .The problem we are facing is about the
>security of the data . The cd goes to common man and we are concerned about
>the security of the data.Is there any option where we can ensure that the
>database cannot be opened by the user . please help
>.Urgent.........................
sql
MSDE ReleaseA
Can i redistribute only osql.exe with my asp.net application
we are using licensed Install Shield for packaging..
we use this osql.exe for creating and setup database...
regards
sahridhayan
hi,
sahridhayan wrote:
> Can i redistribute only osql.exe with my asp.net application
> we are using licensed Install Shield for packaging..
> we use this osql.exe for creating and setup database...
I do not think you can separate oSql.exe from the full MSDE package from a
legal point of view..
but perhaps you've better ask Microsoft representatives...
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
|||I'm not sure about MSDE, but if you have a SQL Server license you can
distribute OSQL. Refer to REDIST.TXT for a listing of all the
redistributable components of SQL Server.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h5uarFf6jcoU1@.individual.net...
> hi,
> sahridhayan wrote:
> I do not think you can separate oSql.exe from the full MSDE package from a
> legal point of view..
> but perhaps you've better ask Microsoft representatives...
> --
> 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
>
|||hi,
Desperado wrote:
> I'm not sure about MSDE, but if you have a SQL Server license you can
> distribute OSQL. Refer to REDIST.TXT for a listing of all the
> redistributable components of SQL Server.
>
again, I'm not sure you can "cannibalize" osql.exe that way... of course,
having a full SQL Server licence, you can install the Client Tools, that
include quiet all tools... but this way I'm little skeptic... but I'm not a
lawyer
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
we are using licensed Install Shield for packaging..
we use this osql.exe for creating and setup database...
regards
sahridhayan
hi,
sahridhayan wrote:
> Can i redistribute only osql.exe with my asp.net application
> we are using licensed Install Shield for packaging..
> we use this osql.exe for creating and setup database...
I do not think you can separate oSql.exe from the full MSDE package from a
legal point of view..
but perhaps you've better ask Microsoft representatives...
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
|||I'm not sure about MSDE, but if you have a SQL Server license you can
distribute OSQL. Refer to REDIST.TXT for a listing of all the
redistributable components of SQL Server.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3h5uarFf6jcoU1@.individual.net...
> hi,
> sahridhayan wrote:
> I do not think you can separate oSql.exe from the full MSDE package from a
> legal point of view..
> but perhaps you've better ask Microsoft representatives...
> --
> 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
>
|||hi,
Desperado wrote:
> I'm not sure about MSDE, but if you have a SQL Server license you can
> distribute OSQL. Refer to REDIST.TXT for a listing of all the
> redistributable components of SQL Server.
>
again, I'm not sure you can "cannibalize" osql.exe that way... of course,
having a full SQL Server licence, you can install the Client Tools, that
include quiet all tools... but this way I'm little skeptic... but I'm not a
lawyer
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
Friday, March 23, 2012
MSDE prototyping
I haven't used MSDE yet. Does it run with an Enterprise Manager & Sql analyser interface?
I'm working on an asp.net vb project using sql2000. Users request me to create a protype for their review and training use. Can I deploy my project with only dlls forthe front end and an MSDE backend created from a script of the original Sql2000 database? Is there any potential discrepacy or problem with my prototyping plan? How can I copy my original database from sql2000 to msde?
I'm working on an asp.net vb project using sql2000. Users request me to create a protype for their review and training use. Can I deploy my project with only dlls forthe front end and an MSDE backend created from a script of the original Sql2000 database? Is there any potential discrepacy or problem with my prototyping plan? How can I copy my original database from sql2000 to msde?
Thanks for any help.Yes, Enterprise Manager and Query Analyzer can be interfaces to MSDE.
Yes, you can use MSDE as the back end for development but deploy to a SQL Server 2000 database.
When I mean "can" I mean "technically possible". I am not 100% sure of "legally possible". The licensing information for MSDE is fairly confusion, IMO.
The SQL Server 2000 Developer's edition is made specifically for situations like yours. It is $49.95 US and would give you the EM and QA tools plus the database. SeeDevelopment Edition Licensing.
I think the best way to transfer the data and schema would be to restore a backup.
Terri
MSDE Performance Governor - knowing when its kicked in
I'm working on a VB.NET project where we are intending to use MSDE as our
back-end database. The actual number of users is expected to be low and I
don't have any concerns as to whether MSDE will be up to the job (most of
the time). I'm aware that if we end up with lots of users connecting to our
site at once (which may happen as certain times in the year when people need
information for deadlines) then the performance governor in MSDE will kick
in and slow everything down.
back-end database. The actual number of users is expected to be low and I
don't have any concerns as to whether MSDE will be up to the job (most of
the time). I'm aware that if we end up with lots of users connecting to our
site at once (which may happen as certain times in the year when people need
information for deadlines) then the performance governor in MSDE will kick
in and slow everything down.
What I don't know is how do I find out whether the performance governor has
kicked in?
I would like to know how to monitor this so we can make an educated decision
as to when we need to migrate to a full version of SQL Server (if at all).
Can anyone point me in the right direction for finding this out?
thanks,
Brian Cryer."Brian Cryer" <brianc@.127.0.0.1.activesol.co.uk> wrote in message
news:1106559318.8377.0@.damia.uk.clara.net...
> I'm working on a VB.NET project where we are intending to use MSDE as our
> back-end database. The actual number of users is expected to be low and I
> don't have any concerns as to whether MSDE will be up to the job (most of
> the time). I'm aware that if we end up with lots of users connecting to
> our
> site at once (which may happen as certain times in the year when people
> need
> information for deadlines) then the performance governor in MSDE will kick
> in and slow everything down.
> What I don't know is how do I find out whether the performance governor
> has
> kicked in?
> I would like to know how to monitor this so we can make an educated
> decision
> as to when we need to migrate to a full version of SQL Server (if at all).
> Can anyone point me in the right direction for finding this out?
> thanks,
> Brian Cryer.
Check out DBCC CONCURRENCYVIOLATION in Books Online. If you don't already
have the latest version of BOL, then you should download it, as it has more
detailed information about MSDE and the workload governor that wasn't in
previous versions.
Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:41f4c703$1_1@.news.bluewin.ch...
> "Brian Cryer" <brianc@.127.0.0.1.activesol.co.uk> wrote in message
> news:1106559318.8377.0@.damia.uk.clara.net...
> > I'm working on a VB.NET project where we are intending to use MSDE as
our
> > back-end database. The actual number of users is expected to be low and
I
> > don't have any concerns as to whether MSDE will be up to the job (most
of
> > the time). I'm aware that if we end up with lots of users connecting to
> > our
> > site at once (which may happen as certain times in the year when people
> > need
> > information for deadlines) then the performance governor in MSDE will
kick
> > in and slow everything down.
> > What I don't know is how do I find out whether the performance governor
> > has
> > kicked in?
> > I would like to know how to monitor this so we can make an educated
> > decision
> > as to when we need to migrate to a full version of SQL Server (if at
all).
> > Can anyone point me in the right direction for finding this out?
> > thanks,
> > Brian Cryer.
> Check out DBCC CONCURRENCYVIOLATION in Books Online. If you don't already
> have the latest version of BOL, then you should download it, as it has
more
> detailed information about MSDE and the workload governor that wasn't in
> previous versions.
> Simon
Excellent Simon. Just what I was after.
Many Thanks.
Brian.
MSDE package doesn't work on win 98
I created a install shield package on windows 98 using the
MSDE merge modules with vb .net. It works fine on 2000 and
xp but on windows 98 it give an ambiguous error: "Error
1723. Theres a problem with this windows installer
package. A DLL required for this installation to complete
could not be run."
This happenes as soon as I click on the msi file. Or if I
click the setup file then after a couple checks and when
setup tryes running the msi file.
Anyone have any ideas what it could be? Which dlls? Which
merge modules could be missing?
Any help would greatly appreciated. I've lost some hair
over this one.
You probably don't have any version of MDAC installed on the Win98 system.
Make MDAC a dependency of your install and install it first if needed before
going forward.
J
"MSDE" <Sebastian@.ilogic.com> wrote in message
news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
> I created a install shield package on windows 98 using the
> MSDE merge modules with vb .net. It works fine on 2000 and
> xp but on windows 98 it give an ambiguous error: "Error
> 1723. Theres a problem with this windows installer
> package. A DLL required for this installation to complete
> could not be run."
> This happenes as soon as I click on the msi file. Or if I
> click the setup file then after a couple checks and when
> setup tryes running the msi file.
> Anyone have any ideas what it could be? Which dlls? Which
> merge modules could be missing?
> Any help would greatly appreciated. I've lost some hair
> over this one.
|||The other problems we've found with Win98 are if file sharing isn't enabled
or if the Windows Family Logon is enabled.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:O3HnrMrnEHA.132@.TK2MSFTNGP09.phx.gbl...
> You probably don't have any version of MDAC installed on the Win98 system.
> Make MDAC a dependency of your install and install it first if needed
before
> going forward.
> J
> "MSDE" <Sebastian@.ilogic.com> wrote in message
> news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
>
MSDE merge modules with vb .net. It works fine on 2000 and
xp but on windows 98 it give an ambiguous error: "Error
1723. Theres a problem with this windows installer
package. A DLL required for this installation to complete
could not be run."
This happenes as soon as I click on the msi file. Or if I
click the setup file then after a couple checks and when
setup tryes running the msi file.
Anyone have any ideas what it could be? Which dlls? Which
merge modules could be missing?
Any help would greatly appreciated. I've lost some hair
over this one.
You probably don't have any version of MDAC installed on the Win98 system.
Make MDAC a dependency of your install and install it first if needed before
going forward.
J
"MSDE" <Sebastian@.ilogic.com> wrote in message
news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
> I created a install shield package on windows 98 using the
> MSDE merge modules with vb .net. It works fine on 2000 and
> xp but on windows 98 it give an ambiguous error: "Error
> 1723. Theres a problem with this windows installer
> package. A DLL required for this installation to complete
> could not be run."
> This happenes as soon as I click on the msi file. Or if I
> click the setup file then after a couple checks and when
> setup tryes running the msi file.
> Anyone have any ideas what it could be? Which dlls? Which
> merge modules could be missing?
> Any help would greatly appreciated. I've lost some hair
> over this one.
|||The other problems we've found with Win98 are if file sharing isn't enabled
or if the Windows Family Logon is enabled.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim Young" <thorium48@.hotmail.com> wrote in message
news:O3HnrMrnEHA.132@.TK2MSFTNGP09.phx.gbl...
> You probably don't have any version of MDAC installed on the Win98 system.
> Make MDAC a dependency of your install and install it first if needed
before
> going forward.
> J
> "MSDE" <Sebastian@.ilogic.com> wrote in message
> news:1ebc01c49a69$81a56400$a301280a@.phx.gbl...
>
Wednesday, March 21, 2012
MSDE or VS.NET Problem
I recently installed a named MSDE instance and created a DB with SQLDMO. I can see the instance in VS.NET, but can't see the tables that SQLDMO created. When I rerun the script to create the tables, I get a SQL Server ODBC driver error saying the tables already exist. I have tried restarting the machine and the services, but still can't see the tables in VS.NET. The other strange thing is I also can't load data into the tables because SQLDMO says my tables are not in the Tables collection. I didn't get any errors when I originally ran the script that created my tables. When I checked the SQL log, I didn't see any errors, but also didn't see anything indicating the tables were created. Would SQL Server have logged this?
Please copy an replies to pearsonbe@.aol.com.Can you check if the SQLDMO statements used the same login as you are using to view the contents of the database? Do you use the correct name for the tables (server.database.owner.tablename)?|||Yes, I'm using the same login info in the code w/SQLDMO as well as when connecting in Visual Studio. For some reason, the ExecuteImmediate does not work with the DB script that was produced by my SQLDMO DB object. I was able to create a new table in VS and then delete it with SQLDMO, so my current workaround is to just deatch the original DB and reattach to the new DB.
Thanks.
Please copy an replies to pearsonbe@.aol.com.Can you check if the SQLDMO statements used the same login as you are using to view the contents of the database? Do you use the correct name for the tables (server.database.owner.tablename)?|||Yes, I'm using the same login info in the code w/SQLDMO as well as when connecting in Visual Studio. For some reason, the ExecuteImmediate does not work with the DB script that was produced by my SQLDMO DB object. I was able to create a new table in VS and then delete it with SQLDMO, so my current workaround is to just deatch the original DB and reattach to the new DB.
Thanks.
MSDE or SQLServer Express
Hi
In our vb.net application we are using sqlserver2000 database. we are
planning to move to another free database engines.I have few queries.
1.in MSDE or SQLServer Express which one i have to select
2.Where can i get the documentation of how to dump my database in those
because those don't have a User interface.
3.can i redistribute those databases
4.can i access those stored in another system in a network.
5.what if 2 or 3 application directly accessing that at the same time.
hope i delivered my question properly.any help is appreciable
-regards
GRK
Hi Andrea ,
Thank you very much for your suggestion.I'll check the links you have
sent and come back to you with other queries.Thanks a lot
-GRK
"Andrea Montanari" wrote:
> hi,
> GRK wrote:
> SQLExpress is newer than MSDE, and MSDE will not be supported on Vista
> platform..
> I'd go for SQLExpress as it will be better supported anyway..
> for SQLExpress you can freely download the "official" management tool, SQL
> Server Management Studio Express at
> http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
> for MSDE there's no official graphical tool available, but you can have a
> look at a free prj of mine, DbaMgr2k, available at
> http://www.asql.biz/en/DbaMgr.aspx
> both engines are free to use.. you have to freely register for distribution
> if you plan to;
> SQLExpress: http://go.microsoft.com/fwlink/?LinkId=64062
> MSDE :
> http://www.microsoft.com/sql/prodinfo/previousversions/msde/redistregister.mspx
> yes... you have to enable remote connections as, by default, both products
> disable network protocols at installation time.. you can modify this
> behaviour both at install time and later, at "runtime"..
> SQL Server is full client/server database engine.. it will handle that
> appropriately :D
> but you have to deal with concurrency scenarios in your apps..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||Small Doubt Mr Andrea,
I'm using visual studio.net 2003 is it compatible when i install
ServerExpress
-GRK
"Andrea Montanari" wrote:
> hi,
> GRK wrote:
> SQLExpress is newer than MSDE, and MSDE will not be supported on Vista
> platform..
> I'd go for SQLExpress as it will be better supported anyway..
> for SQLExpress you can freely download the "official" management tool, SQL
> Server Management Studio Express at
> http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
> for MSDE there's no official graphical tool available, but you can have a
> look at a free prj of mine, DbaMgr2k, available at
> http://www.asql.biz/en/DbaMgr.aspx
> both engines are free to use.. you have to freely register for distribution
> if you plan to;
> SQLExpress: http://go.microsoft.com/fwlink/?LinkId=64062
> MSDE :
> http://www.microsoft.com/sql/prodinfo/previousversions/msde/redistregister.mspx
> yes... you have to enable remote connections as, by default, both products
> disable network protocols at installation time.. you can modify this
> behaviour both at install time and later, at "runtime"..
> SQL Server is full client/server database engine.. it will handle that
> appropriately :D
> but you have to deal with concurrency scenarios in your apps..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
In our vb.net application we are using sqlserver2000 database. we are
planning to move to another free database engines.I have few queries.
1.in MSDE or SQLServer Express which one i have to select
2.Where can i get the documentation of how to dump my database in those
because those don't have a User interface.
3.can i redistribute those databases
4.can i access those stored in another system in a network.
5.what if 2 or 3 application directly accessing that at the same time.
hope i delivered my question properly.any help is appreciable
-regards
GRK
Hi Andrea ,
Thank you very much for your suggestion.I'll check the links you have
sent and come back to you with other queries.Thanks a lot
-GRK
"Andrea Montanari" wrote:
> hi,
> GRK wrote:
> SQLExpress is newer than MSDE, and MSDE will not be supported on Vista
> platform..
> I'd go for SQLExpress as it will be better supported anyway..
> for SQLExpress you can freely download the "official" management tool, SQL
> Server Management Studio Express at
> http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
> for MSDE there's no official graphical tool available, but you can have a
> look at a free prj of mine, DbaMgr2k, available at
> http://www.asql.biz/en/DbaMgr.aspx
> both engines are free to use.. you have to freely register for distribution
> if you plan to;
> SQLExpress: http://go.microsoft.com/fwlink/?LinkId=64062
> MSDE :
> http://www.microsoft.com/sql/prodinfo/previousversions/msde/redistregister.mspx
> yes... you have to enable remote connections as, by default, both products
> disable network protocols at installation time.. you can modify this
> behaviour both at install time and later, at "runtime"..
> SQL Server is full client/server database engine.. it will handle that
> appropriately :D
> but you have to deal with concurrency scenarios in your apps..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||Small Doubt Mr Andrea,
I'm using visual studio.net 2003 is it compatible when i install
ServerExpress
-GRK
"Andrea Montanari" wrote:
> hi,
> GRK wrote:
> SQLExpress is newer than MSDE, and MSDE will not be supported on Vista
> platform..
> I'd go for SQLExpress as it will be better supported anyway..
> for SQLExpress you can freely download the "official" management tool, SQL
> Server Management Studio Express at
> http://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
> for MSDE there's no official graphical tool available, but you can have a
> look at a free prj of mine, DbaMgr2k, available at
> http://www.asql.biz/en/DbaMgr.aspx
> both engines are free to use.. you have to freely register for distribution
> if you plan to;
> SQLExpress: http://go.microsoft.com/fwlink/?LinkId=64062
> MSDE :
> http://www.microsoft.com/sql/prodinfo/previousversions/msde/redistregister.mspx
> yes... you have to enable remote connections as, by default, both products
> disable network protocols at installation time.. you can modify this
> behaviour both at install time and later, at "runtime"..
> SQL Server is full client/server database engine.. it will handle that
> appropriately :D
> but you have to deal with concurrency scenarios in your apps..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
MSDE on machine with SQL Server
Hello,
A named instance of MSDE will be installed on our clients machines along with our VB.Net during the installation. Will this work fine even if the client already has SQL Server on his/her machine. I mean will the installation of named instance of MSDE wor
k smoothly even if SQL Server already exists. If yes, then does that apply for both SQL Server 7 & 2000. If no, then what should I do.
Thanks
dev
You should have no problems, as long as you are installing a uniquely named
instance. This is true even if SQL Server 7 is already installed on the
system.
Jim
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:B46C4961-748E-47E1-AD22-2A712100428F@.microsoft.com...
> Hello,
> A named instance of MSDE will be installed on our clients machines along
with our VB.Net during the installation. Will this work fine even if the
client already has SQL Server on his/her machine. I mean will the
installation of named instance of MSDE work smoothly even if SQL Server
already exists. If yes, then does that apply for both SQL Server 7 & 2000.
If no, then what should I do.
> Thanks
> dev
sql
A named instance of MSDE will be installed on our clients machines along with our VB.Net during the installation. Will this work fine even if the client already has SQL Server on his/her machine. I mean will the installation of named instance of MSDE wor
k smoothly even if SQL Server already exists. If yes, then does that apply for both SQL Server 7 & 2000. If no, then what should I do.
Thanks
dev
You should have no problems, as long as you are installing a uniquely named
instance. This is true even if SQL Server 7 is already installed on the
system.
Jim
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:B46C4961-748E-47E1-AD22-2A712100428F@.microsoft.com...
> Hello,
> A named instance of MSDE will be installed on our clients machines along
with our VB.Net during the installation. Will this work fine even if the
client already has SQL Server on his/her machine. I mean will the
installation of named instance of MSDE work smoothly even if SQL Server
already exists. If yes, then does that apply for both SQL Server 7 & 2000.
If no, then what should I do.
> Thanks
> dev
sql
MSDE not showing up in SQLDMO.ListAvailableServers
I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave Taylor
I had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...[vbcol=seagreen]
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,
> it
>
|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was[vbcol=seagreen]
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not
> on
> MSDE
> machine,
>
|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
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
|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> logic
broadcasts,[vbcol=seagreen]
> have
of
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>
|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
sql
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave Taylor
I had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...[vbcol=seagreen]
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,
> it
>
|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was[vbcol=seagreen]
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not
> on
> MSDE
> machine,
>
|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
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
|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> logic
broadcasts,[vbcol=seagreen]
> have
of
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>
|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
sql
MSDE not showing up in SQLDMO.ListAvailableServers
I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave Taylor
I had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...[vbcol=seagreen]
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,
> it
>
|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was[vbcol=seagreen]
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not
> on
> MSDE
> machine,
>
|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
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
|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> logic
broadcasts,[vbcol=seagreen]
> have
of
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>
|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave Taylor
I had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...[vbcol=seagreen]
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,
> it
>
|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was[vbcol=seagreen]
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not
> on
> MSDE
> machine,
>
|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
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
|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> logic
broadcasts,[vbcol=seagreen]
> have
of
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>
|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
MSDE not showing up in SQLDMO.ListAvailableServers
I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave Taylor
I had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...[vbcol=seagreen]
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,
> it
>
|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was[vbcol=seagreen]
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not
> on
> MSDE
> machine,
>
|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
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
|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> logic
broadcasts,[vbcol=seagreen]
> have
of
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>
|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave Taylor
I had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...[vbcol=seagreen]
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,
> it
>
|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was[vbcol=seagreen]
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not
> on
> MSDE
> machine,
>
|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.n et...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQLServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
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
|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> logic
broadcasts,[vbcol=seagreen]
> have
of
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, MySQL & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>
|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
MSDE not showing up in SQLDMO.ListAvailableServers
I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave TaylorI had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.net...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,[vbcol=seagreen]
> it
>|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopD...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.net...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not[vbcol=seagreen]
> on
> MSDE
> machine,
>|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.net...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
--
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
--
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|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, mysql & MS SQL
Server.
Upscene Productions
http://www.upscene.com|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...
>
> logic
broadcasts,[vbcol=seagreen]
> have
of[vbcol=seagreen]
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, mysql & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
server. I installed a copy of MSDE on the users' machine (this machine did
not have MSDE previously so it was a new copy including latest SP3), then
installed my app. When I start my app, the local computer name does not
show up in the list of available servers. This has happened twice now on
separate machines. Is there something I need to do after installing MSDE
for it to register as a server? Note: I know MSDE is installed and running
because my app creates and properly fills databases on the local machine, it
just doesnt show up in the list of available servers.
Thanks
Dave TaylorI had the same problem. SQL-DMO does two things when it enumerates SQL
Servers:
1. It creates a list of SQL Servers using the Win32 API NetServerEnum
function
2. It creates a list of SQL Servers that respond to a broadcast on Port
1433
3. It combines these two lists.
If you're not connected to a network, NetServerEnum doesn't seem to return
any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
won't pick up the broadcast. If you're just trying to enumerate the LOCAL
MSDE instance(s), you can read the registry subkeys under
HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer and
HKLM\Software\Microsoft\Microsoft SQL Server.
If anyone out there knows of a function that can be used to return named
instances of MSDE, I'd appreciate the info.
Thanks,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>|||Michael,
Thanks for the reply and info. At least now I know it isn't something I was
doing wrong.
I'll use your registry workaround for the local info.
Thanks again
Dave Taylor
"Michael C" <michaelc@.nospam.org> wrote in message
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.net...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
> Thanks,
> Michael C.
>
> "Dave Taylor" <nospam_dave@.processeng.com> wrote in message
> news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
available[vbcol=seagreen]
> did
then[vbcol=seagreen]
on[vbcol=seagreen]
MSDE[vbcol=seagreen]
> running
machine,[vbcol=seagreen]
> it
>|||No problem. I just found a website that has a utility for retrieving all
SQL Server information from all computers on a specified subnet via a UDP
packet sent to Port 1434. I tested it on my home network (I don't have MSDE
installed right now though). It might be another way to go... but right
now I'm not sure if it's robust enough for my purposes. Anyway, here's the
link http://www.sqlsecurity.com/DesktopD...aspx?tabid=26. (One version
includes C# source code). If you do try the SQLPing utility, please let me
know if it returns MSDE info. also.
Enjoy,
Michael C.
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:%234E8NcadEHA.3392@.tk2msftngp13.phx.gbl...
> Michael,
> Thanks for the reply and info. At least now I know it isn't something I
was
> doing wrong.
> I'll use your registry workaround for the local info.
> Thanks again
> Dave Taylor
> "Michael C" <michaelc@.nospam.org> wrote in message
> news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.net...
return[vbcol=seagreen]
LOCAL[vbcol=seagreen]
> available
machine[vbcol=seagreen]
> then
not[vbcol=seagreen]
> on
> MSDE
> machine,
>|||hi Michael,
"Michael C" <michaelc@.nospam.org> ha scritto nel messaggio
news:oicOc.19466$oE1.1984378@.news4.srv.hcvlny.cv.net...
> I had the same problem. SQL-DMO does two things when it enumerates SQL
> Servers:
> 1. It creates a list of SQL Servers using the Win32 API NetServerEnum
> function
> 2. It creates a list of SQL Servers that respond to a broadcast on Port
> 1433
> 3. It combines these two lists.
> If you're not connected to a network, NetServerEnum doesn't seem to return
> any SQL Servers. MSDE runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast. If you're just trying to enumerate the LOCAL
> MSDE instance(s), you can read the registry subkeys under
> HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer and
> HKLM\Software\Microsoft\Microsoft SQL Server.
> If anyone out there knows of a function that can be used to return named
> instances of MSDE, I'd appreciate the info.
SQL-DMO 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.
next problem will be WinXP sp 2 firewall, which will default closing all
ports so that single ports must be manually open by the user in order to
allow network connections... this will defeat dynamic TCP/IP allocation as
you should rely on static assignement for Named instances too...
further method to enlist SQL Server instances available on the LAN can be
found at http://www.sqldev.net/misc/EnumSQLSvr.htm ,
http://www.sqldev.net/misc/ListSQLSvr.htm and
http://www.sqldev.net/misc/OleDbEnum.htm
--
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 runs on Port 1434 instead of 1433, which means it
> won't pick up the broadcast.
default instance always default on port 1433 TCP/IP, while UDP1434 is used
(if network protocols have been enabled) for dynamic named instances
listening in order to redirect to the appropriate TCP/IP dialog port
--
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|||
> 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.
Then again, you might want to quit using SQL-DMO for this,
as Yukon removes SQL-DMO again :-(
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, mysql & MS SQL
Server.
Upscene Productions
http://www.upscene.com|||Yukon does not remove DMO, it replaces the 2000 version with DMO9. It does
add a new API called SMO which is the new management API going fwds.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martijn Tonies" <m.tonies@.upscene-remove-.com> wrote in message
news:ucF3#QbdEHA.3864@.TK2MSFTNGP10.phx.gbl...
>
> logic
broadcasts,[vbcol=seagreen]
> have
of[vbcol=seagreen]
> Then again, you might want to quit using SQL-DMO for this,
> as Yukon removes SQL-DMO again :-(
> --
> With regards,
> Martijn Tonies
> Database Workbench - developer tool for InterBase, Firebird, mysql & MS
SQL
> Server.
> Upscene Productions
> http://www.upscene.com
>|||Dave,
Note that the current MSDE (2000RevA) install disables the network
connections by default. You will have to enable them using the svmetcn.exe
in the 80\Tools\Binn directory under the install directory. This was
supplied by the current install and I now have my MSDE responding to network
queries on port 1433.
You can also just put '(local)' in as the server name and you should get
a connection locally.
Ron Allen
"Dave Taylor" <nospam_dave@.processeng.com> wrote in message
news:OtXGtZZdEHA.3944@.tk2msftngp13.phx.gbl...
> I have a VB.NET app using MSDE and the SQL-DMO to get a list of available
> server. I installed a copy of MSDE on the users' machine (this machine
did
> not have MSDE previously so it was a new copy including latest SP3), then
> installed my app. When I start my app, the local computer name does not
> show up in the list of available servers. This has happened twice now on
> separate machines. Is there something I need to do after installing MSDE
> for it to register as a server? Note: I know MSDE is installed and
running
> because my app creates and properly fills databases on the local machine,
it
> just doesnt show up in the list of available servers.
> Thanks
> Dave Taylor
>
Monday, March 19, 2012
MSDE Not Connected
Hi,
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?Try running the SVRNETCN.exe tool to find out what protocols MSDE is using. I had a similar problem (not with .NET) and found that NO protocols were selected. Ergo, no connection possible.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe
-- Steve
Originally posted by ericscat
Hi,
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?|||Hi,
Thanks I ran it and restarted the MSSQL$VSDOTNET service, but I
don't see any change. Sorry I don't know much of this. Your right
there were no protocols selected so I enabled TCP/IP. What is the
SQLAgent$VSDOTNET service? It's setup as a Manual startup.
Any more tips? I would assume that when I installed MSDE and
setup the instance that I would see the small green right pointing
arrow in the Service Manager icon. The Manager still says Not Connected.
??|||Sorry,
I rebooted and got an automatic connection/Sql Server Service
started.
Thanks for your help.
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?Try running the SVRNETCN.exe tool to find out what protocols MSDE is using. I had a similar problem (not with .NET) and found that NO protocols were selected. Ergo, no connection possible.
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\SVRNETCN.exe
-- Steve
Originally posted by ericscat
Hi,
I installed MSDE 2000 SP3 to use the ASP.NET QuickStart samples on
my Windows 2000 machine. I ran
setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1 SAPWD<my password>
I then ran the QuickStart installer.
These steps were documented by MS.
But when I rebooted, the SQL Service Manager was 'Not Connected'
and the circle in front of the server icon was blank/white. Also the QuickStart samples that connect to MSDE won't and give errors like 'System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.' or '...Login failed for user '<my server name>\ASPNET'
When I run 'osql -E -S <my server name>\VSDOTNET' command I get '1>'. So there is a connection that's possible. Also the MSSQL$VSDOTNET is Started.
Any suggestions?|||Hi,
Thanks I ran it and restarted the MSSQL$VSDOTNET service, but I
don't see any change. Sorry I don't know much of this. Your right
there were no protocols selected so I enabled TCP/IP. What is the
SQLAgent$VSDOTNET service? It's setup as a Manual startup.
Any more tips? I would assume that when I installed MSDE and
setup the instance that I would see the small green right pointing
arrow in the Service Manager icon. The Manager still says Not Connected.
??|||Sorry,
I rebooted and got an automatic connection/Sql Server Service
started.
Thanks for your help.
MSDE merge modules
Hi
I wonder if anyone can help. I am looking for the MSDE merge modules to use
in a .net 2003 set up and deployment module. see
http://support.microsoft.com/kb/325004/EN-US/
However I have already installed SQL server standard edition on my
development server. How do I get these MSM's to merge into my MSI? Am I
barking up the wrong tree?
Thanking you in advance for any help
Richard
Hello,
Personally, I use the last setup of msde (sql2000.msi and I launch it
from my setup with a custom action.)
With that, I don't need to use the merge modules and if a custommer want
to use SQL Server instead, I don't need to change my setup (I don't need
to install MSDE and just connect to sql server and it will work.)
I can give all the parameters to msiexec (or to the property table of
the msi).
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I wonder if anyone can help. I am looking for the MSDE merge modules to use
> in a .net 2003 set up and deployment module. see
> http://support.microsoft.com/kb/325004/EN-US/
> However I have already installed SQL server standard edition on my
> development server. How do I get these MSM's to merge into my MSI? Am I
> barking up the wrong tree?
> Thanking you in advance for any help
> Richard
>
|||Hi
I am interested in how you do this. You suggest that you can supply the
paramters to msiexec or the property table of MSI? Please can you point me
in the right direction.
After the instance has been created how do you then create the database and
insert any data?
Thank you for your help so far.
Richard
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...[vbcol=seagreen]
> Hello,
> Personally, I use the last setup of msde (sql2000.msi and I launch it from
> my setup with a custom action.)
> With that, I don't need to use the merge modules and if a custommer want
> to use SQL Server instead, I don't need to change my setup (I don't need
> to install MSDE and just connect to sql server and it will work.)
> I can give all the parameters to msiexec (or to the property table of the
> msi).
> Marc Allard
> Allcomp
> Richard Wilde wrote:
|||Hello,
Here is how I do that ...
1) Create a
property MSIExecPos
Value : msiexec
in the table property of the msi file (or the merge module)
2) Create a custom action
InstallMsde
Type : 114 (to ignore the return code because in Win98 sometimes the
return code is not 0 so you have problems).
source : MsiExecPos
Target
/i "MSDE\Sql2000.msi" /qb /l c:\msde.log
Personally, I put the full MSDE installation directory into a sub
directory MSDE so the root of my CD is cleaner
3) In the InstallUISequence (you have tu use InstallUISequence or the
installation won't work)
You add the action
InstallMsde
You can put a install condition or not
For the sequence, you put something in the end (1305 in my case).
After that, you can change the parameters of the MSDE file
In the property table, you put
REBOOT Value : ReallySuppress
to avoid a reboot prompt after the installation of MSDE
INSTANCENAME value : NameofYourInstance
I believe that it is necessary because if a custommer has already MSDE
installed, then you will run into very big problems to install your software
DISABLENETWORKPROTOCOLSValue : 0
If you don't do it, your server will only work locally.
SqlSaPwdValue : YourPassword
I think it is better to pass it directly in the custom action instead of
the property table.
Normally with that, all should be fine
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I am interested in how you do this. You suggest that you can supply the
> paramters to msiexec or the property table of MSI? Please can you point me
> in the right direction.
> After the instance has been created how do you then create the database and
> insert any data?
> Thank you for your help so far.
> Richard
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...
>
>
I wonder if anyone can help. I am looking for the MSDE merge modules to use
in a .net 2003 set up and deployment module. see
http://support.microsoft.com/kb/325004/EN-US/
However I have already installed SQL server standard edition on my
development server. How do I get these MSM's to merge into my MSI? Am I
barking up the wrong tree?
Thanking you in advance for any help
Richard
Hello,
Personally, I use the last setup of msde (sql2000.msi and I launch it
from my setup with a custom action.)
With that, I don't need to use the merge modules and if a custommer want
to use SQL Server instead, I don't need to change my setup (I don't need
to install MSDE and just connect to sql server and it will work.)
I can give all the parameters to msiexec (or to the property table of
the msi).
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I wonder if anyone can help. I am looking for the MSDE merge modules to use
> in a .net 2003 set up and deployment module. see
> http://support.microsoft.com/kb/325004/EN-US/
> However I have already installed SQL server standard edition on my
> development server. How do I get these MSM's to merge into my MSI? Am I
> barking up the wrong tree?
> Thanking you in advance for any help
> Richard
>
|||Hi
I am interested in how you do this. You suggest that you can supply the
paramters to msiexec or the property table of MSI? Please can you point me
in the right direction.
After the instance has been created how do you then create the database and
insert any data?
Thank you for your help so far.
Richard
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...[vbcol=seagreen]
> Hello,
> Personally, I use the last setup of msde (sql2000.msi and I launch it from
> my setup with a custom action.)
> With that, I don't need to use the merge modules and if a custommer want
> to use SQL Server instead, I don't need to change my setup (I don't need
> to install MSDE and just connect to sql server and it will work.)
> I can give all the parameters to msiexec (or to the property table of the
> msi).
> Marc Allard
> Allcomp
> Richard Wilde wrote:
|||Hello,
Here is how I do that ...
1) Create a
property MSIExecPos
Value : msiexec
in the table property of the msi file (or the merge module)
2) Create a custom action
InstallMsde
Type : 114 (to ignore the return code because in Win98 sometimes the
return code is not 0 so you have problems).
source : MsiExecPos
Target
/i "MSDE\Sql2000.msi" /qb /l c:\msde.log
Personally, I put the full MSDE installation directory into a sub
directory MSDE so the root of my CD is cleaner
3) In the InstallUISequence (you have tu use InstallUISequence or the
installation won't work)
You add the action
InstallMsde
You can put a install condition or not
For the sequence, you put something in the end (1305 in my case).
After that, you can change the parameters of the MSDE file
In the property table, you put
REBOOT Value : ReallySuppress
to avoid a reboot prompt after the installation of MSDE
INSTANCENAME value : NameofYourInstance
I believe that it is necessary because if a custommer has already MSDE
installed, then you will run into very big problems to install your software
DISABLENETWORKPROTOCOLSValue : 0
If you don't do it, your server will only work locally.
SqlSaPwdValue : YourPassword
I think it is better to pass it directly in the custom action instead of
the property table.
Normally with that, all should be fine
Marc Allard
Allcomp
Richard Wilde wrote:
> Hi
> I am interested in how you do this. You suggest that you can supply the
> paramters to msiexec or the property table of MSI? Please can you point me
> in the right direction.
> After the instance has been created how do you then create the database and
> insert any data?
> Thank you for your help so far.
> Richard
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e4d0e0$0$329$ba620e4c@.news.skynet.be...
>
>
Subscribe to:
Posts (Atom)