Re: SQLServer Connection Problems...

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: SQLServer Connection Problems...
    ... owningObject, SqlConnectionString connectionOptions, String newPassword, ... checking on the rule to limit connection to web server ip address... ...
    (microsoft.public.sqlserver.connect)
  • Re: SQLServer Connection Problems...
    ... Most good judgment comes from experience. ... Only take this step if your server is protected inside a good firewall... ... I can ping the SBS server from the Web Server on a local ip address ... SQL Server is starting at priority class 'normal'. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQLServer Connection Problems...
    ... I don't know if the SQL server must be in the ... Does the SQL server have to reside in the web server domain? ... Would you change the connection string and let me know what happens. ... String newPassword, SqlConnection owningObject, Boolean ...
    (microsoft.public.sqlserver.connect)
  • Re: SQLServer Connection Problems...
    ... Only take this step if your server is protected inside a good firewall... ... Most good judgment comes from experience. ... Windows Firewall is disabled on the web server and is not installed on the ... SQL Server is starting at priority class 'normal'. ...
    (microsoft.public.sqlserver.connect)
  • Re: SQLServer Connection Problems...
    ... making it all the way to SQL but its failing at the SQL login. ... Only take this step if your server is protected inside a good firewall... ... Most good judgment comes from experience. ... I can ping the SBS server from the Web Server on a local ip address ...
    (microsoft.public.sqlserver.connect)