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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Database Migration: SQL Server 2005 Express to SQL Server 2005Database Migration: SQL Server 2005 Express to SQL Server 2005
Previous
 
Next
New Post
6/5/2006 8:01 PM
 

Hello All,

I have a working DNN 4.0.2 site utilizing a database created in SQL Server 2005 Express Edition and have attempted to migrate this database to SQL Server 2005, but an error results.

Yes, the <connectionStrings> strings and a <appSettings> in web.config were updated appropriately to reflect the SQL Server 2005 database.  See below.

When the website is accessed the "Could not find stored procedure 'dbo.GetPortals'." error was reported.  See details below.

I used Microsoft SQL Server Management Studio to export the Express database file to a SQL Server 2005 database. "Copy data from one or more tables or views"

After the web.config change was made, the web site was rebuilt in Visual Web Developer 2005 Express Edition, the IDE used to create the original site.

FYI, this error is mentioned in "DotNetNuke Installation Guide.pdf".  However, the Guide states "To solve this
error, delete the dnn.conifg file from the /Install folder."  "dnn.config" does not exist in the source tree.  Other postings have mentioned this fact, as well.

Any suggestions?

Thank you,

Wayne

<connectionStrings>

<!-- Connection String for SQL Server 2005 Express

<add name="DotNetNuke" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" />

<add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" providerName="System.Data.SqlClient" /> -->

<!-- Connection String for SQL Server 2000/2005 -->

<add name="DotNetNuke" connectionString="Server=(server);Database=(database);uid=(uid);pwd=(pwd;" providerName="System.Data.SqlClient" />

<add name="SiteSqlServer" connectionString="Server=(server);Database=(database);uid=(uid);pwd=(pwd);" providerName="System.Data.SqlClient" />

</connectionStrings>

<appSettings>

<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules

<add key="DotNetNuke" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" />

<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;" /> -->

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->

<add key="DotNetNuke" value="Server=(server);Database=(database);uid=(uid);pwd=(pwd);"/>

<add key="SiteSqlServer" value="Server=(server);Database=(database);uid=(uid);pwd=(pwd);"/>

Error reported:

Server Error in '/DotNetNuke1' Application.

Could not find stored procedure 'dbo.GetPortals'.

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.GetPortals'.

Source Error:

Line 154:            Dim objFolderController As New Services.FileSystem.FolderController
Line 155:            Dim objPortalController As New PortalController
Line 156:            Dim arrPortals As ArrayList = objPortalController.GetPortals()
Line 157:            Dim i As Integer
Line 158:            For i = 0 To arrPortals.Count - 1

Source File: C:\Inetpub\wwwroot\DotNetNuke1\App_Code\Global.asax.vb    Line: 156

Stack Trace:

[SqlException (0x80131904): Could not find stored procedure 'dbo.GetPortals'.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857162
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734774
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838
   System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +31
   System.Data.SqlClient.SqlDataReader.get_MetaData() +62
   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) +886
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +122
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) +62
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) +499
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) +201
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText) +40
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +262
   DotNetNuke.Data.SqlDataProvider.GetPortals() +47
   DotNetNuke.Entities.Portals.PortalController.GetPortals() +16
   DotNetNuke.Common.Global.CacheMappedDirectory() in C:\Inetpub\wwwroot\DotNetNuke1\App_Code\Global.asax.vb:156
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in C:\Inetpub\wwwroot\DotNetNuke1\App_Code\Global.asax.vb:266


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 



 

 
New Post
6/6/2006 2:41 AM
 

Hello All,

Also, when exporting from a MS SQL Server 2000 database to a MS SQL Server 2005 database, the same problem occurred. 

This behaviour was duplicated on 2 different hosts: XP and Server 2003.

It is very, very likely that the connection strings I use are correct.  For example, I created a DNN site using a MS SQL Server 2000, copied the database to Network Solutions, modified the connection string in web.config accordingling, and the DNN site ran perfectly.

The reason I want to move the database from one SQL server platform to another is that Network Solutions supports MS SQL Server 2000 (not 2005), but  MS Visual Web Developer 2005 Express Edition ships with SQL Server 2005 Express, and MS SQL Server 2000 will not install on XP (my laptop / development platform's operating system).

If anyone understands this behaviour, please be in touch.

Thank you,

Wayne

 

 

 
New Post
2/4/2007 1:38 AM
 
Were you able to get DNN to run with Network Solutions hosting?  I saw in another post that NS doesn't support DNN.
 
New Post
3/24/2009 6:35 PM
 

Any luck here yet? I have the same problem and am using shared hosting at www.ixwebhosting.com. Not very impressed with the service so far! :(

Jacob Bushnell


www.watchidaho.net - live web cams in Idaho
 
New Post
3/24/2009 7:07 PM
 

If you just exported data tables and imported them into the new SQL Server, there are quite a few stored procedures that probably didn't make it over.  If fact, I'd guess that NONE of the stored procedures made it over.

I believe that you should make a BACKUP of your database on the original SQL Server Express, and then RESTORE this to your SQL Server 2005.  That will move the data, the stored procedures, and whatever else is there.




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Database Migration: SQL Server 2005 Express to SQL Server 2005Database Migration: SQL Server 2005 Express to SQL Server 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