Re: SQLServer Connection Problems...

Here is a bunch from the SQL Log file...

SQL Server is starting at priority class 'normal'(4 CPUs detected).
SQL Server configured for thread mode processing.
Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
Attempting to initialize Distributed Transaction Coordinator.
Starting up database 'Northwind'.
SQL server listening on 10.0.1.10: 1433.
SQL server listening on 127.0.0.1: 1433.
SQL server listening on TCP, Shared Memory, Named Pipes, Rpc.
SQL Server is ready for client connections

I thought it might help you see what we have here...

Thanks again.


"Jon" <jon_olson@xxxxxxx> wrote in message
news:ueoRcmIvGHA.1436@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for your help Arnie.

OK, I am using providerName="System.Data.SqlClient
I struck the TCP dll reference.
connectionString="Data Source=sbscomputer; Database=Northwind; Integrated
Security=False; User ID=ASPNET_Person; Password=12345

No gain on the play...

You know, Microsoft bills VS2005 as codeless, drag and drop programming.
I have not seen it work yet. I don't know if the SQL server must be in
the web server domain or what, but from within the CLS development
everything is OK. But the world doesn't run in the developement
environment, it runs on production servers. Judging from the activity in
this newsgroup I am not the only one struggling with getting VS2005 to be
useful in building data driven web aplications.

Sorry for the rant...
Just a little stressed, that's all...

Does the SQL server have to reside in the web server domain? I would
prefer that it would not.

I tried SQL authentication from the connection string just to get
something working... Didn't happen...

"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:erlGk3DvGHA.4512@xxxxxxxxxxxxxxxxxxxxxxx
And use the SQLClient object instead of OLEDB or ODBC.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:uiKiw0DvGHA.1512@xxxxxxxxxxxxxxxxxxxxxxx
Jon,

Would you change the connection string and let me know what happens. I
think that "net=dbmssocn" is using an old library that may be
incompatible with VS2005.

Please try:

"Data Source=sbscomputer;Initial Catalog=Northwind;User
Id=ASPNET_Person;Password=12345"

If, by some chance, that works for you, then you could probably return
to Windows authentication by replacing the UserID and Password with
"Integrated Security=SSPI". (As you probably know, using SQL
Authentication on a internet exposed SQL Server is a major security
risk.)

And let me know if the error messages change.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"Jon" <jon_olson@xxxxxxx> wrote in message
news:eS5%23JKBvGHA.324@xxxxxxxxxxxxxxxxxxxxxxx
Sorry for the huge post...
... and thanks for your help.

[SqlException (0x80131904): Login failed for user 'ASPNET_Worker'.]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection) +735043

System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream,
BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
+1838
System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
enlistOK) +33

System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String
newPassword, Boolean redirectedUserInstance) +628

System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo,
String newPassword, SqlConnection owningObject, Boolean
redirectedUserInstance) +170

System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool,
DbConnection owningConnection) +359

System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
+28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject) +424

System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject) +496

System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection) +82

System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset,
DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String
srcTable, IDbCommand command, CommandBehavior behavior) +121
System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32
startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior
behavior) +162
System.Data.Common.DbDataAdapter.Fill(DataTable dataTable) +107
NorthwindTableAdapters.ProductsTableAdapter.GetProducts() +108
AllProducts.Page_Load(Object sender, EventArgs e) +50
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1061

"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:OAloUFBvGHA.2260@xxxxxxxxxxxxxxxxxxxxxxx
I suggest adding some error capturing to the error handling block in
your web page. (Write it to a trace file or a log file.)

What error are you receiving?

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"Jon" <jon_olson@xxxxxxx> wrote in message
news:uwG318AvGHA.3496@xxxxxxxxxxxxxxxxxxxxxxx
SQL port 1433 requests are limited to internal ip address of web
server...


"Jon" <jon_olson@xxxxxxx> wrote in message
news:%23we1bzAvGHA.4512@xxxxxxxxxxxxxxxxxxxxxxx
We are not running ISA.
Port 1433 is open....

... checking on the rule to limit connection to web server ip
address...


"Arnie Rowland" <arnie@xxxxxxxx> wrote in message
news:ur2QCpAvGHA.2436@xxxxxxxxxxxxxxxxxxxxxxx
Is your SBS box running ISA?
Do you have port 1433 open? (Which is a big mistake unless you have
a rule to limit the connection to the web server ip address.)

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


"Jon" <jon_olson@xxxxxxx> wrote in message
news:OPGNMlAvGHA.4880@xxxxxxxxxxxxxxxxxxxxxxx
I have read all I can find and am just frustrated...

Our system uses SBS on a company network and Server 2003 for our
web server that is not in the company domain. I am developing a
web based system with VS2005 Pro.

I can connect to SQLServer Express on my computer running on
localhost. I can not connect to the database on SBS SQL2000 after
I publish the site to the web server.

I have created 2 different sets of matching User Accounts on both
the web server and the SQL server with no luck.

The SQL Server is listening on port 1433, TCP and named pipes are
enabled. MultiUser mode is on. Mixed mode authentication is on.

I have given up on Integrated Authentication and tried SQL
Authentication.

Establishing a database connection within VS2005 is no problem.
here is the connection string, just for the heck of it...

connectionString="Data Source=sbscomputer; net=dbmssocn;
Database=Northwind; Integrated Security=False; User
ID=ASPNET_Person; Password=12345 "

From the webserver I am getting "Login failed for user
'ASPNET_Person'" (my common identity on both web and SBS servers)


Got no idea why... I am stuck...



















.

Relevant Pages

  • Re: Error "SQL Server does not allow remote connections"
    ... The application could not connect to the sql server db. ... network is blocking the connection. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) +737554 ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: New guitar parts website
    ... The user is not associated with a trusted SQL Server connection. ... System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +170 ...
    (uk.music.guitar)
  • Re: New guitar parts website
    ... trusted SQL Server connection. ... host, String newPassword, Boolean redirectedUserInstance, SqlConnection ... owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +349 ...
    (uk.music.guitar)
  • SQL Server connection issue
    ... SQL Server login. ... A database connection could not be established. ... SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 ... integratedSecurity, SqlConnection owningObject) ...
    (microsoft.public.dotnet.general)
  • RE: ASP.NET 2.0 deployment (w/ SQL Srvr 2005) error
    ... The connection string was ok. ... than the SQL Server Instance, ... owningObject, SqlConnectionString connectionOptions, String ...
    (microsoft.public.dotnet.languages.csharp)