Updating Microsoft Dynamics

SL 7.0 Feature Pack 1 to

Microsoft Dynamics SL 7.0
Service Pack 3
Publication Date
April 2010

© 2010 Microsoft Corporation. All rights reserved. Microsoft, Microsoft Dynamics, ActiveX, Excel, FRx, FrontPage, MapPoint, Outlook,
SharePoint, SQL Server, Visual Basic, Visual Studio, Windows, Windows Server, Windows Vista, and Windows® 7 are trademarks of
the Microsoft group of companies. BIO and BIO Vue are trademarks or registered trademarks of NexVue Analytics Corporation in the
United States and/or other countries. Crystal Reports is a registered trademark of Business Objects SA. The names of actual
companies and products mentioned herein may be trademarks or registered marks - in the United States and/or other countries - of
their respective owners.
Your right to copy this documentation is limited by copyright law and the terms of the software license agreement. As the software
licensee, you may make a reasonable number of copies or printouts for your own use. Making unauthorized copies, adaptations,
compilations, or derivative works for commercial distribution is prohibited and constitutes a punishable violation of the law.
The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein
are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event
is intended or should be inferred.
Microsoft Corporation disclaims any warranty regarding the sample code contained in this documentation, including the warranties of
merchantability and fitness for a particular purpose.
The content of this manual is furnished for informational use only, is subject to change without notice, and should not be construed as a
commitment by Microsoft Corporation. Microsoft Corporation assumes no responsibility or liability for any errors or inaccuracies that
may appear in this manual. Neither Microsoft Corporation nor anyone else who has been involved in the creation, production or delivery
of this documentation shall be liable for any indirect, incidental, special, exemplary or consequential damages, including but not limited
to any loss of anticipated profit or benefits, resulting from the use of this documentation or sample code.
Use of this product is covered by a license agreement provided with the software product. If you have any questions, please call the
Customer Assistance Department at 800-456-0025 (in the United States or Canada) or +1-701-281-6500.
1 of 32
Table of Contents
Purpose ..............................................................................................................3
Before You Begin ...........................................................................................3
About This Service Pack .......................................................................................................... 3

Installing Release 7.0 Feature Pack 1 with 7.0 Service Pack 3 ...5
Creating New Databases and Database Scenarios..........................11
Installing Project Connector 2007 ........................................................14
Updating an Existing Installation ..........................................................15
Installing the Service Pack ................................................................................................... 15
Updating Databases ................................................................................................................ 20
Using Database Update ......................................................................................................... 25
Updating Client Workstations.............................................................................................. 26
Updating Doc Share Web Service Servers ..................................................................... 26
Updating Project Connector 2007 ..................................................................................... 26

Technical Details ..........................................................................................32

Installed Modules Check ....................................................................................................... 32
Registered Files ........................................................................................................................ 32
Global Assembly Cache ......................................................................................................... 32

2 of 32
Purpose
The purpose of this document is to inform system administrators and implementers about
Microsoft Dynamics® SL 7.0 Service Pack 3 and to guide them through the installation.

Before You Begin

Before beginning the installation process, be sure to read the Microsoft Dynamics SL
Release 7.0 Service Pack 3 Notes to Implementers (70SP3Notes.pdf) document included
with this service pack. In addition, the ―Planning Security‖ section of the Microsoft Dynamics
SL Installation Guide Release 7.0 Feature Pack 1 is of particular importance to new sites.

Back up all Microsoft Dynamics SL databases before proceeding. See “Backing Up

Databases” in the System Manager online help or user guide for assistance.

It is no longer necessary to turn off User Account Control (UAC) before you install this
service pack on a computer that is running Microsoft Windows Vista or Windows Server
2008.

About This Service Pack

 Microsoft Dynamics SL 7.0 Service Pack 3 is a software update for Release 7.0 Feature
