ASP.NET and SQL 2000 not playing nice?

  • Thread starter Hugh G. Johnson
  • Start date
H

Hugh G. Johnson

Hi,

I have just installed a shopping cart system that is build using the asp.net
1.1 frame work and a SQL 2000 db.

The production server is a WS03 box running IIS 6, SQL 2000 (sp3), and has
asp.net fw 1.1 and the Data Thingy 2.7.

Both the web server and the SQL server are running and I can connect to
either of them directly but I can't get the web.config connnection string to
intialize. I've made this connection string with the MDL thingy (which
tested fine) and copy/pasted into the web.config file. I'm still getthing
this:

Server Error in '/' Application.
----------------------------------------------------------------------------
----

The ConnectionString property has not been initialized.
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.

Exception Details: System.InvalidOperationException: The ConnectionString
property has not been initialized.

Source Error:

An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:

[InvalidOperationException: The ConnectionString property has not been
initialized.]
System.Data.SqlClient.SqlConnection.Open() +433
AspDotNetStorefront31Common.DB.GetDS(String sql, String cacheName,
Boolean useCache, DateTime expiresAt)
AspDotNetStorefront31Common.DB.GetDS(String sql, Boolean useCache,
DateTime expiresAt)
AspDotNetStorefront31Common.Common.AppConfig(String paramName)
AspDotNetStorefront31Common.Common.UserCookieName()
AspDotNetStorefront31Common.Common.SessionStart()
AspDotNetStorefront31.Global.Session_Start(Object sender, EventArgs e)
System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e) +132
System.Web.SessionState.SessionStateModule.CompleteAcquireState() +514
System.Web.SessionState.SessionStateModule.BeginAcquireState(Object
source, EventArgs e, AsyncCallback cb, Object extraData) +697

System.Web.AsyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep
..Execute() +66
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously) +173
 
H

Hans Kesting

Hugh G. Johnson said:
Hi,

I have just installed a shopping cart system that is build using the asp.net
1.1 frame work and a SQL 2000 db.

The production server is a WS03 box running IIS 6, SQL 2000 (sp3), and has
asp.net fw 1.1 and the Data Thingy 2.7.

Both the web server and the SQL server are running and I can connect to
either of them directly but I can't get the web.config connnection string to
intialize. I've made this connection string with the MDL thingy (which
tested fine) and copy/pasted into the web.config file. I'm still getthing
this:
[snipped]

Probably your connection string has a "provider" clause. You don't need that
as you already are using a sqlserver connection. And in fact you will get an error if
you do use it.

Hans Kesting
 
H

Hugh G. Johnson

Hans,

Thank you for your reply. You're saying I should get rid of <add
key="DBProvider" value="MSSQL" />? Thanks!

Here's the Connection string:

<appSettings>

<add key="DBProvider" value="MSSQL" />
<add key="DBConn" value="data source=127.0.0.1;initial
catalog=AspDotNetStore;user id=sa;password=XXXX;;persist security
info=False" />
<add key="UseStaticLinks" value="true" />

</appSettings>




Hans Kesting said:
Hi,

I have just installed a shopping cart system that is build using the asp.net
1.1 frame work and a SQL 2000 db.

The production server is a WS03 box running IIS 6, SQL 2000 (sp3), and has
asp.net fw 1.1 and the Data Thingy 2.7.

Both the web server and the SQL server are running and I can connect to
either of them directly but I can't get the web.config connnection string to
intialize. I've made this connection string with the MDL thingy (which
tested fine) and copy/pasted into the web.config file. I'm still getthing
this:
[snipped]

Probably your connection string has a "provider" clause. You don't need that
as you already are using a sqlserver connection. And in fact you will get an error if
you do use it.

Hans Kesting
 
H

Hans Kesting

Hugh G. Johnson said:
Hans,

Thank you for your reply. You're saying I should get rid of <add
key="DBProvider" value="MSSQL" />? Thanks!

True, only use the value of "DBConn".
Hans Kesting
Here's the Connection string:

<appSettings>

<add key="DBProvider" value="MSSQL" />
<add key="DBConn" value="data source=127.0.0.1;initial
catalog=AspDotNetStore;user id=sa;password=XXXX;;persist security
info=False" />
<add key="UseStaticLinks" value="true" />

</appSettings>




Hans Kesting said:
Hi,

I have just installed a shopping cart system that is build using the asp.net
1.1 frame work and a SQL 2000 db.

The production server is a WS03 box running IIS 6, SQL 2000 (sp3), and has
asp.net fw 1.1 and the Data Thingy 2.7.

Both the web server and the SQL server are running and I can connect to
either of them directly but I can't get the web.config connnection string to
intialize. I've made this connection string with the MDL thingy (which
tested fine) and copy/pasted into the web.config file. I'm still getthing
this:
[snipped]

Probably your connection string has a "provider" clause. You don't need that
as you already are using a sqlserver connection. And in fact you will get an error if
you do use it.

Hans Kesting
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,482
Members
44,901
Latest member
Noble71S45

Latest Threads

Top