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 ...The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )
Previous
 
Next
New Post
2/6/2006 11:00 AM
 
david taylor

taylorsoftware.zapto.org
Joined: 2/3/2006
Posts: 28

I'm trying to install a new version of DNN via WebDevExpress.  I've installed SQLExpress, enabled TCP/IP on it, and created a database called "d2".

I then created a new DNN website (via WebDevExpress).  I modified the connectionAfter doing a build and trying to run the website, I get the error below:

DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.

It's very strange, because I am NOT upgrading at all, I'm trying to get the darn thing to run for the first time.

To eliminate permission problems, I've given have that virtual IIS directory permission of my Administrator account.  Did the same thing at the NTFS level also.  Also strange is that intemittently another error is reported:

Could not find file 'c:\inetpub\wwwroot\dnn\Providers\DataProviders\SqlDataProvider\DotNetNuke_template.mdf'

There is no such MDF is the directory mentioned in the error, but then again, since I used WebDevExpress2005 to install the DNN website, I would have thought it would put all necessary files in place.

This is really disappointing, I expect much more quality from Microsoft tools.  Anyone know the solution?  I've tried several times in different virtual directories, each time with identical results.

 
 
New Post
2/15/2006 5:59 AM
 
don Vickers


www.ExcellentSystems.us
Joined: 12/26/2005
Posts: 68

I have encountered  the

Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version

on a fresh install of 4.02.

I have verified that the SQL 2005 database is setup with  valid User that wns the DotNetNuke database and that SQL is operational.

Does anyone have a suggestion for a resolution? 

Thanks.
 
New Post
2/15/2006 11:05 AM
 
david taylor

taylorsoftware.zapto.org
Joined: 2/3/2006
Posts: 28

My ultimate resolution was the following:

1. During the install, I didn't read the log it generated carefully.  Some steps had failed. 

2. It turned out those steps failed due to insufficient file system access to the directories.

3. By granting full access to the ASPNET account, I was able to reinstall and run successfully.
 
New Post
2/15/2006 4:57 PM
 
Chuck Tilly

Joined: 4/14/2004
Posts: 21

dtaylo75,

Thanks for your update.  I too was having the same problem and this solved it.  I had used the ASPNET account in the past on a previous machine I had and it worked fine.  But this time around when I went to go add the ASPNET account, I couldn't find it using the normal method I used.  I will share that here in case anyone else runs into the same problem.  This is for Windows XP Pro.

From within the security dialog for the directory I typically like to use the "Check Names" feature.  I will type the first couple of characters and then have the "Check Names" feature return for me a list to pick from.  I typed in the letters "asp" and received a "Name Not Found" response.  I thought that was unusual, but I remember the docs saying that sometimes you may need to use the "NETWORK SERVICE" account.  This account I found without any difficulty by typing in "net" followed by "Check Names".  So I chose it, and granted "Full Control".

As I have discovered, this account does not work though.  For Windows XP you need the ASPNET account.  But in order to find it using the "Check Names" feature you must type in "aspnet".

The error I was getting (below) is NOT at all helpful.  It certainly had me barking up the wrong tree.

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

 
 
New Post
2/15/2006 6:13 PM
 
don Vickers


www.ExcellentSystems.us
Joined: 12/26/2005
Posts: 68

Thanks for your kind reply.  Reading logs?  Is that something we should do? I don’t think it will ever catch on.

 

The system is a spare Windows XP system at home so it will be a while before I can check those pesky logs. 

 

Given that the system is just a sandbox to learn DNN and given that it is a standalone XP system not in a domain I had made ASPNET a part of the administrators group thinking that would get it any and all file access. Given that there is no Permissions tab in a workgroup environment I didn’t see any other way to allow ASPNET and friends to have sufficient permissions.

 

Is there another and better way?

 

Thanks again!
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )


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