Pack 1. Do not install this service pack on a computer that is running Release 7.0, 7.0
Service Pack 1 or 7.0 Service Pack 2. It is important that you determine which version is
currently installed before beginning the service pack installation. ―Updating an Existing
Installation‖ on page 15 provides you with the steps to verify your version.
– If you currently have Microsoft Dynamics SL Release 7.0 Feature Pack 1 installed,
start with ―Updating an Existing Installation‖ on page 15 after reading the rest of this
section.
– If you do not have Release 7.0 Feature Pack 1 installed, start with ―Installing Release
7.0 Feature Pack 1 with 7.0 Service Pack 3‖ on page 5 after reading the rest of this
section.
 Business Portal does not have updates with this service pack. To install Business Portal
with 7.0 Service Pack 3 you will need to install the 7.0 Feature Pack 1 release.
 This service pack is compatible with Microsoft® SQL Server® 2005 Service Pack 1 or
later.
 Files that apply to both server and client workstations are included in this service pack.
Therefore, any existing client workstation must be updated with the new 7.0 Service
Pack 3 client files before you can run Microsoft Dynamics SL. See ―Updating Client
Workstations‖ on page 26.

The procedure for updating clients is different from previous service packs. Be sure to read
“Updating Client Workstations” carefully before proceeding.
If the server has a client installed on it, the installation process updates the server’s client
automatically.

 If your organization uses Microsoft FRx, you will need to install 6.7 Service Pack 8 or
later after you install Microsoft Dynamics SL 7.0 Service Pack 3. If the Microsoft FRx
service pack is not installed, the message ―FRx32.OFSIMain.CheckOFSIConnection
40002: Unable to create RDO Environment. Please verify DSN information‖ will appear

3 of 32
 when Microsoft FRx Designer is opened. In addition, the password entered in the
Microsoft FRx Master Password box on the System Specific Information tab of the
Company Information dialog box must match the password that is being used for the
Master60sp user. Go to https://mbs.microsoft.com/customersource/support/
downloads/servicepacks/frx67sp8sol to download the Microsoft FRx service pack.
 Be sure to have the software DVD on hand if you need to install Microsoft Dynamics SL
7.0 Feature Pack 1, as well as printed copies of the Microsoft Dynamics SL Installation
Guide Release 7.0 Feature Pack 1 and instructions for any supporting products you plan
to install. Printed copies of the installation documentation are also recommended if you
are updating your installation from 7.0 Feature Pack 1 to 7.0 Service Pack 3.
 When you install 7.0 Service Pack 3 over an existing installation, files overwrite the
corresponding Release 7.0 Feature Pack 1 files. For example, the 7.0 Service Pack 3
version of 1025000.exe overwrites the existing version of 1025000.exe.
 This service pack does not install files for modules that are not part of your current
Microsoft Dynamics SL installation. For example, 7.0 Service Pack 3 files for Bill of
Material will not be installed if Bill of Material is not already installed.
 This service pack affects:
Accounts Payable Doc Share Web Service Project Controller
Accounts Receivable eCommerce Gateway EDI Purchasing
Edition
Advanced Payroll Flexible Billings Requisitions
Analyzer General Ledger Service Contracts

Advanced Shipment Inventory Service Dispatch

Management
Application Server Microsoft Dynamics SL SDK Shared Information
Bank Reconciliation Object Model System Manager
Bill Of Materials Order Management Time and Expense for
Projects
Cash Manager Payroll/Direct Deposit Work Order
Contract Management Project Budgeting Client workstation
components
Customization Manager Project Connector
 If you add a new Microsoft Dynamics SL client to your system after you install 7.0
Service Pack 3 on the server, you must also install the service pack on the client
computer.

4 of 32
Installing Release 7.0 Feature Pack 1 with 7.0 Service Pack 3
Before you install this service pack, you must first install the Release 7.0 Feature Pack 1
application files. After you have installed the software, you will then create new application
and system databases.

To install Release 7.0 Feature Pack 1 together with 7.0 Service Pack 3:
1. Quit all programs that are currently running on the file server where you will install the
Microsoft Dynamics SL application files, including those displayed as task buttons in the
notification area at the far right of the Windows taskbar, before continuing.

Do not disable virus detection/protection software.

