Microsoft Dynamics SL

Installation Guide Release 7.0

3/2007

Copyright Manual copyright © 2007 Microsoft Corporation. All rights reserved.

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.

Trademarks

Microsoft, Microsoft Dynamics, ActiveX, Excel, FRx, FrontPage, MapPoint, Outlook, SharePoint, Visual Basic, Visual Studio, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation, FRx Software Corporation, or their affiliates in the United States and/or other countries. FRx Software Corporation is a wholly owned subsidiary of Microsoft Corporation. BIO and BIO Vue are trademarks or registered trademarks of NexVue Analytics Corporation in the United States and/or other countries.

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.

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.

Warranty disclaimer

Microsoft Corporation disclaims any warranty regarding the sample code contained in this documentation, including the warranties of merchantability and fitness for a particular purpose.

Limitation of liability

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.

License agreement 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.

Publication Date

March 2007

Table of Contents iii

Table of Contents Introduction 1

Audience.......................................................................................................................................... 1

Installation Preparation 3 Overview .......................................................................................................................................... 3

Summary of Tasks for New and Existing Installations.................................................... 3 Pre-Installation Checklist ................................................................................................................ 5 Installation Options ....................................................................................................................... 10

Guide for New Installations 11 Overview ........................................................................................................................................ 11 Installing Microsoft Dynamics SL ................................................................................................. 12 Microsoft SQL Server Installation................................................................................................. 22 Creating Databases ...................................................................................................................... 23

Creating an Empty Database ......................................................................................... 26 Creating a Demo Database............................................................................................ 30 Creating an Additional Empty Application Database .................................................... 34 Logging On Using the Demo System and Application Databases................................ 35 Preparing the Demo System and Application Databases............................................. 35 Logging On Using the Empty System and Application Databases ............................... 36 Preparing the Empty System and Application Databases ............................................ 37

Installing Supporting Applications................................................................................................ 38 Web Order Starter Site ................................................................................................... 38 Crystal Reports................................................................................................................ 47 Microsoft Office Project Connector ................................................................................ 51

Setting Up Microsoft Dynamics SL on Workstations................................................................... 87 Client Workstation Setup................................................................................................ 87 Running Microsoft Dynamics SL from the Local Client Workstation ........................... 92

Installing Crystal Reports on a Local Workstation....................................................................... 93

Upgrading an Existing Installation 97 Overview ........................................................................................................................................ 97 Before You Install .......................................................................................................................... 97

Export Customizations.................................................................................................... 98 Removing an Existing Installation ................................................................................................ 99

Removing Workstation Components ............................................................................. 99 Removing Server Components....................................................................................... 99

Installing Microsoft Dynamics SL ...............................................................................................101 Updating Databases ...................................................................................................................101

Prepare SQL Server 7.0 Databases to Run with SQL Server 2005 ...........................107 Using Database Update after Completing the Database Maintenance Scenario.....108 Conversion Procedure for Order Management ...........................................................109

Updating Client Workstations.....................................................................................................110 Updating Custom Crystal Reports ..............................................................................................115 Adding Modules...........................................................................................................................116

Troubleshooting 119 Repairing a Microsoft Dynamics SL Installation........................................................................119 Restoring System Database Table Views ..................................................................................121 Technical Resources...................................................................................................................123

Section Contents...........................................................................................................123

iv Installation Guide

Terminology Definitions ................................................................................................123 Technology Tidbits.........................................................................................................123 Backup and Restore Procedures .................................................................................125 Registered Controls.......................................................................................................127 Solomon.ini....................................................................................................................128

Appendices 129 Appendix A: SQL Server Optimization Notes ..............................................................................129

Supported Microsoft SQL Server Versions...................................................................129 Microsoft SQL Server 2005..........................................................................................129

Appendix B: Windows Vista Support ..........................................................................................132 Control Panel Change ...................................................................................................132 Using Windows Vista as a Client ..................................................................................132 User Account Control ....................................................................................................132

Appendix C: Getting Support.......................................................................................................134 Important Phone Numbers and Internet Addresses ...................................................134

Index 135

Introduction 1

Introduction

This guide provides instructions for installing Microsoft Dynamics™ SL in the following environments:

• Microsoft® Windows® XP Professional Service Pack 2

• Microsoft Windows Server™ 2003 Service Pack 1

• Microsoft Windows Vista™

• Microsoft SQL Server™ 2005 Service Pack 1 or later

Note: Web Order is supported in a Windows Server 2003 Internet Information Services 6.0 environment. Windows XP is not a supported platform for Web Order.

The following sections are included:

• Installation Preparation — This section provides an overview of the installation and upgrade processes and a pre-Installation checklist to help you address tasks you must perform before you begin installation. This section also describes the options you will see on the installation options window.

• Guide for New Installations — This section provides steps to help those who do not currently have Microsoft Dynamics SL installed.

• Updating an Existing Installation — This section provides steps to help you upgrade your present Microsoft Dynamics SL installation.

• Troubleshooting — This section provides solutions, hints, and tips to help you resolve common installation, setup, and maintenance issues.

• Appendices — This section provides additional information about Microsoft SQL Server optimization and other information of interest to some readers.

Audience This installation guide is written for the novice, as well as the veteran software installer. It includes checklists and other aids to help make your installation a successful experience.

2 Installation Guide

Installation Preparation 3

Installation Preparation

This section will help you prepare for your Microsoft Dynamics SL installation. The section includes:

• Overview — Read this section for a brief summary of what will happen during and after your installation.

• Pre-Installation Checklist — You must perform many of the tasks on this list before you begin your installation.

• Installation Options — This section describes what you will see on the installation options window.

Overview Where possible, the Setup program for Microsoft Dynamics SL detects operating environment characteristics and installs the components that are appropriate for that environment. Setup also prompts you to answer necessary questions up front so that file copying can proceed efficiently.

Summary of Tasks for New and Existing Installations

First-time installation Upgrading an existing installation

Complete the Pre-Installation Checklist and perform the tasks. Some tasks are optional, while others are required.

Complete the Pre-Installation Checklist and perform the tasks. Some tasks are optional, while others are required.

Perform a system backup of the server on which you will install Microsoft Dynamics SL.

Export all screen customizations from the prior version.

Perform a system backup of the database server.

Perform a system backup of the server that holds your Microsoft Dynamics SL applications.

Install Microsoft Dynamics SL on the server you have selected to hold the program files.

If the Delta.mnu file has been customized, save a copy so that you can refer to it after the installation is complete.

If you do not have Microsoft SQL Server 2005 and required service packs already installed, install them on the database server.

Perform a database backup of the system and application databases.

Create databases and prepare them for use by loading them with system data.

Remove all existing Microsoft Dynamics SL clients from client workstations.

If you intend to implement Web-based sales orders, install the Web Order Starter Site.

Remove the existing Microsoft Dynamics SL installation from the server where it currently resides.

Install supporting application Crystal Reports on the server you have selected to hold the program files.

Install Microsoft Dynamics SL on the server you have selected to hold the program files.

Install the Microsoft Project Connector for Microsoft Dynamics SL if you intend to use it.

If you currently run Microsoft SQL Server 2000, perform the upgrade to SQL Server 2005 and install the required SQL Server service packs on the database server.

Install FRx Financial Reporter and FRx components on the server using your FRx 6.7 CD. Installation documentation is included on the CD. After you install FRx 6.7, you must also install Service Pack 8 or later.

Update databases and prepare them for use by loading them with system data.

Set up Microsoft Dynamics SL on client workstations.

If you intend to implement Web-based sales orders, install the Web Order Starter Site.

http://www.microsoft.com/sql/solutions/upgrade/default.mspx

https://mbs.microsoft.com/customersource/support/downloads/servicepacks/frx67solOverview.htm


First-time installation Upgrading an existing installation

Set up Crystal Reports 10 on the appropriate workstations.

If a release of Crystal Reports that is earlier than version 10 is installed, you must remove it from the server and workstations that will access Microsoft Dynamics SL.

Set up FRx Financial Reporter and FRx components on the appropriate workstations using your FRx 6.7 CD. See the installation documentation on the CD. After you install FRx 6.7, you must also install Service Pack 8 or later.

Unless you have Crystal Reports Version 10 already installed on the server, install it on the server you have selected to hold the program files.

Install Microsoft Project Connector for Microsoft Dynamics SL if you intend to use it.

Unless you have version FRx 6.7 already installed on the server, install FRx Financial Reporter and FRx components on the server using your FRx 6.7 CD. Installation documentation is included on the CD. After you install FRx 6.7, you must also install Service Pack 8 or later.

Set up Microsoft Dynamics SL on client workstations.

Unless you have Crystal Reports version 10 already installed on the appropriate workstations, set up Crystal Reports 10 on workstations.

Unless you already use Crystal Reports 10, update customized Crystal Reports.

Unless you have version FRx 6.7 already installed on the appropriate workstations, set up FRx Financial Reporter and FRx components on workstations using your FRx 6.7 CD. See the installation documentation on the CD. After you install FRx 6.7, you must also install Service Pack 8 or later.








Pre-Installation Checklist The following checklist is provided to help you prepare for your Microsoft Dynamics SL installation and to give you a record to refer to during future upgrade installations.

Notes:

• The input of other individuals during the installation process might be helpful and, in some cases, necessary. For example, you might need to consult with your database administrator when questions arise about how to store your data. Be sure the resources you need are available during pre-installation planning and during the installation or upgrade process.

• If you plan to use Microsoft Office 2003 or 2007 and Microsoft Dynamics SL on the same workstation, install Microsoft Office first, followed by Microsoft Dynamics SL.

• If you plan to utilize the Application Server module to send e-mail requests, be sure that the collaboration data objects (CDOs) setting was selected when Microsoft Office Outlook was installed on the computer that has been designated as the Application Server. Contact your system administrator, Microsoft Certified Partner, or Microsoft Support for assistance.

• If you use Microsoft Office Outlook 2007 with Application Server to send e-mail requests, you may experience the error, “General CDO (Collaboration Data Objects) error. Routing will be disabled for this server. 429.” Go to “Collaboration Data Objects, version 1.2.1” on the Microsoft Download Center site to read information related to this issue and download software that provides CDO 1.2.1 functionality.

To complete the pre-installation checklist:

Contact your Microsoft Certified Partner well in advance of your planned installation to make sure that your operating system, database, and hardware environment are appropriate for the installation.

(Optional) On the line below, record the computer names of the servers where you will create or update the Microsoft Dynamics SL applications and databases. You can install the applications and databases on separate servers.

Server that will hold the applications _____________________________________________

Server that will hold the databases _____________________________________________

Where can I find the computer name?

1. Right-click My Computer on the server where you will install Microsoft Dynamics SL.

2. Choose Properties from the shortcut menu.

3. The Full Computer Name is on the Computer Name tab of System Properties in Microsoft® Windows XP, Microsoft® Windows Server™ 2003, and Microsoft Windows Vista™.

Complete these steps on each server where you will install Microsoft Dynamics SL.

(Optional) On the lines below, record the computer name(s) of the workstations where you will install Microsoft Dynamics SL. Attach a separate sheet of paper if necessary.

_____________________________________________

_____________________________________________

_____________________________________________

_____________________________________________

_____________________________________________

Locate your Microsoft Dynamics SL Release 7.0 DVD.

What does the DVD contain?

The Microsoft Dynamics SL Release 7.0 DVD contains the system and application files, including the Microsoft Dynamics SL Software Development Kit. It also contains Microsoft Project Connector components that are installed on the server running Microsoft Project Server and workstations

http://www.microsoft.com/downloads/details.aspx?familyid=2714320d-c997-4de1-986f-24f081725d36&displaylang=en


running Microsoft Office Project Professional 2003. In addition, the DVD includes Web Order Starter Site, Microsoft Office XP Smart Tag Manager, and the Microsoft Dynamics SL user guides.

On the line below, record the Microsoft Dynamics SL edition that you will install.

_____________________________________________

Which Microsoft Dynamics SL edition should I install?

During installation, you must choose the Microsoft Dynamics SL edition to install. The Business Ready Licensing editions are:

• Business Essentials

• Advanced Management

The Modular Licensing editions are also available so that you can add modules to an existing installation. If you select this option, you will also need to choose one of the following:

• Single-User Standard

• Multi-User Standard

• Professional

To determine which edition to install, contact your Microsoft Certified Partner or log on to VOICE/CustomerSource to view your configuration details and license keys.

If you are installing Microsoft Dynamics SL for multiple users over a network, identify the mapped server share where you will install it. Verify that available disk space is adequate for your installation. For additional help in determining configuration requirements, contact your Microsoft Certified Partner.

Review “Creating Databases” on page 23 to determine:

• Which databases will be created during this installation

• Their approximate sizes

• The server and path to the location where they will be stored

• Their names

• Their types

Record the information on the lines below. Consult your database administrator, your Microsoft Certified Partner, or technical support if you need assistance.

Note: Your installation must include at least one system database. In addition, the system database and all associated application databases must exist within the same instance of Microsoft SQL Server and must run using compatibility mode 80. You must also decide whether you will create demo databases. Demo databases are useful for training and testing unfamiliar areas of the software without affecting your live data.

Empty Databases

_________________________________________ System Application

_________________________________________ Server (include path)










Demo Databases

Demo companies are included with Microsoft Dynamics SL. If you decide to create demo databases, the options in the Database Maintenance (98.290.00) screen are:

• Demo – Business Ready Editions ─ System and application databases are created based on the software package you choose when you install Microsoft Dynamics SL (see “Which Microsoft Dynamics SL edition should I install?” on page 6). The application databases are SLDemoApp10 (companies 0010 and 0020) and SLDemoApp60 (companies 0060, 0070, and 0080). The demo system database for both companies is SLDemoSystem.

• Demo - Professional Edition ─ The application databases are SLDemoApp10 (companies 0010 and 0020) and SLDemoApp60 (companies 0060, 0070, and 0080). The demo system database for both companies is SLDemoSystem.

• Demo - Standard Edition ─ The application database is DemoStandardApp51 (company 0051). The system database is DemoStandardSystem.

Use these names for your demo databases if possible.











On the line below, record the Microsoft SQL Server version installed on the workstation or server where you will create or update the Microsoft Dynamics SL databases.

_____________________________________________

Which Microsoft SQL Server version do I have?

Microsoft Dynamics SL 7.0 supports Microsoft SQL Server 2005 Standard or Enterprise Edition (32- or 64-bit) with Service Pack 1. Microsoft SQL Server must be purchased separately. Contact your Microsoft Certified Partner for assistance.

If you already have Microsoft SQL Server installed, you can determine the SQL Server version by using the OSQL utility or the Query window in SQL Server Management Studio. Type (or copy and paste) the following query:

SELECT @@VERSION

The following table shows the relationship between the product version and the SQL Server release and product level:

Product Version SQL Server 2005 Release and Product Level

9.00.1399.06 SQL Server 2005

9.00.2047.00 SQL Server 2005 SP1

For more information on determining your Microsoft SQL Server version, go to http://support.microsoft.com/default.aspx?scid=kb;en-us;321185.

