Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help install 4.0.2 on shared hostwith SQL Server 2000, ASP.NET 2Help install 4.0.2 on shared hostwith SQL Server 2000, ASP.NET 2
Previous
 
Next
New Post
3/5/2006 7:28 PM
 

My problem: I want to install the latest version possible, on a new installation, on a shared host, when the shared host provides ASP.NET 2.0 but only SQL Server 2000. I've tried for hours and hours but always see error messages related to my web.config

I did the following:

make a new folder, unzip the install.zip file there, FTP'd the whole contents to the shared host account, modified the web.config, used the host's control panel to create the new database in sql server 2000, requested all the permissions on the folders and the DBO role on the database, tried to browse the site. I keep getting messages about not being able to connect to the sql server.

When I was in the web.config, I commented out both the connection strings relating to SQL Server 2005 express and uncommented and modified the connection strings marked "legacy" for SQL Server 2000/2005. I think I used the correct strings for database name, user name, password etc. I keep getting either "unable to log in" or "Login Failed"

What am I doing wrong?
Should I be using a different DNN version?

 

 
New Post
3/6/2006 9:25 AM
 

I'm using the same setup as you, you most likely don't have the correct connection string, this works for me, using the IP of the sql server.

    <!-- Connection String for SQL Server 2000/2005 -->
    <add name="SiteSqlServer" connectionString="Server=xxx.xxx.xxx.xxx,1433;Database=dnndb;User ID=dnnUsername;Password=mypwd;Trusted_Connection=False" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="Server=xxx.xxx.xxx.xxx,1433;Database=dnndb;User ID=dnnUsername;Password=mypwd;Trusted_Connection=False;" />

 
New Post
3/6/2006 10:50 AM
 

Markdidit, Hey, I like your screen name. Thanks for your help. First, my installation completed last night much after midnight and I tried to change the default passwords and had some problems, put it off and went to bed. This AM the  problems are still there. So it is working - but not well. So I want to continue this line of thought.

I notice a couple of differences between your strings and mine. First, you have included what I think is a port number (1433) after your server IP. ="Server=xxx.xxx.xxx.xxx,1433; I did not do that. And the example strings do not have that. What advantage does that give you? Is it required and I missed that advice somewhere?

Secondly, you included ;Trusted_Connection=False" after your password. Is that related to running in a shared host with medium trust?

Thanks for your answers. And just to share some myself for future ref: One big problem for me was an extra semicolon on the second connection string. It was:

    <add key="SiteSqlServer" value="Server=mwservername;Database=mydatabase;uid=MyUID;pwd=MyPass;"/>

It was creating an error and referenced that line. Finally I guessed to remove the last semicolon like this:

    <add key="SiteSqlServer" value="Server=mwservername;Database=mydatabase;uid=MyUID;pwd=MyPass"/>

And the install finished. If it weren't for dumb luck, I'd have no luck at all.

 
New Post
3/6/2006 4:26 PM
 

Hi, I am not a Sql expert, and based on time available as I write this, I won't be able to explain it in detail, but I this link has all the different connection strings and parameters for data connections.  Note the differences between ODBC, OLE DB and SqlConnection (.net) 

http://www.connectionstrings.com/

I just used the ip/port string provided by my hosting provider.  1433 is the default port, but could be changed for security reasons and would need to be specified to connect.

[quote]Secondly, you included ;Trusted_Connection=False" after your password. Is that related to running in a shared host with medium trust?[/quote]
Since I am not able to setup a Trusted Connection without involving my provider, I am simply providing the parameter to make sure that it understands the it is False along with the other parameters.

The semi colons separate the parameters and you would not have one at the end of the string.   

Hope this helped, good luck

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Help install 4.0.2 on shared hostwith SQL Server 2000, ASP.NET 2Help install 4.0.2 on shared hostwith SQL Server 2000, ASP.NET 2


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out