2. Install Release 7.0 Feature Pack 1. Follow the steps in the ―Installing Microsoft Dynamics
SL‖ section of the Microsoft Dynamics SL Installation Guide Release 7.0 Feature Pack 1.
If you plan to install Crystal Reports, DocShare WebService, or a Web Order Starter Site,
follow the instructions in the ―Installing Supporting Applications‖ section. Supporting
applications can be installed later, after you have created your application and system
databases.

Important note to sites that plan to install Microsoft Project Connector:

You must create Microsoft Dynamics SL and Microsoft Project Server databases before you
can install Connector files. For more information about installing Connector files, see the
“Installing Supporting Applications” section of the Microsoft Dynamics SL Installation Guide
Release 7.0 Feature Pack 1 but do not install the Connector files in Release 7.0 Feature
Pack 1. Instead, use the 7.0 Feature Pack 1 procedure to install the Connector files in
Service Pack 3. For more information, see “Installing Project Connector 2007” on page 14.

3. Restart the computer after running Setup for Release 7.0 Feature Pack 1 and before
installing 7.0 Service Pack 3.
4. After restarting, extract the service pack .zip file into a temporary folder under the
existing 7.0 Feature Pack 1 installation (for example, …\Program Files\Microsoft
Dynamics\SL\Applications\70SP3) on the server or workstation where 7.0 Feature Pack
1 is currently installed.
5. Quit all programs that are currently running on the file server, including those displayed
as task buttons in the notification area at the far right of the Windows taskbar, except
for virus protection software.
6. Browse to the temporary folder created earlier, and double-click Setup.exe.

5 of 32
 Note: If you do not have Microsoft Visual Studio C++ Runtime on your computer
you will receive the following message. Select Install. If you select Cancel, the
service pack will not install.

Welcome appears.

7. Click Next to continue.

The window that appears contains important details about the installation process and a
list of documents that are provided to assist you.
8. Before proceeding, carefully read the information in this window and also review the
recommended documentation.
9. When you are ready to continue, click Next. License Agreement appears.

6 of 32
10. Carefully read the software license agreement. To continue, select I accept the terms
of the license agreement, and then click Next.
The Next button is unavailable if you select I do not accept the terms of the license
agreement. Click Cancel to end the installation.
If you accept the License Agreement terms, Choose Destination Location appears,
prompting for the location of your Microsoft Dynamics SL 7.0 Feature Pack 1 installation.

11. If the correct path does not appear, click Browse.

12. When Choose Folder appears, select the path where 7.0 Feature Pack 1 is currently
installed, and then click OK.
If the path you chose in step 12 is incorrect, the message “Cannot find configuration file.
Setup will abort. C:\...” appears. Click OK, and then click Finish to close the InstallShield
Wizard window. Determine the correct path, and then restart Setup.
If you attempt to install 7.0 Service Pack 3 on a client workstation where 7.0 Feature Pack 1
is not already installed, Setup displays the warning message, “The Setup is unable to locate
any Microsoft Dynamics SL 7.0 Feature Pack 1 components to update. Setup will abort.”
Click OK, and then click Finish to close the InstallShield Wizard window. If you were
installing to a client workstation, go to the server or workstation where 7.0 Feature Pack 1
is installed and run Setup from there. See “Updating Client Workstations” on page 26 for
more information.

13. When the correct path to Release 7.0 Feature Pack 1 appears in the Destination Folder
box, click Next.

7 of 32
 Copy Files appears, listing the applications affected by this service pack.

If the Microsoft Dynamics SL client is not installed on the computer, it will not appear in the
list of modules. See “About This Service Pack” on page 3 for the list of modules affected by
this service pack.

8 of 32
14. Click Next to begin the installation. Setup Status shows the progress as system and
application files are replaced with the 7.0 Service Pack 3 version of the files.

15. Additional dialog boxes may appear if Setup determines updates are needed for the
following applications:
 Web Order Starter Site
 Doc Share Web Service
Verify that the path of the installation location is correct and make changes as needed.

9 of 32
16. When the Setup Complete window appears, click Finish.

17. Restart the computer.

This completes the first phase of the installation process.

