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 ...Upgrade problem from DNN 4.x to DNN 5 ERROR: Could not connect to database specified in connectionStUpgrade problem from DNN 4.x to DNN 5 ERROR: Could not connect to database specified in connectionSt
Previous
 
Next
New Post
12/29/2008 6:43 PM
 

Hi,

I am trying to upgrade a DNN 4.x install to a DNN 5 installation. I first had the complete DNN 4.x running on my local machine with the db on a different database server. I copy-paste the DNN 5 install over the DNN 4 files and modified the web.config with aid of subversion filecomparison. I am almost 100% sure my webconfig is fine... Unfortunately I run into next error:

Error Installing DotNetNuke
Current Assembly Version: 05.00.00
ERROR: Could not connect to database specified in connectionString for SqlDataProvider

I removed all dll's and ascx of which I know they should be in DNN 5. But the problem persists. I also removed all 3rd parties desktopmodules and dll's..but still same problem. I switched off the firewall, but still...let's sleep a night on this one..if you have seen this error before and know the fix. Please let me know.

J.

 
New Post
12/29/2008 6:48 PM
 

Check your connection string. I think there are two to look at.

Also check that your ASP.NET application (DNN) has permissions to connect to the database on the database server end.



Alex Shirley


 
New Post
12/29/2008 7:08 PM
 

Thankx for the quick response.

The connection strings tested on VS2008. OK. I found however that I did not pass the objectqualifier into the new webconfig. So now it runs, but with a lot of errors:

Current version: 4.3.5

00:00:00.953 - Upgrading to Version: 5.0.0
00: - Executing Script: 04.03.06.SqlDataProvider Error! (see 04.03.06.log for more information)
00:00:02.968 - Executing Script: 04.03.07.SqlDataProvider Error! (see 04.03.07.log for more information)
00:00:03.781 - Executing Script: 04.04.00.SqlDataProvider Error! (see 04.04.00.log for more information)
00:00:04.875 - Executing Script: 04.04.01.SqlDataProvider Error! (see 04.04.01.log for more information)
00:00:05.812 - Executing Script: 04.05.00.SqlDataProvider Error! (see 04.05.00.log for more information)
00:00:07.546 - Executing Script: 04.05.01.SqlDataProvider Error! (see 04.05.01.log for more information)
00:00:16.046 - Executing Script: 04.05.02.SqlDataProvider Error! (see 04.05.02.log for more information)
00:00:18.750 - Executing Script: 04.05.03.SqlDataProvider Error! (see 04.05.03.log for more information)
00:00:19.828 - Executing Script: 04.05.04.SqlDataProvider Error! (see 04.05.04.log for more information)
00:00:20.859 - Executing Script: 04.05.05.SqlDataProvider Error! (see 04.05.05.log for more information)
00:00:21.562 - Executing Script: 04.06.00.SqlDataProvider Error! (see 04.06.00.log for more information)
00:00:23.031 - Executing Script: 04.06.01.SqlDataProvider Error! (see 04.06.01.log for more information)
00:00:23.625 - Executing Script: 04.06.02.SqlDataProvider Error! (see 04.06.02.log for more information)
00:00:24.562 - Executing Script: 04.07.00.SqlDataProvider Error! (see 04.07.00.log for more information)
00:00:26.406 - Executing Script: 04.08.00.SqlDataProvider Error! (see 04.08.00.log for more information)
00:00:27.500 - Executing Script: 04.08.01.SqlDataProvider Error! (see 04.08.01.log for more information)
00:00:28.578 - Executing Script: 04.08.02.SqlDataProvider Error! (see 04.08.02.log for more information)
00:00:29.421 - Executing Script: 04.09.00.SqlDataProvider Error! (see 04.09.00.log for more information)
00:00:30.156 - Executing Script: 04.09.01.SqlDataProvider Error! (see 04.09.01.log for more information)
00:00:31.125 - Executing Script: 05.00.00.SqlDataProvider Error! (see 05.00.00.log for more information)

Default.aspx?tabid=156&error=The+stored+procedure+'dbo._V4A_DNN_GetPortalSettings'+doesn't+exist.&content=0

I think the objectqualifier _V4A_DNN is giving more problems...


J.

 
New Post
12/29/2008 7:12 PM
 

Most errors contain something like:

Can I simply rerun every script from the lowest to highest number without any problems? Is there a way to do this? I can't run host->sql right now. Is there away to put the 'timestamp' of scripts back in time so that I can rerun automatically?

Any help appreciated.

J.

System.Data.SqlClient.SqlException: Cannot find the object '_V4A_DNN_Forum_NewsArticleAdd', because it does not exist or you do not have permission.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText)
   at DotNetNuke.Data.SqlDataProvider.GrantStoredProceduresPermission(String Permission, String LoginOrRole)

if exists (select * from dbo.sysusers where name='prod1')  begin    declare @exec nvarchar(2000)     declare @name varchar(150)     declare sp_cursor cursor for select o.name as name     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('_V4A_DNN_')) = '_V4A_DNN_' or left(o.name,7) = 'aspnet_')     open sp_cursor     fetch sp_cursor into @name     while @@fetch_status >= 0       begin        select @exec = 'grant EXECUTE on ' +  @name  + ' to [prod1]'        execute (@exec)        fetch sp_cursor into @name       end     deallocate sp_cursor  end


 

 
New Post
12/29/2008 7:22 PM
 

hmm...getting late..and interesting. Seems the <username> is used during creation instead of [dbo] user. How to fix this? I think by altering the dbo owner? But will it also rename all objects from [<username>] to [<dbo>] ? Anybody with DBA experience on this?

CREATE PROCEDURE [<username>].[_V4A_DNN_Forum_NewsArticleAdd]

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade problem from DNN 4.x to DNN 5 ERROR: Could not connect to database specified in connectionStUpgrade problem from DNN 4.x to DNN 5 ERROR: Could not connect to database specified in connectionSt


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