web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / What is removed when B...
Microsoft Dynamics SL (Archived)

What is removed when Business Portal uninstalled?

(0) ShareShare
ReportReport
Posted on by Community Member

My company's SharePoint data (sites, subsites, document libraries, and other content) was developed and deployed in the same web application and site collection as our Business Portal 4.0 (for Dynamics SL 7.0 FP1) installation.

Now we are looking at upgrading to Dynamics SL 2011 FP1, Business Portal 5 (for SL 2011 FP1), and SharePoint Server 2010. I have already tried upgrading the SharePoint content database, but the SharePoint parts of Business Portal seem to be blocking the upgrade of the content database.

I was looking at removing Business Portal from the previous installation to see if that would allow the rest of the SharePoint content to upgrade.

What all is removed when Business Portal is uninstalled? Do the web parts and other features get removed from that web application when BP is uninstalled?

*This post is locked for comments

I have the same question (0)
  • Carolyn Kolpien Profile Picture
    Carolyn Kolpien Microsoft Employee on at

    Hi Casey,

    So you are upgrading from SharePoint 3.0 to SharePoint 2010.   So you are moving the databases from the former SharePoint server to the new server where SharePoint 2010 is installed, since the new install and BP 5 must be on a 64 bit machine.  These steps may help.

    Steps to Upgrade BP 4.0 & BP 4.0 FP1 to BP 5.1 on SharePoint 2010

    1. Setup BP 4.0 or BP 4.0 FP1 and then uninstall BP, but leave the SQL data in the databases.

    2. Run SQL Commands on SL databases:

    a. DBCC CHECKDB

    b. DBCC CHECKCATALOG

    3. Backup the SL and WSS_Content databases.

    4. On another machine, setup Windows Server 2008 (or R2) x64

    5. Setup SQL Server 2008 (or R2) x64 if not using a dedicated SQL Server 2008 (or R2) server.

    6. Install SharePoint Foundation or Server 2010 using Server farm configuration.

    a. Note: Don’t do the standalone installation as that will install a special version of SQL Server that will make working with the WSS_Content databases more difficult.

    7. Make sure to create the Web Application that you want to attach the WSS_Content database.

    a. Note: You don’t need to create the default site collection.

    8. In SharePoint Administration, remove the content database from the Web Application by using the Manage content databases page.  With the proper Web Application selected, click the WSS_Content database, scroll to the bottom of the page, check the Remove content database checkbox, and then click the OK button.

    9. Restore the BP 4.0 (or FP1) databases including the WSS_Content database.

    10. Open the SharePoint 2010 Management PowerShell console from the start menu under the SharePoint 2010 Products folder.

    11. Test the WSS database by running Power Shell command “Test-SPContentDatabase -Name <DatabaseName> -WebApplication <URL>”.

    a. Example: “Test-SPContentDatabase -Name WSS_Content -WebApplication http://localhost”

    b. NOTE: You will get a bunch of errors because the BP features are missing, ignore these errors.

    c. If the SQL Server is not local, then will need to specify.  Refer to SharePoint Documentation for additional arguments required.

    12. Run the PowerShell Command “Mount-SPContentDatabase -Name <DatabaseName> -DatabaseServer <ServerName> -WebApplication <URL> [-Updateuserexperience]”

    a. Example: “Mount-SPContentDatabase –Name WSS_Content  -DatabaseServer LOCALHOST -WebApplication  http://localhost -Updateuserexperience”

    b. NOTE: You will get a bunch of errors because the BP features are missing, ignore these errors.

    13. Using the SL 2011 build, upgrade the SL Databases and register modules.

    a. If the SL databases were moved to a different SQL Server, then the BusinessPortalUser account will be orphaned in the SL App and System databases, you must either remove that user from each database or choose a different user account in the BP install.

    14. Setup BP build.

    Let me know if you have additional questions.

  • Community Member Profile Picture
    Community Member on at

    Thank you for the previous response. I have finally tested reconnecting the Business Portal SharePoint content database and running an upgrade. However, I am getting an error when I visit a Business Portal page.

    In the ULS for SharePoint I get the following:

    ******************************************

    System.Web.HttpException: Cannot find ContentPlaceHolder 'PlaceHolderTopHelpKey' in the master page '~masterurl/default.master', verify content control's ContentPlaceHolderID attribute in the content page.  

    at System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection)    

    at System.Web.UI.Page.get_Master()    

    at System.Web.UI.Page.ApplyMasterPage()    

    at System.Web.UI.Page.PerformPreInit()    

    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    ******************************************

    Would the error be due to not uninstalling BP from the original installation prior to the content database backup and restore or would it be due to security since I have not yet run the synchronization utility.?

  • Carolyn Kolpien Profile Picture
    Carolyn Kolpien Microsoft Employee on at

    Hi Casey,

    I want to give you the correct steps to possibly fix this issue.  However I need to know if you are using Project Server or Foundation?

  • Community Member Profile Picture
    Community Member on at

    I am using SharePoint Server with Project Server 2010.

  • Verified answer
    Carolyn Kolpien Profile Picture
    Carolyn Kolpien Microsoft Employee on at

    Casey,

    Try these steps:

    Browse to the following URL for Business Portal: http://<servername>:port#/BP/layouts/ChangeSiteMasterPage.aspx

    Verify the following settings on this page:

    1. Site Master Page is set to 'default.master'

    2. System Master Page is set to 'BusinessPortalDefault.master'

    3. Alternate CSS URL is set to 'Use Windows SharePoint Services default styles'

    If any changes are made, run an IISRESET and then re-launch Business Portal

  • Community Member Profile Picture
    Community Member on at

    Carolyn,

    I used the following link: http://<servername>:port#/BP/_layouts/ChangeSiteMasterPage.aspx (The underscore was missing before layouts.)

    1. Site Master Page is set to 'BusinessPortalDefault.master'

    2. System Master Page is set to 'BusinessPortalDefault.master'

    3. Alternate CSS URL is set to 'Use Microsoft SharePoint Foundation default styles'

    I don't see a 'default.master' option for Site Master Page. There is a v4.master. Should I try that?

    ~Casey

  • Verified answer
    Carolyn Kolpien Profile Picture
    Carolyn Kolpien Microsoft Employee on at

    Hi Case,

    Yes - use the v4.master.  Let me know how it goes.

  • Community Member Profile Picture
    Community Member on at

    Carolyn,

    Setting the Site Master Page to v4.master corrected the issue in the upgraded test environment.

    Also, when I check the same pages in our production environment, they have the error "The site master page setting currently applied to this site is invalid. Please select a new master page and apply it "

    The same pages are set to "default.master" for Site Master Page, but do not prevent us from visiting the pages. Should I set them to something else so that when I perform the go-live upgrade, I do not encounter this error again?

  • Carolyn Kolpien Profile Picture
    Carolyn Kolpien Microsoft Employee on at

    Hi Casey,

    Glad to hear the issue is corrected.  I would advise leaving the settings as is in the prod environment. If he runs into the issue again when he upgrades the prod environment going to the page and changing the settings is relatively quick and painless.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans