 |
|
|
|
Joined: 3/15/2012
Posts: 4
|
|
|
I upgraded to 6.1.4 last night and the site seemed fine. I was able to bring up the Home page, and browse around to various other pages. This morning, as I tried to open the Home page, hillsdalebaptist.org, I am met with the following, what can I do?:
Server Error in '/' Application.
Procedure or function 'GetPortals' expects parameter '@CultureCode', which was not supplied.
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: Procedure or function 'GetPortals' expects parameter '@CultureCode', which was not supplied.
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): Procedure or function 'GetPortals' expects parameter '@CultureCode', which was not supplied.] System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection) +1950890 System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection) +4846875 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.GetPortals() +71 DotNetNuke.Entities.Portals.PortalController.GetPortals() +28 DotNetNuke.Common.Initialize.CacheMappedDirectory() +38 DotNetNuke.Common.Initialize.InitializeApp(HttpApplication app) +643 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.3623; ASP.NET Version:2.0.50727.3634
|
| |
|
|
 | |
|
|
 |
 |
www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
|
| |
| |
|
|
|
Joined: 3/15/2012
Posts: 4
|
|
|
I did force the upgrade scripts to run, and they went through with no errors.
|
| |
|
|
| |
|
|
 |
www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
|
|
|
Check the file version of the assembly DotNetNuke.SqlDataProvider.dll in the site's /bin folder. If you used the Upgrade package it should be 6.1.4.127. I suspect that it is an earlier version that did not get replaced when you uploaded the files from the upgrade package. While checking that file version, also take a look at the DotNetNuke.dll assembly version. It also should be 6.1.4.127.
BTW, from what version did you upgrade?
Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
|
| |
|
|
| |
|
|
|
Joined: 3/15/2012
Posts: 4
|
|
|
You were right that the files in the bin folder did not get updated. I FTP'd the whole bin folder again, insuring that they overwrote the web files. I am now getting the following error:
DotNetNuke Error
Domain Name Windows Server 2003 Does Not Exist In The Database
DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:
Web Server Processing
When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.
HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )
The Request URL is parsed based on the "/" character
A Domain Name is constructed using each of the relevant parsed URL segments.
Examples:
URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory
Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.
Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.
Example:
URL: http://localhost/DotNetNuke/default.aspx
URL: http://MACHINENAME/DotNetNuke/default.aspx
URL: http://209.32.134.65/DotNetNuke/default.aspx
PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke
Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above.
|
| |
|
|
| |