Considerations for packaging MSDE app

Hi
I have a C# Winform app which runs using SQL Server.
I want to package up the app, so that it deploys with MSDE.
Can anyone offer any pointers or references to help?
Thanks
Hi Paul,
I hope my suggestions will help you, because I have gone through pure h#$l
getting this to work right.
I have a VB.Net winforms app and I use Wise Installation System to install
the .Net framework, MSDE, the app.
A couple of things tried and failed:
1. Within wise, we installed MSDE with the command line option where it sets
the password. We decided to install MSDE into its own instance becasue we
don't want anyone coming behind us and hosing it up by installing an
untested service pack or anything.
2. At the end of the install, we run a batch file to stop and restart the
SQL service. In retrospect, this may not be necessary because of our
decision to reboot before the app is executed the first time.
3. We attempted to run a batch file to attach the database, but no matter
what we tried, it just would not work. It didn't matter if we rebooted and
then ran the batch, nothing worked. So, I added the code to my app that does
this:
a. check to see if the SQL service is running, if its not, warn the user and
shut down the app.
b. if this is the first time the app is executed:
b1. check to see if the database exists, of course it does not, so using
ado.net, execute the command against the master database to attach the
database. Test again to make sure the database is attached, if not, throw an
exception.
b2. Update my configuration file to show that the app has successfully
initialized.
4. Now here's the real McKoy - in order to get all this to work the first
time I connect to the database to check the version I had to use
POOLING=False in the connection string. Problem: The app ran as slow as a
turtle because now it wasn't using connection pooling anywhere. Solution:
Two connection strings, one for initial startup (first time connection) then
one for the rest of the time (without POOLING=false)
5. Another issue came up of how we would update our database, we surely
didn't want to have to detach and then re-attach another database and blow
peoples data away, so I added a version table to the database and I run a
check on the current version each time the app is executed. If the versions
are the same, I don't execute the update executable. So you may ask, how do
you know if you have a new database version and an update needs to take
place? Answer: When a patch is applied (or an executable update) I have a
Version.xml file where we will put the new version number to be compared
against. The executable that runs the update is also new since it will have
code in it to do the update.
But, here's the big question, after you install MSDE, do you need to reboot
or not? The answer is that I was able to get my app to work without having
to reboot, but we have decided to require a reboot because I just believe
there are things in MSDE that need to be set correctly and I think rebooting
is the only way to do it. Again, my app works without it, but I just feel
like its more proper to reboot. I mean after all, you are installing the SQL
desktop engine which is no minor thing, not to mention the .Net framework
install.
Now, there are probably many MSDE experts out there reading my steps
thinking, man, he did this totally wrong, but I'm telling YOU these are
things you are in the end, probably going to have to do to (especially the
POOLING = False setting).
There are many things we haven't even gotten to yet like:
1. What happens if a person doesn't reboot the machine, how do you stop them
from running the app?
2. What if a person runs the install, uninstalls, then reinstalls and
reboots, how does that affect the app?
3. Do you want the uninstall to uninstall the .Net framework and MSDE? I
personally don't think so but then both these items are rather large.
Hope this helps.
STom
"Paul Aspinall" <paul@.aspy.co.uk> wrote in message
news:ctuKd.9606$n9.2569@.fe3.news.blueyonder.co.uk. ..
> Hi
> I have a C# Winform app which runs using SQL Server.
> I want to package up the app, so that it deploys with MSDE.
> Can anyone offer any pointers or references to help?
> Thanks
>

connections to MSDE with .net installed