http://support.microsoft.com/default.aspx?scid=kb;en-us;321185


If you will install the Web Order module, review “Web Order Starter Site” on page 38.

If you will install a Web Order Starter Site, verify that the Web server where you will install it meets the following hardware and software minimum requirements. Remember, these are minimum requirements. Actual needs will depend on your anticipated transaction processing load:

• 1.0 GHz or higher processor speed

• 256 MB of RAM (512+ MB recommended)

• 2 GB of available hard disk space (4 GB recommended)

• Microsoft Windows Server 2003 with Internet Information Services (IIS) 6.0

Note: Windows XP is not a supported platform for Web Order.

Load or install all required and related software and hardware resources on the server and workstations where you will install Microsoft Dynamics SL. Make sure that all environment settings are correct.

Determine whether you will install the Microsoft Dynamics SL Software Development Kit (SDK).

How can I determine if I should install the Microsoft Dynamics SL Software Development Kit?

See whether the Microsoft Dynamics SL Software Development Kit is included in your license keys, or confirm that you should install the Microsoft SL SDK by contacting your Microsoft Certified Partner.

Perform a system backup on the server where you will install Microsoft Dynamics SL. Contact your system administrator if you need assistance.

Note: If you are updating an existing installation of Microsoft Dynamics SL, be sure to create a backup of all custom Crystal Reports in your existing Microsoft Dynamics SL installation so that you can restore them after you install release 7.0. See “Updating Custom Crystal Reports” on page 115 for more information.

You must log on as the local administrator or as a member of the local Administrators group at the server where you will install Microsoft Dynamics SL. Failure to log on with administrator privileges will cause problems in the installation.

Note: If you use Active Directory, you must log on as a member of the Domain Administrators group, which needs to be part of the local Administrators group.

Performing full or client installations on Windows Server 2003 requires Administrator rights because the installation process must update the Windows registry. You might also need to reboot the server during or after installation.

On the server where you will install Microsoft Dynamics SL, close all currently running programs and stop SQL Server Services.

Note: Because Microsoft Dynamics SL Setup may need to update files used by other programs or services, it is important to complete this step before starting the installation.

How do I stop and restart SQL Server Services?

Use the SQL Server Configuration Manager or the SQL Server (MSSQLServer) Properties dialog box in Administrative Tools | Services on the Control Panel to stop and restart SQL Server services in Windows XP, Windows Server 2003, or Windows Vista.

To stop and start services using SQL Server Configuration Manager (recommended procedure):

1. Click the Start button, and then point to All Programs | Microsoft SQL Server 2005 | Configuration Tools.

2. Click SQL Server Configuration Manager.


3. Click the SQL Server 2005 Services icon in the left pane under SQL Server Configuration Manager.

4. Right-click the SQL Server (MSSQLSERVER) service listed in the right pane of the window.

5. Select Stop to stop the SQL Server 2005 services. Select Start to resume the services if you stopped them previously. Select Restart to stop and immediately restart the services.

To stop and start services using the MSSQLSERVER Properties dialog box:

1. Click the Start button, and then click Control Panel.

2. In the Control Panel, double-click Administrative Tools, and then double-click Services.

3. Scroll down until you see SQL Server (MSSQLSERVER), and then double-click to select it.

4. Under Service Status, click the Stop button. SQL Server Services stop.

5. A message stating SQLServerAgent will also shut down might appear if this service is running. Click Yes to stop the SQLServerAgent.

Note: If this message appears, remember to restart SQLServerAgent when restarting MSSQLServer. If SQLServerAgent does not restart, any backups or other jobs scheduled in Microsoft SQL Server will not run.

6. When SQL Server (MSSQLSERVER) Properties (Local Computer) reappears, indicating that the services have been stopped, click OK.

7. To restart SQL Server, select it again in Administrative Tools | Services. click Start, and then click OK in SQL Server (MSSQLSERVER) Properties (Local Computer) when it reappears. Remember to restart SQL Server Agent (if needed) when restarting SQL Server.

If an earlier 32-bit release of Microsoft Dynamics SL is installed (Release 4.x, 5.x or 6.x), you must export all screen customizations. The Export Customizations (91.500.00) screen will help you accomplish this task (see the Customization Manager online help or user guide for assistance). Be sure to store the export file in a safe place.

You can also use the VBA Code window to export the customization’s Visual Basic code for safekeeping (see “Export Customizations” in this installation guide for more information). In addition, print the customization code from within the Visual Basic for Applications integrated development environment (VBA IDE). Having a printed copy of the customization code will help ensure that you can rebuild a customization if necessary.

If an earlier 32-bit release of Microsoft Dynamics SL is installed (Release 4.x, 5.x or 6.x), you must remove the earlier release, first from all workstations and then from the server where it is installed before you start this installation. If you do not remove the earlier release before beginning this installation, the software will require that you do so and will initiate the removal before starting the installation.

How do I remove an earlier release of Microsoft Dynamics SL?

Be sure to perform a system backup before you follow these steps:

1. Select Start | Control Panel.

2. Double-click Add or Remove Programs.

3. Locate your current Microsoft Dynamics SL release on the list of currently installed programs, and then click to select it.

Note: If you are performing these steps on the server where the earlier release is installed, you must remove all Microsoft Dynamics SL clients installed on workstations and on the server first before you remove Microsoft Dynamics SL (see “Removing an Existing Installation” on page 99 for more information).

4. Click Remove.

Your Pre-Installation Checklist is now complete. Be sure to print it so that you can refer to it during the installation tasks.


Installation Options The installation options window displays at the start of the installation process.

Figure 1: Installation options window

The installation options include the following:

• Microsoft Dynamics SL Installation Guide — Opens the Microsoft Dynamics SL Installation Guide in Adobe Acrobat Reader .pdf file format.

• Microsoft Dynamics SL — Starts the installation process.

• Microsoft Dynamics SL Web Order Starter Site — Starts the Web Order Starter Site setup.

• Crystal Reports — Starts the Crystal Reports setup. Install Crystal Reports if you plan to modify standard Microsoft Dynamics SL reports or create custom reports.

• Microsoft SQL Server — Prompts you to exit and insert the Microsoft SQL Server installation CD.

• Microsoft Project Connector — Starts the Microsoft Project Connector installation.

• Microsoft Office XP Smart Tag Manager — Installs Microsoft Office XP Smart Tag Manager to set up and enable Smart Tags.

• FRx — If you choose FRx, you will receive a prompt to use your FRx CD to perform the installation.

• Microsoft Dynamics SL User Guides — Installs the application user guides, including the Microsoft Dynamics SL Software Development Kit, the Security Guidelines for Microsoft Dynamics SL, and the Visual Basic® 2005 Conversion Toolkit for Microsoft Dynamics™ SL.

• BIO for Microsoft Dynamics SL — Installs Business Information Optimization (BIO) for Microsoft Dynamics SL, an easy-to-use analytics solution that helps amplify the impact all people can have in an organization through relevant insight into business drivers.

• Browse DVD — Opens Windows Explorer so that you can view the contents of the DVD.

• Exit Installation — Allows you to quit the Setup program.

If an earlier release of Microsoft Dynamics SL is not installed on your workstations or server, proceed to “Guide for New Installations” on page 11.

If you are updating an earlier release, continue with “Upgrading an Existing Installation” on page 97.

Guide for New Installations 11

Guide for New Installations

Overview This section covers the following topics for those who do not currently have Microsoft Dynamics SL installed:

• “Installing Microsoft Dynamics SL” on page 12 guides you through installing the application files on your company’s server. These steps apply to both new and upgrade installations.

• “Microsoft SQL Server Installation” on page 22 prompts you to install the Microsoft SQL Server database software on your company’s database server.

• “Creating Databases” on page 23 describes the various databases you can create and explains how to create them.

• “Installing Supporting Applications” on page 38 guides you through the installation process for the applications that provide added functionality to Microsoft Dynamics SL.

• “Setting Up Microsoft Dynamics SL on Workstations” on page 87 explains how to set up workstations that will connect to the new environment.

Note: Installation instructions for FRx are on the FRx CD.


Installing Microsoft Dynamics SL This section walks you through the steps to use the product DVD to install Microsoft Dynamics SL on your server. Note that this section pertains equally to creating new installations and updating existing installations. It describes the steps for running the installation for both purposes.

To install Microsoft Dynamics SL:

1. Log on as the local administrator or as a member of the local Administrators group at the server where you will install the software. Failure to do so will cause problems in the installation.

Note: If you are using Active Directory, you must log on as a member of the Domain Administrators group, which in turn needs to be part of the local Administrators group.

2. Insert the DVD into the drive.

a) If AutoPlay is enabled on the DVD drive, the installation options window automatically appears.

b) If AutoPlay is not enabled, run Setup.exe in the root directory of the DVD by choosing Start | Run and browsing to the DVD drive.


3. Click Microsoft Dynamics SL.


Welcome appears.

Figure 3: Welcome

Note: Do not disable virus detection/protection software.

4. Click Next. License Agreement appears, asking you to accept or decline the software license agreement.

5. Carefully read the license agreement. To print the agreement, click Print.

6. To agree to the terms of the license agreement and continue with the installation, click I accept the terms of the license agreement, and then click Next.

If you click I do not accept the terms of the license agreement, and then click Cancel, Exit Setup appears, prompting you to quit or resume installing. You can cancel the installation or accept the license agreement terms and continue.


If you agree to the license agreement terms, Instructions appears.

Figure 4: Instructions

7. Read the installation notes, and then click Next.

Choose Edition appears.

Figure 5: Choose Edition


8. Click the Install button for the appropriate Business Ready Licensing or Module Licensing edition. Your choice is based on the information you verified in “Which Microsoft Dynamics SL edition should I install?” on page 6.

Choose Destination Location appears, displaying the default destination folder for the installation.

Figure 6: Choose Destination Location

9. Install the Microsoft Dynamics SL program files in the default destination folder (C:\Program Files\Microsoft Dynamics\SL\Applications) or at least one directory level from the hard disk root directory (for example, {drive letter}:\Microsoft Dynamics\SL\Applications\7_0\). The folder you install the program files in—the 7_0 folder in the example—must be shared in order to support connections by multiple workstations. Verify that the folder to be shared is acceptable for sharing.

a) If you want to install the program files in the default destination folder, click Next to continue.

b) If you want to override the default destination folder, click Browse and locate the folder in which you want to install the program files. If the destination folder does not already exist, the software will ask whether it should create it, allowing you to confirm that you have selected the correct location. Click Next.

10. If this is an upgrade installation and the software detects a previous Microsoft Dynamics SL installation, it requires you to remove the previous installation before continuing.

Click Yes to uninstall.

11. If this is an upgrade installation and the software detects an existing menu file (Delta.mnu) in the selected destination folder, it lets you save a backup of the existing menu file in the backup subdirectory.

Figure 7: Confirm Backup


12. Click Yes to have the software back up the existing menu file.

Select Microsoft Dynamics SL Applications appears, displaying the applications that will be installed.

Figure 8: Select Applications – Advanced Management selected

13. In this window, you can select modules and applications to install. To select applications individually, clear the module group check box, and then select a module from the list. For example, to install Web Order, clear the E-commerce check box, and then select the Web Order check box in the list of E-Commerce applications.

If you selected Module Licensing in step 8, all modules are selected.

Strongly recommended: Select only those applications you need to install. Do not automatically select all.

Special considerations:

• If you plan to use the Electronic Document Delivery (EDD) feature, select Application Server in the E-Commerce module group. EDD functionality is available only when the Application Server program files are installed, although you do not need to purchase a license for Application Server in order to use EDD.

• If you plan to install the Business Portal, you will need to have the Application server module installed as well. Select Application Server in the E-Commerce module group.

• You can install the application user guides by selecting Microsoft Dynamics SL User Guides on the installation options window. User guides are provided in Adobe Acrobat PDF format.

14. Click Next.

15. If you selected Client Setup Utility in the Foundation Series and the software detects a previous Microsoft Dynamics SL client installation, it requires you to remove the previous installation before continuing.

Click Yes to uninstall.

16. If you selected Tools, Software License Agreement appears again, this time asking you to accept or decline the Microsoft Dynamics SL Software Development Kit license agreement.


Carefully read the software license agreement. To print the agreement, click Print.

17. To agree to the terms of the license agreement and continue with the installation, click I accept the terms of the license agreement, and then click Next.

If you click I do not accept the terms of the license agreement, and then click Cancel, Exit Setup appears, prompting you to quit or resume installing. You can cancel, accept the license agreement terms and continue the installation, or click the Back button to remove Tools from the list of modules to be installed.

18. If you selected Customization Manager in the Foundation module group, Customization Features appears after the installation resumes. It prompts you for the type of customization features to use with the Customization Manager module.

Figure 9: Customization Features

After reading about the choices, select the appropriate customization option.

a) VBA features — Installing Visual Basic for Applications (VBA) features allows you to create new customizations using VBA code and to translate existing Basic Script Language (BSL) customizations to VBA code. If you prefer to use or upgrade to VBA, choose VBA features.

b) BSL features — Installing the Basic Script Language (BSL) features allows installations that are upgrading to having to use VBA if they prefer to continue using current customizations written in BSL. Choose BSL features if you prefer to continue writing and editing code using BSL.


19. Click Next. The message, “Calculating space requirements. Please wait…”, appears briefly, and then Start Copying Files appears, listing all current installation selections.

Figure 10: Start Copying Files

20. Verify that all installation selections are correct. If a change is needed, click Back until arriving at the incorrect selection, and then make the correct selection. Click Next until Start Copying Files displays again.

21. Review the selections to make sure they are correct, and then click Next.

Setup copies files from the DVD. If the Client Setup Utility in the Foundation Series is selected (step 13), Setup next executes the Client Setup program.


22. In order for Client Setup to complete, Microsoft .NET Framework version 2.0 must be installed. If the software is not detected by the Client Setup program, the Microsoft .NET Framework 2.0 Setup window appears.

Figure 11: Microsoft .NET Framework 2.0 Setup

23. Click Next. End-User License Agreement appears, asking you to accept the software license agreement or cancel the installation.


25. To agree to the terms of the license agreement and continue with the installation, select I accept the terms of the License Agreement, and then click Install. If you agree to the license agreement terms, the Files in Use dialog box appears, asking you to close the Client Setup program.

Figure 12: Files In Use

If you click Cancel, the installation will end.


26. In the Files In Use dialog box, click Ignore. The .NET Framework Setup program begins. When it is finished, Setup Complete appears.

Figure 13: Setup Complete

27. Click Finish. The Client Setup program will continue.

Note:

The Setup Complete window recommends installing the latest Microsoft .NET Framework service packs and security updates. Be sure to do this after Client Setup completes.

If the Client Setup program does not resume immediately, click the Client Setup window to return focus to the process.

28. After Setup finishes installing files, View Readme File appears, asking if you would like to review the ReadMe.txt file.

Figure 14: View Readme File dialog box

29. Click Yes.

30. Review ReadMe.txt file on the screen, or choose File | Print to print it.


