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 ...Unable to install dnn v 4-8-04Unable to install dnn v 4-8-04
Previous
 
Next
New Post
9/9/2008 6:57 AM
 

Hi Newbie here

Im unable to install dnn on our test server(win 2003 standard sp2 ) Ive installed IIS,dotnet fremework v2,SQL 2005 express and created a user account in SQL 2005 express and can connect to it when i try manually to connect. When i get to the install od DNN and type in the IP for my server for the install via the browser sometime it starts the install procedure but usually i get the dreaded 'could not connect to the database specified in the connection string for SQL data provider’ . Ive edited the webconfig file, here is a copy of it....

 

<!-- 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=AVVTestPortal;uid=wilcotn;pwd=strategy;"
     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=AVVTestPortal;uid=wilcotn;pwd=strategy;" />

 

Is there something stupid im missing here ? Ive tried to change the Server=(local) to the acutal server name but again no difference(just a guess really).Sometimes the install does start but i get an error message 'named pipes provider error 40,could not open a connection to sql server' on the screen after i test the connection.

 

Any Suggestion would be greatfully appreciated

 

Thanks

 

 

 
New Post
9/9/2008 10:50 AM
 

You will want to make sure that the server name matches the name that is displayed as you connect SQL Server Management Studio to the database.  Additionally you might need to enable remote connections via the Surface Area Configuration wizard.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
9/10/2008 5:06 AM
 

Hi Mitch

I tried that,i named the server to the actual win 2003 server name and both TCP/IP and named pipes were already enabled in the surface area connection wizard.Ive tried a restart of the database. I forgot to mention that i am installing DNN using vmware server consovle v 1-0-6 build 91891 as thats what is used on the live server (which i didnt configure). I either get the same message after i start the DNN install or the 'this site is currently unavailable 'please check back later message.

Any other suggestions ? or do i need a new build from scratch (IIS etc etc)

Thanks

 

 

 

 
New Post
9/10/2008 10:01 AM
 

Hi Avct,

Are you trying to access this server using integrated windows authentication or SQL server authentication?  I assume the latter since you are specifying credentials.  Does your user have a default catalog?  I don't see one specified in the connection string.  You might play with a connection string builder such as this one, in case you are overlooking some setting (I don't see anything obviously incorrect).k

If I were in your shoes, I would write a small .NET console application that opens a connection to the server using the same connection string.  This would remove DNN from the equation and allow you to focus exclusively on connectivity issues.  You may also need to check your event log and/or MSSQL logs to see if an exception is being thrown that might yield more insight into the underlying problem -- so far we don't conclusively know if it's authentication, authorization, or general connectivity.

As a complete aside, you might consider adding a "Persist Security Info=False" to your connection string, AFTER you have solved your current problems.

Hope this gets you started!

Brandon


Brandon Haynes
BrandonHaynes.org
 
New Post
9/11/2008 4:26 AM
 

Hi Brandon

Im using SQL server authentication. Im not sure what a default catalogue is ?
I will check the MSSQL logs to see if there is anything there.
 

Thanks for the advice

 

 

 

 

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Unable to install dnn v 4-8-04Unable to install dnn v 4-8-04


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