Hi,
I had an old web application created during asp.net 1.1 and it have a connection problem with the sql server 2005 when it is mirgrated to a new webserver with dotnet framework 2.0 platform. I have enabled the remote access(TCP/IP and named pipes) in sql server 2005, did all the neccessary things, check whether the TCP/IP is enabled, named pipe is enabled...
I created another web application using VS 2005. The database connection works perfectly well.
This are the connectionString from the old web application.
<appSettings>
<addkey="ConnectionString"value="Server=127.0.0.1;Database=somedb;User id=user; Password=somepassword; Trusted_Connection=False; POOLING=FALSE"/>
</appSettings>
Thankyou in advance!
I am not sure but maybe try this?
<appSettings>
<addk="ConnectionString"value="Server=127.0.0.1;Database=somedb;User id=user; Password=somepassword;"/>
</appSettings>
or
<appSettings>
<addk="ConnectionString"value="workstation id="computername";packet size=4096;data source=yourserver;initial catalog=yourdatabase ;user id=user;password=password"/>
</appSettings>
Thank jpazgier for your help. I have tried and tested it out. However the problem still exist.. =(
|||Could you provide code where you use your connection string? How you read it from config file and how you use it to get data?|||Hi,
This error message is just a basic connectivity error meaning the client could not connect to the target SQL Server. So just follow the basic connectivity troubleshooting guidelines on our SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
This should help you debug the problem.
No comments:
Post a Comment