31. After reviewing or printing, close the file by closing Notepad. InstallShield Wizard Complete appears.

Figure 15: InstallShield Wizard Complete

32. Click Finish.

33. Close the installation options window.

Now that Setup has finished installing the application files, you can create or update databases.

• If this is a new Microsoft Dynamics SL installation, proceed to “Creating Databases” on page 23.

• If you are updating an existing installation, proceed to “Updating Databases” on page 101.


Microsoft SQL Server Installation Microsoft SQL Server 2005 Standard or Enterprise Edition with Service Pack 1 is a requirement of Microsoft Dynamics SL. Microsoft SQL Server must be purchased separately. Contact your Microsoft Certified Partner for more information.

For additional help in determining configuration requirements, contact your Microsoft Certified Partner.

You must install Microsoft SQL Server and start the service(s) before you can create Microsoft Dynamics SL databases. See “Creating Databases” on page 23.

To install Microsoft SQL Server:

1. Insert the Microsoft SQL Server CD into the CD drive. Microsoft SQL Server setup starts.

2. Follow the on-screen prompts to install Microsoft SQL Server.

Note: Microsoft Dynamics SL requires that you install Microsoft SQL Server using the default settings for Sort Order and Character Set. In addition, on the Authentication Mode page of the Microsoft SQL Server Installation Wizard, you must select Mixed Mode (Windows Authentication or SQL Server Authentication).

3. Follow the instructions in “Appendix A: SQL Server Optimization Notes” on page 129 to set up Microsoft SQL Server for use with Microsoft Dynamics SL.


Creating Databases 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.

Before you installed Microsoft Dynamics SL, you recorded information about your databases on your Pre-Installation Checklist. Retrieve the printout of your list. It will be important in the following steps.

In the Database Maintenance (98.290.00) screen, you can create databases based on four different scenarios:

• Empty Databases — Use this scenario to create a new system database and a new application (production) database.

• Demo – Business Ready Editions — Use this scenario to create system and application databases based on the software package you chose when you installed Microsoft Dynamics SL (see “Which Microsoft Dynamics SL edition should I install?” on page 6).

• 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 Series data.

• Additional Empty Application Database — Use this scenario to create an additional application database for use with an existing system database.

To create databases:

Note: These procedures must be performed by your Microsoft Dynamics SL system administrator.

1. Confirm that the SQL Server service is running. Restart it if necessary. See “How do I stop and restart SQL Server Services?” on page 8 for information about starting SQL Server services.


2. Launch 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.

Figure 16: Database Maintenance (98.290.00)

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.

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


6. Click the Create Databases tab.

Figure 17: Database Maintenance (98.290.00), Create Databases tab

7. Follow the setup instructions for the type of database you are creating:

• “Creating an Empty Database” on page 26

• “Creating a Demo Database” on page 30

• “Creating an Additional Empty Application Database” on page 34


Creating an Empty Database

To create an empty database:

1. Choose Empty Databases from the Scenarios list.

2. Click Advanced.

Advanced Configuration Settings appears.

Figure 18: Advanced Configuration Settings

3. Under System Database Definition, change System Database Name, System Database Size (MB), Server Location of Database Files, and Server Location of Transaction Log if necessary.

4. Under Application Database Definition, change Database Name, Size, Database Path, and Transaction Log Path as needed.

5. Click Ok. The Create Databases tab reappears.

6. Click Create. The Authentication dialog box appears.

Figure 19: Authentication


7. Select an authentication mode, and then click OK. It is strongly recommended that you select Windows authentication to provide the most secure system. If you selected SQL Server Authentication, go to step 9. If you selected Windows Authentication, SYSADMIN Windows User Name appears.

Figure 20: SYSADMIN Windows User Name

8. In Windows User Name, type the identifier of the Windows user who will be the Microsoft Dynamics SL administrator for this database. Type the information using the domain\username format, and then click OK.

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

9. If you selected Windows Authentication in the Authentication window, go to step 17.

If you selected SQL Server Authentication, Security appears.

Figure 21: Security


10. Click Yes to confirm that SQL Server authentication is the authentication mode to be used to access the computer that is running SQL Server. SQL Master60SP Login appears if you have not yet created the Master60SP user. This will not happen if you have already installed a database for Microsoft Dynamics SL 6.0 Service Pack 1 or later on the computer that is running SQL Server.

Click No if you should have selected Windows authentication. The Authentication dialog box appears. Go to step 7 and repeat the steps to select Windows authentication and to set up and create the scenario databases.

Note: If you have already created the Master60SP user, proceed to step 14.

Figure 22: SQL Master60sp Login

11. In the Password box, type a password for the Master60sp user that satisfies the strong password requirements listed in the dialog box.

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

12. In Confirm Password, type the password again.


13. Click Ok. The SYSADMIN Login dialog box appears.

Figure 23: SYSADMIN Login

14. In the Password box, type a password for the SYSADMIN user that satisfies the strong password requirements listed in the dialog box.


15. In the Confirm box, type the password again.

16. Click OK.

17. When “Database creation process complete” appears, click OK.

18. Click Close.

19. Review the Dbbuild.log file (typically found in the Microsoft Dynamics SL EventLog folder). If the database creation was successful, Dbbuild.log will only contain the times the process started and ended.

20. If you need to create additional empty application databases for use with the system database you just created, proceed to “Creating an Additional Empty Application Database” on page 34.

If you are finished creating databases, proceed to “Logging On Using the Empty System and Application Databases” on page 36.


Creating a Demo Database

To create a demo database:

1. Choose Demo – Business Ready Editions, Demo – Professional Edition, or Demo – Standard Edition from the Scenarios list.

Note: If you select Demo – Business Ready Editions, the system and application databases will be created based on the software package you chose when you installed Microsoft Dynamics SL.

2. Click Advanced. Advanced Configuration Settings appears.


Note: The demo system database names are SLDemoSystem and DemoStandardSystem. Demo companies are included, and the application database names for these companies are listed below. Use these names for your demo databases when feasible.

• SLDemoApp10 (companies 0010 and 0020)

• SLDemoApp60 (companies 0060, 0070, and 0080)

• DemoStandardApp51 (company 0051)

3. Under System Database Definition, change System Database Name, System Database Size(MB), Server Location of Database Files, and Server Location of Transaction Log if necessary.

4. Under Application Database Definition, change Database Name, Size, Database Path, and Transaction Log Path as needed.



6. Click Create. The Authentication dialog box appears.


7. Select an authentication mode, and then click OK. If you selected SQL Server Authentication, go to step 9. If you selected Windows Authentication, SYSADMIN Windows User Name appears.


8. In Windows User Name, type the identifier of the Windows user who will be the Microsoft Dynamics SL administrator for this database. Type the information using the domain\username format, and then click OK.

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



Figure 27: Security


10. Click Yes to confirm that SQL Server authentication is the authentication mode to be used to access the computer that is running SQL Server. SQL Master60SP Login appears if you have not yet created the Master60SP user. This will not happen if you have already installed a database for Microsoft Dynamics SL 6.0 Service Pack 1 or later on the computer that is running SQL Server.

Click No if you should have selected Windows authentication. The Authentication dialog box appears. Go to step 5 and repeat the steps to select Windows authentication and to set up and create the scenario databases.

Note: If you have already created the Master60SP user, proceed to step 12.











16. Click OK.


18. Click Close.

19. Review the Dbbuild.log file, which is typically found in the Microsoft Dynamics SL EventLog folder. If the database creation was successful, Dbbuild.log contains only the start and end times for the process. If Dbbuild.log contains other text, contact Support Services for assistance.

20. Proceed to “Logging On Using the Demo System and Application Databases” on page 35.


Creating an Additional Empty Application Database

To create an additional empty application database:

1. Choose Additional Empty Application Database from the Scenarios list. This scenario will only be applicable after you have created your original empty database.

2. Click Advanced. Advanced Configuration Settings appears.


3. In the Application Database Definition area, complete the Database Name, Size, Database Path, and Transaction Log Path boxes.

Note: Do not enter information in the boxes under System Database Definition. You will define the system database in step 10.


Click Create. Identify System Database (98.290.40) appears.

Figure 31: Identify System Database (98.290.40)

5. Select the appropriate system database for your new application database from the System Database Name list.

6. Click Ok. Database creation begins.


8. Click Close.

9. Review the Dbbuild.log file, which is typically found in the Microsoft Dynamics SL EventLog folder. If database creation is successful, the Dbbuild.log contains the start and end times for the process.


Logging On Using the Demo System and Application Databases

To log on after creating the demo system and application databases:

1. Go to Start | All Programs and click Microsoft Dynamics SL. Microsoft Dynamics SL Login (98.000.00) appears.

2. Click Find Database. Find Database (98.000.01) appears.

Note: See your system administrator for the server and database names.

3. Select a server name from the Server Name list, or type the name of the server if it does not appear on the list.

4. Select a system database name from the Database Name list, or type the name of the system database if it does not appear on the list (for example, SLDemoSystem).

5. Click OK. Microsoft Dynamics SL Login (98.000.00) appears again. If your system is configured for Windows authentication and you logged on to Windows using the Windows sysadmin user name that was specified when the database was created, only Company will appear. If your system is configured for SQL Server authentication, User ID and Password also appear.

6. In Company, press F3, locate the company you want to access, and click to select it.

7. If your system is configured for SQL Server authentication, enter a user ID and password. The demo database default user ID is SYSADMIN.

8. Click OK.

9. Continue with “Preparing the Demo System and Application Databases” below.

Preparing the Demo System and Application Databases Preparing databases for operation means loading them with data contained in the .csv files. The data includes:

• System messages

• Possible values records

• Report control information

To prepare the demo system and application databases:

1. In the Microsoft Dynamics SL window, click the Administration button.

2. Select Database Update by either clicking it on the application pane on the right side of the window or double-clicking it on the Administration list. Database Update (98.100.00) appears.

3. In Directory, browse for …\DB\CSVs.

4. Select messages.msg, pvrec.csv, and rptcontrol.csv from the Files list by clicking on them. It is not necessary to hold down the CTRL key or SHIFT key.

5. Click Begin Processing.

6. Click OK when processing is complete.

7. Exit Database Update (98.100.00).

Your databases are ready to use. To install other applications that provide additional functionality to Microsoft Dynamics SL, proceed to “Installing Supporting Applications” on page 38.


Logging On Using the Empty System and Application Databases

To log on after creating the empty system and application databases:

1. Go to Start | All Programs and click Microsoft Dynamics SL. Microsoft Dynamics SL Login (98.000.00) appears.

2. Select a server name from the Server Name list, or type the name of the server if it does not appear on the list.

3. Select a system database name from the Database Name list, or type the name of the system database if it does not appear on the list.

4. Click OK. Microsoft Dynamics SL Login (98.000.00) appears again.

5. Verify that Company is blank.

6. If your system is configured for Windows authentication, you must log on to Windows using the Windows sysadmin user name that was specified when the database was created. If your system is configured for SQL Server authentication, you will need to enter your User ID and your Password.

7. Click OK to log on.

8. In the navigation pane on the left side of the Microsoft Dynamics SL window, click the plus sign next to Administration to view the applications, and then double-click Company Maintenance. Company Maintenance (98.280.00) appears.

Figure 32: Company Maintenance (98.280.00)

9. You must create at least one company. Follow these steps to set up a company:

a) In Company ID, type a code to identify the company. It can be up to 10 characters long (for example, 0040).

b) In Company Name, type the company name.

c) In Database Name, specify the application database name you listed on the “Empty Databases” list on page 6.

d) In the Address through Employer Tax ID boxes, type the company’s address and other related information.

10. Click the Save button on the toolbar, or click Save on the Actions menu.

11. Close the screen.

12. Click the Switch Company button on the toolbar. Microsoft Dynamics SL Login (98.000.00) appears.


13. Specify the appropriate company. You can also select the company from a list of possible values by pressing F3.

14. If you are using SQL Server authentication to access the computer that is running SQL Server, enter the SYSADMIN user ID and appropriate password.

15. Click OK.

16. Continue with “Preparing the Empty System and Application Databases.”

Preparing the Empty System and Application Databases Preparing databases for operation means loading them with data contained in the .csv files. These data include:

• System messages

• Possible values records

• Report control information

To prepare the empty system and application databases:

1. In the Microsoft Dynamics SL window, click the Administration button, and then select Database Update. Database Update (98.100.00) displays.


3. Select messages.msg, pvrec.csv, and rptcontrol.csv from the Files list by clicking on them. It is not necessary to hold down the CTRL key or SHIFT key.


5. When processing is complete, click OK to finish preparing the production system and application databases.

6. Close Database Update (98.100.00).

Note: Complete steps 7 through 10 if the Multi-Company module is installed.

7. Open the Multi-Company module, and then select Multi-Company Setup. Multi-Company Setup (13.950.00) appears.

8. Select Activate Multi-Company with Inter-Company Processing.

9. Click the Save button, or click Save on the Actions menu.

10. Close Multi-Company Setup (13.950.00).

11. Open General Ledger, and then define information required for General Ledger module setup.

a) Set up the retained earnings and YTD net income accounts in Chart of Accounts Maintenance (01.260.00).

b) Define subaccount (organizational) information in Subaccount Maintenance (01.270.00).

c) Define ledger information in Ledger Maintenance (01.310.00).

12. Select GL Setup. GL Setup (01.950.00) appears.

13. Define the appropriate setup information on the Options, Fiscal Info, and Currency Info tabs.

Note: This step is required. However, you cannot complete all fields on the tabs until you first define retained earnings and YTD net income accounts, subaccounts, and ledgers. See step 11.

14. Click the Save button, or click Save on the Actions menu.

15. Close GL Setup (01.950.00).

16. Register Microsoft Dynamics SL.

It is strongly recommended that you register your Microsoft Dynamics SL system immediately after completing the installation to avoid running out of TRIALLOC database accesses.


Installing Supporting Applications

Web Order Starter Site

General Installation Information A complete installation of Microsoft Dynamics SL Web Order consists of two parts:

1. Installing the Web Order module.

2. Installing a Web Order Starter Site.

Before an order can be submitted using Web Order, it must be possible to submit an order using Sales Orders (40.100.00) in Order Management.

Web Order Starter Site System Information Web Order Starter Site is an Active Server Pages application that is installed on a Web server running Microsoft Internet Information Services (IIS). It is recommended, but not required, that your Web Order Starter Site run on its own dedicated Web server.

Requirements

Note: The Web server on which you plan to install your Web Order Starter Site must meet the minimum requirements listed in the “Pre-Installation Checklist” on page 8.

Before running the Setup program for the Web Order Starter Site, verify that the following are installed and running on the Web Order Starter Site dedicated Web server:

Microsoft IIS

Web Order module

Order Management module

Inventory module

