Hey, first of all many thanks and grats for 1.9.3 reaching final. I want to try it on my new test DNN 5.0.1 where I am using 1.9.1 which work like charm. But I'm unable to get 1.9.3 working (through new install or upgrade) always ending on following error.

InnerException: Could not find stored procedure 'prov_role_getroles'.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Data.SqlClient.SqlConnection.OnError
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Could not find stored procedure 'prov_role_getroles'. ---> System.Data.SqlClient.SqlException: Could not find stored procedure 'prov_role_getroles'. 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.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.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at YAF.Classes.Data.DBAccess.GetDatasetBasic(SqlCommand cmd, Boolean transaction) at YAF.Classes.Data.DBAccess.GetData(SqlCommand cmd, Boolean transaction) at YAF.Classes.Data.DBAccess.GetData(SqlCommand cmd) at YAF.Providers.Roles.DB.GetRoles(Object appName, Object username) at YAF.Providers.Roles.YafRoleProvider.GetRolesForUser(String username) at System.Web.Security.RolePrincipal.IsInRole(String role) at System.Web.Security.Roles.IsUserInRole(String username, String roleName) at yaf_dnn.DotNetNukeModule.DotNetNukeModule_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:

I'm not uptodate with how you install yaf in DNN but that very clearly means that your YAF database has not been update. You need to run the install routine in order for YAF to upgrade its tables and stored procedures. Which is why your getting "Could not find stored procedure!".

---

I had to pass like 6 errors and they just kept coming so I kept fixing, yet I ended on dumbest one without realizing I haven't upgraded yet :-DD. I probably won now "worst topic ever award". :oops: :-d Ok I had to fix another 2 SQL related errors and upgrade went ok now.

Nope -- we're just happy when it's something simple 😉

Ok I had to fix another 2 SQL related errors and upgrade went ok now.

were those sql errors on our end, and if so what were they? but glad you muddled on through ;-)

---