10 of 32
Creating New Databases and Database Scenarios
A Microsoft Dynamics SL application database contains all of the accounting data for an
individual financial entity. A system database contains shared, site-specific data such as
database field attributes, edit characteristics, product registrations, customizations, and
screen-level security.
You must set up a working application database (also known as a production or empty
database) and a system database before you can begin entering business data.
In the Database Maintenance (98.290.00) screen, you can create databases based on the
following scenarios:
 Empty Databases — Use this scenario to create a new system database and a new
application database.
 Demo – Business Ready Editions — Use this scenario to create system and application
databases based on the software package you chose—either Business Essentials or
Advanced Management—when you installed Microsoft Dynamics SL. See ―Which
Microsoft Dynamics SL edition should I install?‖ in Microsoft Dynamics SL Installation
Guide Release 7.0 Feature Pack 1 for more information.
 Demo – Professional Edition — Use this scenario to create a database for demonstrating
the Professional Edition features. This scenario includes demonstration data for the
Financial Management, Inventory and Order Processing, Manufacturing, Field Service
Management, and Project Management and Accounting modules. It also includes Multi-
Company support.
 Demo – Standard Edition — Use this scenario to create a single-company database for
demonstrating the Standard Edition features. This scenario contains only Financial
Management data.
 Additional Empty Application Database — Use this scenario to create an additional
application database for use with an existing system database.

To create databases:
These procedures must be performed by your Microsoft Dynamics SL system administrator.
Before you begin the following steps, be sure to enable SQL Server Authentication on the
database server. Refer to “How to: Change Server Authentication Mode” for more
information.

1. Confirm that the SQL Server service is running. Restart it if necessary. See ―How do I
stop and restart SQL Server Services?‖ in Microsoft Dynamics SL Installation Guide
Release 7.0 Feature Pack 1 for information about starting SQL Server services.

11 of 32
2. Open Database Maintenance (98.290.00) by going to Start | Control Panel |
Administrative Tools, and then selecting Microsoft Dynamics SL Database
Maintenance. Database Maintenance (98.290.00) appears.

3. On the Connect Server tab, type the Destination SQL Server Name.
4. Windows Authentication is selected as the default security mode to access the
instance of SQL Server. It is recommended for a Windows user who is running Database
Maintenance (98.290.00) as a SQL Server administrator.
Click SQL Server Authentication if you prefer to use it, and then type the SQL Server
―sa‖ Login ID and Password for the instance of SQL Server where the databases will
be created.

The User Import (95.300.00) screen provides you with the ability to add several users at
one time, either for a Windows group or by user name. This screen is available only if your
installation is configured for Windows authentication.

5. Click Connect to connect to the instance of SQL Server. A message in the status bar
will appear, indicating that you are connected.

12 of 32
6. Click the Create Databases tab.

7. To create databases, follow the setup instructions in Microsoft Dynamics SL Installation

Guide Release 7.0 Feature Pack 1 for the type of database you are creating.
 ―Creating an Empty Database‖
 ―Creating a Demo Database‖
 ―Creating an Additional Empty Application Database‖
After database creation and workstation setup are complete, 7.0 Service Pack 3 will be
ready for use.

If you plan to install Business Portal for Microsoft Dynamics SL, refer to the Business Portal
installation guide after you complete the procedure for creating the Microsoft Dynamics SL
databases.

13 of 32
Installing Project Connector 2007
To install Project Connector 2007, you will follow the procedure in the ―Microsoft Dynamics®
SL Connector for Microsoft® Office Project 2007‖ section of the Microsoft Dynamics SL
Installation Guide Release 7.0 Feature Pack 1 except you will install the files from the
PSAConnector folder.
1. Perform the steps in ―Setting up Project Connector Users and Accounts,‖ noting the
integration service user.
2. Browse to the PSAConnector folder in the temporary folder that holds the extracted 7.0
Service Pack 3 files under the existing 7.0 Feature Pack 1 installation and double click
Setup.exe.
3. Complete the rest of the steps in the following procedures from the ―Microsoft
Dynamics® SL Connector for Microsoft® Office Project 2007‖ section of the Microsoft
Dynamics SL Installation Guide Release 7.0 Feature Pack 1:
 ―Installing Project Connector Server Components‖
 ―Setting up the Connection between the Microsoft Project and Microsoft Dynamics SL