Windows Script 5.6 (available for download from Microsoft, http://www.microsoft.com/vbscript)

ActiveX Data Objects (ADO) 2.6 or later (available for download from Microsoft, http://www.microsoft.com/data/download.htm).

Internet Explorer 6.0 Service Pack 1 or later (available for download from Microsoft, http://www.microsoft.com/ie/).

http://www.microsoft.com/vbscript

http://www.microsoft.com/data/download.htm

http://www.microsoft.com/ie/


Installing the Web Order Starter Site

To install the Web Order Starter Site:

1. Insert the Microsoft Dynamics SL DVD into the DVD drive of the Web Order Starter Site server.




2. Click Microsoft Dynamics SL Web Order Starter Site. The Welcome dialog box appears and advises you to close Windows programs before continuing with the installation.

3. Click Next.

The Software License Agreement dialog window appears, asking you to accept or decline the software license agreement.

4. Carefully read the software license agreement. To print the agreement, click Print.


5. To agree to the terms of the license agreement and continue the Web Order Starter Site setup, click I accept the terms of the license agreement, and then click Next.

If you click I do not accept the terms of the license agreement, and then click Cancel, Exit Setup appears, prompting you to exit or resume the Web Order Starter Site setup.

When Web Order Starter Site Setup resumes, Select Features appears, prompting for the Web Order Starter Site features to install.

Figure 34: Select Features

6. Verify that the Web Order System Files and Web Order Application Files check boxes are selected.


7. Click Next. Commerce Site Server Name appears prompting for the name of the server that will host the Web Order Starter Site.

Figure 35: Commerce Site Server Name

8. In Server, type the name of the Web Order Starter Site server. This is the name of the Web server that will host the Starter Site.

In order for the Web Order system to be accessible using the Internet, make sure you type a fully qualified domain name. For example, if the server name is mysiteserver and the domain name is mydomain.com, type mysiteserver.mydomain.com in Server.


9. Click Next.

Commerce Site Alias appears.

Figure 36: Commerce Site Alias

10. In Site Alias, type the name of the Web Order Starter Site virtual directory.

Site Alias is a name that identifies the Web Order Site application. It is part of the URL that is used to access the application. For example, if the server name you typed in step 8 is MyServer and you type WebOrderSite as the Site Alias, then the URL to access the application will be http://MyServer/WebOrderSite.

11. In Manager, type the name of the Web Order Manager virtual directory.

Manager is a name that identifies the Web Order Manager Site application. It is part of the URL used to access the application. For example, if the server name you typed in step 8 is MyServer and if you type WebOrderManager as the Manager, then the URL to access the application will be http://MyServer/WebOrderManager.

Note: You must use a new name for the virtual directory. Do not use the name of an existing virtual directory.

http://myserver/WebOrderSite


12. Click Next. Commerce Site Location appears, prompting for the Web Order Starter Site directory.

Figure 37: Commerce Site Location

13. Type the physical path to the folder where the Setup program should install the Web Order Starter Site Active Server Pages (ASP) applications.

Note: The Web Order Starter Site directory must be a new directory, not an existing one.

14. Click Next. Commerce Site Information appears, prompting for a descriptive title for the Web Order Starter Site.

Figure 38: Commerce Site Information


15. In Title, type the name of the Web Order Starter Site. You can change this title after Web Order Starter Site setup is complete.

16. Click Next. Database Setup and Login appears.

Figure 39: Database Setup and Login

17. In Server, type the name of the database server where the application database to use for Web Order is located.

18. In Database, type the name of the application database to use for Web Order.

19. In User and Password, type the SQL Server user name (sa) and password that the Web Order Starter Site should use to connect to the database.

20. Click Next. Test Database Connection appears.

Figure 40: Test Database Connection

21. Click Yes. If the database connection tests successfully, a message appears to confirm it.

If the connection fails, an error message appears. Verify that the values for Server, Database, User, and Password are correct. Also, verify that the database server is running and accessible from the Web server. If the values for Server, Database, User, and Password are correct and test connection still fails, you can continue with the installation and resolve the connection issue when your installation is finished.


22. If you click No, Web Order Starter Site Setup proceeds with the current database connection values. Start Copying Files appears.


23. Verify that all the choices you made for your Web Order Starter Site installation are correct.

24. If changes are needed, click Back until arriving at the incorrect selection.

25. Make the correct selection.

26. Click Next until you return to Start Copying Files.

27. Review the selections again to make sure they are correct.

28. Click Next. After a few seconds, a message appears, informing you that the new site created successfully.

Figure 42: Successful commerce site creation message


29. Click OK. The Setup program copies the application and system files to the appropriate directories.

InstallShield Wizard Complete appears.


30. Click Finish to complete the Web Order Starter Site installation and exit the Setup program.

Note: If a message appears, advising you to reboot the Web Order Starter Site server, be sure to do so. It may be necessary to reboot the server to fully register all new DLL files in the system registry.

Web Order Module Setup The Web Order module must be set up for operation before users can log on and place orders using the Web Order Starter Site. Module setup procedures include:

• Defining Web Order configuration information in Web Order (83.950.00).

• Configuring inventory sites for use in the Web Order Starter Site in Inventory Sites (10.255.00). By default, inventory sites are not automatically visible in the Web Order Starter Site.

• Setting up Web Order users and user groups in Web Order Maintenance (83.200.00).

See the Web Order user guide in \User Manuals\program files\Microsoft Dynamics SL\sl_wc.pdf on your Microsoft Dynamics SL DVD for additional information.


Crystal Reports Crystal Reports® for Solomon Version 10 is required only if you plan to design new reports. Unless you have version 10 already installed, you must remove Crystal Reports from the server and workstations before you install version 10.

Removing an Earlier Version of Crystal Reports

To remove an earlier version of Crystal Reports before installing version 10:

1. Remove Crystal Reports using Add/Remove Programs in the Windows Control Panel.

2. In Windows Explorer, delete all Crystal Reports program folders. A typical path is \Program Files\Crystal Decisions.

3. Locate the following files in \Crystal\Utilities on the Microsoft Dynamics SL DVD: uSCR5_16.exe uSCR6_32.exe uSCR5_32.exe uSCR7_16.exe uSCR6_16.exe uSCR7_32.exe

4. Open the self-extracting executable file appropriate for the version of Crystal Reports to be removed.

Example: If the 32-bit version of Crystal Reports is installed, uSCR6_32.exe is the correct file to open.

5. Follow the instructions in the Install.txt file that is included in the self-extracting file.

6. Verify that Crystal Reports is completely removed from the server and workstation hard drives by searching in Windows Explorer for the following files: CRW.net CRR*.exe CRW32.net CRPE.dll CRW.exe CRPE32.dll CRW32.exe

Note: Possible cleanup of the registry keys might be needed. Contact your system administrator for assistance with this task.


Installing Crystal Reports Version 10

To install Crystal Reports® Version 10 on the server (repeat these steps at each workstation):

1. Insert the Microsoft Dynamics SL DVD into the server’s DVD drive.




2. Select Crystal Reports®. Crystal Reports for Solomon Setup appears and advises you to close Windows programs before continuing with the installation.

Figure 45: Crystal Reports Setup


3. Click Next. License Agreement appears.

4. Carefully read the software license agreement, and then click I accept the License Agreement.

5. Click Next. Select Installation Type appears.

Figure 46: Select Installation Type

6. Select Typical.

7. Verify the path specified in Destination Folder:

• If the default destination folder is correct, click Next to continue.

• If the default destination folder is not correct, click Browse to locate the correct folder or type in the desired location.

Note: If you specify a path other than the default in Destination Location, be sure to also change the Crystal Location line in the [Miscellaneous] section of the Solomon.ini file so that the paths match. The Solomon.ini file is located in the folder that holds the Microsoft Dynamics SL program files (typically \Program Files\Microsoft Dynamics\SL\Applications).

8. Click Next.

9. Follow the remaining prompts to finish installing Crystal Reports.


10. When Crystal Reports for Solomon has been successfully installed appears, click Finish. Crystal Reports is installed on the server.

Figure 47: Successful installation message

Crystal Enterprise — In Crystal Reports Setup, you may be asked if you want to install Crystal Enterprise. Crystal Enterprise is not included with Microsoft Dynamics SL and is not supported by Support Services.

When using Crystal Reports, keep the following in mind:

• Microsoft Dynamics SL does not use Crystal Reports dictionaries.

• Crystal Reports supports Microsoft Dynamics SL user access control. Any user who is in Crystal Reports is counted as a Microsoft Dynamics SL seat license.

• To access Crystal Reports, you must be logged on to Microsoft Dynamics SL using a valid user ID and password.

• Crystal Reports service packs and hot fixes from Business Objects SA are not compatible with Crystal Reports for Microsoft Dynamics SL.

Note: Due to changes in the standard Microsoft Dynamics SL reports, customized reports from the 4.x, 5.x, and 6.x releases may not run without modification. Contact your Microsoft Certified Partner if your customized reports do not run.


Microsoft Office Project Connector Integrating the Microsoft Dynamics SL and Microsoft Project Server databases entails installing components, running scripts, or configuring options on the following computers (some computers can contain more than one application or service):

• The server where Microsoft Dynamics SL application files are installed (install components)

• The server where Microsoft Project 2003 is installed (install components)

• The IIS server where Business Portal provides Web access to Microsoft Dynamics SL functionality (install components and configure access)

• The database server that holds the Microsoft Project 2003 database (run scripts)

• The workstations where the Microsoft Dynamics SL client is installed (install components)

• The workstations where the Microsoft Office Project Professional 2003 client is installed (install components)

Note: In order to transmit information successfully between the Microsoft Dynamics SL and Microsoft Project Server databases, you must move your Microsoft Project database to a computer that is running Microsoft SQL Server 2005 with Service Pack 1 or later. The database server should have the same service pack as the server where you create or update your Microsoft Dynamics SL databases. To move the Microsoft Project database to a computer that is running Microsoft SQL Server 2005, follow the procedure in the Microsoft Knowledge Base article 917401. The article also describes the procedure for creating a new Microsoft Project database in SQL Server 2005.

After you complete the procedures in Knowledge Base article 917401, complete steps 7 and 8 of “Creating the Project Server Database Manually” in the Project Server 2003 IT Documentation found on Microsoft Office Online. These steps assist you in creating the MSProjectServerUser and MSProjectUser logins and associating them with the MSProjectServerRole and MSProjectRole database roles.

Setting Up Users for the Project Connector In order to use the integration between Microsoft Dynamics SL and Microsoft Project, you must be a valid user in both systems. Using identical logins facilitates trouble-free integration. Whether you choose Windows authentication or Project Server authentication, the user ID and name should remain consistent between Microsoft Project and Microsoft Dynamics SL.

Note: Using Windows authentication entails less user intervention than Project Server authentication and is the recommended authentication method. If you choose Project Server authentication, each user must supply additional credentials in order to log the PSA COM add-in (the component used for entering Microsoft Dynamics SL Project Management and Accounting information) into Microsoft Project Server each time the Microsoft Office Project Professional client is started. Furthermore, when new projects are created in a Microsoft Dynamics SL environment that uses Project Server authentication, the owner of the Project Server user ID in Microsoft Project Connector Setup (PA.MSP.00) must log on to Microsoft Project Server and publish each new project. Failure to do so results in the project being inaccessible to other users, including the project’s manager, until the designated user publishes it to Microsoft Project Server.

http://support.microsoft.com/kb/917401/en-us

http://office.microsoft.com/en-us/projservadmin/HA011654021033.aspx


Using Windows Authentication

To set up Windows authentication on Microsoft Project Server:

1. Log on to Microsoft Project Web Access as a user with administrative privileges.

Figure 48: Microsoft Project Web Access, Home page

2. Select Admin. The Administration overview page displays.

Figure 49: Microsoft Project Web Access, Administration overview page


3. Select Manage users and groups. The Users page displays.

Figure 50: Microsoft Project Web Access, Users page

4. Select Add User. The Add User page displays.

Figure 51: Microsoft Project Web Access, Add User page

5. In the Authenticate user by area, select the Windows Authentication, using the Windows User Account option button.


6. In Windows User Account, type the user’s Windows account information using the format DomainID\UserID.

7. In E-mail, type the user’s e-mail address.

8. In User Name, type the user’s name the way it should appear in the enterprise resource pool.

9. Select the user’s group, category, and global permission.

10. Click Save Changes.

11. Click Log Off.

To set up Windows authentication on Microsoft Office Project Professional 2003:

1. Open Microsoft Office Project Professional 2003 and select Tools | Enterprise Options | Microsoft Project Server Accounts.

Figure 52: Opening Microsoft Project Server Accounts


Project Server Accounts displays.

Figure 53: Project Server Accounts

2. In the When starting area, select the Manually control connection state option button and then click Add.

Account Properties displays.

Figure 54: Account Properties

3. In Account Name, type a description for the account.

4. In Microsoft Project Server URL, type the URL for Microsoft Project Server.

5. In the When connecting area, click the Use Windows user account option button.

6. Click Test Connection to confirm the validity of the information you entered.

7. Click OK to close Account Properties.

8. Click OK to close Project Server Accounts.

To set up Windows authentication in Microsoft Dynamics SL:

1. Log on to Microsoft Dynamics SL as a user with update access rights to Employee and Resource Maintenance (PA.EMP.00).

2. In the Microsoft Dynamics SL window, click the Project button, click Project Controller, and then select Employee and Resource Maintenance.


Employee and Resource Maintenance (PA.EMP.00) appears.

Figure 55: Employee and Resource Maintenance (PA.EMP.00)

3. For a new employee, enter all required information. For an existing employee, retrieve the employee’s record.

4. In User ID, type the user ID used to log on to the domain.

5. Click Save.

6. Close Employee and Resource Maintenance (PA.EMP.00).


Using Project Server Authentication When integrated employees are created in Microsoft Dynamics SL, a Project Server authenticated user is created automatically.

To set up Microsoft Project Server authentication on Microsoft Project Server 2003:

1. Log on to Microsoft Project Web Access as a user with administrative privileges.

Figure 56: Microsoft Project Web Access, Home page

2. Select Admin. The Administration overview page displays.

Figure 57: Microsoft Project Web Access, Administration overview page


3. Click Manage users and groups. The Users page displays.

Figure 58: Microsoft Project Web Access, Users page

4. Click Add User. The Add User page displays.

Figure 59: Microsoft Project Web Access, Add User page

5. In the Authenticate user by area, select the Microsoft Project Server authentication, using a logon ID and password option button.


6. In User Account, type the user’s name the way it should appear in the enterprise resource pool.

7. In E-mail, type the user’s e-mail address.

8. In Password, have the user type the password that he or she will use to log on to Project Connector.

9. In Confirm Password, have the user type the password again.

10. Select the user’s group, category, and global permission.

11. Click Save Changes.

12. Click Log Off.

To set up Project Server authentication on Microsoft Office Project Professional 2003:

1. Open Microsoft Office Project Professional 2003 and select Tools | Enterprise Options | Microsoft Project Server Accounts.

Figure 60: Opening Microsoft Project Server Accounts


Project Server Accounts displays.

Figure 61: Project Server Accounts

2. In the When Starting area, select the Manually Control Connection State option button and then click Add. Account Properties displays.

Figure 62: Account Properties

3. In Account Name, type a description for the account.

4. In Microsoft Project Server URL, type the URL for Microsoft Project Server.

5. In the When connecting area, select the Use a Microsoft Project Server account option button.

6. In User name, type the user’s name exactly as you entered it in User Account in step 6 of “Using Project Server Authentication” on page 57.

7. Click Test Connection to confirm the validity of the information you entered.

8. Click OK to close Account Properties.

9. Click OK to close Project Server Accounts.

To set up Project Server authentication in Microsoft Dynamics SL:

1. Log on to Microsoft Dynamics SL as a user with update access rights to Employee and Resource Maintenance (PA.EMP.00).

2. In the Microsoft Dynamics SL window, click the Project button, click Project Controller, and then select Employee and Resource Maintenance.


Employee and Resource Maintenance (PA.EMP.00) appears.

Figure 63: Employee and Resource Maintenance (PA.EMP.00)

3. For a new employee, enter all required information. For an existing employee, retrieve the employee’s record.

4. In User ID, type the user ID that will be used to log on to both Microsoft Dynamics SL and Microsoft Project Connector exactly as you entered it in step 6 of “Using Project Server Authentication” on page 57.

5. Click Save.

6. Close Employee and Resource Maintenance (PA.EMP.00).

Installing the Microsoft Project Connector

To add Microsoft Project Connector components to the application environment:

If you selected the Project Controller module in step 13 of “Installing Microsoft Dynamics SL”, you have already installed the Project Connector components that Microsoft Dynamics SL needs, although you must still install additional components for the Microsoft Project Server and Microsoft Office Project Professional application environments.

To add the Microsoft Project Connector to the Microsoft Project Server application environment:

1. Close all other programs running on the server where Microsoft Project Server is installed.

Because Microsoft Project Connector for Microsoft Dynamics SL Setup may need to update files used by other programs or services, it is important to complete this step before starting Microsoft Project Connector for Microsoft Dynamics SL Setup.

2. Insert the Microsoft Dynamics SL DVD into the DVD drive of the server where Microsoft Project Server is installed.


Note: The server where Microsoft Project Server is installed must have SQL Server workstation components, including OSQL.exe, installed on it, even if the Microsoft Project database is on a different server. If SQL Server workstation components are not installed, the scripts to update the Microsoft Project database cannot run.


b) If AutoPlay is not enabled, run Setup.exe in the root directory of the DVD by choosing Start | Run and browsing to the DVD drive. Select Setup.exe and click OK.

Figure 64: Microsoft Dynamics™ SL installation options window


3. Select Microsoft Project Connector. The Microsoft® Project Connector for Microsoft Dynamics™ SL installation options window appears.

Figure 65: Microsoft® Project Connector for Microsoft Dynamics™ SL installation options window

4. Select Microsoft Project Server components. The Microsoft Project Connector – Server Welcome window displays.

Figure 66: Welcome


5. Click Next. License Agreement displays, offering the option to accept or decline the end-user license agreement.

Figure 67: License Agreement

6. Carefully read the software license agreement. To print the agreement, click Print.

7. To agree to the terms of the license agreement and continue with the installation, select the I accept the terms of the license agreement option button, and then click Next.

If you select the I do not accept the terms of the license agreement option button, and then click Cancel, Exit Setup appears, prompting you to quit or resume installing. You can cancel or accept the license agreement terms and continue with the installation.


8. Microsoft Project Connector Setup Information displays.

Figure 68: Microsoft Project Connector Setup Information

9. Type the URL for Microsoft Project Web Access and click Next. Microsoft Project Server settings displays.

Figure 69: Microsoft Project Server settings


10. On the Microsoft Project Server Settings screen, do the following:

• In Microsoft Project Server Name, type the name of the database server that hosts the Microsoft Project Server database.

• In Microsoft Project Server Database Name, type the name of the Microsoft Project Server database (usually ProjectServer, sometimes with a four-digit number appended).

• In Project Server SQL User ID, type the login for the SQL Server administrative user (“sa”).

• In Project Server SQL User Password, type the password for the SQL Server administrative user.

• In IIS Virtual Root Directory, type the path to the folder where the database scripts and log files will be stored (such as …\Inetpub\wwwroot\PSA\).

11. Click Next. Since the number of files copied is small, InstallShield Wizard Complete appears almost immediately.


12. Click Finish. After Setup completes all operations, it exits automatically. Keep the DVD in the drive, however, as you will need to reference a file on the DVD when you proceed to step 3 on page 68.

13. Review the contents of the PA_Connect.txt and InitMSPProject.txt log files, which record information related to the installation. These files are located in the Temp variable directory.

To determine the Temp variable directory:

a) On your Windows desktop, right-click My Computer.

b) Click Properties.

