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 ...Remote connection to DotNetNuke fails.Remote connection to DotNetNuke fails.
Previous
 
Next
New Post
4/9/2007 2:31 PM
 

Hi

I am running DotNetNuke 4.5.0 with the following specifications:

Windows 2003 server, MSSQL 2000 server, MS .NET framework 2.0, IIS 6.0.

No errors when installing and the webpage works when loading locally on the server. However when trying to connect from a remote computer within the network or  outside the network  I  get the following error: 'Internet Explorer cannot display the webpage'. This problem is only related to the DotNetNuke application, other webpages running on the IIS server works fine.  Have been trying to change connectionString values in web.config file: Server= (local) ,  Server='ip-address' ,  Server='servername', without solving the problem. Next I were trying to change the MSSQL Authentication from 'SQL Server Authentication' to 'Windows Authentication' but were not able to do this, need some input how to do this? The reason for doing this was to grant access to the server  through the 'Security settings'. 

Security settings on files and IIS application allows 'Network Service' and IUSR full access.

Web.config:

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 -->
    <add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid='uid';pwd='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="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid='uid';pwd='pwd';" />
    <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-->
    <add key="InstallationDate" value="4/9/2007" />
  </appSettings>

This is my first DotNetnuke installation (4.1.1 and 4.5.0) and I have been installing and uninstalling the application for while now and getting the same result as described above. Could someone please help?

Svein.

 
New Post
4/9/2007 2:42 PM
 

The error you are getting ... 'Internet Explorer cannot display the webpage'  is an IIS error, and I would think does not have anything to do with your SQL Server connection

When you get the error from IIS, what is the URL in the address window? if the URL is being redirected to 'localhost', then you'll need to log onto your site locally on the server and add an alias in Host->Portal Settings. ( I'm guessing that if you look now, you'll only see a portal alias pointing to a localhost URL )

 
New Post
4/9/2007 3:32 PM
 

I expect the same issue as Steve described, here the concrete steps to add a portal alias:

  • on the installation server, log in locally as "host" user
  • in Host menu go to Portals item
  • select your portal to get the site settings displayed
  • scroll to the end of the page, where portal aliases are listed (I assume there is only one "localhost" or "localhost/dotnetnuke"
  • add a new alias "mypcname" or "mypcname/dotnetnuke"

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
4/9/2007 5:21 PM
 

I too am having a similar problem.  I an also getting different error messages from the first time I start it to the subsequent tries.

 <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 -->
    <add
      name="SiteSqlServer"
      connectionString="Server=(local);Database=DNNWEBSITE;uid=DNN;pwd=DNN;"
      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="SiteSqlServer" value="Server=(local);Database=DNNWEBSITE;uid=DNN;pwd=DNN;"/>
   


1st Error

Error Installing DotNetNuke
Current Assembly Version: 04.04.01
ERROR: Could not connect to database specified in connectionString for SqlDataProvider


2nd Error

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

ERROR: Could not connect to database.

Login failed for user 'DNN'. The user is not associated with a trusted SQL Server connection.

 

So what am I doing wrong?

Barry

 

 
New Post
4/10/2007 2:35 PM
 

Hi sfabian@gooddogs.com and leupold

Your advice did solve my problem.

Thank you!

Svein.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Remote connection to DotNetNuke fails.Remote connection to DotNetNuke fails.


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