Databases‖
 ―Installing Project Connector Workstation Components‖ – run Setup from the
following location in the temporary folder that holds the extracted 7.0 Service Pack 3
files:
\PSAConnector\program files\Microsoft
Dynamics\SL\Connector\Addin\Installation\Setup.exe.
 ―Adding the Project Connector Add-In to Microsoft Office Project Professional‖

14 of 32
Updating an Existing Installation

Installing the Service Pack

All Microsoft Dynamics SL users must log off and remain out of applications and databases
during the 7.0 Service Pack 3 installation and database update process. Failure to do so
may result in the error message ―An error occurred during the move data process‖ and
problems may occur with your installation.
Microsoft Dynamics SL Release 7.0 Feature Pack 1 must already be installed on each server
that will be upgraded to 7.0 Service Pack 3. If it is not installed on the target computer, the
message, ―Solomon 7.0 Feature Pack 1 must be installed before running this program.
Microsoft Business Solutions–Solomon 7.0 SP3 Setup will abort‖ appears, and Setup will
automatically quit.

Do not install this service pack on a computer that is running Microsoft Dynamics SL 7.0,
7.0 Service Pack 1, or 7.0 Service Pack 2.

To verify that Microsoft Dynamics SL 7.0 Feature Pack 1 is installed:

1. In Microsoft Dynamics SL, select Help | About Microsoft Dynamics SL from the
toolbar. About Microsoft Dynamics SL appears.
2. Verify that 7.03.21026.00 or newer is listed (the last seven digits may be greater if a
hot fix was applied to the installation).
3. Click OK.
4. Quit Microsoft Dynamics SL.

To install 7.0 Service Pack 3:

1. Quit all Windows programs that are currently running on the server, including those
displayed as task buttons in the notification area at the far right of the Windows taskbar,
before continuing.

Do not disable virus detection/protection software.

2. Extract the Service Pack 3 .zip file into a temporary folder (for example, C:\Program
Files\Microsoft Dynamics\SL\Applications\70SP3) on the server or workstation where
Release 7.0 Feature Pack 1 is currently installed.

Note: If your 7.0 Feature Pack 1 environment includes Project Connector 2007, you
must stop the Project Connector Integration service before proceeding. See ―To stop the
Project Connector Integration service‖ on page 26 before continuing with the next step.

3. Choose Start | Run and browse to the temporary folder.

4. Select Setup.exe.
5. Click Open, then OK.

15 of 32
 Note: If you do not have Microsoft Visual Studio C++ Runtime on your computer
you will receive the following message. Select Install. If you select Cancel, the
service pack will not install.

Welcome appears.

6. Click Next to continue.

The window that appears contains important details about the installation process and a
list of documents that are provided to assist you.
7. Before proceeding, read the information in this window carefully and also review the
recommended documentation.
8. When you are ready to continue, click Next. License Agreement appears.

16 of 32
9. Carefully read the software license agreement. To continue, select I accept the terms
of the license agreement, and then click Next.
The Next button is unavailable if you select I do not accept the terms of the license
agreement. Click Cancel to end the installation.
If you accept the License Agreement terms, Choose Destination Location appears,
prompting for the location of your Microsoft Dynamics SL Feature Pack 1 installation.

10. If the correct path is not shown, click Browse.

11. When Choose Folder appears, select the path where Release 7.0 Feature Pack 1 is
currently installed.
12. Click OK.

If the path you chose in step 11 was incorrect, The message “Cannot find configuration
file. Setup will abort. C:\...” appears. Click OK, and then click Finish to close the
InstallShield Wizard window. Determine the correct path, and then restart Setup.
If you attempt to install 7.0 Service Pack 3 on a client workstation where 7.0 Feature
Pack 1 is not already installed, the warning message, “The Setup is unable to locate any
Microsoft Dynamics SL 7.0 Feature Pack 1 components to update. Setup will abort”
appears. Click OK, and then click Finish to close the InstallShield Wizard window. If you
were installing to a client workstation, go to the server or workstation where Release 7.0
Feature Pack 1 is installed and run Setup from there. See “Updating Client Workstations”
on page 26 for more information.