c) Click the Advanced tab.

d) Click the Environment Variables button. The Environment Variables dialog box appears. The Temp variable directory path is listed in User variables for <your user name>.

e) Note the path, and then click Cancel.

If the installation was successful, the log files contain a series of digits followed by right angle brackets (1> 2> 3>, etc.). If errors occurred, the log files contain text describing the nature of the errors. Correct the errors and rerun the Microsoft Project Server components option of Setup.


14. If this is an upgrade installation, open Microsoft Project Connector Setup (PA.MSP.00) after you have installed the updated server extension and resubmit the Microsoft Dynamics SL connection information. Be sure to click Test Connection to verify that Microsoft Project Server can access Microsoft Dynamics SL.

Note: In obscure cases, the server name recorded in the PDS.wsdl file is “servername," rather than the name of the server where Microsoft Project Server is installed. If you are unable to establish or restore connectivity between the Microsoft Dynamics SL and Microsoft Project databases after completing all of the steps in this section, follow these steps:

a) Browse to ...\Program Files\Microsoft Office Project Server 2003\IIS Virtual Root\PDS.wsdl.

b) Right-click on the PDS.wsdl file, and then select Open With.

c) In Open With, select Notepad, and then click OK.

d) When the file opens in Notepad, scroll down until you see the following indented line: <soap:address location="http://servername/ProjectServer/PDS.wsdl"/>

e) Verify that the name of your server appears instead of “servername.”

f) If the PDS.wsdl file contains “servername," replace “servername” with the name of the server where Microsoft Project Server is installed.

g) Save and close the file.

Installing the PSA Accounting View to the Microsoft Project Enterprise Global Template The Microsoft Project Connector includes a new view that displays the Project Series Task ID, Revenue, and Other Expenses for integrated tasks. Installing the PSA Accounting view to your Microsoft Project Server environment entails modifying the enterprise global template. Be sure to back up the enterprise global template before you install the new view.

Note: You must have Microsoft Project Server administrator rights to open the enterprise global template in order to perform this procedure.


To install the PSA Accounting View to Microsoft Project Server:

1. Back up the enterprise global template by opening Microsoft Office Project Professional 2003, logging on to Microsoft Project Server, and selecting Tools | Enterprise Options | Backup Enterprise Global.

Figure 71: Backup Enterprise Global

The Save As dialog displays.

Figure 72: Enterprise Global Save As dialog

2. Maintain the location and file name as needed, then click Save.

3. Open Windows Explorer and browse to the Microsoft Dynamics SL DVD.

4. Open MSPPSAServer\program files\MSP_Server\, and then double-click PSAView.mpt to open the Microsoft Project template file.


5. Select Tools | Enterprise Options | Open Enterprise Global.

Figure 73: Open Enterprise Global

6. When both the enterprise global template and PSAView.mpt are open, select Tools | Organizer. Organizer displays.

Figure 74: Organizer, Views tab

7. Be sure that the drop-down lists at the bottom of the screen show PSAView and Checked-out Enterprise Global (it does not matter which is on the left and which is on the right).

8. In the PSAView area, select PSA Accounting View and click Copy >>. If the PSAView area is on the right, the Copy button will appear as << Copy.


PSA Accounting View appears in the Checked-out Enterprise Global area.

Figure 75: Organizer after adding the PSA Accounting View to the enterprise global template

9. Select the Tables tab.

10. In the PSAView area, highlight PSA Accounting Table and click Copy >>. PSA Accounting Table appears in the Checked-out Enterprise Global area.

Figure 76: Organizer, Tables tab

11. Click Close to close Organizer. 12. Close file PSAView.mpt.

13. Close the enterprise global template, clicking Yes to “Do you want to save changes to ‘Checked-out Enterprise Global?’”


14. To display the PSA Accounting View in Microsoft Office Project Professional, you must first close Microsoft Project, then re-open it, log on to Microsoft Project Server, and select View | PSA Accounting View.

Figure 77: Microsoft Project showing the PSA Accounting View

The PSA Accounting View adds columns for Project Series Task ID, Revenue, and Other Expenses to the Enterprise Gantt Chart. The Revenue and Other Expenses amounts originate in Microsoft Dynamics SL as actual transactions and update the Microsoft Project database in display-only mode (once saved, existing Project Accounting Task IDs are also display-only).


Each user can specify a default view for Microsoft Office Project Professional by opening Microsoft Project and selecting Tools | Options. On the View tab, select a view from the Default view list and click OK. To make a specific view the default view for all users, open the enterprise global template and select Tools | Options. On the View tab, select a view from the Default view list and click OK. Save and close the enterprise global template.

Figure 78: Selecting the PSA Accounting View as the default view

Setting Up the Connection Between the Microsoft Project and Microsoft Dynamics SL Databases The following instructions are intended for IT personnel who do not implement or configure the Microsoft Dynamics SL application environment. Following this procedure will provide the minimum configuration necessary to connect the Microsoft Dynamics SL and Microsoft Project databases and to test the connection from all workstations that will use the integration.

If you are responsible for both installing and implementing the integration, please read the full setup instructions in the section “Setting Up the Integration Between the Microsoft Dynamics SL and Microsoft Project Server Databases” in the Microsoft Project Connector Implementation and User Guide before proceeding.

1. If you are using SSL with Microsoft Project Server, browse to the following location:

… \Program Files\Microsoft Office Project Server 2003\IIS Virtual Root\PDS.wsdl.

2. Right-click on the PDS.wsdl file and select Open With.

3. Choose Select the program from a list, and then click OK.

4. In Open With, select Notepad, and then click OK.

5. When the file opens in Notepad, scroll down until you see the following indented line:

<soap:address location="http://servername/ProjectServer/PDS.wsdl"/>

6. Change “http” to “https” and verify that “servername” is the name of the server where Microsoft Project Server is installed.

7. Save and then close the file.

8. Start Microsoft Dynamics SL.


9. Click the Project button and select Project Controller. The Project Controller menu displays.

Figure 79: Project Controller menu


10. Select Project Controller Setup. Project Controller Setup (PA.SET.00) displays.

Figure 80: Project Controller Setup (PA.SET.00), General Information tab


11. Click Microsoft Project Connector Setup. Microsoft Project Connector Setup (PA.MSP.00) displays.

Figure 81: Microsoft Project Connector Setup (PA.MSP.00), General Parameters tab

12. Select the Activate Microsoft Project Connector check box.

13. Select the Microsoft Project Connection tab.

Figure 82: Microsoft Project Connector Setup (PA.MSP.00), Microsoft Project Connection tab


For more information about authentication methods, see “Setting Up Users for the Project Connector” on page 51.

14. In Server URL Name, type the URL of the server where Microsoft Project Server is installed.

15. If you select the Windows Authentication check box, users are authenticated and authorized without any added user intervention. If you do not select the Windows Authentication check box, Microsoft Project uses Project Server authentication, which involves prompting each user for credentials each time Microsoft Project is started. Selecting this check box disables Project Server User ID and Password.

16. Project Server User ID is enabled if Windows Authentication is not selected. Type the user ID that Microsoft Dynamics SL will use to log on to Microsoft Project.

Note: If you elect to use Project Server authentication, be aware that the user ID in Microsoft Project is case-sensitive. The user ID in this field must exactly match (in case sensitivity) the user ID in Microsoft Project. The user Administrator is a built-in account in Microsoft Project and the “A” must be capitalized if you choose to type it here. Furthermore, when new projects are initially created in a Microsoft Dynamics SL environment that uses Project Server authentication, the user specified in Project Server User ID must log on to Microsoft Project Server and publish each new project. Failure to do so results in the project being inaccessible to other users, including the project’s manager, until the designated user publishes it to Microsoft Project Server.

17. Password is enabled if Windows Authentication is not selected. Type the password for the Project Server User ID.

18. After typing the information for all fields on this tab, click Test Connection to test the connection to Microsoft Project Server. If the information supplied on this tab is correct, PC Message Number 1391, “Connection Successful,” appears.

19. Select the Microsoft Dynamics SL Connection tab.

Figure 83: Microsoft Project Connector Setup (PA.MSP.00), Microsoft Dynamics SL Connection tab

20. In Database Server Name, type the name of the server that hosts the Microsoft Dynamics SL databases.


21. In Application Database Name, type the name of the application database that will integrate with the Microsoft Project Server specified on the Microsoft Project Connection tab.

22. In System Database Name, type the name of the system database used by the application database specified in Application Database Name.

23. In SQL Server User ID, type the user ID that Microsoft Project will use to log on to the Microsoft Dynamics SL database. Since the purpose of the SQL Server login is to transmit information between the two server environments, be sure that the login is exactly the same as in Microsoft SQL Server and set the permissions for this user ID accordingly.

24. In Password, type the password for the SQL Server User ID.

25. After typing the information for all fields on this tab, click Test Connection to test the connection between the databases. If the information supplied on this tab is correct, PC Message Number 1391, “Connection Successful,” appears.

26. Click Save.

27. Once you have confirmed that connectivity between the Microsoft Dynamics SL and Project Server databases is functioning correctly from all client workstations that are set up to use the integration, you may need to clear the Activate Microsoft Project Connector check box in Microsoft Project Connector Setup (PA.MSP.00) until the implementation is complete. If you do not perform the implementation of the Microsoft Project Connector features when all client installations are complete, users will have access to the integration features before they are properly configured. If you choose to clear the Activate Microsoft Project Connector check box until all implementation tasks are complete, Microsoft Project users who have the PSA COM add-in installed on their workstation might receive an error message until you reactivate the integration.

Installing Microsoft Project Connector Components to the Microsoft Office Project Professional 2003 Client Workstation Each client workstation in a Microsoft Project Server 2003 environment must have certain additional files installed on its local hard disk in order to access and use the integration. Complete the client workstation setup procedures at each client workstation that you want to have access to the integration features.

Important: You must have Administrator rights on the computer due to the need to register components.


To install the integration components to Microsoft Office Project Professional 2003:

1. Insert the Microsoft Dynamics SL DVD into the DVD drive.


b) If AutoPlay is not enabled, run Setup.exe in the root directory of the DVD by choosing Start | Run and browsing to the DVD drive. Select Setup.exe and click OK.

Figure 84: Microsoft Dynamics™ SL installation options window


2. Select Microsoft Project Connector. The Microsoft® Project Connector for Microsoft Dynamics™ SL installation options window appears.

Figure 85: Microsoft® Project Connector for Microsoft Dynamics™ SL installation options window

