How to move Business Portal for Microsoft Dynamics GP 10.0 and for Microsoft Dynamics SL 7.0 from one server to another server

INTRODUCTION

This article describes how to move Business Portal for Microsoft Dynamics GP 10.0 and for Microsoft Dynamics SL 7.0 from one server to another server.

More Information

Note This information is only intended to be used if there are no customizations to the Business Data Catalog (BDC). There is currently no process to move Web Services from one server to another. If Web Services is not going to reside on the original IIS server, it must be removed from the original server with the "remove SQL Objects and Data" option marked. Once removed, web services can be re-intalled on the new server prior to the Business Portal installation and all security must be re-configured.


To move Business Portal from one server to another server, follow these steps.

Step 1: Move the databases from one server to another server

  1. Move the Microsoft Dynamics GP databases or the Microsoft Dynamics SL databases from one server to another server.

    For more information about how to move the databases, click the following article numbers to view the articles in the Microsoft Knowledge Base:

    878449 How to transfer an existing Microsoft Dynamics GP, Microsoft Small Business Financials, or Microsoft Small Business Manager installation to a new server that is running Microsoft SQL Server

    846350 How to move the Microsoft Dynamics SL databases to a different computer that is running SQL Server 2000 or SQL Server 2005

  2. If you are moving the Microsoft Office SharePoint Server 2007 or Windows SharePoint Server 3.0 databases, you only need to move the SharePoint content database. To do this, follow these steps:

    1. If you do not know the SharePoint content database name, follow these steps to determine the name and the server:

      1. In SharePoint 3.0 Central Administration, click the Application Management tab.

      2. In the SharePoint Web Application Management section, click Content databases.

      3. On the Manage Content Databases page, click the SharePoint content database name.

      4. On the Manage Content Database Settings page, note the SharePoint content database server and the SharePoint content database name.

    2. Back up the SharePoint content database. To do this, follow these steps:

      1. In Microsoft SQL Server Management Studio, expand Databases.

      2. Right-click the SharePoint content database from step a, point to Tasks, and then click Back Up.

      3. In the Destination section, click Add.

      4. In the File name box, type the path and the file name, and then click OK.



        Note The file name must have a .bak extension.

    3. Restore the SharePoint content database. To do this, follow these steps:

      1. In SQL Server Management Studio, right-click Databases, and then click Restore Database.

      2. In the Destination for restore section, type the SharePoint content database name in the To database box.

      3. In the Source for restore section, click From device, and then click the ellipsis button.

      4. In the Backup Media list, click File, and then click Add.

      5. In the Select the file section, click the backup file, click OK, and then click OK.

      6. In the Select the backup sets to restore section, click to select the Restore check box next to the backup file that you want to restore.

      7. In the Select a Page section, click Options, and then click to select the Overwrite the existing database check box.

      8. In the Restore the database files as section, change the Restore As column so that the data file and the log file use the correct paths on the new server.



        Note The default paths for SQL Server 2005 are as follows:

        %systemroot%\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\_Data.mdf

        %systemroot%\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\_Log.ldf

      9. Click OK.

  3. If you plan to move only the databases and if you do not plan to move SharePoint Server 2007 or Windows SharePoint Server 3.0 and Business Portal, follow these additional steps:

    1. Update two configuration files by using the new name of the server that is running SQL Server. To do this, follow these steps:

      1. Make backup files of the following files:

        • BusinessFramework.config

        • ~privatefile.dbauthentication.config

        Note By default, these files are in the following location:

        C:\Inetpub\wwwroot\wss\VirtualDirectories\Portnumber\binPortnumber is a placeholder for the port number for the site that is running Business Portal.


      2. In both of the files that are mentioned in step 1, change the name of the server that is running SQL Server to be the new server name.

    2. Delete the BusinessPortalUser user from the system and from the company databases that are on the new server that is running SQL Server. To do this, follow these steps:

      1. In SQL Server Management Studio, expand Databases, expand the system database, expand Security, and then expand Users.

      2. Right-click BusinessPortalUser, and then click Delete.

      3. Repeat steps 1 and 2 for each company database.


        Note If you are using Microsoft Dynamics GP, the system database is the DYNAMICS database. If you are using Microsoft Dynamics SL, the system database is named during the installation of Microsoft Dynamics SL.

    3. Create a new BusinessPortalUser login, and give the new BusinessPortalUser login access to the system and to the company databases. To do this, follow these steps:

      1. In SQL Server Management Studio, expand Security, right-click Logins, and then click New Login.

      2. In the Login name box, type BusinessPortalUser.

      3. Click SQL Authentication, type a password for the user, and then confirm the password.

      4. In the Select a page section, click User Mapping.

      5. In the Users Mapped to this Login section, click the system database.

        Note If you are using Microsoft Dynamics GP, the system database is the DYNAMICS database. If you are using Microsoft Dynamics SL, the system database is named during the installation of Microsoft Dynamics SL.

      6. In the Database role membership for section, click BFGROUP.


        Note If you are using Microsoft Dynamics GP, also click DYNGRP.

      7. Repeat steps 5 and 6 for each company database or for each application database.


    4. Run the DBAuthenticationUtility.exe tool to reset the password for the BusinessPortalUser user who is in the ~privatefile.dbauthentication.config file.

