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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryerror on repositoryerror on repository
Previous
 
Next
New Post
4/21/2009 9:55 AM
 

hi
my portal instal on server
when i add the Ropository module to the page
I visit this error ?

A critical error has occurred.
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: SQL Network Interfaces,
 error: 26 - Error Locating Server/Instance Specified)

what can i do?

 
New Post
4/22/2009 11:46 PM
 

 Check your web.config file. There are 2 connection strings. The Repository module is a 'legacy' module, so it uses the second connection string.

 
New Post
4/24/2009 3:25 AM
 

 


hi
this is my web.config
i realy confuse!!!!
what can i do?

<

connectionStrings> Connection String for SQL Server 2005 Express --> Connection String for SQL Server 2000/2005-->add name="SiteSqlServer" connectionString="Server=******;Database=******;uid=******;pwd=******;" providerName="System.Data.SqlClient" />connectionStrings>appSettings> Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" /> Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules-->add key="InstallTemplate" value="DotNetNuke.install.config" />add key="AutoUpgrade" value="true" />add key="UseInstallWizard" value="true" />add key="InstallMemberRole" value="true" />add key="ShowMissingKeys" value="false" />add key="EnableWebFarmSupport" value="false" />add key="EnableCachePersistence" value="false" />add key="HostHeader" value="" /> Host Header to remove from URL so "www.mydomain.com/johndoe/Default.aspx" is treated as "www.mydomain.com/Default.aspx" -->add key="RemoveAngleBrackets" value="false" />optionally strip angle brackets on public login and registration screens-->add key="PersistentCookieTimeout" value="0" />use as persistent cookie expiration. Value is in minutes, and only active if a non-zero figure--> set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the standard)-->add key="InstallationDate" value="3/12/2009" />appSettings> 

<!--

<add

name="SiteSqlServer"

connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"

providerName="System.Data.SqlClient" />

<!--

<

</

<

<!--

<

<!--

<add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>

 

<

<

<

<

<

<

<

<

<!--

<

<!--

<

<!--

<!--

<add key="UsePortNumber" value="true" />

<

</

 

 
 
New Post
4/24/2009 9:33 AM
 

 Ok. in your web.config there are connections strings in 2 places, the connectionStrings and appSettings sections. In each section, there are 2 connections strings, 1 for SQL Server and 1 for SQL Server Express. By default, the entries for SQL Server are commented out and the 2 strings for SQL Express are active. If you are using SQL Server, you need to comment out the 2 entries for SQL Express and un-comment the 2 entries for SQL Server, then modify the connection string values for BOTH SQL Server connection strings.

In the following example, I have commented out the SQL Express entries (lines 2 thru 7 and 16 thru 21) and un-comments the entries for SQL Server (lines 10 thru 12 and 25 thru 26. I would then need to modify the connections strings to contain the correct database name, user id and password in BOTH connection strings, lines 11 and 26.

I hope this makes it clearer.  The second connection string is for use with Legacy modules for backward compatibility, which means modules built prior to the release of DNN 4.x which changed the location of the connection string in the web.config.

   1:  <connectionStrings>
   2:    <!-- Connection String for SQL Server 2005 Express
   3:    <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;
   4:         Integrated Security=True;User Instance=True;
   5:         AttachDBFilename=|DataDirectory|Database.mdf;" 
   6:         providerName="System.Data.SqlClient" />
   7:    -->
   8:   
   9:    <!-- Connection String for SQL Server 2000/2005  -->
  10:     <add name="SiteSqlServer" connectionString="Server=(local);
  11:         Database=DotNetNuke;uid=****;pwd=****;" 
  12:         providerName="System.Data.SqlClient"/>
  13:  </connectionStrings>
  14:   
  15:  <appSettings>
  16:    <!-- Connection String for SQL Server 2005 Express - kept for backwards 
  17:         compatability - legacy modules  
  18:      <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated
  19:         Security=True;User Instance=True;
  20:         AttachDBFilename=|DataDirectory|Database.mdf;" />
  21:    -->
  22:   
  23:    <!-- Connection String for SQL Server 2000/2005 - kept for backwards
  24:         compatability - legacy modules  -->
  25:      <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;
  26:         uid=****;pwd=****;"/>

 

 
New Post
4/25/2009 4:43 AM
 

I'm sorry but

i changed it :

 

<connectionStrings>
    <!-- Connection String for SQL Server 2005 Express
            <add
             name="SiteSqlServer"
             connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
             providerName="System.Data.SqlClient" /> -->
    <!-- Connection String for SQL Server 2000/2005-->
    <addname="SiteSqlServer"connectionString="Server=*******;Database=******;uid=*****;pwd=*****;"providerName="System.Data.SqlClient" />
 </connectionStrings>
 <appSettings>
    <!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules   -->
    <addkey="SiteSqlServer"value="Server=******;Database=*****;uid=*******;pwd=******;" />
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>
    -->

but now when add repository on a page :
A critical error has occurred.
Invalid value for key 'attachdbfilename'. 

i forget say that my portal (dnn 4.09.00) and install on server (not local)

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryerror on repositoryerror on repository


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