13. After you are satisfied that the path to Release 7.0 Feature Pack 1 is correct, click Next.

17 of 32
 Copy Files appears, listing the applications affected by 7.0 Service Pack 3.

If the Microsoft Dynamics SL client is not installed on the computer, it will not appear on
this list. See “About This Service Pack” on page 3 for the list of modules affected by this
service pack.

18 of 32
14. Click Next to begin the installation. Setup Status shows the progress as system and
application files are replaced with the 7.0 Service Pack 3 version of the files.

15. Additional dialog boxes may appear if Setup determines updates are needed for the
following applications:
 Office XP Smart Tab Manager
 Web Order Starter Site
 Microsoft Project Connector – Server
 Doc Share Web Service
Verify that the path of the installation location is correct and make changes as needed.

19 of 32
16. When the Setup Complete window appears, click Finish.

17. Restart the computer.

This completes the installation phase of the process. You must now update your databases
to correspond with 7.0 Service Pack 3. If you want to change the authentication method
that is used to access your Microsoft Dynamics SL databases, continue with ―Changing the
Database Authentication Mode.‖ Otherwise, go to ―Updating Databases‖ on page 20 to
continue the process.

Updating Databases
After installing the 7.0 Service Pack 3 files, you must complete a Database Maintenance
scenario.

Important Points:
 Back up all Microsoft Dynamics SL system and application databases before beginning
the following procedure.
 Before upgrading your databases, export your Microsoft Dynamics SL customizations to
a .cst file so you can import the file into the upgraded database. See the Customization
Manager online help or user guide for information about exporting and importing .cst
files. It is also a good idea to print the code associated with the customization using the
Visual Basic for Applications integrated development environment (IDE).
 The update procedure deletes the standard data in three system database tables:
Messages, Screen, and Rptcontrol. It then imports the current required data and
repopulates the three tables.
 All records that you added to the Messages, Screen, or Rptcontrol table will remain
intact. However, if changes were made to standard records in these tables, the changes
will be overwritten. If changes were made to the database schema, it will be necessary

20 of 32
 to verify that these changes are still in place after the update to release 7.0 Service Pack
3 is complete.

To update Microsoft Dynamics SL databases:

1. Start SQL Server Services if they are stopped. See ―How do I stop and restart SQL
Server Services?‖ in the Microsoft Dynamics SL Installation Guide Release 7.0 Feature
Pack 1 guide if you need assistance.
2. In SQL Server Management Studio, connect to the database server as an administrator
(sa or a user who is a member of the sysadmin server role).
3. Back up the system and application databases. See Microsoft SQL Server 2005 Books
Online if you need assistance.
4. Open Database Maintenance (98.290.00) by going to Start | Control Panel |
Administrative Tools, and then selecting Microsoft Dynamics SL Database
Maintenance. Database Maintenance (98.290.00) appears.

5. On the Connect Server tab, type the Destination SQL Server Name.
6. Windows Authentication is the default security mode to access the instance of SQL
Server. It is also the recommended authentication mode. Click SQL Server
Authentication if you prefer to use it, and then type the SQL Server ―sa‖ Login ID and
Password for the instance of SQL Server where the databases are located.
7. Click Connect to connect to the instance of SQL Server.

21 of 32
8. When the status bar at the bottom of the screen indicates that you have connected to
the SQL Server instance, click the Update Databases tab.

9. Select the system database name from the System Database Name list.
10. In Update Scenario, note that the correct scenario was selected by default based on
the system database name you selected.
11. In Databases, select one or more application databases associated with the system
database specified in step 9.
12. Click Update Database to apply the update to your databases. If your database is SQL
authenticated, Authentication appears. If your database is Windows authenticated skip
to step 15.

13. Select an authentication method, and then click Ok. Windows authentication is
recommended. Note that if you change authentication methods after setting up users
and groups, you must redo your user and group setup.

22 of 32
 If you selected SQL Server Authentication, Security appears.

