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 ...SQL2005 Exp User Instance-Incorrect Error Msg in 4.4.1SQL2005 Exp User Instance-Incorrect Error Msg in 4.4.1
Previous
 
Next
New Post
3/9/2007 11:41 AM
 

I just reinstalled SQL2005 Express on my laptop after unsuccessfully attempting to install SP2 for it (SP2 worked for all components except the database engine).  There are many issues without resolution in the installation of SQL2005 SP2, if you have not installed it yet, make sure you have a good backup before proceeding.

After doing the whole installation using the SQL 2005 Exp package with Advanced Services, which went flawlessly, I tried to run a recent installation of 4.4.1 I had done and it did not work, gave me the error below:

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

ERROR: Could not connect to database.

Generating user instances in SQL Server is disabled. Use sp_configure 'user instances enabled' to generate user instances.

I did unselect the User Instances feature during installation thinking that none of my databases was setup that way.  I had forgotten that I did not modify the setup of the 4.4.1 database because it was supposed to be a quick and dirty test configuration on this machine.

Anyway, the recommended remedy in the error message is not correct, instead of using the recommendation to "Use sp_configure 'user instances enabled' to generate user instances" the correct command sequence is below:

EXEC sp_configure 'user instances enabled',1
GO
RECONFIGURE
GO

After the commands above you can just do F5 in the browser and DNN will connect to the database.

For an article on how to change the database from a "User Instance" to a regular SQL database you can manage with Management Studio see this link: http://www.dotnetnuke.com/Community/BlogsDotNetNuke/tabid/825/EntryID/1202/Default.aspx

Carlos

 
New Post
3/9/2007 11:47 AM
 

Do you think this is related?

I have a DNN4 site running on Windows 2003 server with a SQL Server2000 DB. It has been running great until about an hour ago when Microsoft-released Security patches were installed. The site now give the following error. Any ideas? Oh, NO upgrade was performed on DNN. The installation has been untouched.

DotNetNuke Upgrade Error

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

ERROR: Could not connect to database.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

 
New Post
3/9/2007 12:36 PM
 

Mbiro:

I don't think so.  There has not been a service pack for SQL 2000 recently.  But the service pack for 2005 will be installed automatically if your WindowsUpdate settings are doing unattended updates.

First thing I would do is to reboot the server(s).  Is SQL 2000 running on the same box as DNN?  If not, reboot both and see if you can connect to SQL with Query Analyzer on the same box and from a separate one.

Edited to add that if you are indeed using SQL 2000, then the error message by DNN is also misleading/incorrect.

Carlos

 

 
New Post
3/9/2007 12:59 PM
 
Yes, I can connect to the database outside of DNN. In fact, I have other websites, both .net 1.1 and .net2 that run on that same box and connect to the same sql server 2000 box and they are unaffected by the patches. I agree the error is misleading because I am certainly running SQL Server 2000. Again, DNN and SQL reside on different boxes.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL2005 Exp User Instance-Incorrect Error Msg in 4.4.1SQL2005 Exp User Instance-Incorrect Error Msg in 4.4.1


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