Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

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.
6/9/2011 4:09:44 PM
ddoutel
Gravatar
Total Posts 114
View Posts

Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

Saved the web.config and user.config files from the live site before copying per instructions here: http://www.mojoportal.com/upgrading.aspx. I updated to deal with any changes in the Artisteer 3 Release version you may have incorporated. This is a client site; if you can help me out, I'd greatly appreciate it.

Many thanks!

Duane

 

Getting this on the setup page:

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.
1 site(s) found.
Running script mojoportal-core - 2.2.1.9 - 00:00:00.4680000
System.Data.SqlClient.SqlException (0x80131904): Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is wrong. 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() 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, 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) - 00:00:00.4992000
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.

6/9/2011 4:19:33 PM
ddoutel
Gravatar
Total Posts 114
View Posts

Re: Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

Just pulled all your latest changes from source control, and am rebuilding and will redeploy. If I still have the problem after that, I'll post back here.

Thanks!

Duane

 

6/9/2011 4:37:14 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

Hi Duane,

You've got something more than an upgrade going on, I guess you are making your own deployment packages from code. It should never run the script 2.2.1.9, neither for an upgrade nor for a new install. On a new installation it would start from version 2.3.4.8 and on an upgrade it would start from the next version above the current one from the mp_SchemaVersion table.

So what seems to be happening is it sees that the mp_Sites table exists so it knows it should be an upgrade but somehow it doesn't know what the current version is from mp_SchemaVersion so it is trying to run all the really old upgrade scripts.

I really have no idea other than those, but can only guess that something about the way you are packaging your own upgrades from source is not the same as mine or something funky happened in your database or the connection string user changed and doesn't have permission/visibility to some table or procedure than when it was initially installed. Hope these ideas help, but this doesn't sound to me like anything related to upgrading from my packages so I don't think it is any kind of bug in mojoPortal but I'm not entirely sure what is going on. Nothing like this has not been reported by the many other people who have upgraded.

Hope that helps,

Joe

6/9/2011 4:42:53 PM
ddoutel
Gravatar
Total Posts 114
View Posts

Re: Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

Joe,

Do you think it would help to update from the 2.3.6.6 production binaries? Odd; I did a fresh pull from the repository, blew away everything and did a full rebuild, blew away everything on the publishing folder, did a fresh publish from VS 2010, then followed the directions as stated above. BTW, I did another fresh build and live deployment, and still getting the error.

Best!

Duane

 

6/9/2011 4:43:48 PM
ddoutel
Gravatar
Total Posts 114
View Posts

Re: Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

BTW, I haven't changed any code; all I've been doing is skinning with Artisteer...

Duane

 

6/9/2011 4:48:53 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

Hi Duane,

I wish I could be more help but really I have no idea about the condition of your db or whether changing to my packages would solve it at this point. It might be worth a try, I'd probably try that, I hope you made a backup of the site and db before upgrading so you can go back if all else fails.

But the symptoms are of a db problem (ie the things I mentioned previously) more than of a code problem, so having a backup of the db from before the upgrade would be the most important thing.

Hope that helps,

Joe

6/9/2011 4:55:31 PM
ddoutel
Gravatar
Total Posts 114
View Posts

Re: Hey, Joe; got a major prob updating from 2.3.6.5 to 2.3.6.6...

There wasn't much content on the site yet, mostly just skinning; I'm gonna try the 2.3.6.6 deployment package, and if that doesn't do it, I'll just blow away the database and start from scratch; not a lot lost.

Thanks, Joe!

Duane

 

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