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 ...DNN 4.8.2 on Vista install problemDNN 4.8.2 on Vista install problem
Previous
 
Next
New Post
4/25/2008 7:31 AM
 

Hello all,

I'm attempting a local install of DotNetNuke 04.08.02 on Vista with SQL Server 2005 Standard and IIS7 and am running into a consistent problem in installation. I've created a database called DotNetNuke, created a user who is set as dbo and has sql authentication, set the user to dbo on the database (schema and role membership), set permissions for NetworkService on the folder for the DNN files, set the Application Pool in IIS to Classic .NET AppPool, etc. I'm using pass-through authentication in IIS.
I've been scouring the Net and this forum for answers. I'm simply stumped. I really appreciate any help. I'm including some info below that hopefully will help someone spy my error.

Much thanks!

Here's the start of the installation report page where I get the error:

00:00:00.078 - Installing Version: 4.4.0
00:00:00.078 -   Executing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.124 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Error! (see DotNetNuke.Schema.log for more information)
00:00:02.589 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success

And the beginning of DotNetNuke.Schema.log:
System.Data.SqlClient.SqlException: Must declare the scalar variable "@ModuleDefID".
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)

And relevant snippets from the web.config file:
  <connectionStrings>
    <!-- Connection String for SQL Server 2000/2005 -->
    <add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=username;pwd=password;" providerName="System.Data.SqlClient" />
  </connectionStrings>

  <appSettings>
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
    <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=username;pwd=password;" />
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
    <add key="AutoUpgrade" value="false" />
    <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="" />
    <add key="RemoveAngleBrackets" value="false" />
    <add key="PersistentCookieTimeout" value="0" />
    <add key="UsePortNumber" value="true" /> -->
    <add key="InstallationDate" value="4/25/2008" />
  </appSettings>

        <add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="dnn_" databaseOwner="dbo" />

 
New Post
4/27/2008 7:35 AM
 

Hello again!

I had read earlier that there is an installation problem caused when database collation is not set to case insensitive:
http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/186153/scope/posts/Default.aspx

I tried to create a database with Latin1-general-CI-AS collation and run install again but this didn't solve the problem. After re-reading the post, I decided to give a shot to  uninstalling and reinstalling SQL Server with case insensitive collation. I did this and created a DotNetNuke db with Latin1-general-CI-AS collation. I went through the installation process one last time and... voila - Success!

Hope this helps somebody...

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 4.8.2 on Vista install problemDNN 4.8.2 on Vista install problem


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