Installation

Post here for help with installing or upgrading mojoPortal pre-compiled release packages. When posting in this forum, please provide all relevant details. You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

Post here for help with installation of mojoPortal pre-compiled release packages

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.

You may also want to review the installation or upgrading documentation.

If you have questions about using the source code or working with mojoPortal in Visual Studio, please post in the Developer forum.

This thread is closed to new posts. You must sign in to post in the forums.
7/22/2008 11:21:44 AM
Gravatar
Total Posts 2

Installation

When trying to install (on IIS a MSSQL 2000 server instance) the setup script creates a partial database and then falls over with the following:

 

Probing system...
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.
0 site(s) found.
Running script mojoportal-core - 2.2.6.0 - 00:00:00.1248424
System.Data.SqlClient.SqlException: The text, ntext, and image data types are invalid in this subquery or aggregate expression. 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.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at mojoPortal.Data.SqlHelper.ExecuteNonQuery(SqlTransaction transaction, CommandType commandType, String commandText, 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) - 00:00:00.1716583
Note: This page shows some information that is helpful during setup and upgrades but for security it would be best not to show any information when the system is up to date. You can disable setup and suppress all information on this page by setting DisableSetup=true in Web.config. When you need to upgrade, you can set this back to false. If you are logged in as Administrator setup will run and you will be able to see this page even if it is disabled in Web.config so you can easily leave it disabled and just login before upgrading. But if you are not logged in you will need to enable setup in Web.config.

 

Any advice (other than upgrading to MSSQL 2005)?

Thx.

 

7/22/2008 12:05:28 PM
Gravatar
Total Posts 18439

Re: Installation

Hi,

I've tried very hard to keep SQL 2000 compatibility, I always generate the scripts using SQL 2000 compatibility mode, but apparently something got in there that it isn't happy with. I don't have SQL 2000 running on any machine around here anymore myself so admittedly my testing doesn't cover it anymore.

I can give you a little strategy to try and resolve it. Basically the setup routine runs the scripts in version order and then records the new version in mp_SchemaVersion after running each script that doesn't throw an error. The scripts are located in the /Setup/applications/mojoportal-core/SchemaUpgradeScripts/mssql folder. What I would do is open up the 2.2.6.0.config file in a text editor and then paste it into Query Analyzer one at a time and run them. When you come to the one or ones that error, let me know or if you are good with sql maybe you can come up with an alterate. My best guess at where the error is happening is in this update:

UPDATE mp_ModuleSettings
SET RegexValidationExpression = (SELECT TOP 1 mds.RegexValidationExpression
FROM mp_ModuleDefinitionSettings mds
WHERE mds.ModuleDefId IN (SELECT ModuleDefId
FROM mp_Modules m
WHERE m.ModuleID = mp_ModuleSettings.ModuleID)
AND mds.SettingName = mp_ModuleSettings.SettingName
)

I think SQL 2000 might not like using the SELECT TOP with an ntext field. On a new install, I think you can skip this particluar update statement altogether with no side effects. So you could just chop that out and visit the setup  page again instead of running anything manually in Query analyzer, but if it still errors then run them one by one and let me know where it breaks. Hopefully it will go through the rest without issues. If you do end up running any scripts manually, after running it set the version in mp_SchemaVersion for the mojoportal-core application row.

Best,

Joe

7/23/2008 4:44:09 AM
Gravatar
Total Posts 2

Re: Installation

Hi Joe,

Thanks for the prompt response :)

Well, my SQL is not quite good enough to debug that one, so I commented out that particular update statement, removed all tables and stored procedures and re-ran setup from scratch and that seems to have worked ok.

Just curious - are there any implications of leaving this out?  Anything I should be aware of?

Cheers,

Dave

7/23/2008 6:27:11 AM
Gravatar
Total Posts 18439

Re: Installation

Hi Dave,

No, there should be no problems at all. That part of the script was only for upgrades. We added a column to a table and that script was to update existing data, but in a new install there is no existing data so its not a problem as that sql will never need to be run and since no other errors happened it means all the stored procs are ok with SQL 2000.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.