3. Select Microsoft Project Professional components. If Setup detects a previous client add-in, Modify, repair, or remove the program appears. Select the Remove option button to remove the previous version of the client add-in and click Next. When prompted to confirm that you want to remove the selected application, click Yes. When Uninstall Complete appears, click Finish and restart Setup to install the new add-in.


4. Welcome appears, advising you to exit other Windows programs before continuing.

Figure 86: Welcome

5. Click Next. Software License Agreement displays, offering the option to accept or decline the end-user license agreement.

Figure 87: License Agreement


6. Carefully read the software license agreement. Click Yes. If you decline, another window appears advising you Microsoft Project Connector for Microsoft Dynamics SL Setup will stop operating.

7. Click Finish. After Microsoft Project Connector for Microsoft Dynamics SL Setup completes all operations, it exits automatically.



Adding the PSA COM Add-In to Microsoft Office Project Professional To assign valid Microsoft Dynamics SL project and task IDs to projects and tasks using Microsoft Project, you must first add the PSA COM add-in to the Microsoft Office Project Professional toolbar. In Microsoft Office Project Professional 2003:

1. Choose View | Toolbars | Customize.

Figure 89: Customizing the Microsoft Project toolbar

2. In Customize, click the Commands tab and highlight the Tools category.

Figure 90: Customize window


3. Scroll down the list of commands and select COM Add-Ins.

4. Drag the COM Add-Ins button to the toolbar.

Figure 91: Microsoft Project toolbar customized with COM Add-Ins button

5. Click Close to close Customize.

6. Click COM Add-Ins. COM Add-Ins displays.

Figure 92: COM Add-Ins

7. Click Add.

Important: The installation process copies PSAAddin.dll to …\WinNT (or Windows) \System32, making it accessible to all users of each workstation. Browse to the System32 folder and select the file from there.


8. Select PSAAddIn.dll and click OK.

Figure 93: Add Add-In

9. Make sure that the Microsoft Dynamics Integration check box is selected and click OK.

Figure 94: COM Add-Ins after adding Microsoft Dynamics Integration

If you see an error message immediately after adding the PSA add-in, the likely cause is that the connection to Microsoft Dynamics SL is not active.

You might also see a logon prompt. If the connection to Microsoft Dynamics SL is set up, you can log on the add-in by providing the appropriate credentials.

Figure 95: PSA Add-in Logon Prompt


10. Since the add-in loads when you start Microsoft Project, close Microsoft Office Project Professional, then reopen it. If the Integration toolbar does not appear automatically, add it to Microsoft Project by selecting View | Toolbars | Microsoft Dynamics Integration.

Figure 96: Adding the Microsoft Dynamics Integration toolbar


The Microsoft Dynamics Integration toolbar is small enough that you can place it on the same row as an existing toolbar.

Figure 97: The Microsoft Dynamics Integration toolbar

Note: Since the Integration toolbar writes data to the Microsoft Dynamics SL database from Microsoft Project, each user who has the COM add-in installed in Microsoft Office Project Professional must also be a Microsoft Dynamics SL user.


Setting Up Microsoft Dynamics SL on Workstations Each client workstation must have certain resources loaded on its local hard disk in order to access and use Microsoft Dynamics SL. Two client workstation setup options are available:

• Execute Microsoft Dynamics SL from a shared directory on the server

• Execute Microsoft Dynamics SL from the local client workstation (only for workstations that will not have network access to the applications)

You must complete one of the client workstation setup procedures at each client workstation where access to Microsoft Dynamics SL is required.

The Microsoft .NET Framework version 2.0 is a required part of the client installation. The Microsoft Dynamics SL client installation will install the software if it detects that.NET Framework is not present on the client computer. After the .NET Framework installation is finished, the Microsoft Dynamics SL client installation will continue.

Client Workstation Setup

Executing Microsoft Dynamics SL from a Shared Directory on the Server

To set up a workstation to execute Microsoft Dynamics SL from a shared server directory:

1. Log on as the local Administrator or as a member of the local Administrators group at each workstation where Microsoft Dynamics SL will be set up. Failure to do so will cause problems in the setup.


2. Map a network drive to the shared application folder on the server where the Microsoft Dynamics SL programs are installed. For example:

E:\<computer_name>\<share_name>

where:

<computer_name> is the computer name of the server.

<share_name> is the share name established for the directory above the Microsoft Dynamics SL directory on the server (for example, Microsoft_Dynamics_SL_Share).

Example: If the application files are in C:\Program Files\Microsoft Dynamics\SL\Applications, share the Applications folder, and then map a drive to it.


3. Run Setup.exe from the …\Wrkstn folder to start the client setup. Welcome appears, advising you to exit other Windows programs before continuing.

Figure 98: Welcome

4. Click Next. Choose Destination Location appears.


5. Click Next to accept the path that appears.


If the appropriate path does not appear, click Browse and navigate via the mapped network drive to the shared folder where the application files are located. Then click Next.

Note: If Setup detects an existing installation, it requires you to remove it before continuing. Click Yes to uninstall. If existing Microsoft Dynamics SL databases must be made compatible with release 7.0, see “Upgrading an Existing Installation” on page 97.

Start Copying Files appears, displaying the disk space required to complete the installation.



6. Click Next to start Setup.












Note:




13. After Setup copies all resources to the workstation’s hard disk and registers them where needed, InstallShield Wizard Complete appears.


14. Click Finish.

Running Microsoft Dynamics SL from the Local Client Workstation To install Microsoft Dynamics SL so that it can be used by a single user on a local drive, follow the installation steps in the “Installing Microsoft Dynamics SL” section on page 12.


Installing Crystal Reports on a Local Workstation Before installing Crystal Reports for Solomon version 10 on the workstation, it will be necessary to remove any previous versions of Crystal Reports.

To remove an earlier version of Crystal Reports before installing Crystal Reports version 10:

1. Remove Crystal Reports using Add/Remove Programs in the Windows Control Panel.

2. In Windows Explorer, delete all Crystal Reports program folders. A typical path is \Program Files\Crystal Reports.

3. Locate the following files in \Crystal\Utilities on the Microsoft Dynamics SL DVD:

uSCR5_16.exe uSCR6_32.exe



4. Open the self-extracting executable file appropriate for the version of Crystal Reports to be removed. For example, if the 32-bit version of Crystal Reports is installed, uSCR6_32.exe is the correct file to open.

5. Follow the instructions in the Install.txt file that is included in the self-extracting file.

6. Verify that Crystal Reports is completely removed from the server and workstation hard drives by searching in Windows Explorer for the following files:

CRW.net CRR*.exe

CRW32.net CRPE.dll

CRW.exe CRPE32.dll

CRW32.exe

Note: Cleanup of the registry keys might be needed. Contact your system administrator for assistance with this task.


To install Crystal Reports version 10 on a local workstation:

1. Close all running Windows applications.

2. Insert the Microsoft Dynamics SL DVD into the DVD drive.




3. Select Crystal Reports® in the installation options window. Crystal Reports Setup appears.

4. If no other version of Crystal Reports is installed, the Crystal Reports Welcome appears. If another version is found, follow the removal procedure on page 93.

5. Click Next. License Agreement appears.

6. Carefully read the software license agreement.

7. Click I accept the License Agreement.

8. Click Next. Select Installation Type appears.

9. Click Typical.

10. Verify the path specified in Destination Folder:

• If the default destination folder is correct, click Next to continue.

• If the default destination folder is not correct, click Browse to locate the correct folder or type in the desired location.

11. Click Next.

12. Follow the remaining prompts to finish installing Crystal Reports.

13. When Crystal Reports has been successfully installed appears, click Finish. The Crystal Reports installation is finished.

Crystal Enterprise — In Crystal Reports Setup, you may be asked if you want to install Crystal Enterprise. Crystal Enterprise is not included with Microsoft Dynamics SL and is not supported by Support Services.


When using Crystal Reports with Microsoft Dynamics SL, keep the following in mind:

• Microsoft Dynamics SL does not use Crystal Reports dictionaries.

• Crystal Reports supports Microsoft Dynamics SL user access control. Any user who is in Crystal Reports is counted as a Microsoft Dynamics SL seat license.

• To access Crystal Reports, you must be logged on to Microsoft Dynamics SL using a valid user ID and password.

• Crystal Reports service packs from Crystal Decisions are not compatible with Crystal Reports for Microsoft Dynamics SL. Microsoft provides these service packs.

Note: Due to changes in the standard reports, customized reports from earlier Microsoft Dynamics SL releases may not run without modification. Contact your Microsoft Certified Partner if your customized reports do not run.


Upgrading an Existing Installation 97

Upgrading an Existing Installation

Overview This section explains how to upgrade an existing Microsoft Dynamics SL installation.

• “Before You Install” on page 97 lists important tasks you will need to do before you install release 7.0. Included in this section are details on how to export customizations for safekeeping.

• “Removing an Existing Installation” on page 99 describes how to remove existing Microsoft Dynamics SL installations on servers and client workstations to prepare for installing.

• “Installing Microsoft Dynamics SL” on page 101 explains how to use Microsoft Dynamics SL Setup to install the software. These steps apply to both new and upgrade installations.

• “Updating Databases” on page 101 describes how to update existing Microsoft Dynamics SL databases.

• “Updating Client Workstations” on page 110 explains how to update Microsoft Dynamics SL client workstations to this release.

• “Installing Supporting Applications” on page 38 describes the procedure for installing applications included with Microsoft Dynamics SL 7.0. Note that, unless you have Crystal Reports 10 already installed, you must remove the previous version of Crystal Reports from the server and workstations in order to install Crystal Reports 10. This section includes the following topics:

– “Removing an Earlier Version of Crystal Reports” on page 47 describes how to remove the previous installation of Crystal Reports in order to install Crystal Reports version 10.

– “Installing Crystal Reports Version 10” on page 48 describes how to install Crystal Reports 10.

– “Updating Custom Crystal Reports” on page 115 describes how to update your existing Crystal reports from a previous version to work with Crystal Reports version 10.

• “Using Database Update after Completing the Database Maintenance Scenario” on page 109 explains how to update Microsoft Dynamics client workstations to this release.

• “Adding Modules” on page 116 provides you with the steps you will need if you want to add individual modules to your Microsoft Dynamics SL installation.

Be sure to grant access rights to enable users to access the added Microsoft Dynamics SL applications, screens, and reports. Contact your Microsoft Certified Partner to obtain a list of new features. Rights granted previously to screens and reports will remain intact. This step helps you set up rights to new screens.

Before You Install Create a backup copy of the server where your Microsoft Dynamics SL applications are stored, including all custom Crystal Reports so that they can be restored after you are finished installing release 7.0.

In addition, export all screen customizations and store the export file in a safe place before you begin the installation. See “Export Customizations” for more information.

Important: Microsoft Dynamics SL (formerly Microsoft Business Solutions—Solomon) release 4.10 or higher is required in order to update directly to release 7.0. If you currently use a release that is older than 4.10, contact your Microsoft Certified Partner to get information about upgrading your environment to release 4.10 so that you can install release 7.0.

To verify the Microsoft Dynamics SL release currently installed, see “Which Microsoft Dynamics SL edition should I install?” on page 6 of the Pre-Installation Checklist.


Export Customizations It is always a good practice to export your screen customizations before you upgrade to a new release of Microsoft Dynamics SL. This action is required before you upgrade to release 7.0. Before you remove your earlier Microsoft Dynamics SL installation, do the following:

• Use Customization Manager’s Export Customizations (91.500.00) to export all screen customizations (see the Customization Manager online help or user guide for more information). Export each customization to a separate export (.cst) file, and then save the export files for later use.

• In addition, if your installation includes Visual Basic for Applications (VBA), use the integrated development environment (VBA IDE) to export the customization source code.

1. Open the screen customization file in the VBA IDE.

2. Right-click on an item in the project tree (ThisScreen in the example below).

Figure 106: VBA IDE window

3. On the menu that appears, click Export File.

4. Export each item in the project tree to a separate file.

Note: You do not need to export the VTools_VBA item.

5. Make a backup of the files, and store it in a safe place.


Removing an Existing Installation Note: Be sure to perform a system backup before you follow these steps. In addition, remove the Microsoft Dynamics SL client from all workstations before removing it from the server. Also, if your Delta.mnu file has been customized, create a backup folder and place a copy of the file in it so that you can refer to it later when you are ready to customize the new menu system.

On the “Pre-Installation Checklist” on page 5, you were instructed to remove any existing 32-bit release of Microsoft Dynamics SL (release 4.x or later) from all client workstations and from the server where it is installed before you start your Microsoft Dynamics SL 7.0 installation. Otherwise, Microsoft Setup will require that you do so and will initiate the removal before starting the installation process.

If you missed those steps, you can perform them now.

Removing Workstation Components

To remove all Microsoft Dynamics SL client files from each workstation:

1. Close Microsoft Dynamics SL and all Windows programs.

2. Open the Windows Control Panel, and then double-click Add or Remove Programs.

3. On the list of currently installed programs, click the entry for the Microsoft Dynamics SL client that is currently installed on your system. The name of this entry depends upon the release that is installed. For example, the name of the entry for a 6.5 installation is Microsoft Business Solutions Solomon 6.5 Client.

4. Click Remove.

5. Click Yes to confirm that you want to completely remove the client and all of its components.

6. Click Yes if you are prompted to remove Visual Basic for Applications.

7. Click Yes if you are prompted to remove shared components, and then click Yes if you have prompted to confirm your response.

8. Click OK in response to the message that the client files were uninstalled successfully.

9. Click OK if you are prompted to restart your computer.

Removing Server Components Microsoft Dynamics SL server components include the program files, supporting product program files, and database components.

To remove Microsoft Dynamics SL from the server:


2. At the server where Microsoft Dynamics SL is installed, open the Windows Control Panel.

3. Double-click Add or Remove Programs.

4. If you installed the Microsoft Dynamics SL client, you must remove it before uninstalling the server components. See ”Removing Workstation Components” for instructions.

5. After the client components have been removed, select your Microsoft Dynamics SL installation from the list of currently installed programs, and then click Change/Remove. The InstallShield Wizard Welcome window appears.

6. Click Remove, and then click Next.

7. Since you already removed your earlier installation of the client, click OK to remove the program files.

8. If you are prompted to remove Visual Basic for Applications, click Yes.

9. If you are prompted to remove a shared file, click Yes To All.

10. When the uninstall process completes, click Finish.


11. View your file system to make sure the Solomon or Solomon IV folder (in the Program Files folder) was removed. If it still exists, delete it.

12. Restart your computer.


Installing Microsoft Dynamics SL The procedure for installing the release 7.0 components of Microsoft Dynamics SL is the same for upgrade installations as it is for new installations. See “Installing Microsoft Dynamics SL” on page 12 for instructions. When Microsoft Dynamics SL Setup completes, continue the upgrade process by following the instructions beginning with “Updating Databases” below.

Updating Databases Before updating databases for use with Microsoft Dynamics SL, make sure you first upgrade your version of Microsoft SQL Server to Microsoft SQL Server 2005 Service Pack 1 Standard or Enterprise Edition. To obtain your upgrade, contact your Microsoft Certified Partner.

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, and then 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 to verify that these changes are still in place after the update to release 7.0 is complete.

