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 ...The stored procedure The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist.
Previous
 
Next
New Post
1/20/2012 4:02 AM
 

Hi all 

i hope there is one out there that can help me, if you need access to the server i can provide it 

im trying to install a ned DNN but iv got problems :

Installing DotNetNuke

Version: 06.00.01



Installation Status Report

00:00:00.140 - Checking File and Folder permissions Success
00:00:00.217 - Installing Version: 06.00.00
00:00:00.248 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Error! (see DotNetNuke.Schema.log.resources for more information)
00:00:11.205 -   Executing Script: DotNetNuke.Data.SqlDataProvider Error! (see DotNetNuke.Data.log.resources for more information)

 


Server Error in '/' Application.

The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.InvalidOperationException: The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist.

Source Error: 

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace: 

[InvalidOperationException: The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist.] System.Data.SqlClient.SqlCommand.DeriveParameters() +2858261 System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) +246 Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) +122 Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) +241 Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) +105 Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName) +12 Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) +97 DotNetNuke.Data.SqlDataProvider.UpdateDatabaseVersion(Int32 Major, Int32 Minor, Int32 Build, String Name) +287 DotNetNuke.Common.Globals.UpdateDataBaseVersion(Version version) +98 DotNetNuke.Services.Upgrade.Upgrade.InstallDatabase(Version version, String providerPath, XmlDocument xmlDoc, Boolean writeFeedback) +456 DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +132 DotNetNuke.Services.Install.Install.InstallApplication() +451 DotNetNuke.Services.Install.Install.OnLoad(EventArgs e) +328 System.Web.UI.Control.LoadRecursive() +66 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2428


 
New Post
1/20/2012 9:54 AM
 
this most commonly occurs when the site can connect to the database server but the user does not have permissions e.g. it is a basic user with only public permissions - please check what permissions that user has in your database (typically db_owner) - if it is a restored database the user record may be "orphaned" (as part of it's user record is in the MASTER database) - you can check for orphans via http://msdn.microsoft.com/en-us/library/ms175475.aspx , and http://www.dotnetnuke.com/Resources/Wiki/Page/Testing-database-connections.aspx covers testing database connections.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/26/2012 8:17 AM
 
ok i got it working thx 
 
New Post
3/11/2013 1:15 PM
 
My user has db_owner access and I am receiving the error: UpdateDatabaseVersionAndName' doesn't exist.

Please help!!! I've tried everything.
 
New Post
3/11/2013 2:58 PM
 
I tested my connectivity to the database server from my Dotnetnuke server and the test connection succeeded. So the servers can talk to each other, the SQL login is valid, it has db_owner access.... Am I perhaps missing a vital setting in my IIS 7.5 set up?
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...The stored procedure The stored procedure 'dbo.UpdateDatabaseVersionAndName' doesn't exist.


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