469,643 Members | 1,906 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,643 developers. It's quick & easy.

Problem connecting to my database

Hi, i have SQL Server 2005 and a database set that is called, myCompany
the problem is that i cant connect from my page to it,
here is from the web.config: ( i have got this connectionstring from my
sqldataobject on my page)
<add name="ConStr" connectionString="Data Source=localhost;Initial
Catalog=myCompany;Integrated Security=True"
providerName="System.Data.SqlClient" />

the strange part is that its trying to connect to a SQL express database,
but i have it on in my SQL Server 2005. I dont have SQL Express installed
since i was intending to work oly with SQL Server 2005 and i have all
memberships and rols inside my SQL Server aswell.
keep getting this error message:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
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.

SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express instance using a
database location within the applications App_Data directory. The provider
attempted to automatically create the application services database because
the provider determined that the database does not exist. The following
configuration requirements are necessary to successfully check for existence
of the application services database and automatically create the application
services database:
If the applications App_Data directory does not already exist, the web
server account must have read and write access to the applications directory.
This is necessary because the web server account will automatically create
the App_Data directory if it does not already exist.
If the applications App_Data directory already exists, the web server
account only requires read and write access to the applications App_Data
directory. This is necessary because the web server account will attempt to
verify that the Sql Server Express database already exists within the
applications App_Data directory. Revoking read access on the App_Data
directory from the web server account will prevent the provider from
correctly determining if the Sql Server Express database already exists. This
will cause an error when the provider attempts to create a duplicate of an
already existing database. Write access is required because the web server
accounts credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local user
profile. See the readme document for details on how to create a local user
profile for both machine and domain accounts.
Oct 1 '06 #1
2 3872
Hi Patrick,

To enable remote connections see this page

http://support.microsoft.com/default...b;EN-US;914277

Before you change, try specifying the actual server name. It may be the
use of 'localhost' is causing this exception.

--
Happy Coding!
Morten Wennevik [C# MVP]
Oct 2 '06 #2
According to the exception message, you have a connection string (which could
be the default in the master web.config) that is attempting to use a
SQLExpress connection string that uses the Auto-attach feature, which is not
supported by SQL Server 2005.
You may need to use the <remove name="LocalSqlServer" ...>
element to get rid of this, before adding in your own connection string.
Also, you need to Attach the database in SQL Managment Studio, it cannot be
loaded dynamically as in SQLEXPRESS.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Patrick F" wrote:
Hi, i have SQL Server 2005 and a database set that is called, myCompany
the problem is that i cant connect from my page to it,
here is from the web.config: ( i have got this connectionstring from my
sqldataobject on my page)
<add name="ConStr" connectionString="Data Source=localhost;Initial
Catalog=myCompany;Integrated Security=True"
providerName="System.Data.SqlClient" />

the strange part is that its trying to connect to a SQL express database,
but i have it on in my SQL Server 2005. I dont have SQL Express installed
since i was intending to work oly with SQL Server 2005 and i have all
memberships and rols inside my SQL Server aswell.
keep getting this error message:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified)
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.

SQLExpress database file auto-creation error:
The connection string specifies a local Sql Server Express instance using a
database location within the applications App_Data directory. The provider
attempted to automatically create the application services database because
the provider determined that the database does not exist. The following
configuration requirements are necessary to successfully check for existence
of the application services database and automatically create the application
services database:
If the applications App_Data directory does not already exist, the web
server account must have read and write access to the applications directory.
This is necessary because the web server account will automatically create
the App_Data directory if it does not already exist.
If the applications App_Data directory already exists, the web server
account only requires read and write access to the applications App_Data
directory. This is necessary because the web server account will attempt to
verify that the Sql Server Express database already exists within the
applications App_Data directory. Revoking read access on the App_Data
directory from the web server account will prevent the provider from
correctly determining if the Sql Server Express database already exists. This
will cause an error when the provider attempts to create a duplicate of an
already existing database. Write access is required because the web server
accounts credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local user
profile. See the readme document for details on how to create a local user
profile for both machine and domain accounts.
Oct 2 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Suresh | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.