• The ScreenCategory and ScreenMenu records that define the menu for the EVERYONE user group are replaced during an upgrade. Any changes or additions that you have made to these records will be lost. After the EVERYONE user group records are removed, the remaining records will be upgraded to SLMenutItem records for use with the new menu system.

The Database Maintenance (98.290.00) utility can update databases based on two scenarios, 6.5x to 7.0 or 4.1x/4.2x/4.5x/5.x/6.x to 7.0.


To update Microsoft Dynamics SL databases:

1. Start SQL Server Services if they are stopped using one of the procedures described in “Pre-Installation Checklist” on page 5.

2. 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.




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.


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.

Figure 108: Database Maintenance (98.290.00), 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 the databases. The Authentication dialog box appears.



13. Select an authentication mode, and then click OK. If you selected SQL Server Authentication, go to step 15. If you selected Windows Authentication, SYSADMIN Windows User Name appears.


14. In Windows User Name, type the identifier of the Windows user who will be the Microsoft Dynamics SL administrator for the system database and all associated application databases. Type the information using the domain\username format, and then click OK.

Note: 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.



Figure 8: Security

16. Click Yes to confirm that SQL Server authentication is the authentication mode you want to use. SQL Master60SP Login appears if you have not yet created the Master60SP user. This will not happen if you have already installed a database for Microsoft Dynamics SL 6.0 Service Pack 1 or later on the computer that is running SQL Server.


Click No to return to the previous screen in order to select Windows authentication. The Authentication dialog box appears. Go to step 13 and repeat the steps to select Windows authentication and to set up and create the scenario databases.

Note: If you have already created the Master60SP user, Login appears. Proceed to step 20.











22. Click OK. When the update is finished, the 9829000 message box appears.

Figure 112: 9829000 message

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

23. Click OK.

24. Click Close.

25. 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.

26. Follow the instructions in “Using Database Update after Completing the Database Maintenance Scenario” on page 108 to continue the database update process.

27. Repeat this process for each remaining system database and respective application databases.


Prepare SQL Server 7.0 Databases to Run with SQL Server 2005 The Prepare SQL Server 7.0 Databases for running with SQL Server 2005 scenario is required to ensure that Microsoft Dynamics SL databases created in a SQL Server 7.0 environment are ready for use with Microsoft SQL Server 2005.

Before running a database update scenario, make sure that you have upgraded the computer that is running Microsoft SQL Server to Microsoft SQL Server 2005 Standard or Enterprise Edition with Service Pack 1 or later. See “Updating Databases” on page 101 for more information.

Note: Do not run the Prepare SQL Server 7.0 Databases for running with SQL Server 2005 scenario if you have not upgraded from SQL Server 7.0 to SQL Server 2005. If it is necessary for you to use this scenario, run it after you have upgraded the SQL Server 7.0 databases to SQL Server 2005 and after you have run the scenario to upgrade the databases to Microsoft Dynamics SL 7.0.

After you have upgraded the databases to SQL Server 2005 Service Pack 1 and to Microsoft Dynamics SL 7.0, prepare the databases.


2. Click the Update Databases tab.

3. In Update Scenarios, click Prepare SQL Server 7.0 Databases for running with SQL Server 2005.

4. Click Update Database.

This process takes a short time and allows Microsoft Dynamics SL to access the databases on a SQL Server 2005 database server.


Using Database Update after Completing the Database Maintenance Scenario After completing a database maintenance scenario (see “Updating Databases” on page 101), you must use Database Update (98.100.00) to populate the system database with current system data.

Note: 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.


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.


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.


Conversion Procedure for Order Management The conversion procedure outlined below is required if you are upgrading from a release earlier than Microsoft Dynamics SL 6.0 to any future release. It addresses new Order Management data fields that were implemented in the 6.0 release. These new fields were part of the back order visibility enhancement. If you do not perform the conversion procedure, existing open orders will be re-planned incorrectly, causing shipper creation to occur earlier than it should.

Notes:

• You only need to do this conversion once. It does not have to be done with each subsequent upgrade.

• If you do not perform the conversion before you run Process Manager (40.990.00), you will need to place the original sales orders on administrative hold and cancel the shippers that were created before following the steps below. After you release the sales orders from administrative hold, the shippers will create accurately, and the fields and SOPLAN table will populate correctly.

• The back order visibility quantities will not be accurate on open shippers that were created prior to the upgrade. The back order visibility quantities on a shipper are dependent upon snapshot information from the sales order at the time of shipper creation, so shippers that are created after the conversion will have accurate back order visibility quantities.

• Reports were modified to print the back order quantities. As a result, back order quantities for open shippers created prior to the upgrade will be inaccurate on the reports.

To run the conversion procedure:

1. Open OM Integrity Check (40.990.00). This process is used to populate quantity fields and Requested Pick Date for the sales order schedules.

2. Select the following check boxes:

• Check Sales Orders

• Verify Shipment Quantities on Sales Orders

• Correct Shipment Quantities on Sales Orders

• Rebuild Inventory Plan

3. Click Begin.

4. Exit the screen after the process completes.

5. Open Process Manager (40.400.00) and click Start. This process will

• Calculate the requested pick date for all open schedules on all open sales orders. This is required because, as part of the back order visibility enhancement, planning will use the requested pick date from the sales order schedule and will not calculate this date as it did previously.

• Calculate back order visibility quantities on open and closed lines for all open orders.

• Rebuild the inventory plan (SOPLAN).


Updating Client Workstations To update Microsoft Dynamics SL client workstations:

1. Log on as the local Administrator or as a member of the local Administrators group at each workstation that will be updated. This is required. Failure to do so will cause problems in the setup.


2. Map a network drive to the shared application folder on the server where the Microsoft Dynamics SL programs are installed. For example:

E:\<computer_name>\<share_name>

where:

<computer_name> is the computer name of the server.

<share_name> is the name of the shared folder above the Microsoft Dynamics SL directory on the server.

Example: If the software is installed in C:\Program Files\Microsoft Dynamics\SL\Applications, Applications is the shared directory. You would map to that shared directory.

3. To start the client setup, run Setup.exe from the …\Wrkstn folder on the server where Microsoft Dynamics SL is installed.

Welcome appears, advising you to exit other Windows programs before continuing.

Figure 113: Welcome


4. Click Next. Choose Destination Location appears.


5. Click Next to accept the path that appears.

If no path is shown, click Browse and navigate using the mapped network drive to the shared folder where the Microsoft Dynamics SL application files are located.

Note: If Setup detects an existing client installation, it requires you to remove it before continuing. Click Yes to uninstall. If existing databases must be made compatible with release 7.0, see “Upgrading an Existing Installation” on page 97.


Start Copying Files appears, displaying the disk space required to complete the installation.


6. Click Next to start Setup.













Note:



13. After all resources are copied to the workstation’s hard disk, InstallShield Wizard Complete appears.


14. Click Finish.


Updating Custom Crystal Reports Crystal Reports® for Solomon Version 10 is shipped with Microsoft Dynamics SL Release 7.0. Most of the standard reports for the application modules were created in this version of Crystal Reports.

To update custom Crystal Reports:

Open and save all existing custom reports.

This ensures that current customizations are incorporated into the reports. This also helps ensure the compatibility of the reports with the Crystal Reports 10 print engine used in Microsoft Dynamics SL.

Note: In most cases, opening and saving custom reports is sufficient for updating them to version 10. However, in certain cases it may be necessary to make minor report layout adjustments to your custom reports to ensure that the output is acceptable. For example, you may notice that a field value on a custom report is truncated. If you experience this problem, open the affected report in Crystal Reports and extend the length of the truncated fields.

Expect that you may need to adjust the layout of custom reports as necessary whenever the integrated version of Crystal Reports changes.


Adding Modules After you install Microsoft Dynamics SL, it is easy to add modules.

To install an additional module to the Microsoft Dynamics SL Program files on the server:



3. On the list of currently installed programs, click the entry for Microsoft Dynamics SL 7.0, and then click Change/Remove. The InstallShield Wizard Modify, repair, or remove the program window appears.

Figure 120: InstallShield Wizard – Modify, repair, or remove the program


4. Click Modify, and then click Next. Select Microsoft Dynamics SL Applications appears.

5. Select the modules you would like to install, and then click Next.

6. Continue with the installation steps. See “Installing Microsoft Dynamics SL” on page 101 if you need assistance.


Troubleshooting 119

Troubleshooting

Repairing a Microsoft Dynamics SL Installation It is possible to repair a Microsoft Dynamics SL installation. The repair will recopy the files that were previously installed. For example, if you install the General Ledger module, and then run the repair program, all of the General Ledger executable files and reports will be replaced with versions matching the ones from the installation DVD.

To repair all Microsoft Dynamics SL client files on a workstation:



3. Click the entry for the Microsoft Dynamics SL Client on the list of currently installed programs, and then click Change. The InstallShield Wizard Modify, repair, or remove the program window appears.

Figure 121: Modify, repair, or remove the Microsoft Dynamics SL Client

4. Click Repair, and then click Next to repair the installation.

To repair all Microsoft Dynamics SL program files on the server:




3. Click the entry for Microsoft Dynamics SL on the list of currently installed programs, and then click Change. The InstallShield Wizard Modify, repair, or remove the program window appears.

Figure 122: Modify, repair, or remove Microsoft Dynamics SL

4. Click Repair, and then click Next to repair the installation.

Troubleshooting 121

Restoring System Database Table Views Two occurrences can create the need to restore the system database table views:

• Dropping views in an application database

• Changing the name of the system database

Note: The following procedures must be performed by the Microsoft Dynamics SL system administrator.

To restore the system database table views:



2. In the Connect Server tab, type the Destination SQL Server Name.

3. 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 will be created.





6. In the System Database Name list, click your system database name.

7. In Databases, click the appropriate application databases.

8. Click Update Views to update the views in the selected application databases.

9. Click OK.

10. Click Close.

Troubleshooting 123

Technical Resources

Section Contents • Terminology Definitions — Key terms that are used in Microsoft Dynamics SL.

• Technology Tidbits — Foundational changes appearing in release 7.0.

• Backup and Restore Procedures — Processes used to back up and restore to databases of the same or different names.

• Registered Controls — Proper uninstall and re-install processes, as well as how to register a control manually.

• Solomon.ini — How the Solomon.ini file is used.

Terminology Definitions • View — A view is an alternate way of looking at data in one or more tables. Microsoft Dynamics SL

uses database views in many reports to facilitate the multi-company or inter-company implementation. To continue the company metaphor, we view the system database’s Company table.

• Index — An index is a set of pointers that are logically ordered by the values of a key. Indexes provide quick access to data and can enforce uniqueness on the rows in a table. Indexes are used everywhere in Microsoft Dynamics SL. They are foundational to the performance of a database structure.

• Stored Procedure — A stored procedure is a multi-statement compiled Transact-SQL query with control-of-flow language that can take parameters and allows user-declared variables, conditional execution, and other powerful programming features. Stored procedures are used by the software to perform tasks such as database navigation and possible values lookups.

• Proper Order of Rebuild — If a view is incorrect or dropped due to an error, the proper order of build is the correct way to recreate the view and the underlying components on which the view depends.

• Backup/Restore — Backup/restore is the process of making a physical backup copy of a database and subsequently restoring the database from the backup to the computer system. Backup/restore implements the standard Microsoft SQL Server Backup and Restore utility programs.

• Registered Controls — A registered control is an object with a visible interface used within Microsoft Dynamics SL. Control examples include text boxes on a screen, Swimapi.dll, and Customization Manager components. Here, the scope of registered controls is limited to installing, registering, and unregistering critical controls. It includes common issues that may cause conflict when you remove the software.

• Solomon.ini File — The Solomon.ini file is used by the applications to control user-specific and global preferences in the Microsoft Dynamics SL environment.

Technology Tidbits

Recommended Protocols for Microsoft SQL Server

• TCP/IP sockets is the recommended protocol for production environments. TCP/IP is the communication protocol used by the server and workstation and is also the standard Internet protocol. Sockets transport database calls across the TCP/IP protocol. The terms TCP/IP sockets and sockets are used interchangeably.

• Named pipes, a protocol alternative to TCP/IP sockets, was developed for local area networks. A part of memory is used by one process to pass information to another process so that the output


of one is the input of the other. The second process can be local (on the same computer as the first) or remote (on a networked computer).

Note: Use the SQL Server Configuration Manager to validate proper protocols on the workstation and the server. The protocols on both machines must match in order to establish a connection.

Company Record The central storage point for companies, the company record in the system database cross-references the application database(s) where a company’s financial data is stored. Since companies can have a one-to-one or a one-to-many relationship of company to application database, the Company table is the central cross-reference for all companies.

Preset companies exist within the demo databases included on the Microsoft Dynamics SL DVD. These databases are built from the \Microsoft Dynamics\SL\Applications\DB\demo folder, which contains these databases:

Company Application Database Name

0010 SLDemoApp10

0020 SLDemoApp10

0060 SLDemoApp60

0070 SLDemoApp60

0080 SLDemoApp60

0051 DemoStandardApp51

Since the system database’s company table stores the relationship of company to application database, backing up and restoring to a different database name invalidates the company records (backup and restore procedures are discussed later).

AcctXRef Record To facilitate cross-referencing accounts, subaccounts, and company information, the software uses a table called AcctXRef. This table is built when you first set up the chart of accounts or subaccounts and is rebuilt when you make and save changes in Chart of Accounts Maintenance (01.260.00) or Subaccount Maintenance (01.270.00).

Using SQL Server Optimization Microsoft Dynamics SL makes extensive use of views. A view is an alternate way of viewing records or multiple records in a single or multiple databases. When creating custom reports, it is good practice to implement views to facilitate reporting, advanced features, functionality, and performance.

Consider how views are used:

• Reports — Most of the critical reports are based on views. Therefore, if you need additional fields on a report, the modifications must be made in the view used by that report.

• Advanced features and functionality — Views are used as part of multi-company or inter-company implementations to facilitate viewing the system database’s company table. The company table is the single repository for company and database relationships.

• Performance — Views and stored procedures use Microsoft SQL Server Transact SQL (TSQL) to create performance-optimized processes that execute in the workspace on the computer that is running SQL Server. This saves considerable time when lengthy processes are executed. Processes can run from 10 to 100 times faster using this methodology.

Note: Should you need to recreate database views, certain activities must subsequently occur to complete the process. This is due to the nature of the company metaphor throughout the database. See “Appendix A: SQL Server Optimization Notes” on page 129 for more information.

Troubleshooting 125

Backup and Restore Procedures Regular database backups and periodic testing of the restore process is strongly recommended. Backing up databases and restoring them to their original name should not present problems and does not require special handling. To do this, use Microsoft SQL Server.

Backing up a database and restoring it to a different database name can cause problems if not handled properly. This results from the tracking of application databases by company table in the system database.

For example, suppose a company configuration looks like this:

Company Original Application Database Name New Application Database Name

0010 SLDemoApp10 NEWAPPDB

