AttachDBfilename
Dec 13, 2005
I was getting SQL Server errors trying to run the Time Tracker kit, so
I tried to establish a connection with the timetracker.mdf from the
VWD Database Explorer - but no luck:
Data Source: Microsoft SQL Server Database File (SqlClient)
Database File name: Visual Studio2005WebSitesTimeTracker1App_DataTimeTracker.mdf
Using either Windows or SQLServer authentication, they both fail when I test the connection.
Any ideas ? I gave myself and the ASPNET account every permission possible in SQLServer.
View 1 Replies
Nov 8, 2006
HI,
We upgraded to SQL Server 2005 Standard Edition for our ASP.NET 2.0 website. We were using SQL Server Express 2005. That worked fine. Now we are unable to connect to the database. I have googled, but I just cann't figure out what is going on. Any help is appreciated. Here is the error.
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)
In our firewall sqlbrowser.exe and sqlservr.exe are allowed.
Thanks Matt
View 11 Replies
View Related
Nov 22, 2005
I've been working with VWD Express since its Beta 1, then Beta 2 and finally the final release.
With the Beta 2 I've been worked with crystalreports without any problem in connections to SQL Server 2000.
The problem arrives now: I'm working with godaddy.com (good guys)
They tell me to connect to my databases (SQLServer 2005) with this:
<connectionStrings>
<add name="Personal" connectionString="
Server=whsql-v04.prod.mesa1.secureserver.net;
Database=DB_675;
User ID=user_id;
Password=password;
Trusted_Connection=False" providerName="System.Data.SqlClient" />
<remove name="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="
Server=whsql-v04.prod.mesa1.secureserver.net;
Database=DB_675;
User ID=user_id;
Password=password;
Trusted_Connection=False" providerName="System.Data.SqlClient" />
</connectionStrings>
But I've been always using this:
<connectionStrings>
<add name="AppConnectionString1"
connectionString="Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory|myMDF.mdf;
Integrated Security=True;
User Instance=True"
providerName="System.Data.SqlClient"/>
</connectionStrings>
Does it means that I cannot use "AttachDbFilename"? I mean, I can't use an attached db file?
Should I create all my tables another time? (they use a Web database Admin)
Thanks in advance.
View 1 Replies
View Related
Feb 14, 2008
Hi,
After publishing my ASP.NET application from my local development machine to a server, I cannot get it to attach the database file to the SQL Server instance. The SQL Server is full version 2005. The error I receive is:
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: 25 - Connection string is not valid)
My connection string is:
<add name="WiggleITAdminDBConnectionString1" connectionString="Server=.MSSQLSERVER;AttachDbFilename=|DataDirectory|ITAdmin.mdf; Database=ITAdmin;Trusted_Connection=Yes" />
My ASP.NET version information is:
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
According to http://forums.asp.net/t/966680.aspx the full version of SQL Server 2005 doesn't allow the word AttachDbFilename.
Our DBA tells me that there are ways to attach .mdf & .ldf files to a full SQL Server instance. Does anyone know how?
Can anyone resolve this dillema? All help will be greatly appreciated.
Rype, UK
View 2 Replies
View Related
Aug 23, 2007
I used the following connection string when working with a SQL server DB locally in an ASP.NET code-behind module:
dim source as string="data source=.SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|Registration.mdf;User Instance=true"
However, when I uploaded the application to a web server where my site is hosted, I spent considerable time debugging the "Cannnot establish connection" exception, I was getting.
After adding "Database=Registration.mdf;server=<server N/W address>" and removing
"AttachDBFilename=|DataDirectory|Registration.mdf;" from the connection string, the connection was finally established.
Now, I have two questions: What's the difference between database and attachDBFileName options (And when should I use which)?
Secondly, why I had to add the server option, when it worked fine locally, and the application & db are located on the same web server?
View 5 Replies
View Related
