I have the app working on my development PC which has SQLServer Express, and ready to move to a test web server which has MS SQL Server 2000. The Test web server also has sharepoint installed on it, which installed SQLServerExpress by mistake. So it has
two instances of SQL, but I know that the name of the MS SQL Server 2000 instance is "MSSQLSERVER"
I getting getting the error in IE that I'm connecting to a SQL Server 2005 express database. I've been trying to follow the directions I found in this forum, but I'm still stuck. Here's what I've done so far.
1. Created a new database in MS SQL Server 2000 called "timetracker"
2. Ran aspnet_regsql to create the roles user tables required by the app
3. Ran the timetracker-add.sql on SQL server to generate the tables, sprocs and such.
4. Made sure the IIS user has the necessary rights to the database
But no matter what I try, I getting the below error when trying to login. Any idea what I'm doing wrong?
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)
I checked that the first time I ran across this problem after installing Sharepoint. You see, the issue is I have two instances of SQL Server, one for sharepoint (SQL Express 2005), and the full MS SQL 2000. The problem in the past has been I have to configure
the web.config to make sure it pointing to the full MS SQL Server 2000 database, by default it's looking at the Express version, thus the "SQL Server 2005 " included in the error txt.
I don't think I have the web.config configured correctly to point to the MS SQL Server 2000 instance database "timetracker".
I am new at this but an easy way to get a correct connectionString is to open the Database Explorer (VWD -> View|Database Explorer) . Add a Data Connection by right-clicking the Data Connections and select the Add Connection... option) . Once you have created
and tested the new connection, select that connection in the Data Explorer and then select the Properties tab. The Connection String property value can be selected, copied and pasted into your web.config connectionString = "".
Is the SQL Server on Windows server 2003? If so does it have the critical update installed?
Windows server 2003 disables the TCP/IP connections to SQL Server to protect against the slammer worm if you have an old mscordb.dll (I think that's the right one), whilst still allowing connections through named pipes.
tomhirt
Member
149 Points
124 Posts
Problems moving to SQL Server 2000
Aug 13, 2007 09:58 PM|LINK
I have the app working on my development PC which has SQLServer Express, and ready to move to a test web server which has MS SQL Server 2000. The Test web server also has sharepoint installed on it, which installed SQLServerExpress by mistake. So it has two instances of SQL, but I know that the name of the MS SQL Server 2000 instance is "MSSQLSERVER"
I getting getting the error in IE that I'm connecting to a SQL Server 2005 express database. I've been trying to follow the directions I found in this forum, but I'm still stuck. Here's what I've done so far.
1. Created a new database in MS SQL Server 2000 called "timetracker"
2. Ran aspnet_regsql to create the roles user tables required by the app
3. Ran the timetracker-add.sql on SQL server to generate the tables, sprocs and such.
4. Made sure the IIS user has the necessary rights to the database
5. Trying to modify the web.config from this....
<connectionStrings><
add name="aspnet_staterKits_TimeTracker" connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|TimeTracker.mdf;User Instance=true" /> <remove name="LocalSqlServer"/><
add name="LocalSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|TimeTracker.mdf;User Instance=true" /></
connectionStrings>to this....
<connectionStrings><
remove name="LocalSqlServer" /> <add name="LocalSqlServer" connectionString="Data Source=.\MSSQLSERVER;Integrated Security=True;database=timetracker;User Instance=true" /><
add name="aspnet_staterKits_TimeTracker" connectionString="Data Source=localhost;Integrated Security=True;database=timetracker;User Instance=true" /></
connectionStrings>But no matter what I try, I getting the below error when trying to login. Any idea what I'm doing wrong?
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)
chetan.sarod...
All-Star
65759 Points
11153 Posts
Re: Problems moving to SQL Server 2000
Aug 14, 2007 03:40 AM|LINK
You have to enable TCP/IP & named pipes option
Go to SQL Server Surface area configuration, under surface area configuration & connection, go to DataBase engine then Remote connection
check there Using both TCP/IP & Named pipes checkbox
Let me know if this helpful to you
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
tomhirt
Member
149 Points
124 Posts
Re: Problems moving to SQL Server 2000
Aug 14, 2007 08:17 PM|LINK
I checked that the first time I ran across this problem after installing Sharepoint. You see, the issue is I have two instances of SQL Server, one for sharepoint (SQL Express 2005), and the full MS SQL 2000. The problem in the past has been I have to configure the web.config to make sure it pointing to the full MS SQL Server 2000 database, by default it's looking at the Express version, thus the "SQL Server 2005 " included in the error txt.
I don't think I have the web.config configured correctly to point to the MS SQL Server 2000 instance database "timetracker".
chetan.sarod...
All-Star
65759 Points
11153 Posts
Re: Problems moving to SQL Server 2000
Aug 17, 2007 03:51 AM|LINK
You have to use only one connectionString in web.config, or you can check connection whether it is connecting to SQL Server or not?
Let me know if this helps you
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
bob.powell
Member
11 Points
9 Posts
Re: Problems moving to SQL Server 2000
Aug 21, 2008 09:43 PM|LINK
I am new at this but an easy way to get a correct connectionString is to open the Database Explorer (VWD -> View|Database Explorer) . Add a Data Connection by right-clicking the Data Connections and select the Add Connection... option) . Once you have created and tested the new connection, select that connection in the Data Explorer and then select the Properties tab. The Connection String property value can be selected, copied and pasted into your web.config connectionString = "".
chetan.sarod...
All-Star
65759 Points
11153 Posts
Re: Problems moving to SQL Server 2000
Aug 22, 2008 03:53 AM|LINK
Whether you are getting blank connectionString
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
bob.powell
Member
11 Points
9 Posts
Re: Problems moving to SQL Server 2000
Aug 22, 2008 01:09 PM|LINK
I'm using SQLServer 2000 and here is the connection string I'm using:
<
connectionStrings><add name="aspnet_staterKits_TimeTracker"
connectionString="Data Source=SQLSERVER_NAME;
Initial Catalog=TimeTracker;
Persist Security Info=True;
User ID=USERNAME;
Password=PASSWORD"/>
<remove name="LocalSqlServer"/><
add name="LocalSqlServer" connectionString="Data Source=SQLSERVER_NAME;Initial Catalog=TimeTracker;Persist Security Info=True;User ID=USERNAME;Password=PASSWORD"/></
connectionStrings>chetan.sarod...
All-Star
65759 Points
11153 Posts
Re: Problems moving to SQL Server 2000
Sep 05, 2008 03:26 AM|LINK
Whats wrong in that
what kinf of error you are facing, Please explain it in details
So it will help to solve your problem
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.
WiGgLr
Member
4 Points
2 Posts
Re: Problems moving to SQL Server 2000
Sep 09, 2008 01:27 PM|LINK
Is the SQL Server on Windows server 2003? If so does it have the critical update installed?
ownloads/details.aspx?displaylang=en&familyid=9552d43b-04eb-4af9-9e24-6cde4d933600
Windows server 2003 disables the TCP/IP connections to SQL Server to protect against the slammer worm if you have an old mscordb.dll (I think that's the right one), whilst still allowing connections through named pipes.
Here is the update you need:
http://www.microsoft.com/d
the exact file you need is linked on that page as SQLCritUpdPkg_ENU.exe
chetan.sarod...
All-Star
65759 Points
11153 Posts
Re: Problems moving to SQL Server 2000
Sep 10, 2008 03:24 AM|LINK
As far i am concerned the error means that "It is not allowing remote connections"
So i think the solution is if you are using Express edition
Go to the Configuration Manager and open it.
After openeing there will be two attributes by name SQL Server(Browser),SQL Server
right click on it and click Stop and restart both of the services
Then check the properties part and everything works fine or not
Let me know if this helps you
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/sql-server-2005-connectivity-issue-troubleshoot-part-i.aspx
Have a look at the following KB article, it will take you through the process of allowing remote connections.
How to configure SQL Server 2005 to allow remote conections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
Senior Software Engineer,
Approva Systems Pvt Ltd, Pune, India.