0020 SLDemoApp10 NEWAPPDB

0060 SLDemoApp60

0070 SLDemoApp60

0080 SLDemoApp60

0051 DemoStandardApp51

If restored to a different database name, company 0010, stored in the system database, is still pointing to SLDemoApp10, not the new database name. To correct this, issue the following SQL statement in SQL Server Management Studio against the system database:

Update company set databaseName = 'NEWAPPDB' where company = '0010' or where company = '0020'

Problems result due to the views within that database now pointing to different database names. This type of processing happens in the following business-use cases:

• Taking a snapshot of a database to test with or report from

• Setting up a database to deliver to the customer

• Setting up a database to develop on using customer data for testing

Use the following recommended procedure to back up and restore a database from one name to another:

1. Back up the original application and system databases (for example, ORIGINALAPPDB and ORIGINALSYSDB) to a backup device.

2. Restore the databases to new names (for example, NEWAPPDB and NEWSYSDB).

3. In SQL Server Management Studio, choose the new system database (NEWSYSDB) from the DB list.

4. Issue the following SQL statements in NEWSYSDB to update the Company and Domain records to reference the new application database (NEWAPPDB):

Update Company set DatabaseName = 'NEWAPPDB' where CpnyID = 'YOURCOMPANYID'

Update Domain set DatabaseName = 'NEWAPPDB' where DatabaseName = 'OLDAPPDB'

Note: Make sure that the correct database is selected from the SQL Server Management Studio DB list before executing these statements.


If you are restoring to a different computer, follow the procedure below to run the Synchronize All Ownership & Security update scenario in Database Maintenance (98.290.00) and rebuild the database views:




3. 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 will be created.


Troubleshooting 127



6. In Update Scenarios, click Synchronize All Ownership & Security. Because this scenario processes all system and application databases on the server to which you are connected, it is not necessary to select system or application databases.

7. Click Update Database. This process will update each system database domain table with the correct server name and update SQL Server logins and permissions for the Microsoft Dynamics SL databases.

8. After the process is complete, click OK.

9. In the System Database Name list, click your system database name.

10. In Databases, click the appropriate application databases.

11. Click Update Views.

12. Click OK.

13. Click Close.

Registered Controls The software’s 32-bit architecture introduced the use of registered controls. These controls can range from add-on product controls that facilitate data input to the Microsoft Dynamics SL kernel file, Swimapi.dll. Registered controls are installed and registered in the workstation’s Registry database.

The Setup program automatically installs and registers the necessary components. When Microsoft Dynamics SL is installed on a server, the following components are installed:

• Program files

• Client control components required to run the software

You must remove any existing Microsoft Dynamics SL client installation before upgrading your software. If you do not, the new software may not install correctly.

You must remove all client workstation components before removing the server components. If you do not, the new client components will not uninstall correctly.

Improperly removing an earlier release of Microsoft Dynamics SL can cause unusual program behavior and unexpected results. The recommended procedure for removing an existing installation before


installing new software is described in “Removing Workstation Components” and “Removing Server Components” on page 99.

Solomon.ini Microsoft Dynamics SL uses the Solomon.ini file to save workstation-specific information, such as the last database that was logged on to, printer preferences, and other settings.

The Solomon.ini file is divided into sections indicated by double brackets [ ]. Each section performs its own characteristic functions. See Appendix A in the System Manager user guide for more information on the Solomon.ini settings. For example, the [Company] section stores local company login information.

Under each section are several settings that control the workstation’s options.

[Company] — Company section

CompanyID=0010 — CompanyID setting

UserID=SYSADMlN — UserID setting

The Solomon.ini file is specific to the local workstation and stored in \Windows (or \Winnt) folder. If a setting or section is not found in the Solomon.ini file, the program looks in alternate locations. The behavior occurs in the following order:

1. After executing MSDynamicsSL.exe, it looks for \Windows\Solomon.ini on the local client workstation.

2. If the Solomon.ini files does not exist, the program creates it with just the basic sections needed. These sections are [System32 Database] and [Company].

3. For sections MSDynamicsSL.exe does not find locally, it looks in the Solomon.ini file in the same tree structure from which MSDynamicsSL.exe was called on the server.

4. If a setting is not found in the local Solomon.ini file, it is obtained from the server’s Solomon.ini file.

A section and settings in the local \Windows\Solomon.ini overrides the same section and detail lines in the shared Solomon.ini file on the server. If a setting is found in the local Solomon.ini file, it overrides the settings in the server’s file.

Appendices 129

Appendices

Appendix A: SQL Server Optimization Notes This Appendix presents information on installing and setting up Microsoft SQL Server to operate with Microsoft Dynamics SL.

Supported Microsoft SQL Server Versions This Microsoft Dynamics SL release supports Microsoft SQL Server 2005 Service Pack 1 Standard or Enterprise Edition. Microsoft SQL Server must be purchased separately.

Microsoft SQL Server 2005 For an application user, the interface to Microsoft Dynamics SL remains unchanged. The underlying Microsoft SQL Server 2005 Service Pack 1 database is optimized for performance and usability.

Microsoft SQL Server 2005 must be installed to run in SQL Server and Windows authentication mode. This setting can be made during or after you install SQL Server.

To set SQL Server and Windows authentication mode after SQL Server installation:

1. Go to All Programs | Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2. Connect to the database server.

3. In the Object Explorer pane on the left side of the window, right-click the server where the Microsoft Dynamics SL application and system databases are maintained.


4. Click Properties. Server Properties appears.

Figure 127: Server Properties

5. Click Security.

6. Under Server authentication, click SQL Server and Windows Authentication mode.

7. Click OK, and close SQL Server Management Studio.

To set dynamic and reserve memory:

1. Go to All Programs | Microsoft SQL Server 2005, and then click SQL Server Management Studio.

2. In the Object Explorer pane on the left side of the window, right-click the server where the Microsoft Dynamics SL application and system databases are maintained.

Appendices 131

3. Click Properties. Server Properties appears.

Figure 128: Server Properties

4. Click Memory.

5. The default setting Minimum server memory (in MB) to zero MB. Do not change this setting.

6. Set Maximum server memory (in MB) based on the following guidelines:

Server Memory SQL Server Memory

128 MB 100 MB

256 MB 205 MB

512 MB 410 MB

1 GB 820 MB

1.5 GB 1230 MB

2 GB 1640 MB

7. Click OK. The following message window appears:

Figure 129: SQL Server service message window

8. Ask all SQL Server users to log out so that SQL Server Services can be stopped and restarted safely.

9. Click Yes. This stops and restarts the SQL Server Services.

10. Close SQL Server Management Studio.


Appendix B: Windows Vista Support The topics that follow discuss the impact of Microsoft Windows Vista™ on Microsoft Dynamics SL.

Control Panel Change In Windows Vista, use Programs and Features to view information about Microsoft Dynamics SL and other installed programs, or to install or uninstall a program. This control panel item takes the place of Add or Remove Programs. For assistance installing or uninstalling programs in Windows Vista, see “Windows Vista Help: Troubleshoot installing or uninstalling programs.”

Using Windows Vista as a Client Windows Vista is compatible with Microsoft Dynamics SL installed on network client and standalone computers. Windows Vista is not recommended for use on a server on which Microsoft Dynamics SL is installed.

User Account Control User Account Control (UAC) is a security feature provided by Windows Vista that changes the way applications work with the operating system. A protection level is implemented to help eliminate access by malicious users and programs. For a complete review of this feature, see the Microsoft TechNet discussion, “User Account Control.”

Changes are required when you use this security feature with Microsoft Dynamics SL. The following topics explain how to properly set up a user’s environments to adhere to UAC requirements.

Note: UAC is enabled automatically in Windows Vista installations.

Locating Solomon.ini and Other Profiles In earlier Windows releases, profiles (.ini files) were stored in the Windows folder. However, in Windows Vista, UAC does not allow write access to the Windows folder outside of the installation process. Windows Vista overrides any non-installation access to the Windows folder by placing .ini files in the user’s local application data directory. On a computer on which Windows Vista is installed, the customizable Solomon.ini file is placed in \Users\<user name>\AppData\Local\Microsoft Dynamics SL\.

Making Required Message File Location Changes To generate a message file (Messages.csv) using Database Update (98.100.00) with the UAC feature active, you must move the message file location. Do this by editing the Solomon.ini file (see the “[Read Directory] Section” topic in Appendix A of the System Manager online help or user guide). For example:

[Read Directory]

Message File= C:\Users\Public\Documents\Microsoft Dynamics SL\.csv

After you have established the location of the Messages.csv file, copy Messages.csv from the Microsoft Dynamics SL program folder to the newly designated location. For the example below, the file would be copied from C:\Program Files\Microsoft Dynamics\SL\Applications\Messages.csv to C:\Users\Public\Documents\Microsoft Dynamics SL\Messages.csv.

http://g.msn.com/9SE/1?http://windowshelp.microsoft.com/Windows/en-US/Help/95d4ed9a-1d7d-4b62-84e0-649fc98069f51033.mspx&&DI=6066&IG=d3adbafbb87c44c0b5178fd34b35b153&POS=3&CM=WPU&CE=3&CS=AWP&SR=3

http://technet.microsoft.com/en-us/windowsvista/aa905108.aspx

Appendices 133

Event Log Location Changes Required

If you are using Windows Vista and UAC is active, you must move the file location for individual users’ event logs. Do this by editing the Solomon.ini file (see the “[Event Log] Section” topic in Appendix A of the System Manager online help or user guide). In the following example, the Public folder allows several users to share the same file location:

[Event Log]

Directory=C:\Users\Public\Documents\Microsoft Dynamics SL

The Microsoft Dynamics SL event logs are written to the EventLog folder under the Microsoft Dynamics SL program folder by default. As a result of UAC’s virtualization, the new event log location is \Users\<user name>\AppData\Local\VirtualStore\Program Files\Microsoft Dynamics SL\EventLog. This location is not acceptable for event log viewing.

Selecting Application File Locations With UAC active, Windows Vista prevents write access to many folders, such as the program file and Windows system areas. It moves affected files to file system virtualization locations. When you select a location for file output, be sure to choose a folder that is user accessible. Place files for output in a user’s profile folders or shared public folder areas.

Example:

\Users\<user name>\Documents

\Users\Public\Documents

Some of the applications where directory choices must be made are:

• System Manager Transaction Import (98.500.00), Control Macro Generator (98.510.00), and Export Customizations (91.500.00)

• General Ledger Generate Consolidation (01.500.00)

• Application Server


Appendix C: Getting Support Various support plans are available that provide the exact product support you need for your Microsoft Dynamics SL installation:

• Local support through your Microsoft Certified Partner

• Support by mail from Support Services

• Electronic Microsoft Support access (fax, e-mail, Web-based)

• Telephone support, including priority telephone support plans

• CustomerSource on the Web at www.microsoft.com/dynamics/CustomerSource

• Visit www.microsoft.com/dynamics/support for the latest details on these professional support services

Important Phone Numbers and Internet Addresses

Microsoft Business Solutions 800-456-0025 U.S. and Canada

701-281-6500 Worldwide

Fax 425-936-7329 include e-mail alias of addressee

Microsoft Support Guaranteed and Premium Support clients only

Via phone 888-477-7877

Via the Internet www.microsoft.com/dynamics

Training/Seminars Phone — 800-476-5666

Fax — 425-936-7329 include ATTN: Microsoft Business Solutions University, [email protected]

Product Registration Phone — 800-476-5666

Fax — 425-936-7329

To view your software registration information, go to the CustomerSource Product and Service Summary Web page. To submit an order inquiry or request information about your account, go to the CustomerSource New Service Request Web page.

http://www.microsoft.com/dynamics/customersource.mspx

http://www.microsoft.com/dynamics/support/default.mspx

http://www.microsoft.com/dynamics/default.mspx

mailto:%[email protected]

https://mbs.microsoft.com/customersourceapp/myprofile/product_service_summary.aspx

https://mbs.microsoft.com/support/createincident.aspx

Index 135

Index

A AcctXRef record 124 Adding PSA COM add-in to Microsoft Office

Project Professional 82

B Backup procedures 125

C Client workstations, updating 110 Company record 124 Computer name 5 Creating

databases 23 Crystal Reports 47

installing 47 installing on local workstation 93 updating 115

Customized reports, updating 115

D Database

creating 23 demo 7 preparing application database 35 preparing the system database 35 updating 101

Database Update after following database maintenance scenario 108

Demo database 7 DVD, installing from 12

E Edition

determining which is installed 6 Professional 6 Standard 6

Empty application database, preparing 37 Empty system database, preparing 37 Existing installation

removing 99 upgrading 97

I Installing

Crystal Reports 47

Crystal Reports on local workstation 93 integration components to Microsoft Office Project Professional 2003 client workstation 77 Microsoft Dynamics SL from DVD 12 Microsoft SQL Server 22 new Microsoft Dynamics SL installations 11 preparing for 3 Project Connector 61 PSA Accounting View to Microsoft Project Server 2003 67 supporting products 38 updating an existing installation 97 Web Order Starter Site 38

K Key terms 123

M Microsoft Dynamics SL Support 134 Microsoft Office Project Professional

Adding PSA COM add-in 82 Microsoft SL SDK 8 Microsoft SQL Server

2000 7 7.0, preparing databasesto run with SQL Server 2000 107 installing 22 optimization notes 129 optimizing 124 recommended protocols 123 supported versions 129 version 200 0 129

Microsoft Support phone numbers 134 Web site URL 134

O Optimizing Microsoft SQL Server 124 Options, installation setup 10

P Pre-installation checklist 5 Preparing

demo application database 35 demo system database 35 empty application database 37 empty system database 37 pre-installation checklist 5


SQL Server 7.0 databases for running with SQL Server 2000 107

Procedures backup and restore 125

Project Connector 51 installing 61 setting up users 51

Protocols for Microsoft SQL Server 123 PSA Accounting View, installation 67 PSA COM, adding add-in to Microsoft Office

Project Professional 82

R Record

AcctXRef 124 Company 124

Registered controls 127 Removing

existing installation 99 Restoring

database view 121 procedures 125

S Server components, uninstalling 99 Setting up

client workstations 87 connection between Microsoft Project and Microsoft Dynamics SL databases 72 Microsoft Dynamics SL on a single-user workstation 92 Microsoft Dynamics SL options 10 users 51 Web Order 46

Solomon.ini 128 Starting SQL Services 8 Supported Microsoft SQL Server

versions 129 System database

preparing 37 preparing demo 35

T Technical resources

backup and restore 125 foundational changes 123 terminology 123

Troubleshooting 121 restoring a database view 121

U Uninstall

workstation components 127 Uninstalling

server components 99 Update prerequisites 97 Updating

client workstations 110 customized reports 115 databases 101 existing applications 97

User setup 51 Using

Database Update after database maintenance scenario 108

W Web Order

module setup 46 Starter Site requirements 38

Web Order Starter Site installing 38 system information 38

Workstation installing Microsoft Dynamics SL for a single user 92 setting up the Microsoft Dynamics SL client 87, 92 uninstalling components 127