Hi,
Does the .net framework take up a connection to MSDE when starting up? We
are experiencing the following scenario:
Start up computer
Start our program that uses MSDE and the .net framework
Runs very slow
Shut down program on all computers
Stop MSDE service and Start again and it runs fine.
The reason I ask about the .net framework is that our program ran fine
before we migrated it to .net.
It seems like the govenor kicks in as soon as the machine is started - maybe
..net checks liscences or something?
..Net does not automatically take up connections or check licenses to MSDE or
any other DBMS. Run SQL Profiler (you have the Developers Edition of SQL
Server, don't you?) and see if any unexpected connections are being made to
the MSDE instance.
Jim
"Andrew" <Andrew@.discussions.microsoft.com> wrote in message
news:BF7838CC-CC14-4953-82A4-280A7B8213F7@.microsoft.com...
> Hi,
> Does the .net framework take up a connection to MSDE when starting up? We
> are experiencing the following scenario:
> Start up computer
> Start our program that uses MSDE and the .net framework
> Runs very slow
> Shut down program on all computers
> Stop MSDE service and Start again and it runs fine.
> The reason I ask about the .net framework is that our program ran fine
> before we migrated it to .net.
> It seems like the govenor kicks in as soon as the machine is started -
maybe
> .net checks liscences or something?

Connectiong to MSDE 2000

I installed MSDE 2000 on my machine running XP home
edition.
I can connect with all client utilities, include, query
analiser, enterprise manager, odbc, etc if i use the
builtin/administrator id, but i cant connect in the SQL
MODE.
If i set up an odbc connection for test, i get the
following error
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection.
The ODBC error returns a state 28000 error, with is an
authenticaton error, please how can i correct thisMSDE is installed by default with Windows authentication, not with mixed
authentication, so you can't login with a SQL login, like 'sa'. You can
change this from Enterprise Manager by rightclicking the server, choosing
properties, and change the Authentication on the Security tab. You ahve to
restart SQL Server for the setting to take effect.
Jacco Schalkwijk
SQL Server MVP
"Lanre" <larry548997@.yahoo.com_anonymous> wrote in message
news:1b8701c3fc16$8a0ec650$a401280a@.phx.gbl...
> I installed MSDE 2000 on my machine running XP home
> edition.
> I can connect with all client utilities, include, query
> analiser, enterprise manager, odbc, etc if i use the
> builtin/administrator id, but i cant connect in the SQL
> MODE.
> If i set up an odbc connection for test, i get the
> following error
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login
> failed for user 'sa'. Reason: Not associated with a
> trusted SQL Server connection.
> The ODBC error returns a state 28000 error, with is an
> authenticaton error, please how can i correct this|||If you don't have Enterprise Manager, you can change the setting with the
steps from this article:
285097 INF: How to Change the Default Login Authentication Mode to SQL While
http://support.microsoft.com/?id=285097
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection Trusted with Windows98

Hi everybody,
we just developed a standalone application using .NET+ C# + MSDE.
So, we're working to get a setup installation in order to deploy our
application for Windows2000/NT/XP/98 Opertaing System.
At the moment we're making some test on W/98 machine but we've got some
problems:
MSDE has been installed with flag SECURITYMODE=SQL allowing connection
trusted. In fact, after installation by W/XP we're able to connect to db
with OSQL command with -E option and with our application specifying
Integrated Security=SSPI in ConnectionString.
We don't have the same behaviour on Windows98 Operating System.
In spite of the flag mentioned above in installation I can using a
connection trusted.
Any suggestion ?
Thanks in advance, Pierluigi.
hi Pierluigi,
"Pierluigi Terzoli" <pierluigi_terzoli@.hotmail.com> ha scritto nel messaggio
news:eguAq2PZEHA.2816@.TK2MSFTNGP11.phx.gbl...
> Hi everybody,
> we just developed a standalone application using .NET+ C# + MSDE.
> So, we're working to get a setup installation in order to deploy our
> application for Windows2000/NT/XP/98 Opertaing System.
> At the moment we're making some test on W/98 machine but we've got some
> problems:
> MSDE has been installed with flag SECURITYMODE=SQL allowing connection
> trusted. In fact, after installation by W/XP we're able to connect to db
> with OSQL command with -E option and with our application specifying
> Integrated Security=SSPI in ConnectionString.
> We don't have the same behaviour on Windows98 Operating System.
> In spite of the flag mentioned above in installation I can using a
> connection trusted.
> Any suggestion ?
> Thanks in advance, Pierluigi.
>
I don't know if I correctly undertand your question...
SECURITYMODE=SQL stands for supporting both trusted WinNT connections as SQL
Server authenticated connections...
trusted connections are available only when MSDE(SQL Server) is installed on
WinNT platform... Win9x boxes only allow standard SQL Server authenticated
connections
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
|||Yes Andrea,
you understood right and you gave me the right answer.
I'm sorry, but I don't realise that trusted connection concept is valid with
WinNT only (I suppose even for WinXP, of course).
So, it means if I want to have a application .net+msde who wants to run on
all MS Operating System including W/98 I MUST use a SQL autentication.
Right ?
We've to consider this fact on the setup routine and in the Connection
String specified inside the C# application.
Thanks so much, Pierluigi.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:2l59icF8qs72U1@.uni-berlin.de...
> hi Pierluigi,
> "Pierluigi Terzoli" <pierluigi_terzoli@.hotmail.com> ha scritto nel
messaggio
> news:eguAq2PZEHA.2816@.TK2MSFTNGP11.phx.gbl...
> I don't know if I correctly undertand your question...
> SECURITYMODE=SQL stands for supporting both trusted WinNT connections as
SQL
> Server authenticated connections...
> trusted connections are available only when MSDE(SQL Server) is installed
on
> WinNT platform... Win9x boxes only allow standard SQL Server authenticated
> connections
> --
> 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
>
|||hi Pierluigi,
"Pierluigi Terzoli" <pierluigi_terzoli@.hotmail.com> ha scritto nel messaggio
news:e9XFykQZEHA.1656@.TK2MSFTNGP09.phx.gbl...
> Yes Andrea,
> you understood right and you gave me the right answer.
> I'm sorry, but I don't realise that trusted connection concept is valid
with
> WinNT only (I suppose even for WinXP, of course).
> So, it means if I want to have a application .net+msde who wants to run on
> all MS Operating System including W/98 I MUST use a SQL autentication.
yep... MSDE must be installed on WinNT platform to take advantage of trusted
connections... the clients can be installed on all OS supported by .Net
thought...
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
|||Thanks again, Andrea.
Tomorrow we'll start working to use SQL autentication by our application,
supporting in this manner even W/98 platform.
So, we'll install MSDE on our instance with our user/pwd.
We'll use the parameters above in any ConnectionString on our application.
Have a good day, bye, Pierluigi.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> ha scritto nel messaggio
news:2l5c5dF8l8f7U1@.uni-berlin.de...
> hi Pierluigi,
> "Pierluigi Terzoli" <pierluigi_terzoli@.hotmail.com> ha scritto nel
messaggio[vbcol=seagreen]
> news:e9XFykQZEHA.1656@.TK2MSFTNGP09.phx.gbl...
> with
on
> yep... MSDE must be installed on WinNT platform to take advantage of
trusted
> connections... the clients can be installed on all OS supported by .Net
> thought...
> --
> 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
>

Connection to the database on MSDE

Hi,

I installed MSDE and the sample databases with it. They work fine.

Well I am using the server explorer of visaula studio standard 2002. I can see all the sample databases there and connect to them as well.

1.
---------------------
Now i created a new database named "testDb" and in a similar fashion i am using windows login thingy.

When i write my connection string in the program now it doesnt work

string connectionStr =@."Server=IMRAN\NetSDK;" + "Integrated Security=SSPI;" + "Connection Timeout=7;" + "Database=testDB;";

If i replace my Database clause to Northwind it works absolutely fine.

The ERROR it gives is:

Cannot open database requested in login 'testDB'. Login fails. Login failed for user 'IMRAN\ASPNET'.

Why is this happenning? :(.

============================================

2.
--------
How can i configure the MSDE to use the SQL Authentication.
It doesnt allow me to do that?

Thanx Heaps,
ImranHi Guys,

I got the solution for the first problem of mine.

We need to Grant Access to the ASPNET user

The ASP.NET process runs under the MACHINENAME\ASPNET account. In order for the data access samples to access the database, this user must be granted rights to the sample databases. To manually grant access to the ASPNET user, replace MACHINENAME with the name of your computer, and run the following commands from the command line. Note: The path to the osql.exe command must be located in your PATH environment variable.

osql -E -S (local)\NetSDK -Q "sp_grantlogin 'MACHINENAME\ASPNET'"

osql -E -S (local)\NetSDK -d DATABASENAME -Q "sp_grantdbaccess 'MACHINENAME\ASPNET'"
osql -E -S (local)\NetSDK -d DATABASENAME -Q "sp_addrolemember 'db_owner', 'MACHINENAME\ASPNET'"

and if you are using the Sql Server Enterprise then just open the Enterprise manager and give the database rights to the [machine_name]\ASPNET user in the database users

Hope that can be useful for someone there.

Thanx.
Imran|||Hi,
Glad you found an answer. BTW, ASPNET is the default user name for Windows 2000 and XP, but it's 'NETWORK SERVICE' on Windows 2003 Server running native mode with IIS 6 (default). I found that out the hard way. After adding 'NT AUTHORITY\NETWORK SERVICE' as a login to SQL Server (MSDE), I was able to have my application access the database using the VS and IE browsers - clearying a major roadblock for me.

Also, you can use the Web Data Administrator to create a new login, if you don't have Enterprise manager, or don't want to use OSQL.

MS sure didn't make ASP.NET appliaction database access clear and simple! Maybe ASP.NET 2.0 will, but at what cost?

Good luck with your projects.

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
KahkashanDownload the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
KahkashanDownload the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL Server 2005

Hi all,
When I installed SPS 2003 , it installed MSDE as part of onstallation.
I also installed WSS SP 2 and SPS SP2 on it. I have SQL Server 2005
also installed on my machine.
How do I connect to this database for my WSS sites? How my sites in WSS
will be communicating to this sequal server?
Someone has suggeted that I should install SPS with SQLServer 2000 and
then upgrade it to SQL Server2005.I don't now why is it important to
install SQLServer 2000 and then upgrade it to 2005?
Is there any way that I can cope with the already made installations on
my machine?
Thanks
Kahkashan
Download the WindowsSharePointServicesAdmin BOL from Microsoft, looks
into the section of 'Deployment Scenarios', it has very details how to
set up SPS to connect to a existing SQL Server (rather than use the
default WMSDE)
I followed the instruction and built a test SPS for our department, no
problem.
In the BOL, it only mention you need to have a SQL Server 2000 sp3 or
above to host the SPS databases. So you may need to check if they are
compatible with MSSQL 2005.
Mel

Connection to SQL remote server

I'm using vb.net to connect to a MSDE 2000 database on a remote server.
While in VB.NET, I'm able to view data using Server Explorer. In addition,
I've configured an ODBCDATAADAPTER that fills the dataset under preview data.
When I tried to retrieve data through webform/datagrid I get the error
"ERROR [08001] [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server
does not exist or access denied. ERROR [01000] [Microsoft][ODBC SQL Server
Driver][Named Pipes]ConnectionOpen (Connect())."
I created a system dsn to connect to remote server. Test connection
succeeded. Any ideas what's wrong?
Hutty
The connection string I'm using in vb.net is
Dim Conn As New SqlConnection("Persist Security Info=False;Data
Source=INTL_INSTANCE;Extended
Properties=DSN=INTL_INSTANCE;UID=Hutty;APP=Microso ft? Visual Studio
..NET;WSID=CUI0113;DATABASE=Hutty;Network=DBNMPNTW ;Address=\\INTL\pipe\MSSQL$MYINSTANCE\sql\query;Tr usted_Connection=Yes;Initial Catalog=Hutty")
Hutty
"Hutty" wrote:

> I'm using vb.net to connect to a MSDE 2000 database on a remote server.
> While in VB.NET, I'm able to view data using Server Explorer. In addition,
> I've configured an ODBCDATAADAPTER that fills the dataset under preview data.
> When I tried to retrieve data through webform/datagrid I get the error
> "ERROR [08001] [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server
> does not exist or access denied. ERROR [01000] [Microsoft][ODBC SQL Server
> Driver][Named Pipes]ConnectionOpen (Connect())."
> I created a system dsn to connect to remote server. Test connection
> succeeded. Any ideas what's wrong?
> --
> Hutty
|||I have the same problem.
I want to connect to a SQL server with this connection string:
Dim Conn As New SqlConnection( "Data Source=83.240.161.155;
User Id=sa;password=;Initial Catalog=Avaliacao Desempenho")
Any help?
Ze
"Hutty" wrote:
[vbcol=seagreen]
> The connection string I'm using in vb.net is
> Dim Conn As New SqlConnection("Persist Security Info=False;Data
> Source=INTL_INSTANCE;Extended
> Properties=DSN=INTL_INSTANCE;UID=Hutty;APP=Microso ft? Visual Studio
> .NET;WSID=CUI0113;DATABASE=Hutty;Network=DBNMPNTW; Address=\\INTL\pipe\MSSQL$MYINSTANCE\sql\query;Tru sted_Connection=Yes;Initial Catalog=Hutty")
> --
> Hutty
>
> "Hutty" wrote:

connection to MSDE from WebMatrix

Hi,

I've just started to learn ASP.net using Scott Mitchell's book:ASP.NET in 24 hours. But i've got a little problem in the database section.
I couldn't connect with a MSDE from webmatrix using sql server authentication even the username and password are correct.
The error message :
"unable to connect to the database server:Login failed for user 'sa'. Reason:not associated with a trusted SQL server connection".
What does it mean? Have any of you ever had this kind of problem?
Thank you for helping me.

Regards,
tomhi!

the sa user is SysAdmin ;) the password and login authentification depends on how you set up your MSDE. what parameters have you used at the msde setup?

i'm not sure why some sql-requests require a trusted connection but it seems that if you use windows authentification you can connect to the db-server..
so the windows login seems to be a "trusted connection" but maybe you have to use the SSPI for the sql-login, just an idea how you could try to solve this ;)

hth, greetz

i might be wrong as i started learning about asp.net and sql some days ago too ^^ if that's the case plz correct me|||By default MSDE is installed with Windows Authentication only. You will have to change to mixed mode. That is my first guess on this one (may come back and edit this later with more info).

Connection to MSDE fails

I'm troubleshooting a connection to an MSDE install. I tried to register
the MSDE install on the server's EM. The register server wizard shows the
laptop's MSDE install but it refuses to connect.
-No software firewall is running on the laptop
-I added TCP/IP using port 1433 to the MSDE install
-The MSDE server shows up when I browse for SQL servers on the network
-I've tried integrated security and SQL authentication but neither work.
-I can connect to the MSDE install from the laptop using both authentication
types
Any ideas why EM can browse the MSDE server but not connect?
I'm using MSDE 2000 sp3 and SQL Server 2000 sp3
ThanksIf you come up with an answer, I would appreciate notice. I am having
the same problem.
If I connect an .adp directly it is fine. Query Analyzer is fine.
I cannot connect to either remote SQL Server DB I have. It is very
frustrating.
Thank you. Sorry I can't help you either.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Check the SQL Errorlogs for the MSDE instance. See what protocols it's
listening on.
You should see Shared Memory, Named Pipes and TCP.
Also, the default security is Windows Authentication.
Next try connecting using either ISQL.exe or a Test ODBC DSN. You need the
OS error to tshoot the problem.
Example:
OS Error 53 == Network Name not found. (Named Pipe connection without
Netbios Name Resolution)
OS Error 10060 == TCP Connection Timeout
OS Error 10061 == TCP connection Refused. Possibly the client is
connecting on the wrong socket. Or the server isn't listening on tcp.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connection to MSDE fails

I'm troubleshooting a connection to an MSDE install. I tried to register
the MSDE install on the server's EM. The register server wizard shows the
laptop's MSDE install but it refuses to connect.
-No software firewall is running on the laptop
-I added TCP/IP using port 1433 to the MSDE install
-The MSDE server shows up when I browse for SQL servers on the network
-I've tried integrated security and SQL authentication but neither work.
-I can connect to the MSDE install from the laptop using both authentication
types
Any ideas why EM can browse the MSDE server but not connect?
I'm using MSDE 2000 sp3 and SQL Server 2000 sp3
Thanks
If you come up with an answer, I would appreciate notice. I am having
the same problem.
If I connect an .adp directly it is fine. Query Analyzer is fine.
I cannot connect to either remote SQL Server DB I have. It is very
frustrating.
Thank you. Sorry I can't help you either.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Check the SQL Errorlogs for the MSDE instance. See what protocols it's
listening on.
You should see Shared Memory, Named Pipes and TCP.
Also, the default security is Windows Authentication.
Next try connecting using either ISQL.exe or a Test ODBC DSN. You need the
OS error to tshoot the problem.
Example:
OS Error 53 == Network Name not found. (Named Pipe connection without
Netbios Name Resolution)
OS Error 10060 == TCP Connection Timeout
OS Error 10061 == TCP connection Refused. Possibly the client is
connecting on the wrong socket. Or the server isn't listening on tcp.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connection to MSDE

Hi,
Is it possible to connect to a MSDE engine
from Management Studio 2005 ?
With tcpview, I didn't see a port which it listens
Thanks in advance
hi,
astalavista wrote:
> Hi,
> Is it possible to connect to a MSDE engine
> from Management Studio 2005 ?
> With tcpview, I didn't see a port which it listens
>
yes, you can connect from Management Studio to MSDE database...
MSDE installs by default disabling remote connections and network protocols,
thus tcp/ip protocol is not enable and local connections will be available
via shared memory only...
to enable remote connections and tcp/ip protocol you have to run the Server
Network Utility (svrnecn.exe) and enable the required protocol..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Thank you very much ...
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> a crit dans le message de
news: 5ccv2sF30j4u5U1@.mid.individual.net...
> hi,
> astalavista wrote:
> yes, you can connect from Management Studio to MSDE database...
> MSDE installs by default disabling remote connections and network
> protocols, thus tcp/ip protocol is not enable and local connections will
> be available via shared memory only...
> to enable remote connections and tcp/ip protocol you have to run the
> Server Network Utility (svrnecn.exe) and enable the required protocol..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>

Connection String to SQL Express on another computer

I have an XP Pro machine running a classic ASP site in IIS - the version that comes on the XP Pro CD. The site makes a connection to an MSDE database on the same machine named InControl. I have moved that database to SQL Express 2005 and want to test it with the ASP site. SQL Express 2005 is running on a separate Vista machine. I am currently using this connection string:

objConn.ConnectionString = "Provider=SQLOLEDB;Data Source=400SC;Initial Catalog=InControl;User ID=" & uid & ";Password=" & upass & ""

Where 400SC is the name of the XP Pro machine and InControl is the database. The variables uid and upass are pulled from Session when the connection string is created.

I have tried different Provider names and various combinations of server name and ip address with and without port numbers for the Data Source. All of them yield some variation of this error:

Microsoft OLE DB Provider for SQL Server (0x80004005)
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

What should the connection string look like?

Thanks for the help.

PS - If the solution involves a port, do I need to make that port an exception in the Vista Firewall?

The sqlexpress server may have an instance name. Try changing it to "Data Source=400SC\SQLEXPRESS"

|||

This is the string I initially tried to access SQL Express on the other computer - CSC_DELL. I recieved the error message in the original post. Hard coding the User ID and Password also yeilds the same error. The User is set-up in SQL and the database.

objConn.ConnectionString = "Provider=SQLOLEDB;Data Source=CSC_DELL\SQLEXPRESS;Initial Catalog=InControl;User ID=" & uid & ";Password=" & upass & ""

|||

Create a new file on your desktop. Rename the file to "test.udl" Double-click the file, and create a connection to your database. Once the "Test Connection" succeeds, then close the dialog box and view the contents of your .udl file in notepad. This will give you a connection string to compare against.

|||

Created a .udl file, but the SQL Express server on the Vista machine was not listed in the Server drop down list. I used the SQL Configuration tool and enabled listening with TCP/IP and Named Pipes - both were disabled. Also made a 1433 port exception in the Vista firewall. Tried udl, again, and the server still did not show. Both computers are in the same workgroup on my home network. I tried typing the name of the SQL Express server in the drop down list - didn't work. Everything I try yields the "SQL Server does not exist or access denied." Still stuck.

Connection string problem

I'm converting a simple Access application to ASP.NET with MSDE to run on our Intranet. The app has just one page with 2 SqlDataSource controls. Initially I configured the data source to connect directly to the .mdb file. Once I got the code running, I used the "Upsize Wizard" in Access to convert the data to a SQL database using the MSDE instance running on my web server. I then re-configured the SqlDataSources to connect to the MSDE database.

I am able to step all the way through the configuration wizard, and when I test the query, the correct data is returned. However, when I run the app (from within Visual Web Developer Express) I get the following exception when I bind a drop-down list to one of the SqlDataSources:

An OLE DB Provider was not specified in the ConnectionString.  An example would be, 'Provider=SQLOLEDB;'.

The connection string generated by the Wizard in my web.config is this:

<

addname="ConnectionString"connectionString="Data Source=BCFWEB01;Initial Catalog=InOut;User ID=XXX;Password=XXXXXXXXX"providerName="System.Data.SqlClient" />

Any idea why its complaining that I don't have an OLE DB provider, and why the query works fine from the Configuration Wizard but not when I run the page?

Thanks,

what is your code to bind your datasource? This errors mostly occurs when you are using OleDb connections in your code, and you have an Sql connection in your web.config file.|||Problem went away when I deleted & recreated the data source. I no longer have the code that didn't work :) but I suspect that's what the issue was. Thanks for the help!

Connection string for MSDE 2000

Hi,
I have a simple asp.net application running ok on my WinXP development
server with SQL Server Express 2005 installed locally. After moving to
the live server (Win 2000 server with MSDE 2000 installed locally),
it's giving me the 'SQL Network Interface Error (error 25): connection
string is not valid'.
So far, i've tried using the following connection string in my
web.config file:
connectionString="Data
Source=.\SQLEXPRESS;AttachDbFilename=|DataDirector y|\registration.mdf;Integrated
Security=True;User Instance=True" providerName="System.Data.SqlClient"
(this works fine on the development server)
connectionString="Data Source=(local);Initial
Catalog=registration;Integrated Security=SSPI"
Does anyone know how to solve this issue? Or is it just not possible to
use Sql Server .NET Data Provider (System.Data.SqlClient) that I used
in the development server to connect to a MSDE 2000 database on the
live server? Originally I wanted to use SQL Server Express 2005 on the
live server, but I didn't enough memory on it, so I figured I tried
MSDE 2000 first to see if I can get the right connection string.
Any help would be appreciated.
THanks,
hfk0
Microsoft SQL Server .NET Data Provider (System.Data.SqlClient) allows
you to connect to a Microsoft SQL Server 7.0, 2000, and 2005 databases
MSDE2000 does not support user instatnce, with which you can attach a
database file (*.mdf) by specifying a file name in connectionString. The
database file (*.mdf) must be attached/installed on the MSDE first before
your ASP.NET app runs.
Also, is the MSDE instance named as "ComputerName\SQLExpress"?
"hfk0" <hery@.infoventures.com> wrote in message
news:1142448305.817752.118520@.j33g2000cwa.googlegr oups.com...
> Hi,
> I have a simple asp.net application running ok on my WinXP development
> server with SQL Server Express 2005 installed locally. After moving to
> the live server (Win 2000 server with MSDE 2000 installed locally),
> it's giving me the 'SQL Network Interface Error (error 25): connection
> string is not valid'.
> So far, i've tried using the following connection string in my
> web.config file:
> connectionString="Data
> Source=.\SQLEXPRESS;AttachDbFilename=|DataDirector y|\registration.mdf;Integrated
> Security=True;User Instance=True" providerName="System.Data.SqlClient"
> (this works fine on the development server)
> connectionString="Data Source=(local);Initial
> Catalog=registration;Integrated Security=SSPI"
> Does anyone know how to solve this issue? Or is it just not possible to
> use Sql Server .NET Data Provider (System.Data.SqlClient) that I used
> in the development server to connect to a MSDE 2000 database on the
> live server? Originally I wanted to use SQL Server Express 2005 on the
> live server, but I didn't enough memory on it, so I figured I tried
> MSDE 2000 first to see if I can get the right connection string.
> Any help would be appreciated.
> THanks,
> hfk0
> Microsoft SQL Server .NET Data Provider (System.Data.SqlClient) allows
> you to connect to a Microsoft SQL Server 7.0, 2000, and 2005 databases
>
|||Hi Norman,
How do I attach/install the *.mdf file on MSDE? Also how do I find out
the MSDE instance name? On the dev server I have SQL Express 2005
installed locally so on the connection string, Data Source=.\SQLEXPRESS
(the dot refers to localhost and SQLEXPRESS the instance name).
Thanks for your help.
hfk0
|||hi,
hfk0 wrote:
> Hi Norman,
> How do I attach/install the *.mdf file on MSDE?
you have to use sp_attach_db system stored procedure,
http://msdn.microsoft.com/library/de...ae-az_52oy.asp
or
http://msdn.microsoft.com/library/de...ae-az_4wrm.asp
...

>Also how do I find out
> the MSDE instance name? On the dev server I have SQL Express 2005
> installed locally so on the connection string, Data
> Source=.\SQLEXPRESS (the dot refers to localhost and SQLEXPRESS the
> instance name).
try having a look at the SQL Server Service Manager in the icon tray.. it
should list the available local instances.. or use oSql.exe command tool
like
c:\>osql.exe -L
(parameters are case sensitive) that will list all available Instances in
you lan... or open the service management applet and seek for MSSQLSERVER
(default instance) or MSSQL$InstanceName (named instance)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea and Norman,
After trying the following:
- Reconfigured MSDE authentication mode to mixed mode.
- Enabled and configured Named Pipes and TCP/IP protocol using SQL
server network utility.
- Changed connection string on web.config file to
connectionString="Data Source=90.0.0.55,1433;Network
Library=DBMSSOCN;Initial Catalog=registration;User
ID=sa;Password=fmypassword;"
I'm now getting a different error message on the browser:
Cannot open database requested in login 'registration'. Login fails.
Login failed for user 'sa'.
I'm also getting the following message when trying to attach my SQL
database (default instance):
Error 602 Could not find row in sysindexes. run DBCC CHECKTABLE on
sysindexes.
Any clues?
|||hi,
hfk0 wrote:
> Hi Andrea and Norman,
> After trying the following:
> - Reconfigured MSDE authentication mode to mixed mode.
> - Enabled and configured Named Pipes and TCP/IP protocol using SQL
> server network utility.
> - Changed connection string on web.config file to
> connectionString="Data Source=90.0.0.55,1433;Network
> Library=DBMSSOCN;Initial Catalog=registration;User
> ID=sa;Password=fmypassword;"
> I'm now getting a different error message on the browser:
> Cannot open database requested in login 'registration'. Login fails.
> Login failed for user 'sa'.
SQLExpress and MSDE install by default dsabling standard SQL Server
authenticated connections, allowing only truste WinNT connections..
to modify this behavior at "run-time", please have a look at
http://support.microsoft.com/default...b;en-us;285097 in the
section regardin "windows registry" hacking ..

> I'm also getting the following message when trying to attach my SQL
> database (default instance):
> Error 602 Could not find row in sysindexes. run DBCC CHECKTABLE on
> sysindexes.
>
If during the attach process, SQL Server finds the DB to be corrupt, it will
not attach and you can't run DBCC's against it. If this is your problem, you
need to find a valid backup.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
hfk0 wrote:
> I did changed to windows registry to enable mixed authentication mode
> as well as replaced the seemingly corrupted SQL database, but i'm
> still getting the very same message when attaching the database
> (which is created in Visual Studio.Net 2005) to MSDE:
> Msg 602, Level 21, State 50, Server [name], Line 1
> Couldnot find row in sysindexes for database ID 5, object ID 1, index
> ID 1
> Run DBCC CHECKTABLE on sysindexes
> I wish microsoft would write this error message in plain english
> I'm stuck now and don't know what to do. Perhaps SQL Server Express
> database instance is just not backward compatible with MSDE instance?
SQL Server 2005 database can not be attached to SQL Server 2000 instances..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

connection stiring for MSDE

Dear All,
I tried to write the connection string for MSDE in JSP, but I had no luck
with it.
Is there anyone solved this problem?
Thank you..
The following link is a good resource for connection strings of all
flavors:
http://able-consulting.com/ADO_Conn.htm
--Mary
On Thu, 23 Sep 2004 09:58:21 +0200, "Loay Olabi"
<big_faceNO-SPAM@.lycos.coom> wrote:

>Dear All,
>I tried to write the connection string for MSDE in JSP, but I had no luck
>with it.
>Is there anyone solved this problem?
>Thank you..
>

Connection problem with ODBC to MSDE

Dear Friends
I am facing problem to connect to the SQL server which is in the network
through ODBC. I can ping to the machine all shares are available but not abl
e
to get the ODBC connection with SQL. Please suggest what can be the reason
and how i can solve the same.
Best regards
ShaileshHi
You may have installed MSDE with DISABLENETWORKPROTOCOLS=1 which does not
enable the network protocols. In which case you should still be able to
connect to the server on the machine itself. You can enable them by running
the command utility svrnetcn.exe
John
"Sharad2005" wrote:

> Dear Friends
> I am facing problem to connect to the SQL server which is in the network
> through ODBC. I can ping to the machine all shares are available but not a
ble
> to get the ODBC connection with SQL. Please suggest what can be the reason
> and how i can solve the same.
> Best regards
> Shailesh

Connection problem to MSDE

Hi,
I installed MSDE in my server and I have tried to connect
to my server over the Internet using Query Analyser and
Enterprise Manager. Both fail during the connection.
Testing the connection to MSDE locally in the server shows
me I can connect using the server
name "dedbxx\machinename", but I can't connect using the
server IP address.
Why is this happening?
I have already ran c:\Program Files\Microsoft SQL Server\80
\Tools\Binn\SVRNETCN.exe to configure the Net Protocols
supported by my server instance, including TCP/IP, but
nothing happens using IP to connect to the server.
Also tried to configure a ODBC entry in the server using
the IP address, but it shows me this message:
Coonection Failed:
SQLState: '01000'
SQL Server Error: 14
Coonection Failed:
SQLState: '08001'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][DBNETLIB] Invalid
connection
And here is the server log:
2004-04-29 13:02:08.28 server Microsoft SQL Server 2000 -
8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: )
2004-04-29 13:02:08.32 server Copyright (C) 1988-2002
Microsoft Corporation.
2004-04-29 13:02:08.32 server All rights reserved.
2004-04-29 13:02:08.32 server Server Process ID is 208.
2004-04-29 13:02:08.32 server Logging SQL Server messages
in file 'D:\MSSQLMSSQL$WKS\LOG\ERRORLOG'.
2004-04-29 13:02:08.43 server SQL Server is starting at
priority class 'normal'(1 CPU detected).
2004-04-29 13:02:10.37 server SQL Server configured for
thread mode processing.
2004-04-29 13:02:10.39 server Using dynamic lock
allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-04-29 13:02:10.60 spid3 Starting up database 'master'.
2004-04-29 13:02:11.17 server Using 'SSNETLIB.DLL'
version '8.0.766'.
2004-04-29 13:02:11.17 spid5 Starting up database 'model'.
2004-04-29 13:02:11.26 spid3 Server name is 'DEDBxx\WKS'.
2004-04-29 13:02:11.26 spid3 Skipping startup of clean
database id 4
2004-04-29 13:02:11.35 spid5 Clearing tempdb database.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
127.0.0.1: 1433.
2004-04-29 13:02:12.45 spid5 Starting up database 'tempdb'.
2004-04-29 13:02:12.68 spid3 Recovery complete.
2004-04-29 13:02:12.68 spid3 SQL global counter collection
task is created.
2004-04-29 13:02:27.15 server SQL server listening on TCP,
Shared Memory, Named Pipes.
2004-04-29 13:02:27.15 server SQL Server is ready for
client connections
Any ideas?
Thanks,
Do you mean over the internet using a VPN?
If so, is the VPN giving you full access to the remote network?
Is the ServerIP address the public IP address, or the LAN IP?
Cheers,
James Goodman
"Rogerio" <anonymous@.discussions.microsoft.com> wrote in message
news:620e01c42e13$8e873b20$a301280a@.phx.gbl...
> Hi,
> I installed MSDE in my server and I have tried to connect
> to my server over the Internet using Query Analyser and
> Enterprise Manager. Both fail during the connection.
> Testing the connection to MSDE locally in the server shows
> me I can connect using the server
> name "dedbxx\machinename", but I can't connect using the
> server IP address.
> Why is this happening?
> I have already ran c:\Program Files\Microsoft SQL Server\80
> \Tools\Binn\SVRNETCN.exe to configure the Net Protocols
> supported by my server instance, including TCP/IP, but
> nothing happens using IP to connect to the server.
> Also tried to configure a ODBC entry in the server using
> the IP address, but it shows me this message:
> Coonection Failed:
> SQLState: '01000'
> SQL Server Error: 14
> Coonection Failed:
> SQLState: '08001'
> SQL Server Error: 14
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] Invalid
> connection
> And here is the server log:
> 2004-04-29 13:02:08.28 server Microsoft SQL Server 2000 -
> 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.2 (Build 3790: )
> 2004-04-29 13:02:08.32 server Copyright (C) 1988-2002
> Microsoft Corporation.
> 2004-04-29 13:02:08.32 server All rights reserved.
> 2004-04-29 13:02:08.32 server Server Process ID is 208.
> 2004-04-29 13:02:08.32 server Logging SQL Server messages
> in file 'D:\MSSQLMSSQL$WKS\LOG\ERRORLOG'.
> 2004-04-29 13:02:08.43 server SQL Server is starting at
> priority class 'normal'(1 CPU detected).
> 2004-04-29 13:02:10.37 server SQL Server configured for
> thread mode processing.
> 2004-04-29 13:02:10.39 server Using dynamic lock
> allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-29 13:02:10.60 spid3 Starting up database 'master'.
> 2004-04-29 13:02:11.17 server Using 'SSNETLIB.DLL'
> version '8.0.766'.
> 2004-04-29 13:02:11.17 spid5 Starting up database 'model'.
> 2004-04-29 13:02:11.26 spid3 Server name is 'DEDBxx\WKS'.
> 2004-04-29 13:02:11.26 spid3 Skipping startup of clean
> database id 4
> 2004-04-29 13:02:11.35 spid5 Clearing tempdb database.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 127.0.0.1: 1433.
> 2004-04-29 13:02:12.45 spid5 Starting up database 'tempdb'.
> 2004-04-29 13:02:12.68 spid3 Recovery complete.
> 2004-04-29 13:02:12.68 spid3 SQL global counter collection
> task is created.
> 2004-04-29 13:02:27.15 server SQL server listening on TCP,
> Shared Memory, Named Pipes.
> 2004-04-29 13:02:27.15 server SQL Server is ready for
> client connections
> Any ideas?
> Thanks,
>