Step 2: Move SharePoint Server 2007 or Windows SharePoint Server 3.0 and Business Portal from one server to another server

  1. Install SharePoint Server 2007 or Windows SharePoint Server 3.0. For detailed steps about how to do this, see the BusinessPortalInstallation.pdf file that is located on the Business Portal CD in the Documentation folder.

  2. Create a Web application for Business Portal. To do this, follow these steps:

    1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

    2. Click the Application Management tab.

    3. In the SharePoint Web Application Management section, click Create or extend Web application.

    4. Click Create a new Web application.

    5. Click Create a new IIS Web site.

    6. In the IIS Web Site section, type a name in the Description box.

    7. In the IIS Web Site section, type a port number in the Port box.

    8. In the Application Pool section, type a name in the Application pool name box.

    9. In the Application Pool section, select a security account for the application pool.

      Note For more information about the security account, see "User accounts for Windows SharePoint Services" on page 28 of the Business Portal Installation Guide.

    10. In Database Name and Authentication, note the database name. This database is only temporary.

    11. Click OK.

  3. Delete the new blank content database that you created in step 2. To do this, follow these steps:

    1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

    2. Click the Application Management tab.

    3. In the SharePoint Web Application Management section, click Content Databases.

    4. On the Manage Content Databases page, click the content database that you noted in step 2j.

    5. On the Manage Content Databases Settings page, click to select the Remove Content database check box, and then click the OK.

  4. Add the original content database. To do this, follow these steps:

    1. Click Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

    2. Click the Application Management tab.

    3. In the SharePoint Web Application Management section, click Content Databases.

    4. On the Manage Content Databases page, click Add a content database.

    5. In the Web Application list, make sure that you click the Web application for Business Portal.

    6. In the Database Server box, type the name of the server that is running SQL Server.

    7. In the Database Name box, type the name of the original content database.

    8. In the Number of sites before a warning event is generated box, type 9000.

    9. In the Maximum number of sites that can be created in this database box, type 15000, and then click OK.

      Note After you return to the Manage Content Databases page, make sure that the content database displays 1 for the
      Current Number of Sites.

  5. Delete the BusinessPortalUser user. To do this, follow these steps:

    1. In SQL Server Management Studio, expand Databases, expand the DYNAMICS database or the Microsoft Dynamics SL system database, expand Security, and then expand Users.

    2. Right-click BusinessPortalUser, and then click Delete.

    3. Repeat steps a and b for each company database or for each application database.

  6. Install Business Portal. For detailed steps about how to install Business Portal, see the BusinessPortalInstallation.pdf file that is located on the Business Portal CD in the Documentation folder.

Additional steps

If you install SharePoint Server 2007, follow these additional steps:

  1. Create a Shared Service Provider (SSP). To do this, follow these steps:

    1. Click
      Start, click Administrative Tools, and then click SharePoint 3.0 Central Administration.

    2. Click Shared Services Administration.

    3. On the Manage This Farm's Shared Services page, click New SSP.

    4. In the SSP Name section, type a name in the SSP Name box.

    5. In the Web application list, click a Web application that will host an administration site for the new SSP.



      Notes

      • If you want to create a new Web application to host the administration site for the new SSP, click Create a new web application.

      • The SSP Administration Site URL box is automatically populated with the administration URL.

    6. In the My Site Location section, click a Web application to host My Sites in the Web application list.

      Notes

      • If you want to create a new Web application to host My Sites for the new SSP, click Create a new web application.

      • We recommend that you use different Web applications to host My Sites and the SSP administration site so that you can independently back up and restore My Sites.

      • If you want to host My Sites at a location other than the root, change the relative URL in the Relative URL box.

    7. In the SSP Service Credentials section, type the user name and the password, and then click OK.

      Note The user name is used by SSP Web Services for communication and by the SSP timer service for running jobs.

    8. Click OK.

  2. Install Web Services. For detailed steps about how to install Web Services, see the WSInstallAdminGuide.pdf file that is located on Microsoft Dynamics GP CD 2 in the AdProd\WebServices folder.

    Note The user security setup in Web Services must be re-created.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×