Did you try the connection strings I suggested,
or are you still using the other connection strings ?
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
I eventually got past the Login Failed error by adding permissions for
NJS\ASPNET to the database file. However, I am now recieving the
following error:
Server Error in '/PAPresenters' Application.
--------------------------------------------------------------------------------
SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: SQL Server does
not exist or access denied.
Source Error:
Line 33: cmdTesting.CommandText = txtSQLStatement.Text
Line 34: cmdTesting.Connection = myconnection
Line 35: myconnection.Open()
Line 36: cmdTesting.ExecuteNonQuery()
Line 37: myconnection.Close()
Source File: c:\inetpub\wwwroot\PAPresenters\DBtest.aspx.vb Line: 35
Stack Trace:
[SqlException: SQL Server does not exist or access denied.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction) +474
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString
options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
PAPresenters.DBtest.btnExecute_Click(Object sender, EventArgs e) in
c:\inetpub\wwwroot\PAPresenters\DBtest.aspx.vb:35
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
+33
System.Web.UI.Page.ProcessRequestMain() +1292
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
ASP.NET Version:1.1.4322.2032
I have SQL Server Desktop Engine running (when I hover my cursor over
the icon in the system tray it says "Running - \\NJS - MSSQLSERVER" and
the icon shows the green arrow, which means it is running). What am I
not doing? Thank you very much for your help, I greatly appreciate the
quick responses.
--
Nathan Sokalski
(e-mail address removed)
http://www.nathansokalski.com/
I think I tried it under .NET Beta 2, instead of .NET 1.1.
Nevertheless, try the simpler connection string I suggested.
Per
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde2kwrk/html/msde2000webapp.asp
a slightly more optimized connection string is :
"Server=localhost;Database=Pics2Share;Trusted_Connection=True;
Connection Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=5"
But the simpler connection string I suggested
should give you basic connectivity :
"Server=NJS;Trusted_Connection=True;Database=papresenters"
The optimized connection string for your case would be :
"Server=NJS;Database=papresenters;Trusted_Connection=True;
Connection Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=5"
You could also use
"Server=(local);Database=papresenters;Trusted_Connection=True;
Connection Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=5"
Using Trusted_Connection should prevent the error you're getting:
Login failed for user 'NJS\ASPNET'.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
That is not one of the listed providers. the listed providers that are
brought up are:
If there is somewhere on the web that I can download the provider you
mentioned from, I would like to know about it, but right now all I
have are the ones shown above. Thanks.
--
Nathan Sokalski
(e-mail address removed)
http://www.nathansokalski.com/
It looks like you selected the wrong provider when creating the
connection.
You should select the ".NET Framework Data Provider for SQL Server"
for a provider.
Try it using that provider. You should get a correct string if you
do.
If you still have problems, try a simpler connection string :
"Server=NJS;Trusted_Connection=True;Database=papresenters"
That assumes that your MSDE's instance name is "NJS"
and that your database name is "papresenters".
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
I have tried that, but the connectionstring that is created has
plenty of stuff in it
that gives me errors. For example:
Server Error in '/PAPresenters' Application.
--------------------------------------------------------------------------------
Keyword not supported: 'provider'.
Description: An unhandled exception occurred during the execution of
the current web
request. Please review the stack trace for more information about
the error and where it
originated in the code.
Exception Details: System.ArgumentException: Keyword not supported:
'provider'.
Source Error:
Line 28:
Line 29: Private Sub btnExecute_Click(ByVal sender As
System.Object, ByVal e As
System.EventArgs) Handles btnExecute.Click
Line 30: Dim myconnection As New
System.Data.SqlClient.SqlConnection("Provider=SQLOLEDB.1;Integrated
Security=SSPI;Persist Security Info=False;Initial
Catalog=papresenters;Data
Source=NJS;Use Procedure for Prepare=1;Auto Translate=True;Packet
Size=4096;Workstation
ID=NJS;Use Encryption for Data=False;Tag with column collation when
possible=False")
Line 31: Dim cmdTesting As New
System.Data.SqlClient.SqlCommand
Line 32: Dim dataadapter As New
System.Data.SqlClient.SqlDataAdapter
Source File: c:\inetpub\wwwroot\PAPresenters\DBtest.aspx.vb Line:
30
Stack Trace:
[ArgumentException: Keyword not supported: 'provider'.]
System.Data.Common.DBConnectionString.ParseInternal(Char[]
connectionString,
UdlSupport checkForUdl, NameValuePair& keychain) +1133
System.Data.Common.DBConnectionString..ctor(String
connectionString, UdlSupport
checkForUdl) +114
System.Data.SqlClient.SqlConnectionString..ctor(String
connectionString) +13
System.Data.SqlClient.SqlConnectionString.ParseString(String
connectionString) +96
System.Data.SqlClient.SqlConnection.set_ConnectionString(String
value) +11
System.Data.SqlClient.SqlConnection..ctor(String connectionString)
+158
PAPresenters.DBtest.btnExecute_Click(Object sender, EventArgs e)
in
c:\inetpub\wwwroot\PAPresenters\DBtest.aspx.vb:30
System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String
eventArgument) +57
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler
sourceControl, String
eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection
postData) +33
System.Web.UI.Page.ProcessRequestMain() +1292
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
ASP.NET
Version:1.1.4322.2032
Although I don't know much about connectionstrings, the little bit
of experience I have
leads me to think that the connectionstring generated by Visual
Studio .NET has a lot
more stuff in it than necessary, but either way it is not working.
Why is this, and how
can I fix it? Thanks.
--
Nathan Sokalski
(e-mail address removed)
http://www.nathansokalski.com/
1. Create at least one empty table in that database,
using the Server Explorer.
2. Use the Server Explorer's "Add Connection" wizard
( right-click "Data Connections" ) to create a connection.
3. The connection string will be created for you.
4. Right-click the created connection and select Properties.
5. Copy the connection string from the "Properties" box.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
I have Visual Studio .NET and SQL Server Desktop Engine on my
computer. I
have created an empty database using Visual Studio .NET's Server
Explorer.
However, I am having trouble connecting to the database using
ASP.NET. I
think the problem is somewhere in my connection string, but
because I do not
know much about connection strings, I am not sure what it should
look like.
Can someone please help me determine what my connection string
should look
like? I am using the version of IIS that comes with XP Pro.
Thanks.
