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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuring web.config to allow PostgreSQL8.1 as DNNConfiguring web.config to allow PostgreSQL8.1 as DNN's database
Previous
 
Next
New Post
2/20/2006 5:45 AM
 

Is there an appropriate tag in updating the web.config file when PostgreSQL8.1 is used instead of SQL Server 2000?  I've searched the internet and looked for tutorials/pages in configuring web.config but all are using Microsoft SQL Server.

Here's the list of steps I did.

1.  Using pgAdminIII in PostgreSQL 8.1, I created a new login role namely "dnnuser" and a new database namely "dotnetnuke" - owned by dnnuser.  I've updated the web.config and under the <appsettings>, the information I used is

  <add key="SiteSqlServer" value="Server=127.0.0.1;Database=dotnetnuke;uid=dnnuser;pwd=password;" />

I am not really sure if there's a SitePostgreSQL as the key name but i still used the default value (SiteSqlServer).  When I browsed http://localhost/dotnetnuke,  I encountered an error as shown below:





Error Installing DotNetNuke

Current Assembly Version: 03.02.02

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

So i did another research and verified that i needed to update the databaseOwner to <data defaultProvider="SqlDataProvider"> tag and replaced "dbo" by "dnnuser".  The next error I've encountered is

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Could you please help?

 
New Post
3/4/2006 4:23 PM
 
Have you got a custom / 3rd party data provider which supports PostgreSQL for DotNetNuke then? A default out-of-the-box install of DNN only supports SQL Server.

Gavin
Portfolio: www.gavinharriss.com


 
New Post
3/5/2006 1:34 AM
 

Like he said your only out of the box DB support is for SQL Server of one veritiy or another. Postgre support would be really cool though. 

Sorry I don't have anything to actually add to the subject.  :)


Paul Davis
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuring web.config to allow PostgreSQL8.1 as DNNConfiguring web.config to allow PostgreSQL8.1 as DNN's database


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