MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack ye
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE setup problems

I am attempting to install SharePoint Services (with
MSDE) using all standard/default options. The WSS setup
appears to proceed normally until it attempts to
configure the MSDE. This portion of the WSS setup fails
and I receive the following error message:
MICROSFOT SQL SERVER DESKTOP ENGINE
Setup failed to configure the server. Refer to the server
error logs and setup error logs for more information.
Not sure where to find these two logs are located or why
the MSDE setup failed.
Any help resolving this problem will be appreciated.
Jim
hi Jim,
<anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:ecbf01c43d3c$230fb2e0$a401280a@.phx.gbl...
> I am attempting to install SharePoint Services (with
> MSDE) using all standard/default options. The WSS setup
> appears to proceed normally until it attempts to
> configure the MSDE. This portion of the WSS setup fails
> and I receive the following error message:
> MICROSFOT SQL SERVER DESKTOP ENGINE
> Setup failed to configure the server. Refer to the server
> error logs and setup error logs for more information.
> Not sure where to find these two logs are located or why
> the MSDE setup failed.
> Any help resolving this problem will be appreciated.
> Jim
please have a look at
http://support.microsoft.com/default...99&Product=sql
hth
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea. This is just the KB article that I was
looking for.
Jim

>--Original Message--
>hi Jim,
><anonymous@.discussions.microsoft.com> ha scritto nel
messaggio[vbcol=seagreen]
>news:ecbf01c43d3c$230fb2e0$a401280a@.phx.gbl...
server[vbcol=seagreen]
why
>please have a look at
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;816499&Product=sql
>hth
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||I have the same problem. However, after using the
solutions mentioned in that KB, I still got the same
error " Setup failed to configure the server".
Choi

>--Original Message--
>hi Jim,
><anonymous@.discussions.microsoft.com> ha scritto nel
messaggio[vbcol=seagreen]
>news:ecbf01c43d3c$230fb2e0$a401280a@.phx.gbl...
server
>please have a look at
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;816499&Product=sql
>hth
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtm
http://italy.mvps.org
>DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and
MSDE 2000 a visual
>interface)
>-- remove DMO to reply
>.
>

MSDE or SQL on a DC?

I am running a small shop where we have a dual XEON (1) 2003 Standard Server
serving as our DC, File & Print and DNS server. We have the opportunity to
upgrade to an application we currently use but it will require us to install
SQL 2000 or MSDE on this server. My question is this, can SQL 2000 or MSDE
exist on the same box?
Thanks - Sean
Yes. However, consider the performance and security aspects of this. As for security, I'm particularly
referring to the service account. Is the machine is a DC, the account is now a domain account...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"HelpPls" <smd6169@.hotmail.com> wrote in message news:eNHg3u7NEHA.1312@.TK2MSFTNGP12.phx.gbl...
> I am running a small shop where we have a dual XEON (1) 2003 Standard Server
> serving as our DC, File & Print and DNS server. We have the opportunity to
> upgrade to an application we currently use but it will require us to install
> SQL 2000 or MSDE on this server. My question is this, can SQL 2000 or MSDE
> exist on the same box?
> Thanks - Sean
>

MSDE on SBS2003 from Network

I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:

>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.

>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?

>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:

>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?

>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:

>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)

MSDE login problem

Hi all,

I have bought Visual C# .NET 2003 Standard and downloaded the MSDE to use
with it.

I did install it with it's default options and now i'd like to administer it
with Web Data Administrator but it keeps telling me that i should enable SQL
Server Authentication.

