Hello Joe,
I did go to the /Setup page (assuming it would go to the /Setup/Default.aspx page. At least I saw a long list of upgrade procedures perform.
In the Features page I get:
System Information
mojoPortal Version 2.3.9.4 MSSQL
Operating System Microsoft Windows NT 6.2.9200.0
ASP.NET Info v4.0.30319 Running in Full Trust
Server Time Zone Central Standard Time
Server Local Time (GMT -6) 2.12.2012 16:45:28
Greenwich Mean Time (GMT/UTC) 2.12.2012 22:45:28
Feature Versions [Help]
Feature Schema Version
blog 2.6.0.0
contactform 0.0.0.6
eventcalendar 0.0.0.6
feed-manager 0.0.1.0
forums 2.2.0.1
imagegallery 0.0.0.8
kdmediaplayer 1.0.0.1
linksmodule 0.0.0.9
pollfeature-byChristianFredh 0.0.0.5
sharedfiles 0.0.1.0
surveyfeature 1.8.0.0
webstore 0.0.7.3
Pretty sure I uploaded everything, I also did another fresh install where the blog feature worked fine.
And then I looked at the features page on another Arvixe install where the blog is working OK and I get:
Operating System Microsoft Windows NT 6.2.9200.0
ASP.NET Info v4.0.30319 Running in Full Trust
Server Time Zone Central Standard Time
Server Local Time (GMT -6) 2.12.2012 16:53:36
Greenwich Mean Time (GMT/UTC) 2.12.2012 22:53:36
Feature Versions
Feature
Schema Version
blog
2.6.0.7
contactform
0.0.0.6
eventcalendar
0.0.0.6
feed-manager
0.0.1.0
forums
2.2.0.1
imagegallery
0.0.0.8
kdmediaplayer
1.0.0.1
linksmodule
0.0.0.9
pollfeature-byChristianFredh
0.0.0.5
sharedfiles
0.0.1.0
surveyfeature
1.8.0.0
webstore
0.0.7.3
so it seems that only the blog feature has not been upgraded for some reason as it is in v. 2.6.0.0 but not in 2.6.0.7 as it should be.
OK, then I rerun the setup and read more closely what happens and I see:
Running script blog - 2.6.0.1 - 00:00:00.1875047
System.Data.SqlClient.SqlException (0x80131904): String or binary data would be truncated. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at mojoPortal.Data.SqlHelper.ExecuteNonQuery(SqlTransaction transaction, CommandType commandType, String commandText, Int32 commandTimeout, SqlParameter[] commandParameters) at mojoPortal.Data.DBPortal.DatabaseHelperRunScript(String script, String overrideConnectionInfo) at mojoPortal.Data.DBPortal.DatabaseHelperRunScript(FileInfo scriptFile, String overrideConnectionInfo) at mojoPortal.Business.DatabaseHelper.RunScript(Guid applicationId, FileInfo scriptFile, String overrideConnectionInfo) ClientConnectionId:48811829-cd76-4599-a230-37fc5ebf7826 - 00:00:00.2031299
Could there be some problem data in my blog that is preventing the first blog upgrade script from running? The old blog entries were not of any significance so I could throw them away. But I am not sure how I could delete something blog related from the database without doing more problems. There is some icelandic text in these entries that has not been any problem for mojoPortal so far.
regards
-Finnur