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 ...SQL Connection problem with some modulesSQL Connection problem with some modules
Previous
 
Next
New Post
6/12/2009 9:50 AM
 

Hi

I am fairly new to DNN so this may be a simple solution. I have just taken my DNN install and put it on a production server. The production server is set up exactly like my development server. When my site loads 85% of my modules load fine. 2 of them however (ZDNNFAQ and 3DCourasal from Media Ant) throw a load excetion with the following message:

 A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Named pipes is enabled on the production box and it is set up to allow remote connections. Surely either all the modules load or none of them. Has anybody got any ideas about this??

Kind Regards

Andrew

 

 

 
New Post
6/12/2009 8:57 PM
 

Some modules still make use of the legacy connection string found in the <appSettings> section of your site's web.config. It will have a key = "SiteSqlServer". If the value for this connection string has not been properly set to the same value as the connectionString attribute of your site's primary connection string or if there are missplaced comment tags i.e. <!-- and --> surrounding the legacy connection string, this error will be received.

Modify your legacy connection string appropriately to correct the error.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL Connection problem with some modulesSQL Connection problem with some modules


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