So i tried debugging the question creating an .udl file and trying to test
various authentication methods:
- Integrated Windows authentication works fine
- SQL Server authentication (when i try logging in using user 'sa' with the
password i've set keeps telling me that user 'sa' is not associated with a
trusted SQL Server connection.

How do i solve this puzzle? Tried googling (and reading some faqs) but
didn't come up with anything useful.

Unfortunately the Web Data Administrator doesn't allow using integrated NT
authentication. :-(

Thank You,
LorenzoCheck out MSKB 321698:

https://mvp.support.microsoft.com/d...kb;en-us;321698

--
Hope this helps.

Dan Guzman
SQL Server MVP

--------
SQL FAQ links (courtesy Neil Pike):

http://www.ntfaq.com/Articles/Index...epartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--------

"Lorenzo Bolognini" <lorenzo@.mysurname.net> wrote in message
news:jNaYa.42647$cl3.1359277@.news2.tin.it...
> Hi all,
> I have bought Visual C# .NET 2003 Standard and downloaded the MSDE to
use
> with it.
> I did install it with it's default options and now i'd like to
administer it
> with Web Data Administrator but it keeps telling me that i should
enable SQL
> Server Authentication.
> So i tried debugging the question creating an .udl file and trying to
test
> various authentication methods:
> - Integrated Windows authentication works fine
> - SQL Server authentication (when i try logging in using user 'sa'
with the
> password i've set keeps telling me that user 'sa' is not associated
with a
> trusted SQL Server connection.
> How do i solve this puzzle? Tried googling (and reading some faqs) but
> didn't come up with anything useful.
> Unfortunately the Web Data Administrator doesn't allow using
integrated NT
> authentication. :-(
> Thank You,
> Lorenzo|||"Dan Guzman" <danguzman@.nospam-earthlink.net> ha scritto nel messaggio
news:p_hYa.241$BC2.47@.newsread2.news.atl.earthlink .net...
> Check out MSKB 321698:

Thank you very much Dan.

Lorenzo

MSDE Installation error message

Thanks in advance for any assistance. I am trying to install a defaul instance of MSDE server on a 2003 Standard server. I have installed and updated MDAC 2.8. I have searched this forum and searched the web for clues. Any help would be appreciated.
Thanks
################################################## #############################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
Specified driver could not be loaded due to system error 126 (sql server).
SQL Server configuration failed.
################################################## #############################
126 translates to "module not found" (OS error - NET HELPMSG gets). Maybe a
missing / mismatched DLL
1. I would recommend running the MDAC Compnent Checker as per
http://www.microsoft.com/downloads/d...displaylang=en
2. Maybe check for exisitance of SQLSRV32.dll (SQL ODBC Driver) in
WINDOWS\SYSTEM32
and also run DEPENDS.exe on the SQLSRV32.dll to see if its missing any
modules(Dll's) it needs - in various Resource kits but also here
http://www.dependencywalker.com/
3. Check registry to see if
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server\ Driver and Setup
keys point at the right DLL in System32
cheers.
Andy.
"IseriesBuff" <IseriesBuff@.discussions.microsoft.com> wrote in message
news:7CFCD995-CF88-4D83-8324-6BA6D52BE297@.microsoft.com...
> Thanks in advance for any assistance. I am trying to install a defaul
instance of MSDE server on a 2003 Standard server. I have installed and
updated MDAC 2.8. I have searched this forum and searched the web for
clues. Any help would be appreciated. Thanks
>
################################################## ##########################
###
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> SQL Server configuration failed.
>
################################################## ##########################
###

MSDE Installation error message

Thanks in advance for any assistance. I am trying to install a defaul insta
nce of MSDE server on a 2003 Standard server. I have installed and updated
MDAC 2.8. I have searched this forum and searched the web for clues. Any h
elp would be appreciated.
Thanks
########################################
####################################
###
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=SVRDC1;UID=sa;PWD=;databa
se=master
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=SVRDC1;UID=sa;PWD=;databa
se=master
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=SVRDC1;UID=sa;PWD=;databa
se=master
Specified driver could not be loaded due to system error 126 (sql server).
SQL Server configuration failed.
########################################
####################################
###126 translates to "module not found" (OS error - NET HELPMSG gets). Maybe a
missing / mismatched DLL
1. I would recommend running the MDAC Compnent Checker as per
4332ef092c9&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en
2. Maybe check for exisitance of SQLSRV32.dll (SQL ODBC Driver) in
WINDOWS\SYSTEM32
and also run DEPENDS.exe on the SQLSRV32.dll to see if its missing any
modules(Dll's) it needs - in various Resource kits but also here
http://www.dependencywalker.com/
3. Check registry to see if
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINS
T.INI\SQL Server\ Driver and Setup
keys point at the right DLL in System32
cheers.
Andy.
"IseriesBuff" <IseriesBuff@.discussions.microsoft.com> wrote in message
news:7CFCD995-CF88-4D83-8324-6BA6D52BE297@.microsoft.com...
> Thanks in advance for any assistance. I am trying to install a defaul
instance of MSDE server on a 2003 Standard server. I have installed and
updated MDAC 2.8. I have searched this forum and searched the web for
clues. Any help would be appreciated. Thanks
>
########################################
####################################
###
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql server};server=SVRDC1;UID=sa;PWD=;databa
se=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> driver={sql server};server=SVRDC1;UID=sa;PWD=;databa
se=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> driver={sql server};server=SVRDC1;UID=sa;PWD=;databa
se=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> SQL Server configuration failed.
>
########################################
####################################
###

MSDE Installation error message

Thanks in advance for any assistance. I am trying to install a defaul instance of MSDE server on a 2003 Standard server. I have installed and updated MDAC 2.8. I have searched this forum and searched the web for clues. Any help would be appreciated. Thanks
###############################################################################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
Specified driver could not be loaded due to system error 126 (sql server).
SQL Server configuration failed.
###############################################################################126 translates to "module not found" (OS error - NET HELPMSG gets). Maybe a
missing / mismatched DLL
1. I would recommend running the MDAC Compnent Checker as per
http://www.microsoft.com/downloads/details.aspx?familyid=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en
2. Maybe check for exisitance of SQLSRV32.dll (SQL ODBC Driver) in
WINDOWS\SYSTEM32
and also run DEPENDS.exe on the SQLSRV32.dll to see if its missing any
modules(Dll's) it needs - in various Resource kits but also here
http://www.dependencywalker.com/
3. Check registry to see if
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server\ Driver and Setup
keys point at the right DLL in System32
cheers.
Andy.
"IseriesBuff" <IseriesBuff@.discussions.microsoft.com> wrote in message
news:7CFCD995-CF88-4D83-8324-6BA6D52BE297@.microsoft.com...
> Thanks in advance for any assistance. I am trying to install a defaul
instance of MSDE server on a 2003 Standard server. I have installed and
updated MDAC 2.8. I have searched this forum and searched the web for
clues. Any help would be appreciated. Thanks
>
############################################################################
###
>
> Starting Service ...
> SQL_Latin1_General_CP1_CI_AS
> -m -Q -T4022 -T3659
> Connecting to Server ...
> driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> driver={sql server};server=SVRDC1;UID=sa;PWD=;database=master
> Specified driver could not be loaded due to system error 126 (sql
server).
> SQL Server configuration failed.
>
############################################################################
###

MSDE Install

I'm running Server 2003 Standard Edition... I'm having
problems installing MSDE (light).
Is it mandatory to run Server 2003 Enterprise Edition in
order to install MSDE?
Thanks!
CJ
It is not necessary to have a previous installation of any edition of SQL
Server for installing MSDE. Please go through the following Microsoft
Articles for more information and how to custom install MSDE.
Software and Hardware requirements for various editions of SQL Server 2000
http://msdn.microsoft.com/library/de...us/instsql/in_
overview_74vn.asp
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_7eur.asp
MSDE Installation
http://msdn.microsoft.com/library/de...us/distsql/dis
tsql_3usf.asp
http://msdn.microsoft.com/library/de...us/distsql/dis
tsql_84xl.asp
Thanks
Soma Sekhara Reddy