14. Click Yes to confirm your selection and continue.

15. Follow the steps below that apply to the authentication method you selected.
 If you selected Windows Authentication:
a.) SYSADMIN Windows User Name appears.

b.) Click Ok to accept the default Microsoft Dynamics SL administrator, or make

changes as needed, and then click OK. The database update process begins.

A user defined as an administrator automatically has access to all screens within Microsoft
Dynamics SL and becomes a member of the SQL Server sysadmin server role.

23 of 32
  If you selected SQL Server Authentication:
a.) Login appears.

b.) In the Password box, type the password that was created for the Master60sp
user when your Release 7.0 Feature Pack 1 databases were generated, and then
click OK.
Default Password appears.

c.) Follow the instructions to enter a default user password in the Password box.
The password must satisfy the strong password requirements listed in the dialog
box.

For more information about strong passwords, see the Microsoft Dynamics SL Security
Guide.

d.) In Confirm Password, type the password again.

e.) Click Ok. The database update process begins.
16. When the update is finished, the 9829000 message box appears.

24 of 32
Note: If the update was unsuccessful, you will not see this message. Instead, a database
update failure message will appear.

17. Click OK.

18. In the Database Maintenance (98.290.00) window, click Close.
19. Review the Dbbuild.log file, which is typically found in the Microsoft Dynamics SL
EventLog folder. A successful database update results in a zero-byte Dbbuild.log file.
20. Follow the instructions in ―Using Database Update‖ to continue the database update
process.
21. Repeat this process for each remaining system database and respective application
databases.

Using Database Update

After completing a database maintenance scenario (see ―Updating Databases‖ on page 20),
you must use Database Update (98.100.00) to populate the system database with current
system data.

Populating the Screen table occurs during database creation (databases are created using
Database Maintenance (98.290.00)). The Screen.csv file is no longer a part of Database
Update (98.100.00).

To use Database Update (98.100.00):

1. Start Microsoft Dynamics SL.
2. Log on to the system database and company (SLDemoSystem and company 0060 for
example) as a user with Microsoft Dynamics SL system administrator rights.
3. Click the Administration button, and then select Database Update, or click All
Modules, expand Administration, and double-click Database Update.
4. In Database Update (98.100.00), select all application databases associated with the
company specified in step 2.
5. In Directory, browse for \DB\CSVs.
6. From the Files list, select messages.msg, pvrec.csv, and rptcontrol.csv. You do not need
to hold down the CTRL or SHIFT key to select multiple files.
7. Click Begin Processing.
8. When processing is complete, click OK.
9. Repeat steps 1 through 8 for each additional system and application database
combination.
10. Back up all system and application databases.

25 of 32
Updating Client Workstations
To update existing client workstations, run Setup.exe from the folder where the extracted
7.0 Service Pack 3 files reside. This action makes it unnecessary to use Add/Remove
Programs to uninstall the existing client before you install the 7.0 Service Pack 3 client.
You do not need to update the client on the server where your Microsoft Dynamics SL
installation resides. That was done automatically during the installation of 7.0 Service Pack
3.
To add a client workstation to your system after installing 7.0 Service Pack 3 on the server,
you must first install the Microsoft Dynamics SL 7.0 Feature Pack 1 client from the server to
the client workstation and then apply the service pack to the client workstation installation.

Updating Doc Share Web Service Servers

To update existing Doc Share Web Service Servers, run Setup.exe from the folder where the
extracted 7.0 Service Pack 3 files reside from the DocShare WebService Server.
To add a Doc Share Web Service Server to your system after installing 7.0 Service Pack 3
on the server, you must first install the Microsoft Dynamics SL 7.0 Feature Pack 1 Doc
Share Web Service and then apply the service pack to the Doc Share Web Service Server
installation.

Updating Project Connector 2007

This service pack includes bug fixes for the Project Connector 2007 components. If you use
Project Connector 2007,you must stop the Project Connector Integration service before you
run Setup for 7.0 Service Pack 3. You can then remove the existing Project Connector
components on both the server and the client workstations running Office Project
Professional 2007 and install the new components in the service pack.

