Upgrade problem

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/17/2012 6:56:52 AM

xmen

Total Posts 38

View Posts

Upgrade problem

I upgrade the site with new version now when I click "Edit This Page" or "Page Settings", it redirects to /Setup/Defaul.aspx. Which says

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.

and here is System Log of a click

2012-06-17 04:37:10,466 ERROR 59.180.143.42 - en-IN - /Admin/PageLayout.aspx?pageid=1 - mojoPortal.Web.mojoBasePage - XX.XX.XX.XX-en-IN - /Admin/PageLayout.aspx?pageid=1
System.ArgumentNullException: Value cannot be null.
Parameter name: format
   at System.String.Format(IFormatProvider provider, String format, Object[] args)
   at mojoPortal.Web.AdminUI.PageLayout.PopulateControls()
   at mojoPortal.Web.AdminUI.PageLayout.Page_Load(Object sender, EventArgs e)
   at System.Web.UI.Control.OnLoad(EventArgs e)
   at mojoPortal.Web.mojoBasePage.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
2012-06-17 04:37:10,482 INFO XX.XX.XX.XX - en-IN - /Admin/PageLayout.aspx?pageid=1 - mojoPortal.Web.mojoBasePage - detected need for upgrade so redirecting to setup

6/17/2012 6:59:40 AM

xmen

Total Posts 38

View Posts

Re: Upgrade problem

[Blank post to subscribe]

6/17/2012 7:47:38 AM

Joe Audette

Total Posts 18439

View Posts

Re: Upgrade problem

If it says it needs to upgrade the schema, it means it needs to run some database scripts. If it isn't running those scripts on the setup page it means the scripts don't exist on disk. So you did not deploy all the files, especially the ones under /Setup folder.

Once it runs the upgrade scripts it will solve the other errors.

6/17/2012 8:22:14 AM

xmen

Total Posts 38

View Posts

Re: Upgrade problem

The server's Setup directory has more files than my local Setup directory. I uploaded the entire setup folder, still nothing.

6/17/2012 8:47:16 AM

Joe Audette

Total Posts 18439

View Posts

Re: Upgrade problem

look in the folder /Setup/applications/mojoportal-core/SchemaUpgradeScripts/mssql/

Do the files exist 2.3.8.6.config, 2.3.8.7.config, 2.3.8.8.config, 2.3.8.9.config?

If they do exist, make sure the user that is the identity on the application pool has read permission on those files.

Then visit /Setup/Default.aspx again

6/17/2012 11:13:46 AM

xmen

Total Posts 38

View Posts

Re: Upgrade problem

No, it doesnt have them. The server got max to 2.3.8.5.config and local directory max to 2.3.2.7.config.

How do I get those files, I published the MojoPortal.Web by VS 2010 ?

6/17/2012 12:12:10 PM

Joe Audette

Total Posts 18439

View Posts

Re: Upgrade problem

They are included in the latest source code so they should have been in the published package. What I do is rebuild the solution using the Release build profile, then I publish the mojoPortal.Web project to a local folder. You must rebuild the entire solution in Release mode before publishing, using the mojoportal.sln solution.

Maybe you don't have the latest code from the repository if you are missing files in the sources.

6/17/2012 7:56:21 PM

xmen

Total Posts 38

View Posts

Re: Upgrade problem

Thats exactly what I did, rebuilt the entire solution twice with Release then Published. And about latest source code, so I looked in the Setup folder of source and those files are in there.

Alright, so I checked the Setup folder in VS and only "Application" top dir and "Default.aspx" was in there. Now wondering how VS published the files from there if they were excluded ? is there some kind of setting done by you ? Anyways, Published this time to different location and all files came. Uploaded those 3 files. It Upgraded successfully but I still get same error I posted in first post.

PS : An "Edit" button to post and "Subscribe to Topic" button would be very nice.

6/18/2012 5:42:46 AM

xmen

Total Posts 38

View Posts

Re: Upgrade problem

Fixed after updating App_GlobalResources folder :)

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