Hi Edwin ,

How you package your production files? and how you uploads them to your production server?

It seems you compile mojoportal-core.sln solution that contains only core features. To have all features you must compile mojoportal_mssql_only.sln if your database platform is MS SQL .

In your way you have more and more extra files in you package that not require for production.

The best way for deploying  is following the steps here.

Thanks. The problem persists. I followed the step-by-step instructions described in http://www.mojoportal.com/deploymentfromwindows.aspx.

I made sure I was compiling mojoportal_mssql_only.sln. I deleted all files in production server, I used Unleash It to filter the files from the Release folder, uploaded them to the server, deleted the database and created a new one, hit /setup/Default.aspx, waited for all scripts to execute successfully. Then I logged in as Admin, and when attempting to add content to a page, the Feature dropdown list is just empty. So I can't select anything at all, and if I click "Create New Content" button, I get a JavaScript error message (Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500)

Why would something so essential fail to get configured correctly during setup anyway?

Thanks for any help.

Thanks Joe, I have tried everything you say. I've checked the IsServerAdminSite column in mp_Sites table, and it is set to True. And its SiteID is 1. Then I added a new site via Site Settings, and I could see a Features tab in that new site. I clicked the Features tab as instructed in http://www.mojoportal.com/muliplesites.aspx , but right there I found exactly the same problem: the "All Features" and "Selected Features" listboxes are both empty, so there is nothing to select from. Everything else in the Administration menu seems to working fine, except for this Features issue.

I don't know what else to try.

Thanks for any help.

Thanks Asad, you got it. There are no records in mp_ModuleDefinitions table. Why did the setup scripts fail to configure that? Anyway, should I add the module definitions manually, or should I modify some configuration to activate them automatically?

Thanks for your help.

Thanks Joe. I've just compared the /Setup folder in my package with the one in your deployment package, and the difference is that my package /Setup folder is heavier because it contains SchemaInstallScripts for all the supported databases while your package only contains SchemaInstallScripts for MSSQL and MYSQL. Everything else is there including mojoportal-core\FeatureDefinitions.

Anyway, I decided to start all over from scratch and just upload your deployment package (and not mine) to my production server. And it all works fine, except that now I don't get to use some custom code I added myself to the VS solution. I'll have to live with it while I figure out how to do it right.

So I probably must have done something wrong in my package, and probably the deployment procedures are under-documented, because I'm telling you I just defined myself to follow the online documentation.

Thanks for your help.

Edwin