To stop the Project Connector Integration service:

1. Open Microsoft Dynamics SL and log on as a Windows user who is an Administrator in
Microsoft Dynamics SL, an Administrator in Office Project Server 2007, and an
Administrator on the server where the Project Connector Integration service is installed.

26 of 32
2. In the Microsoft Dynamics SL window, click the Project button and select Project
Controller. The Project Controller menu appears.

3. Select Project Controller Setup. Project Controller Setup (PA.SET.00) appears.

27 of 32
4. Click the Microsoft Project Connector Setup button. Microsoft Project Connector
Setup (PA.MSP.00) appears.

5. In the Project Connector Integration Service area, click the Stop button to stop the
Project Connector Integration service.

28 of 32
To remove existing Project Connector components from the server:
1. On the IIS server where Office Project Web Access 2007 is installed, open the
Add/Remove Programs control panel.
2. Select Microsoft Office Project 2007 Connector for Microsoft Dynamics SL and
click Remove.
3. When Uninstall Complete appears, click Finish to exit the Setup wizard.

4. If the Project Connector add-in is installed on the server, remove it by selecting

Microsoft Dynamics SL Project Connector Add-in in Add/Remove Programs and
clicking Remove.

To install updated Project Connector components on the server:

1. Browse to the PSAConnector folder in the temporary folder that holds the extracted 7.0
Service Pack 3 files (under the existing 7.0 Feature Pack 1 installation) and double click
Setup.exe.

29 of 32
2. After Installation appears.

Click Next. During installation, an additional window, Finish Admin Install, may appear
in the background, advising you not to interrupt Setup while installation processes are
still running.
3. Project Server 2007 Information appears.

Type the URL for Office Project Web Access and click Next.

30 of 32
4. After Setup validates the URL, Finish Admin Install appears in the foreground.

5. Click Finish.
6. Restart the Project Connector Integration service.

To update the Project Connector add-in on client workstations:

To install the updated Project Connector 2007 add-in, you will follow the ―Installing Project
Connector Workstation Components‖ and ―Adding the Project Connector Add-In to Microsoft
Office Project Professional‖ procedures from the Microsoft Dynamics SL Installation Guide
Release 7.0 Feature Pack 1 except you will run Setup in following location in the temporary
folder that holds the extracted 7.0 Service Pack 3 files (under the existing 7.0 Feature Pack
1 installation):
\PSAConnector\program files\Microsoft Dynamics\SL\Connector\Addin\Installation.

Note: Each Project Connector user must perform his or her own removal and installation on
each workstation that he or she uses to access Office Project Server 2007.

1. Open the Add/Remove Programs control panel, select Microsoft Dynamics SL Project
Connector Add-in, and click Remove.
2. Browse to the temporary folder that holds the 7.0 Service Pack 3 files and go to the
\PSAConnector\program files\Microsoft Dynamics\SL\Connector\Addin\Installation
folder.
3. Double click Setup.exe.
4. Complete the rest of the steps in the ―Installing Project Connector Workstation
Components‖ and ―Adding the Project Connector Add-In to Microsoft Office Project
Professional‖ sections of the Microsoft Dynamics SL Installation Guide Release 7.0
Feature Pack 1.

31 of 32
Technical Details

Installed Modules Check

After Setup verifies the presence of Release 7.0 Feature Pack 1, it compares the files of all
Microsoft Dynamics SL applications currently installed (listed in SolInst.cfg) with the list of
updated files included in 7.0 Service Pack 3 to determine which modules will be affected by
the service pack.
If the client installation registry key is found, Setup adds the workstation files to the list of
files to be updated.

Registered Files
Setup updates several registered files. Before the file copy process begins, Setup un-
registers the Release 7.0 Feature Pack 1 version of these files. After the new 7.0 Service
Pack 3 files are copied to the appropriate directories, each of the new files is registered.

Global Assembly Cache

Setup updates many assemblies that are in the global assembly cache (GAC), which
contains assemblies that are shared by several applications. Setup first removes an
assembly from the cache, installs the updated file, and then adds the new file to the GAC.

32 of 32