Hi, I'm receiving the exception below whenever trying to add a new page.  Either from the tool menu or from the page management page.

We're running 7.3.3  My research has suggested this could be caused by a failure during an upgrade.  We did upgrade to this version, but that was at least 6 months ago and I do not recall any failures at the time.

Would someone be able to tell if this is indeed caused by an issue during upgrade and/or how me can resolve this at this point?  Since the upgrade was so long ago, restoring to before the upgrade is not a feasible solution.

Thanks for your time.

Exception::

ModuleId:-1

ModuleDefId:-1

FriendlyName:

ModuleControlSource:DesktopModules/Admin/Tabs/ManageTabs.ascx

AssemblyVersion:7.3.3

PortalID:0

PortalName:****

UserID:1

UserName:host

ActiveTabID:103

ActiveTabName:Contact Us

RawURL:/ContactUs/tabid/103/ctl/Tab/activeTab/settingTab/Default.aspx?popUp=true

AbsoluteURL:/Default.aspx

AbsoluteURLReferrer:http://www.****.com/ContactUs/tabid/103/ctl/Tab/activeTab/settingTab/Default.aspx?popUp=true

UserAgent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.81 Safari/537.36

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:bdc9d97c-df0f-4464-be1d-755cc8044601

InnerException:Procedure or function 'AddTabAfter' expects parameter '@IsSystem', which was not supplied.

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:System.Data.SqlClient.SqlConnection.

StackTrace:

Message:

DotNetNuke.Services.Exceptions.ModuleLoadException: Procedure or function 'AddTabAfter' expects parameter '@IsSystem', which was not supplied. ---> System.Data.SqlClient.SqlException: Procedure or function 'AddTabAfter' expects parameter '@IsSystem', which was not supplied.
   at System.Data.SqlClient.SqlConnection. (SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection. (SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at PetaPoco.Database.ExecuteScalar[T](String sql, Object[] args)
   at DotNetNuke.Data.PetaPoco.PetaPocoHelper.ExecuteScalar[T](String connectionString, CommandType type, Int32 timeout, String sql, Object[] args)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScalar[T](String procedureName, Object[] commandParameters)
   at DotNetNuke.Data.DataProvider.AddTabAfter(TabInfo tab, Int32 afterTabId, Int32 createdByUserID)
   at DotNetNuke.Entities.Tabs.TabController.AddTabInternal(TabInfo tab, Int32 afterTabId, Int32 beforeTabId, Boolean includeAllTabsModules)
   at DotNetNuke.Entities.Tabs.TabController.AddTabAfter(TabInfo tab, Int32 afterTabId)
   at DotNetNuke.Modules.Admin.Tabs.ManageTabs.SaveTabData(String strAction)
   at DotNetNuke.Modules.Admin.Tabs.ManageTabs.cmdUpdate_Click(Object Sender, EventArgs e)
   --- End of inner exception stack trace ---

Source:

Server Name: ********

I do not have either of those files, I assume because I'm on 7.3.3.

All of the log.resources files I have are 1 kb and appear to be empty.

It looks like we ran the 7.4 upgrade on a test version of the website while it was mistakenly still pointed to our live database.  So the live database was upgraded to comply with 7.4, while the live website is still configured for 7.3.3.  Luckily it's still mostly functional.

Rather than try and revert anything we are going to accelerate our plans to move the live site to 7.4

Thanks for pointing us in the right direction.