I managed to login and get to the Admin pages and whatever skin I choose has the error for mp:WatermarkTextBox'. Removing this code from each theme.skin file allows me to load the page again with a different skin but not found one yet which does have the problem with the layout.master file of the site or page skin.

I will plan to download a new skin from here and see if that helps. 

Does not contain a folder 

pageskin-1chem-moasic5/

so I don't understand how it is reading the file theme.skin 

C:/websites/mojoportalcms/mojoportal

to have everything in 

C:/websites/mojoportalcms

That improved the situation and the again the /setup/default.aspx ran fine and then when pressing on the home page link, the error for favicon.html was not seen.

I am seeing this error message though on the local host, which seems to be linked to a skin I had made. Obviously, the skin used to run fine. 

 

Server Error in '/' Application.

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Unknown server tag 'mp:WatermarkTextBox'.

Source Error:
 

Line 135:/>

Line 136:

Line 137:<mp:WatermarkTextBox runat="server"

Line 138: CssClass=" "

Line 139:/>

Source File: /App_Themes/pageskin-1chem-moasic5/theme.skin    Line: 137

I'll log a bug for this to see what we can do about it including the favicons.html properly when the site is installed in a virtual directory, which seems to be what you're doing. 

Thanks,
Joe

meta name="SKYPE_TOOLBAR" content="SKYPE_TOOLBAR_PARSER_COMPATIBLE" 

-- #include file="/Content/failsafeskin/includes/favicons.html"

portal:MetaContent ID="MetaContent" runat="server" DisableContentType="true" PreZoomForIPhone="false"

Server Error in '/mojoportal' Application.

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not find a part of the path 'C:\websites\mojoportalcms\Content\failsafeskin\includes\favicons.html'.


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4110.0

The site should be in this path location C:\websites\mojoportalcms\mojoportal so it seems the PATH has got confused. I'll look for that in the config files. 

Getting a local browser message is weird. Have you checked the log (/data/currentlog.config)?

I know you added the user account but you may not have done all of what is needed there. 

-- Create a SQL Server authenticated login
CREATE LOGIN NewLogin WITH PASSWORD = 'StrongPassword123!';
GO

-- Enable the login if it was disabled
ALTER LOGIN NewLogin ENABLE;
GO   

-- Switch to the target database
USE TargetDatabase;
GO

-- Create the user mapped to the existing login
CREATE USER NewUser FOR LOGIN NewLogin;
GO   

I think I have everything correct, the mojoportal database has been backed up and restored in the new 2025 database platform, and I have edited the line 

add key="MSSQLConnectionString" value="server=DatabaseServerName\SQLExpress;UID=DatabaseSQLUser;PWD=SQLUserPassword;database=DatabaseName"

to match my new instance.

like this

add key="MSSQLConnectionString" value="server=.\SQLExpress01;UID=DatabaseSQLUser;PWD=SQLUserPassword;database=mojoportal"

and have put the user account into the logins group for the new database. 

I am now facing a local browser message can't reach this page for the url /setup/default.aspx and no asp.net error messages which is unusual. 

If I restore the old settings string the need upgrade message appears but the /setup/default.aspx page at least runs fine. 

Karl

I'll upgrade this asap. 

Which version of SQL Express are you running?

It looks like you're upgrading from 2.9.0.3. The script trying to run is to upgrade to 2.9.04 and it is trying to run several DROP .... IF EXISTS statements. That feature was added in SQL Server 2016, so if you're on an older version than 2016, you'll need to edit the/Setup/applications/mojoportal-core/SchemaUpgradeScripts/mssql/2.9.0.4.config file to remove the IF EXISTS from each line. Once you do that, you can re-run setup and it should get you to the next upgrade script at least.

I recommend upgrading to a newer version of SQL Server because we don't target or test for 2016 anymore.

Thanks,
Joe

Welcome to mojoPortal Setup

Checking Filesystem and Database

File system permissions ok.

MSSQL database connection ok.

database permissions are sufficient to alter schema.

database initial schema already exists.

database core schema needs upgrade.

94 site(s) found.

Upgrading mojoportal-core

2.9.0.4

System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near the keyword 'IF'. at System.Data.SqlClient.SqlConnection.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, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry) 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.Business.DatabaseHelper.RunScript(Guid applicationId, FileInfo scriptFile, String overrideConnectionInfo) ClientConnectionId:89e9898b-129d-4d2f-9c45-c4648f0cecfb Error Number:156,State:1,Class:15

 

Note

upgradeNeeded

 

Database Platform

MSSQL

Database Schema Version

2.9.0.3

Application Code Version

3.1.6.0

Message

upgradeNeeded

Yes. It's ready to be used. We added a blog post about it as well. 

Thanks,
Joe

Is this recommended and ready to use?

Crispin

Good news, I found the issue you are having and fixed it.

The fix will be in the shortly upcoming release.

Thanks,

Elijah

Also, noticed in passing that this setting does nothing: "Show Web Site Url in Comments?". Setting this to true doesn't show an additional control. (This setting does do what it says "Allow Comment Titles?".) However I cannot find any combination of settings that allows the comment to actually save, and there's nothing in the System Log.

And another thing!... "Show Author Name?:" appears not to do anything.

Incidentally, editing an existing comment (CommentDialog.aspx) does work, though the dialog iframe doesn't close on Submit. However creating a new comment does not.

Thank you for the report. Did you have Disqus turned on intentionally in the past?

Thanks, 
Joe

I've now set this to Internal. The commenting control now appears on new posts, however the Submit button still doesn't post the comment.

After successfully upgrading to 3.1.2.0 MSSQL I'm seeing odd behaviour in the Blog module regarding comments. 

All published posts have "Allow comments for" set to "Unlimited".

On posts with no comments already, nothing appears below the post (or below the Previous / Next Post links). This div element is on the page, but empty:

ctl00_mainContent_BlogView1_InternalCommentSystem_divCommentService

On posts with at least one comment, the Comments section (with the comments) appears, including a "New comment" editor with "Submit" button. However the Submit button does nothing - it does a round trip and reloads the page but doesn't submit the comment.

In Site Settings > API Keys I have no keys in place for Intense Debate, Disqus or Facebook, so I'm expecting the internal comments system to work - I think!

Any help appreciated!