Connection problem OSQL - MSDE

Hello All
I have recently installed MSDE to use with
a trial version of Visual Studio .NET 2003
I installed MSDE 2000 release A with the following command:
Setup.exe /qb+ INSTANCENAME=3D"NetSDK" DISABLENETWORKPROTOCOLS=3D1
SAPWD=3D"notthisone"
I now have to install a database to be used in exercises
that is installed through a bat file:
rem The following command line installs the Contact SQL database
osql -E -i InstContacts.Sql
osql.exe refused to connect with sqlserver. It should communicate
using shared memory but that fails.I have enabled tcp/ip and named
pipes (which are disabled by default) using the Server Network Utility
but that did not work either. It usually fails with the following
messages:
[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).
With tcpip enabled it gives the messages
[Shared Memory]Invalid connection.
[Shared Memory]ConnectionOpen (Invalid Instance()).
after running ther TDIMON utility (www.sysinternals.org)
I get the first error message,
TDIMON seems to screw up some tcpip related settings as I encounter
other problems connecting with ADSL with a ethernet card.
(Could this be causing confusion for OSQL?)
The messages suggest to me that it is using shared memory also
when TCPIP is available.
I have no control over the communications by OSQL,
there seem to be no switches to control it.
I tried several solutions I found in this group and on
a Microsoft site, but none worked so far.
I have one named instance NETSDK of SQL server (desktop engine)
I am running Windows 2000 with
Norton Internet Security 2002
computer/instance=3DSTARSHIP\NETSDK
instance name=3DMSSQL$NETSDK
some version info: 'SSNETLIB.DLL' version '8.0.766'.
I think I have MDAC 2.7 when looking in the registry
Does anyone has an idea what is wrong?
Martin Kramer
mkramer@.wxs.nl
http://home.wxs.nl/~mkramer/
hi Martin,
Martin Kramer wrote:
> rem The following command line installs the Contact SQL database
> osql -E -i InstContacts.Sql
please add the full instance name ...
osql -E -S(Local)\NetSDK -i InstContacts.Sql
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
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin Kramer wrote:
>please add the full instance name ...
>osql -E -S(Local)\NetSDK -i InstContacts.Sql
Thanks a lot
It certainly worked much bettert than anything I tried
There is a database created. I only have doubts about the
access rights for the ASPNET user that the selfstudy samples use.
But this was syntax from microsoft. It should have worked
as it came with the samples. Or has anything gone wrong
initially when osql searches for a database server?
There is only one on my system.
I copied the original bat file to a new one,
adding a pause statement to see the feedback,
because the original flashed away before I could have a look at it.
It seems the problem was not with TCPIP after all,
However, I can not get osql into a command promt mode with
the same syntax. Is that possible and if so, how.
Oracle and DB2 had similar functions.
Or is osql not intended/suitable for such use?
Martin Kramer
mkramer@.wxs.nl
http://home.wxs.nl/~mkramer/
|||hi Martin,
Martin Kramer wrote:
> But this was syntax from microsoft. It should have worked
> as it came with the samples. Or has anything gone wrong
> initially when osql searches for a database server?
> There is only one on my system.
without specifying the destination server, the (Local) server is assumed,
but as long you installed a named instance you have to full qualify it..

