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 ...Upgrading 4.9 to 5.1 on SQL 2005Upgrading 4.9 to 5.1 on SQL 2005
Previous
 
Next
New Post
11/1/2009 9:12 AM
 

After quite some time, and allot of trial and error I have come to the conclusion that this error is caused by the function GrantUserDefinedFunctionsPermission() ignoring the database owner setting in the web.config file. Does anyone know if this will be fixed in the next version?

 
New Post
11/2/2009 6:48 PM
 

Having looked more closely at the SQL script that is run by GrantUserDefinedFunctionsPermissions() I think I can see what the problem is.

The script first runs:

select * from dbo.sysobjects o where ( OBJECTPROPERTY(o.id, N'IsProcedure') = 1 or OBJECTPROPERTY(o.id, N'IsExtendedProc') = 1 or OBJECTPROPERTY(o.id, N'IsReplProc') = 1 )     and OBJECTPROPERTY(o.id, N'IsMSShipped') = 0     and o.name not like N'#%%'     and (left(o.name,len('')) = '' or left(o.name,7) = 'aspnet_')

This returns all the stored procedure names but without the database owner appended. So for example it returns "AddSearchItem" which is actually called "dbo169059670.AddSearchItem" in the database. I actually ran the above SQL on my DNN to check.

It then runs:

grant EXECUTE on AddSearchItem to [dbo169059670]

but this will always fail unless you append the database owner, so it should be:

grant EXECUTE on dbo169059670.AddSearchItem to [dbo169059670]

which when I check runs happily. Also pointed out in another bug it should be:

grant EXECUTE on [dbo169059670].[AddSearchItem] to [dbo169059670]

There are other errors in the log but these can be fixed by manually changing the permsions which is what this function should do. When I run all the upgrade scripts manually and apply the permissions it seems to work.

Can this be fixed please it is a pain to install all the scripts manually.

 

 

 

 

 

 

 

 

 

 
New Post
11/13/2009 4:19 PM
 

I finally found the time to manually install all the SQL files. The tricky part was with the HTML module as I had to remove the scripts from the install and put them in manually. If you do not remove the scripts then the install will fail and the module will not be installed. Doing all this I managed to get it all working.

During testing however I found that my disappearing module problem due to the fact that the caching provider does not like dual core servers had returned. Even with Web Farm support enabled (which fixed it last time) I add modules, only for them to appear and disappear at random refreshes.

I have given up on 5.1 for the moement, and am going back to 4.9 where I will probably stay. Just means I have to re-write my plugin but that is probably simpler than getting 5.1 working.

:-(

 

 

 

 
New Post
11/14/2009 1:33 AM
 

Mine is failing becasue it appears that I am some how missing the  GetDatabaseserver stored procedure if anyone has this laying around and can send it my way it would be greatly appreciated.  I had a huge problem upgrading this, this evening on my GoDaddy acct and I am now stuck with this error.

I ended up starting over and letting GoDaddy install the 5.1 for me and then I took my 4.9DB and restored it in hopes that the upgrade would just run thorugh it and bring the database up to par but that errored as well so now I"m trying to get it fixed by hand.  Thanks.

 

Server Error in '/dotnetnuke' Application.

Could not find stored procedure 'dbo.GetDatabaseServer'.

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.Data.SqlClient.SqlException: Could not find stored procedure 'dbo.GetDatabaseServer'.

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:

[SqlException (0x80131904): Could not find stored procedure 'dbo.GetDatabaseServer'.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +1949258
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4845243
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2392
   System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +33
   System.Data.SqlClient.SqlDataReader.get_MetaData() +83
   System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +297
   System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +954
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +141
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +70
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) +541
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +234
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText) +48
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +279
   DotNetNuke.Data.SqlDataProvider.GetDatabaseServer() +71
   DotNetNuke.Common.Initialize.GetDatabaseEngineVersion() +59
   DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +721
   DotNetNuke.Common.Initialize.Init(HttpApplication app) +152
   DotNetNuke.Common.Global.Global_BeginRequest(Object sender, EventArgs e) +560
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75


Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3053

Jason
Webmaster of

thefuzz4.net

Were going to be HUGE

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrading 4.9 to 5.1 on SQL 2005Upgrading 4.9 to 5.1 on SQL 2005


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