Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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.3.3 Install vm_view errorDNN 4.3.3 Install vm_view error
Previous
 
Next
New Post
7/26/2006 6:32 PM
 
Joseph Nyleen

Joined: 4/13/2006
Posts: 5
~Hey again

When I'm doing an install of DNN 4.3.3, my installation goes like this:

Installing DotNetNuke

Version: 04.03.03



Installation Status Report

00:00:00.109 - Installing Version: 3.1.0
00:00:00.109 - Installing Script: DotNetNuke.SetUp.SqlDataProvider
00:00:00.171 - Installing Script: DotNetNuke.Schema.SqlDataProvider
00:00:08.921 - Installing Script: DotNetNuke.Data.SqlDataProvider
00:00:24.919 - Installing MemberRole Provider:
00:00:24.919 - Executing InstallCommon.sql
00:00:26.107 - Executing InstallMembership.sql
00:00:27.279 - Executing InstallProfile.sql
00:00:27.716 - Executing InstallRoles.sql
00:00:28.950 - Upgrading to Version: 3.1.1
00:00:32.060 - Upgrading to Version: 3.2.0
00:00:32.231 - Upgrading to Version: 3.2.1
00:00:32.356 - Upgrading to Version: 3.2.2
00:00:32.388 - Upgrading to Version: 3.2.3
00:00:34.872 - Upgrading to Version: 3.2.4
00:00:34.950 - Upgrading to Version: 3.2.5
00:00:35.012 - Upgrading to Version: 3.2.6
00:00:35.075 - Upgrading to Version: 3.2.7
00:00:35.091 - Upgrading to Version: 3.3.0
00:00:35.231 - Upgrading to Version: 3.3.1
00:00:35.309 - Upgrading to Version: 3.3.2
00:00:35.387 - Upgrading to Version: 3.3.3
00:00:35.903 - Upgrading to Version: 4.0.0
00:00:36.590 - Upgrading to Version: 4.0.1
00:00:36.731 - Upgrading to Version: 4.0.2
00:00:36.762 - Upgrading to Version: 4.0.3
00:00:36.778 - Upgrading to Version: 4.0.4
00:00:38.497 - Upgrading to Version: 4.0.5
00:00:38.512 - Upgrading to Version: 4.0.6
00:00:38.512 - Upgrading to Version: 4.0.7
00:00:38.528 - Upgrading to Version: 4.3.0
00:00:38.575 - Upgrading to Version: 4.3.1
00:00:38.622 - Upgrading to Version: 4.3.2
00:00:38.715 - Upgrading to Version: 4.3.3
00:00:39.200 - Performing General Upgrades
00:00:39.793 - Loading Host Settings:
00:00:40.059 - Configuring SuperUser:
00:00:40.371 - Installing Desktop Modules:
00:00:40.371 - Installing Modules:
00:00:40.418 - Executing Additional Scripts:
00:00:40.450 -   Creating Portal: My Website
00:00:41.106 -   Error: Invalid object name 'vw_Users'.
00:00:41.106 -   Portal failed to install:
00:00:41.106 - Installing Optional Resources:

Installation Complete



Click Here To Access Your Portal



Is this something that needs to be taken care of on the database side? Or is there a function in the source doing this? Our DB has vw_aspnet_Users, not vw_Users. Could this be the problem? These entries do not exist in the DB before the installation starts rolling, any hints? If I try to access the protal, of course, I get a null reference exception.
 
New Post
7/27/2006 7:38 PM
 
Joseph Nyleen

Joined: 4/13/2006
Posts: 5
~Hey Everyone!

Okay, got the above problem solved.  Here's what the issue was. In my older version of DNN that I have running (3.2.2), in my web.config, instead of the default database owner (dbo), I have it set to a specific user w/ dbo permissions. This works fine. I attempted this again in my install of 4.3.3.  I went though all DNN's SqlDataProvider logs, and went hunting for errors. It turns out that starting in roughly 3.2.3 it seems that the macro controlling db ownership got a little flakey. Errors started popping up randomly (some updates went okay, some not so much) regarding null references to tables that didn't exist. The fact was that they DID exist, but they were being created for 'dbo' not my specificed 'user' (regardless of the config file). Rather than re-write all the DataProviders, I simply returned my web.config  DatabaseOwner back to "dbo" and gave a heaving *sigh* as that worked flawlessly. For reference:

OS: Windows Server 2003
Database: MS SQL 2000
Server: IIS 6.0
DNN Versions Installed: 3.2.2  and 4.3.3

This may not be an issue in other setups, as I could not find this problem referenced anywhere else (which I found odd). At least I have a better feel for how DNN talks to the DB! *grin*
 
New Post
8/18/2006 7:09 PM
 
Donny

Joined: 8/18/2006
Posts: 1

For the sake of anyone else experiencing similar issues, I had to make the following edit to the web.config file before DNN would install successfully:

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

By default, the objectQualifier property was set to an empty string.  With the empty string set as the objectQualifier, installation would fail when attempting to create the default portal everytime.  Once it set this value to "DotNetNuke" , installation worked perfectly.  Hope this helps someone out there!

Cheers,
Donny
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 4.3.3 Install vm_view errorDNN 4.3.3 Install vm_view error


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