> I copied the original bat file to a new one,
> adding a pause statement to see the feedback,
> because the original flashed away before I could have a look at it.
> It seems the problem was not with TCPIP after all,
Shared Memory is used instead of network protocol(s) to connect to local
server..

> However, I can not get osql into a command promt mode with
> the same syntax. Is that possible and if so, how.
> Oracle and DB2 had similar functions.
> Or is osql not intended/suitable for such use?
are you using the one I proposed?
http://msdn.microsoft.com/library/de..._osql_1wxl.asp
http://support.microsoft.com/default...;EN-US;q325003
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
|||"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin Kramer wrote:
>without specifying the destination server, the (Local) server is =
assumed,=20
>but as long you installed a named instance you have to full qualify it..
I understand. Having a named instance requires specifying it.
>
>Shared Memory is used instead of network protocol(s) to connect to local=
=20
>server..
OK. Seems logical as it should be efficient.
>
>are you using the one I proposed?
>http://msdn.microsoft.com/library/de...y/en-us/copro=
mpt/cp_osql_1wxl.asp
>http://support.microsoft.com/default...;EN-US;q325003
I don't understand this question, as you are proposing it only now,
but I found the links very helpful and now have osql.exe running in
command promt mode so I can try all kinds of commands.
This was what I was looking for.
You have been very helpful
Thank you.
Martin Kramer