Вы находитесь на странице: 1из 120

Installation Guide

Release 2011

Copyright 2011 Microsoft Corporation. All rights reserved. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes only. Trademarks Microsoft, Microsoft Dynamics, FRx, Outlook, SharePoint, Visual Basic, Visual Studio, Windows, and Windows Server are trademarks of the Microsoft group of companies. BIO and BIO Vue are trademarks or registered trademarks of NexVue Analytics Corporation in the United States and/or other countries. All other trademarks are property of their respective owners. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. Sample Code 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 This documentation is furnished as-is for informational use only and is subject to change without notice. Microsoft Corporation assumes no responsibility or liability for any errors or inaccuracies that may appear in this documentation. 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 2011

Contents

iii

Contents
Introduction Installation Preparation 1 3
Audience .......................................................................................................................................... 1

Overview .......................................................................................................................................... 3 What You Must Know about User Account Control ......................................................... 3 Summary of Tasks for New and Existing Installations .................................................... 3 Preinstallation Checklist ................................................................................................................. 6 Installation Options ....................................................................................................................... 11

Guide for New Installations

13

Overview ........................................................................................................................................ 13 Installing Microsoft Dynamics SL ................................................................................................. 14 Changes Needed for User Account Control ................................................................................. 23 Microsoft SQL Server Installation ................................................................................................. 25 Creating Databases ...................................................................................................................... 26 Creating an Empty Database ......................................................................................... 29 Creating a Demo Database ............................................................................................ 34 Creating an Additional Empty Application Database .................................................... 38 Logging On....................................................................................................................... 39 Preparing the Demo System and Application Databases............................................. 40 Preparing the Empty System and Application Databases ............................................ 40 Installing Supporting Applications ................................................................................................ 42 Crystal Reports ................................................................................................................ 42 Microsoft Dynamics SL Provider for Management Reporter ERP ................................ 51 Project Connector 2011 for Microsoft Project 2010 .................................................. 52 Microsoft Dynamics SL Users Guides ........................................................................... 53 Microsoft Dynamics SL SharePoint Web Service .......................................................... 58 Microsoft Dynamics SL Web Services ........................................................................... 61 Microsoft.Dynamics.SL.OutlookAddin ............................................................................ 62 .NET Framework 3.5 Service Pack 1 (SP1) ................................................................... 64 Setting Up Microsoft Dynamics SL on Workstations ................................................................... 65 Running Microsoft Dynamics SL from a Shared Directory on the Server .................... 65 Running Microsoft Dynamics SL from the Local Client Workstation ........................... 68

Upgrading an Existing Installation

69

Overview ........................................................................................................................................ 69 Before You Install .......................................................................................................................... 70 Export Customizations .................................................................................................... 70 Removing an Existing Installation ................................................................................................ 71 Removing Workstation Computer Components ............................................................ 71 Removing Server Components....................................................................................... 71 Removing Doc Share Web Service................................................................................. 72 Installing Microsoft Dynamics SL ................................................................................................. 73 Updating Databases ..................................................................................................................... 74 Prepare SQL Server 7.0 Databases to Run With The Latest Release ......................... 81 Using Database Update after Completing the Database Maintenance Scenario ....... 82 Conversion Procedure for Order Management ............................................................. 83 Updating Client Workstations ....................................................................................................... 84 Updating Custom Crystal Reports ................................................................................................ 88 Updating Microsoft Dynamics SL Doc Share Web Service ......................................................... 89 Adding Modules ............................................................................................................................. 90

iv

Installation Guide

Troubleshooting

93

Repairing a Microsoft Dynamics SL Installation .......................................................................... 93 Restoring System Database Table Views ..................................................................................... 95 Technical Resources ..................................................................................................................... 97 Section Contents ............................................................................................................. 97 Terminology Definitions .................................................................................................. 97 Technology Tidbits........................................................................................................... 97 Backup and Restore Procedures ................................................................................... 98 Solomon.ini ....................................................................................................................101

Appendixes

103

Appendix A: SQL Server Optimization Notes ..............................................................................103 Supported Microsoft SQL Server Versions ..................................................................103 Microsoft SQL Server 2008 ..........................................................................................103 Appendix B: Changing the Database Authentication Mode ......................................................106 Considering whether to change the database authentication mode .........................106 To change the database authentication mode later ...................................................106 Appendix C: Creating SQL Server Users and Logins ..................................................................111 Appendix D: Getting Support ......................................................................................................113 Important Telephone Numbers and Internet Addresses ............................................113

Index

115

Introduction

Introduction
This guide provides instructions for installing Microsoft Dynamics SL in the following environments: Microsoft Windows Vista Service Pack 1 or later versions Microsoft Windows 7 or later versions Windows Server 2008 or Windows Server 2008 R2 or later versions Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2, Standard or Enterprise edition

Note: See the Microsoft Dynamics SL 2011 System Requirements Guide that is available for download from the CustomerSource website or the PartnerSource website for the latest operating system versions and service packs supported. You can run Microsoft Dynamics SL 32-bit applications by using Windows 64-bit emulation (WoW64) on the 64-bit version of a supported operating system. When you install the Microsoft Dynamics SL client in a 64-bit environment, the path of the files is \Program files (x86)\Common Files\Microsoft Shared\DynamicsSL and \%Windir%\syswow64. The server is installed in \Program Files (x86)\Microsoft Dynamics\SL\Applications. All Visual Basic Tools-developed applications must be compiled to target the x86 architecture. If you plan to use Terminal Services for Windows Server 2008 to provide access to Microsoft Dynamics SL, you must install the Microsoft Dynamics SL client on the terminal server (minimum requirement). For maximum performance, we recommend that you do a full installation. Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010 is required if you plan to use Doc Share to post customer, vendor, or project documents on a SharePoint site. See the System Manager Help or users guide for information about Doc Share. Installation Preparation This section provides an overview of preinstallation and upgrade processes and a preinstallation checklist to help you address tasks that you must perform before you begin installation. This section also describes the options that you see on the installation options window. Guide for New Installations This section provides steps to help those who currently do not have Microsoft Dynamics SL installed. Upgrading 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. Appendixes This section provides additional information about Microsoft SQL Server optimization and other information interesting to some readers.

The following sections are included:

Audience
We designed this installation guide for anyone from novice software installers to veterans of the process. It includes checklists and other aids to help make your installation a successful experience

2 .

Installation Guide

Installation Preparation

Installation Preparation
This section will help you prepare for a Microsoft Dynamics SL installation. The section includes the following: Overview Read this section for a summary of the installation process and related setup tasks. Preinstallation Checklist You must perform many of the tasks on this list before you begin your installation. Installation Options This section describes what you see on the installation options window.

Overview
When it can, 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 continue efficiently.

What You Must Know about User Account Control


User Account Control (UAC) is a security feature that is included with Windows. UAC changes the way applications work with the operating system. A protection level is implemented to help eliminate access by malicious users and programs. UAC is enabled automatically. The Microsoft Dynamics SL installation process is not affected by UAC. However, setup changes are required when you use this security feature with Microsoft Dynamics SL. See Changes Needed for User Account Control on page 23 for topics that explain how to set up a users environment to follow UAC requirements. For more information about this feature, see the Microsoft TechNet discussion, User Account Control.

Summary of Tasks for New and Existing Installations


First-time installation Perform the tasks on the Preinstallation Checklist. Some are optional, whereas other tasks are required. Perform a system backup of the server on which you will install Microsoft Dynamics SL. Perform a system backup of the database server. Install Microsoft Dynamics SL on the server that you have selected to hold the program files. If you do not have Microsoft SQL Server and the required service packs already installed, install them on the database server. See Introduction on page 1 to see the list of supported SQL Server versions. Create databases and prepare them for use by loading them with system data. Install Crystal Reports 2008 on any workstation computer where it will be used to create new reports or revise existing reports. Install the Microsoft Project 2010 Connector for Microsoft Dynamics SL if you intend to use it Upgrading an existing installation Perform the tasks on the Preinstallation Checklist. Some are optional, whereas other tasks are required. Export all screen customizations from the earlier version. Perform a system backup of the server that holds the Microsoft Dynamics SL applications. If your installation includes a customized Delta.mnu file, save a copy so that you can refer to it after the installation is completed. Perform a database backup of the system and application databases.

Remove all existing Microsoft Dynamics SL clients from workstation computers. Remove the existing Microsoft Dynamics SL installation from the server where it currently resides. Install Microsoft Dynamics SL on the server that you have selected to hold the program files.

Installation Guide
First-time installation Upgrading an existing installation

Install the server components for Feature Pack 1 of Management Reporter for Microsoft Dynamics SL 2011 from the Management Reporter installation package. Installation documentation is included in the installation package. Next, install the Microsoft Dynamics SL Provider for Management Reporter from the Microsoft Dynamics SL installation package. Installation documentation is included in the Microsoft Dynamics SL Provider for Management Reporter users guide (DynamicsSLDataProvider.pdf). Last, install the client components for Feature Pack 1 of Management Reporter for Microsoft Dynamics SL 2011 from the Management Reporter installation package.

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

Install Microsoft .NET Framework 3.5 Service Pack 1. After the installation is complete, you must restart the computer before you install the Microsoft Dynamics SL client on workstation computers. To install the .NET Framework, see .NET Framework 3.5 Service Pack 1 (SP1) on page 64.

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

Install the Microsoft Dynamics SL client on workstation computers.

If a release of Crystal Reports that is earlier than version 2008 is installed, remove it from the server and workstation computers that will access Microsoft Dynamics SL. Install Crystal Reports 2008 on workstation computers where it will be used to create new reports or revise existing reports.

Install the Microsoft Dynamics SL SharePoint Web Service if you want to use the following features in Microsoft Dynamics SL:

Doc Share to a SharePoint site Printing to a SharePoint site Upload Attachments to a SharePoint site
Install Microsoft Project 2010 Connector for Microsoft Dynamics SL if you intend to use it.

Installation Preparation
First-time installation Upgrading an existing installation

Install the server components for Feature Pack 1 of Management Reporter for Microsoft Dynamics SL 2011 from the Management Reporter installation package. Installation documentation is included in the installation package. Next, install the Microsoft Dynamics SL Provider for Management Reporter from the Microsoft Dynamics SL installation package. Installation documentation is included in the Microsoft Dynamics SL Provider for Management Reporter users guide (DynamicsSLDataProvider.pdf). Last, install the client components for Feature Pack 1 of Management Reporter for Microsoft Dynamics SL 2011 from the Management Reporter installation package. If you are moving from Microsoft FRx 6.7 to Microsoft Dynamics Management Reporter, use the Management Reporter Migration Wizard to migrate your reports. For detailed steps, download Migrating to Management Reporter for Microsoft Dynamics ERP from the Microsoft Dynamics File Exchange System. Note: If you will not be upgrading to Management Reporter for Microsoft Dynamics SL 2011 when you upgrade to Microsoft Dynamics SL 2011, you must apply Microsoft FRx 6.7 Service Pack 12 (SP12). Installation documentation is included in the Microsoft FRx installation package.

Install Microsoft .NET Framework 3.5 Service Pack 1. After the installation is complete, you must restart the computer before you install the Microsoft Dynamics SL client on workstation computers. To install the .NET Framework, see .NET Framework 3.5 Service Pack 1 (SP1) on page 64.

Install the Microsoft Dynamics SL client on workstation computers. If you have the Microsoft Dynamics SL Doc Share Web Service installed, uninstall that from the Windows SharePoint Services Server, and then install the Microsoft Dynamics SL SharePoint Web Service. Install the Microsoft Dynamics SL SharePoint Web Service if you want to use the following features in Microsoft Dynamics SL:

Doc Share to a SharePoint site Printing to a SharePoint site Upload Attachments to a SharePoint site

Installation Guide

Preinstallation Checklist
The following checklist is provided to help you prepare for a Microsoft Dynamics SL installation and to give you a record to refer to during future upgrade installations. Note: Make sure that you determine whether your system meets the minimum configuration needs before you install this release. The Microsoft Dynamics SL 2011 System Requirements Guide that is available for download from the CustomerSource website or the PartnerSource website, provides information to help you with this task. The input of other people during the installation process might be helpful and, in some cases, necessary. For example, you might have to talk to your database administrator when questions arise about how to store your data. Make sure that the resources that you need are available during preinstallation planning and during the installation or upgrade process. If you plan to use Microsoft Office and Microsoft Dynamics SL on the same workstation, install Microsoft Office first, followed by Microsoft Dynamics SL. Microsoft Dynamics SL screens work with email through Microsoft Visual Studio Tools for Office, (VSTO). VSTO enables Microsoft Dynamics SL screens to communicate with Microsoft Office Outlook through an add-in. This add-in is named Microsoft.Dynamics.SL.OutlookAddin and is included in the Microsoft Dynamics SL client installation. When you run a screen that works with email for the first time, Microsoft Dynamics SL will try to install the add-in. Depending on your computers configuration, you may see a window asking for permission to install the add-in. If Outlook is running while the add-in is installed, the computer must restart to finish installing the add-in. You can install the add-in before you need it for the first time. To install the add-in manually see Microsoft.Dynamics.SL.OutlookAddin on page 62. Note: The add-in must be installed one time by each user who runs a screen that works with email. Upon uninstall of the Microsoft Dynamics SL client, we recommend that the add-in also be uninstalled by each user who installed it. To uninstall the add-in see Microsoft.Dynamics.SL.OutlookAddin on page 62. Microsoft .NET Framework 3.5 Service Pack 1 is a prerequisite for the Microsoft Dynamics SL client installation. You can install the .NET Framework from a Microsoft Dynamics SL installation package. After the .NET Framework installation is complete, you must restart the computer before you begin the client installation. To install the .NET Framework, see .NET Framework 3.5 Service Pack 1 (SP1) on page 64.

To complete the preinstallation checklist:

Contact a 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 that follows, 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. On the server where you plan to install Microsoft Dynamics SL, right-click My Computer, and then click Properties. 2. The Full Computer Name is located on the Computer Name tab of System Properties. Complete these steps on each server where you plan to install Microsoft Dynamics SL. _____________________________________________

Installation Preparation

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

Locate the Microsoft Dynamics SL Release 2011 installation package. What does the installation package contain? The Microsoft Dynamics SL installation package contains the system and application files. This includes the Microsoft Dynamics SL Software Development Kit. In addition, the installation package includes SharePoint Web Service, Web Services, the Microsoft Dynamics SL users guides, and the Release Notes and Summary of Changes documents.

On the line that follows, record the Microsoft Dynamics SL edition that you will install. _____________________________________________ Which Microsoft Dynamics SL edition should I install? During installation, you must select the Microsoft Dynamics SL edition to install. The Business Ready Licensing editions and their product codes are as follows: Business Essentials Business Essentials = 60 Advanced Management Advanced Management = 61

The Modular Licensing editions are available so that you can add modules to an existing installation. If you select this option, you also have to select one of the following: Single-User Standard Single-User Standard (Solomon Single User) = 49 Multi-User Standard Multi-User Standard (Solomon Multi-User) = 48 Professional Professional (Solomon) = 47

If you want more help determining which edition to install, contact a Microsoft Certified Partner or log on to VOICE at https://mbs.microsoft.com/voice/Default.aspx?wa=wsignin1.0 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. Verify that available disk space is sufficient for your installation. For additional help in determining configuration requirements, contact a Microsoft Certified Partner. Review Creating Databases on page 26 to determine the following: Which databases will be created during this installation Their approximate sizes The server and path of the location where they will be stored Their names Their types

Record the information on the lines that follow. Contact your database administrator, a Microsoft Certified Partner, or technical support for help. 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 SQL Server. Compatibility mode 90 is the default for new and upgraded Microsoft Dynamics SL databases. For more information about compatibility modes, see Microsoft Dynamics SL Release Notes.

Installation Guide You must also decide whether you will create demo databases. Demonstration databases are useful for training and for testing unfamiliar areas of the software without affecting your live data. System Application Server (include path) System Application Server (include path) System Application Server (include path) System Application Server (include path) System Application Server (include path)

Empty Databases _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ Demo Databases Demonstration 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 as follows: Demo Business Ready Editions System and application databases are created based on the software package that you select when you install Microsoft Dynamics SL (see Which Microsoft Dynamics SL edition should I install? on page 7). 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. System Application Server (include path) System Application Server (include path) System Application Server (include path) System Application Server (include path) System Application Server (include path)

Use these names for your demo databases if you can do this. _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________ _________________________________________

On the line that follows, record the SQL Server version installed on the computer where you will create or update the Microsoft Dynamics SL databases. _____________________________________________

Installation Preparation Which Microsoft SQL Server version do I have? Microsoft Dynamics SL 2011 supports 2008 (Standard or Enterprise Edition) and Microsoft SQL Server 2008 R2 (Standard or Enterprise Edition). You must purchase SQL Server separately. Contact a Microsoft Certified Partner for help. If you already have SQL Server installed, determine your 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:
Supported products SQL Server 2008 Product version 10.00.1600.22 10.00.2531 10.00.4000 SQL Server 2008 R2 10.5.1600.1 Software release and product level SQL Server 2008 SQL Server 2008 SP1 SQL Server 2008 SP2 SQL Server 2008 R2

For more information about how to determine the Microsoft SQL Server version, see How to identify your SQL Server version and edition at http://support.microsoft.com/default.aspx?scid=kb;en-us;321185 or contact a Microsoft Certified Partner.

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). Note: A full installation of Microsoft Dynamics SL is required on a computer where you plan to install the Microsoft Dynamics SL SDK. A client-only installation is insufficient and causes the Microsoft Dynamics SL SDK installation to fail. How can I determine whether I should install the Microsoft Dynamics SL SDK? Check whether the Microsoft Dynamics SL Software Development Kit is included in your license keys, or confirm that you should install the Microsoft Dynamics SL SDK by contacting a Microsoft Certified Partner.

Perform a system backup on the server where you will install Microsoft Dynamics SL. Contact your system administrator for help. Note: If you are updating an existing installation of Microsoft Dynamics SL, make sure that you create a backup of all custom Crystal Reports in your existing Microsoft Dynamics SL installation so that you can restore them after you install this release. See Updating Custom Crystal Reports on page 88 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 do this causes problems in the installation. Note: If you use Active Directory, you may log on as a member of the Domain Administrators group that must be part of the local Administrators group. You must have Administrator rights to perform a full installation or client installation on a computer that is running Windows Server because the installation process updates the Windows registry. You might also have to restart the server during or after installation.

10

Installation Guide On the server where you will install Microsoft Dynamics SL, close all currently running programs and stop SQL Server services. For more information, see SQL Server Books Online for your SQL Server release. Note: Because Microsoft Dynamics SL Setup may have to update files that are used by other programs or services, it is important to complete this step before you start the installation. Remember to restart the SQL Server Agent service when you restart SQL Server, if you do not have SQL Server Agent service set to restart automatically when you restart the computer. If SQL Server Agent does not restart, any backups or other jobs scheduled in SQL Server will not run. Do not disable virus detection/protection software.

If an earlier version of Microsoft Dynamics SL is installed (Release 4.x, 5.x, 6.x, or 7.x), you must export all screen customizations. The Export Customizations (91.500.00) screen will help you perform this task (see the Customization Manager Help or user's guide for help). Make sure that you store the export file in a safe location. You can also use the VBA Code window to export the customizations Visual Basic code for safekeeping (for more information, see Export Customizations on page 70). In addition, print the customization code from the Visual Basic for Applications integrated development environment (VBA IDE). Having a printed copy of the customization code will be helpful if you have to rebuild a customization.

If an earlier version of Microsoft Dynamics SL is installed (Release 4.x, 5.x, 6.x, or 7.x), you must remove the earlier release. Remove the earlier version 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, the software will require you to do this. How do I remove an earlier release of Microsoft Dynamics SL? Make sure that you perform a system backup before you follow these steps: 1. Open Control Panel, and then open Programs and Features. 2. Locate the 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. For more information, see Removing an Existing Installation on page 71. 3. Click Remove or Uninstall.

Uninstalling/Installing the Microsoft Dynamics SL Outlook add-in. If you installed an earlier version of the MicrosoftDynamics.SL.Addin, we recommend that you uninstall the Microsoft Dynamics SL Outlook add-in, and then reinstall the add-in from the installation package. You should do this immediately before or immediately after you uninstall the Microsoft Dynamics SL client. Note: Unlike the client that must be uninstalled one time on each computer, the add-in must be uninstalled one time by each user who ran a screen that works with email in the client. Before uninstalling the add-in, make sure that neither Outlook, nor the Microsoft Dynamics SL client are running. See Microsoft.Dynamics.SL.OutlookAddin on page 62 for information about how to uninstall the add-in.

Your Preinstallation Checklist is now complete! Make sure that you print the checklist so that you can refer to it during the installation tasks.

Installation Preparation

11

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

Figure 1: Installation options window

The installation options include the following:

Prepare
View Release Notes Opens the Microsoft Dynamics SL Release 2011 Release Notes in .pdf file format. This document contains information about changes that are important to those who manage and use Microsoft Dynamics SL applications. View Summary of Changes Opens the Microsoft Dynamics SL Release 2011 Summary of Changes in .pdf file format. In this document, you will find a module-by-module list of the issues this release addresses. View Security Guide Opens the Security Guidelines for Microsoft Dynamics SL Release 2011 in .pdf file format. In this document, you will find security considerations with which you should be familiar. View Installation Guide Opens the Microsoft Dynamics SL Installation Guide Release 2011 in.pdf file format. View Readme Opens the ReadMe.txt file.

12

Installation Guide

Install
Microsoft Dynamics SL Starts the installation process. User Guides Installs the application user guides. This includes the Microsoft Dynamics SL Software Development Kit, the Visual Basic 2005 Conversion Toolkit for Microsoft Dynamics SL, and the Microsoft Dynamics SL Provider for Management Reporter.
Hint: You can make the user guides more easily available to users by creating a shortcut to the folder where you install the files and then adding the shortcut to users desktops.

Additional Products
Crystal Reports Starts the Crystal Reports 2008 setup. Install Crystal Reports 2008 if you plan to change standard Microsoft Dynamics SL reports or create custom reports. Microsoft Dynamics SL Provider for Management Reporter ERP Starts the Microsoft Dynamics SL Provider for Management Reporter ERP setup. Install the provider if you plan to use Management Reporter for Microsoft Dynamics SL. Microsoft Dynamics SL SharePoint Web Service Installs software that you will need if you want to use the Doc Share feature to post documents to a SharePoint site, print to a SharePoint site, or upload Attachments to a SharePoint site. See Microsoft Dynamics SL SharePoint Web Service on page 58 for more information. Microsoft Office Project 2010 Connector for Microsoft Dynamics SL Starts the Microsoft Office Project Connector installation. Microsoft Dynamics SL Web Services Starts the Microsoft Dynamics SL Web Services installation. Install Web Services if you plan to consume, extend, or author Web Services.

If an earlier release of Microsoft Dynamics SL is not installed on your workstation computers or server, see Guide for New Installations on page 13. If you are updating an earlier release, see Upgrading an Existing Installation on page 69.

Guide for New Installations

13

Guide for New Installations


Overview
This section covers the following topics for those who currently do not have Microsoft Dynamics SL installed: Installing Microsoft Dynamics SL on page 14 guides you through installing the application files on your companys server. These steps apply to both new and upgrade installations. Changes Needed for User Account Control on page 23 discusses actions that you must take if you have User Account Control (UAC) enabled in Windows. Microsoft SQL Server Installation on page 23 discusses installing the Microsoft SQL Server database software on your companys database server. Creating Databases on page 26 describes the various databases that you can create and explains how to create them. Installing Supporting Applications on page 42 guides you through the installation of programs that provide additional functionality to Microsoft Dynamics SL. Microsoft Dynamics SL Users Guides on page 53 describes the steps that you must follow to install the users guides. Setting Up Microsoft Dynamics SL on Workstations on page 65 explains how to configure workstations that will connect to the new environment.

14

Installation Guide

Installing Microsoft Dynamics SL


This section discusses the steps to use to install Microsoft Dynamics SL on the server. Be aware that this information 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 this causes problems in the installation Note: If you are using Active Directory, you must log on as a member of the Domain Administrators group that must be part of the local Administrators group. 2. Download and extract the installation package. Then, run Setup.exe in the root directory of the installation package by selecting Start | Run and browsing to the installation package.

Figure 2: Installation options window

3. Click Microsoft Dynamics SL. Note: You can install the application users guides by selecting User Guides on the installation options window. Users guides are provided in Adobe Acrobat PDF format. If Setup detects an existing installation, Setup prompts you to modify, repair, or remove the existing installation before you continue. Click Remove to uninstall. If existing Microsoft Dynamics SL databases must be made compatible with Microsoft Dynamics SL 2011, see Upgrading an Existing Installation on page 69.

Guide for New Installations Welcome appears.

15

Figure 3: Welcome

4. Click Next. License Agreement appears that asks you to accept or decline the software license agreement. Carefully read the license agreement. To print the agreement, click Print. Note: You can read or print the license agreement details or the privacy statement after the software is installed. To do this, click Help | About Microsoft Dynamics SL in the Microsoft Dynamics SL window. Then click either View the Microsoft Software License Terms or Read our privacy statement. 5. 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.

Figure 4: Exit Setup

Click Yes to cancel the installation or click No to accept the license agreement terms and continue.

16

Installation Guide If you agree to the license agreement terms, Choose Edition appears.

Figure 5: Choose Edition

6. Click the Install button for the appropriate Business Ready Licensing or Module Licensing edition. Your choice is based on the information that you verified in Which Microsoft Dynamics SL edition should I install? on page 7. Choose Destination Location appears, displaying the default destination folder for the installation.

Figure 6: Choose Destination Location

Guide for New Installations

17

7. Install the Microsoft Dynamics SL program files in the default destination folder (typically C:\Program Files\Microsoft Dynamics\SL\Applications) or at least one directory level from the hard disk root directory (for example, C:\Microsoft Dynamics\SL\Applications\2011\). The folder that you install the program files inthe SL folder in the examplemust be shared in order to support connections by multiple workstations. Verify that the folder that you want to share is acceptable for sharing. If you want to install the program files in the default destination folder, click Next to continue. If you want to override the default destination folder, click Browse to locate the folder to which you want to install the program files. If the destination folder does not already exist, the Setup program will ask whether it should create the folder. This lets you confirm that you have selected the correct location. Click Next.

8. If this is an upgrade installation and Setup detects an existing menu file (Delta.mnu) in the destination folder that you selected, a message appears that asks you if you want Setup to keep a copy of the menu file. It will save the copy in the Backup subdirectory. Click Yes to have Setup save the existing menu file.

Figure 7: Confirm Backup

9. Select Microsoft Dynamics SL Applications appears that shows the programs that you automatically selected for installation based on the option that you chose in step 5.

Figure 8: Select Microsoft Dynamics SL Applications Advanced Management selected

10. In this window, you can change the list of modules and applications that you install. To select applications individually, clear the check box for the module group that you want to change, and then select an application from the list that is displayed to the right side of the modules list. For

18

Installation Guide example, to install Application Server without installing the other E-Commerce applications, clear the E-Commerce check box, and then select the Application Server check box in the list of ECommerce applications. If you selected Module Licensing in step 5, all modules are selected. Strongly recommended: Select only those applications that you need to install. Do not automatically select all. Special considerations: If you plan to use the Doc Share feature or the Quick Send feature, select Application Server in the E-Commerce module group. Doc Share functionality and Quick Send functionality are available only if the Application Server program files are installed, although you do not have to purchase a license for Application Server in order to use Doc Share or Quick Send. If you plan to install Business Portal, you must have the Application Server module installed also. Select Application Server in the E-Commerce module group. You must select Client Setup Utility in the Foundation group if you want to log on to Microsoft Dynamics SL or Microsoft Dynamics SL Database Maintenance on the computer.

11. Click Next. 12. If you selected Tools, License Agreement appears again, this time that asks you to accept or decline the Microsoft Dynamics SL Software Development Kit (SDK) license agreement. Carefully read the software license agreement. To print the agreement, click Print. 13. 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.

Figure 9: Exit Setup

Click Yes to cancel the installation, click No to accept the license agreement terms and continue, or click No and then click Back to remove Tools from the list of modules to install.

Guide for New Installations

19

14. If you selected Customization Manager in the Foundation module group, Customization Features appears. It prompts you for the kind of customization features to use with the Customization Manager module.

Figure 10: Customization Features

After you read about the choices, select the appropriate customization option. VBA features Installing Visual Basic for Applications (VBA) features lets you create new customizations by using VBA code and to translate existing Basic Script Language (BSL) customizations to VBA code. If you prefer to use VBA, select VBA features. BSL features Installing the Basic Script Language (BSL) features allows for installations that are upgrading to continue using current customizations that are written in BSL without converting them to VBA. Select BSL features if you prefer to continue writing and editing code by using BSL.

20

Installation Guide

15. Click Next. The message, Calculating space requirements. Please wait, briefly appears, and then Start Copying Files appears that lists all current installation selections.

Figure 11: Start Copying Files Professional selected

16. Verify that all installation selections are correct. If a change is needed, click Back until you arrive at the incorrect selection, and then make the correct selection. Click Next until Start Copying Files appears again. 17. Review the selections to make sure that they are correct, and then click Next. Setup copies files from the installation package. If you selected the Client Setup Utility in the Foundation Series in step 10, Setup next runs the Client Setup program. Note: For Client Setup to complete, the Microsoft .NET Framework 3.5 Service Pack 1 must be installed. If the software is not detected by the Client Setup program, you receive the following message and the client installation ends.

Figure 12: Start Copying Files Professional selected

To install the .NET Framework, see .NET Framework 3.5 Service Pack 1 (SP1) on page 64. After you install the .NET Framework, restart the client installation by running setup.exe from the WRKSTN folder in the Microsoft Dynamics SL installation. A typical location is \Program Files\Microsoft Dynamics\SL\Applications\WRKSTN.

Guide for New Installations 18. Client Setup may prompt you to install the Visual Studio Tools for Office (VSTO).

21

Figure 13: InstallShield Wizard, Visual Studio Tools for Office

Click Install. For more information about VSTO, see Microsoft.Dynamics.SL.OutlookAddin on page 62. 19. After Setup has installed the selected files, View Readme File is displayed and asks you if you want to review the ReadMe.txt file. Click Yes. 20. Review the ReadMe.txt file on the screen, or select File | Print to print it. 21. After reviewing or printing, close the file by closing Notepad. InstallShield Wizard Complete is displayed and asks whether you want to restart the computer now.

Figure 14: InstallShield Wizard Complete

22

Installation Guide

22. Click Finish to restart immediately. Note: We strongly recommend that you restart immediately to make sure that the software functions correctly. 23. Close the installation options window. If you use User Account Control (UAC) in Windows, go to Changes Needed for User Account Control on page 23 before you create or update the databases. Now that Setup has finished installing the application files, you can create or update databases. If this is a new Microsoft Dynamics SL installation, see Creating Databases on page 26. If you are updating an existing installation, see Updating Databases on page 74.

Guide for New Installations

23

Changes Needed for User Account Control


User Account Control (UAC) is a security feature that changes the way applications work with the operating system. A protection level is implemented to help eliminate access by malicious users and programs. UAC is enabled automatically. 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 correctly set up a users environments to follow UAC requirements.

Locating Solomon.ini and Other Profiles


In earlier Windows releases, profiles (.ini files) were stored in the Windows folder. However, UAC does not allow for write access to the Windows folder outside the installation process. Windows overrides any non-installation access to the Windows folder by putting .ini files in the users local application data directory. The customizable Solomon.ini file is put in the following location: \Users\<username>\AppData\Roaming\Microsoft Dynamics SL\.

Making Required Messages File Location Changes


To generate a message file (Messages.csv) by 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 Help or users guide). For example:
[Read Directory] Message File= C:\Users\Public\Documents\Microsoft Dynamics SL\Messages.csv

After you have established the new location of the Messages.csv file, copy it from the Microsoft Dynamics SL program folder to the newly designated location. Example: 32-bit Copy from: Copy to: Copy from: Copy to: C:\Program Files\Microsoft Dynamics\SL\Applications\ C:\Users\Public\Documents\Microsoft Dynamics SL\ C:\Program Files x86\Microsoft Dynamics\SL\Applications\ C:\Users\Public\Documents\Microsoft Dynamics SL\

64-bit

Event Log Location Changes Required


If UAC is active, you must move the location of individual users event log files. By default, the Microsoft Dynamics SL event logs are stored in the EventLog folder under the Microsoft Dynamics SL program folder. Because of UACs virtualization, the new event log location is unacceptable for event log viewing. The new location is as follows: \Users\<user name>\AppData\Local\VirtualStore\Program Files\Microsoft Dynamics SL\EventLog Change the event log location by editing the Solomon.ini file (see the [Event Log] Section topic in Appendix A of the System Manager Help or users 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

24

Installation Guide

Selecting Program File Locations


With UAC active, Windows prevents write access to many folders, such as Program Files and the Windows system areas. It moves affected files to file system virtualization locations. When you select a location for file output, make sure that you select a folder that is available to users. Put files for output in a users profile folders or shared public folder areas. Example: \Users\<user name>\Documents \Users\Public\Documents Some applications where you must make directory choices are as follows: System Managers Transaction Import (98.500.00), Control Macro Generator (98.510.00), and Export Customizations (91.500.00) General Ledgers Generate Consolidation (01.500.00) Application Server Tax updates

Guide for New Installations

25

Microsoft SQL Server Installation


Microsoft SQL Server is required by Microsoft Dynamics SL (see Introduction and Which Microsoft SQL Server version do I have? for information about the SQL Server versions that are supported with this Microsoft Dynamics SL release). To purchase Microsoft SQL Server or to get help determining your configuration requirements, contact a Microsoft Certified Partner. You can install Microsoft SQL Server either before or after you install Microsoft Dynamics SL. However, you must install Microsoft SQL Server and start the SQL Server services before you create Microsoft Dynamics SL databases. See Creating Databases on page 26.

To install Microsoft SQL Server:


1. Run Setup.exe from the SQL Server installation package. SQL Server Setup starts. 2. Follow the on-screen prompts to install SQL Server. Note: Microsoft Dynamics SL requires you to install SQL Server By 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 and SQL Server Authentication).

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

26

Installation Guide

Creating Databases
A Microsoft Dynamics SL application database contains all the accounting data for a single 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 start to enter business data. Retrieve your printout of the Preinstallation Checklist you completed before you installed Microsoft Dynamics SL. The database information that it contains will be important in the following steps. In the Database Maintenance (98.290.00) screen, you can create databases by using any of four 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 that you chose when you installed Microsoft Dynamics SL (see Which Microsoft Dynamics SL edition should I install? on page 7). 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.

Guide for New Installations

27

To create databases:
Note: Your database administrator must perform these procedures. 1. Confirm that the SQL Server service is running. Restart the service if it is necessary. For more information, see SQL Server Books Online for your SQL Server release 2. In Control Panel, select Administrative Tools, and then Microsoft Dynamics SL Database Maintenance. Database Maintenance (98.290.00) appears.

Figure 15: Database Maintenance (98.290.00)

3. On the Connect Server tab, type the Destination SQL Server Name. 4. Windows Authentication is the default security mode for accessing the instance of SQL Server. We recommend this security mode 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 That You will connect with to create the databases. 5. Click Connect. A message appears in the status bar that indicates that you are connected to the instance of SQL Server.

28

Installation Guide

6. Click the Create Databases tab.

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

7. Follow the setup instructions for the kind of database that you are creating: Creating an Empty Database on page 29 Creating a Demo Database on page 34 Creating an Additional Empty Application Database on page 38

Guide for New Installations

29

Creating an Empty Database


To create an empty database:
1. On the Create Databases tab in Database Maintenance (98.290.00), select Empty Databases from the Scenarios list. 2. Click Advanced. Advanced Configuration Settings appears.

Figure 17: Advanced Configuration Settings

3. In the System Database Definition area, change the following settings if it is necessary: System Database Name System Database Size (MB) Server Location of Database Files Server Location of Transaction Log Database Name Size Database Path Transaction Log Path

4. In the Application Database Definition area, change the following settings if it is necessary:

5. Click Ok. The Create Databases tab reappears.

30

Installation Guide

6. Click Create. The Authentication dialog box appears.

Figure 18: Authentication

7. Select an authentication mode, and then click OK. We strongly recommend that you select Windows authentication to provide the most secure system. For more information about authentication modes, see Considering whether to change the database authentication mode on page 106. 8. Verify that the correct authentication mode is selected, and then click OK. If SQL Server Authentication is selected, go to Step 12. If Windows Authentication is selected, SYSADMIN Windows User Name appears.

Figure 19: SYSADMIN Windows User Name

9. In Windows User Name, type the identifier of the Windows user who will be the system administrator for this database. Type the information by using the domain\username format. Note: A user defined as an administrator automatically has access to all screens and reports within Microsoft Dynamics SL. If Microsoft Dynamics SL is running on a network, the user name that you enter here must be associated with the networks domain name. You can associate a Windows user name with a network domain name in Windows User Name in the System Managers User Maintenance (95.260.00) to create an additional administrator.

Guide for New Installations

31

10. If you do not want to let the user create new SQL Server users and logins, clear the Grant this user permission to create SQL Server logins and users check box that is selected by default. An administrator becomes a member of the SQL Server SYSADMIN server role if the Grant this user permission to create SQL Server logins and users check box is selected. Note:

Clearing the check box implies that the database administrator will generate SQL Server users and logins manually by using SQL Server tools. See Appendix C: Creating SQL Server Users and Logins on page 111 for help with setting up SQL Server users and logins manually. If the user is a Microsoft Dynamics SL SYSADMIN and also part of the SQL Sysadmin group, it is basically the same as selecting the Grant this user permission to create SQL Server logins and users check box in the SYSADMIN Windows User Name screen of Database Maintenance (98.290.00). To avoid a situation in which the check box is cleared for a Microsoft Dynamics SL administrator who needs to access databases and perform administrative tasks, enter the following SQL statement in a query window:
sp_addrolemember 'db_owner', 'domain\name'

Run the command for each Microsoft Dynamics SL system and application database. Example:
use SLSystemDatabase GO sp_addrolemember 'db_owner', 'domain\name' GO use SLApplicationDatabase GO sp_addrolemember 'db_owner', 'domain\name' GO

11. Click OK. 12. If you selected Windows Authentication in the Authentication window, go to Step 20. If you selected SQL Server Authentication, Security appears.

Figure 20: Security

13. 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 Master80 Login appears if you have not yet created the Master80 user. Click No if you should have selected Windows authentication. The Authentication dialog box appears. Go to step 6 and repeat the steps to select Windows authentication and to create the scenario databases.

32

Installation Guide Note: If you have already created the Master80 user, see step 17.

Figure 21: SQL Master80 Login

14. In Password, type a password for the Master80 user that satisfies the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide (securityguide.pdf). 15. In Confirm Password, type the password again. 16. Click Ok. The SYSADMIN Login dialog box appears.

Figure 22: SYSADMIN Login

17. In the Password box, type a password for the SYSADMIN user that satisfies the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide (securityguide.pdf). 18. In the Confirm box, type the password again. 19. Click OK.

Guide for New Installations 20. The Database creation process complete message appears.

33

Figure 23: Database creation process complete

21. Click OK. Database Maintenance (98.290.00) reappears. Click Close. 22. Review the Dbbuild.log file. If the database creation was successful, Dbbuild.log will only contain the times the process started and ended. If Dbbuild.log contains other text, contact Support Services for help. For more information about where you can find the Dbbuild.log, see Event Log Location Changes Required on page 23. For more information about how to contact Support Services, see Appendix D: Getting Support on page 113. If you need to create additional empty application databases to use with the system database that you just created, see Creating an Additional Empty Application Database on page 38. If you are finished creating databases, see Preparing the Demo System and Application Databases on page 40.

34

Installation Guide

Creating a Demo Database


To create a demo database:
1. On the Create Databases tab in Database Maintenance (98.290.00), select 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 edition that you chose when you installed Microsoft Dynamics SL. 2. Click Advanced. Advanced Configuration Settings appears.

Figure 24: Advanced Configuration Settings

Note: The demo system database names are SLDemoSystem and DemoStandardSystem. Demo companies are included, and the application database names for these companies are listed in the following list. Use these names for your demo databases when possible. SLDemoApp10 (companies 0010 and 0020) SLDemoApp60 (companies 0060, 0070, and 0080) DemoStandardApp51 (company 0051)

3. In the System Database Definition area, change the following settings if it is necessary: System Database Name System Database Size (MB) Server Location of Database Files Server Location of Transaction Log Database Name Size Database Path Transaction Log Path

4. In the Application Database Definition area, change the following settings if it is necessary:

5. Click Ok. The Create Databases tab reappears.

Guide for New Installations 6. Click Create. The Authentication dialog box appears.

35

Figure 25: Authentication

7. Select an authentication mode, and then click OK. We strongly recommend that you select Windows Authentication. For more information about authentication modes, see Considering whether to change the database authentication mode on page 106. If you selected SQL Server Authentication, go to Step 11. If you selected Windows Authentication, SYSADMIN Windows User Name appears.

Figure 26: 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 by using the domain\username format. Note: If Microsoft Dynamics SL is running on a network, the user name that you enter here must be associated with the networks domain name. You can associate a Windows user name with a network domain name in Windows User Name on the System Manager modules User Maintenance (95.260.00) screen to create an additional administrator. 9. If you do not want to give the individual the ability to create new SQL Server users and logins, clear the Grant this user permission to create SQL Server logins and users check box. (By default, the check box is selected.)

36

Installation Guide Clearing the check box implies that the database administrator will generate SQL Server users and logins manually by using SQL Server tools. See Appendix C: Creating SQL Server Users and Logins on page 111 for help with setting up SQL Server users and logins manually. Note: A user defined as an administrator automatically has access to all screens and reports within Microsoft Dynamics SL. An administrator becomes a member of the SQL Server SYSADMIN server role if the Grant this user permission to create SQL Server logins and users check box is selected.

10. Click OK. 11. If you selected Windows Authentication in the Authentication window, go to Step 19. If you selected SQL Server Authentication, Security appears.

Figure 27: Security

12. 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 Master80 Login appears. Click No if you should have selected Windows authentication. The Authentication dialog box appears. Go to step 6 and repeat the steps to select Windows authentication and to create the scenario databases.

Figure 28: SQL Master80 Login

13. Type a Password for the Master80 user that satisfies the strong password requirements that are listed in the dialog box Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide (securityguide.pdf) in the User Guides. 14. In Confirm Password, type the password again.

Guide for New Installations 15. Click Ok. The SYSADMIN Login dialog box appears.

37

Figure 29: SYSADMIN Login

16. Type a Password for the SYSADMIN user that satisfies the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide (securityguide.pdf) in the User Guides. 17. In the Confirm box, type the password again. 18. Click OK. Database creation begins. 19. When database creation is complete, the Database creation process complete message appears.

Figure 30: Database creation process complete

20. Click OK. Database Maintenance (98.290.00) appears. Click Close. 21. Review the Dbbuild.log file. If the database creation was successful, Dbbuild.log contains only the start times and the end times for the process. If Dbbuild.log contains other text, contact Support Services for help. For more information about where you can find the Dbbuild.log, see Event Log Location Changes Required on page 23. For more information about how to contact Support Services, see Appendix D: Getting Support on page 113. 22. See Logging On on page 39.

38

Installation Guide

Creating an Additional Empty Application Database


To create an additional empty application database:
1. On the Create Databases tab in Database Maintenance (98.290.00), select 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.

Figure 31: Advanced Configuration Settings

3. In the System Database Definition area, do not type any information. 4. In the Application Database Definition area, change the following settings if it is necessary: Database Name Database Path Transaction Log Path

5. Click Ok. The Create Databases tab reappears. 6. Click Create. Identify System Database (98.290.40) appears.

Figure 32: Identify System Database (98.290.40)

7. In the System Database Name list, select the appropriate system database for your new application database, and then click Ok. Database creation begins. 8. When Database creation process complete appears, click OK. 9. Click Close. 10. Review the Dbbuild.log file that is typically found in the Microsoft Dynamics SL EventLog folder. If database creation was successful, Dbbuild.log contains only the start times and the end times for the process. If Dbbuild.log contains other text, contact Support Services for help. For more information about where you can find the Dbbuild.log, see Event Log Location Changes Required on page 23.

Guide for New Installations

39

Logging On
When you first open Microsoft Dynamics SL after you install and creating databases, Microsoft Dynamics SL Login (98.000.00) does not appear if your company uses Windows authentication and you are not required to enter a password. In the Microsoft Dynamics SL window, click the Switch Company button, and then click More Companies to open the Select a Company window to open a company by selecting it from the list that appears. Note: The color of the Switch Company button depends on the company ID. Specify the color for each company ID by using System Managers Company Maintenance (98.280.00). If your organization uses SQL Server authentication or Windows authentication with logon passwords required, see the instructions that follow. For later logons, the user ID That You entered last appears on Microsoft Dynamics SL Login (98.000.00) if you are using SQL Server authentication. If you select a company configured for Windows authentication and you are not required to enter a password (see Using Passwords in the Quick Reference Guide), Microsoft Dynamics SL Login (98.000.00) does not appear. The software uses your Windows credentials to automatically log on to the last company that you accessed.

To log on the first time (Windows authentication with a password that is required or SQL Server authentication):
1. Click Start | All Programs and select Microsoft Dynamics SL. Find Database (98.000.01) appears.

Figure 33: Find Database (98.000.01)

2. In the Server Name list, select the name of the instance of SQL Server or type the name if it does not appear on the list. 3. In the Database Name list, select a system database name or type the name of the system database if it does not appear on the list. Note: See your database administrator if you need help determining the names of your instance of SQL Server and system database. 4. Click OK. Microsoft Dynamics SL Login (98.000.00) appears.

Figure 34: Microsoft Dynamics SL Login (98.000.00) Windows authentication, password required

5. Type your User ID and Password, and then click OK.

40

Installation Guide

Preparing the Demo System and Application Databases


Preparing a database for operation means loading it with data that is contained in the .csv files. The data includes the following: System messages Possible values records (PVs) Report control information

To prepare the demo system and application databases:


1. In the Microsoft Dynamics SL navigation pane, click Administration. 2. In the System Manager details pane, under Utilities, click Database Update. Database Update (98.100.00) appears. 3. In the Directory box, browse for \DB\csvs. 4. In the Files box, select messages.msg, pvrec.csv, and rptcontrol.csv by clicking them. You do not have to hold down the CTRL key or SHIFT key. 5. Click Begin Processing. 6. Click OK when the process is completed. 7. Close Database Update (98.100.00). Your database is ready to use. To install other applications that provide additional functionality to Microsoft Dynamics SL, see Installing Supporting Applications on page 42.

Preparing the Empty System and Application Databases


Preparing a database for operation means loading it with data that is contained in the .csv files. These data include the following: System messages Possible values records (PVs) Report control information

To prepare the empty system and application databases:


1. In the Microsoft Dynamics SL navigation pane, click Administration. 2. In the System Manager details pane, under Utilities, click Database Update. Database Update (98.100.00) appears. 3. In the Directory box, browse for \DB\csvs. 4. In the Files box, select messages.msg, pvrec.csv, and rptcontrol.csv by clicking them. You do not have to hold down the CTRL key or SHIFT key. 5. Click Begin Processing. 6. When the process is complete, click OK to finish preparing the production system and application databases. 7. Close Database Update (98.100.00). Note: Complete steps 8 through 11 if you installed the Multi-Company module. 8. In the Microsoft Dynamics SL navigation pane, click Foundation, and then click Multi-Company. 9. In the Multi-Company details pane, under Setup, click Multi-Company Setup. Multi-Company Setup (13.950.00) appears.

10. Click to select the Activate Multi-Company with Inter-Company Processing check box. 11. Click Save, and then close Multi-Company Setup (13.950.00).

Guide for New Installations 12. In the Microsoft Dynamics SL navigation pane, click Financials, and then click General Ledger.

41

13. In the General Ledger details pane, define information that is required for General Ledger module setup. a.) Set up the retained earnings and year-to-date 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). 14. Under Setup, click GL Setup. GL Setup (01.950.00) appears. 15. 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 year-to-date net income accounts, subaccounts, and ledgers. See Step 13. 16. Click Save, and then close GL Setup (01.950.00). 17. Register Microsoft Dynamics SL. For more information, see the System Manager help or users guide. We strongly recommend that you register the Microsoft Dynamics SL system immediately after you complete the installation to avoid running out of TRIALLOC database accesses.

42

Installation Guide

Installing Supporting Applications


Crystal Reports
Crystal Reports 2008 SP3 is required if you plan to design new or change existing reports. You must remove any earlier version of Crystal Reports from the server and workstations before you install Crystal Reports 2008 SP3.

Removing an Earlier Version of Crystal Reports


To remove an earlier version before you install Crystal Reports 2008 SP3:
1. Remove Crystal Reports by using Programs and Features in Control Panel. 2. In Windows Explorer, delete all Crystal Reports program folders. A typical path is \Program Files\Crystal Decisions. Note: Possible cleanup of the registry keys might be needed. Contact your system administrator for help with this task.

Guide for New Installations

43

To install Crystal Reports 2008 SP3 on the server (repeat these steps at each workstation):
1. Run Setup.exe in the root directory of the installation package by clicking Start | Run and browsing to the installation package location.

Figure 35: Installation options window automatically appears.

44

Installation Guide

Note: When you select Crystal Reports, a submenu appears with a choice to install Crystal Reports 2008 SP3 or Crystal Reports 2008 SP3 Fix Pack 3.1. You must first select Crystal Reports 2008 SP3. When the Crystal Reports 2008 SP3 installation is complete, you are prompted to install Fix Pack 3.1. You can accept or decline the installation of Fix Pack 3.1. We recommend that you accept the installation of Fix Pack 3.1.

Figure 36: Installation options window Crystal Reports selected

Guide for New Installations 2. Click Crystal Reports 2008 SP3. Crystal Reports 2008 SP3 Setup appears.

45

Figure 37: Crystal Reports 2008 SP3 Setup

3. Select the setup language that you want to use. If you do not want to create an installation log file, clear the Create log file during installation check box. 4. Click OK. Welcome to the Crystal Reports 2008 SP3 Installation Wizard appears.

Figure 38: Welcome

5. Click Next. License Agreement appears.

46

Installation Guide

6. Carefully read the software license agreement, click I accept the License Agreement, and then click Next. User Information appears.

Figure 39: User Information

7. Enter your software registration information, and the product keycode included with your Microsoft Dynamics SL registration keys. Note: The Crystal Reports registration information is available as a note at the end of the list of Microsoft Dynamics SL registration keys. To view your software registration information, visit the CustomerSource Product and Service Summary webpage

Guide for New Installations 8. Click Next. Choose Language Packs appears.

47

Figure 40: Choose Language Packs

9. Click Next to accept the English language pack. Select Installation Type appears.

Figure 41: Select Installation Type

10. Select Typical. If it is necessary, change the path of the destination folder by using Browse. Note: If you specify a path other than the default in Destination Location, make sure that you 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).

48

Installation Guide

11. Click Next. Start Installation appears.

Figure 42: Start Installation

12. Click Next to start the installation. When it is complete, the following window appears. This indicates that the installation was successful.

Figure 43: Successful installation message

13. Click Finish. Crystal Reports Installation appears.

Figure 44: Crystal Reports 2008 SP3 Fix Pack 3.1 installation message

Guide for New Installations 14. Click Yes. CrystalReports 2008 FP 3.1 Update Setup Choose Setup Language appears.

49

Figure 45: Choose Setup Language

15. Click OK. Welcome to the Crystal Reports 2008 FP 3.1 Installation Wizard appears.

Figure 46: Welcome

16. Click Next. License Agreement appears. 17. Carefully read the software license agreement, click I accept the License Agreement, and then click Next. Start Installation appears.

Figure 47: Start Installation

50

Installation Guide

18. Click Next to start the installation. When it is complete, the following window appears that indicates that the installation was successful.

Figure 48: Successful installation message

Note: When you use Crystal Reports, remember the following: Microsoft Dynamics SL does not use Crystal Reports dictionaries. Anyone who is using Crystal Reports is counted as a Microsoft Dynamics SL seat license. Crystal Reports 2008 no longer supports the following report export options: MAPI, Application, Exchange Folder, Lotus Domino, and Lotus Domino Mail.

Because of changes in the standard Microsoft Dynamics SL reports, customized reports from the 4.x, 5.x, 6.x, and 7.x releases may not run without modification. Make sure that you follow the steps in Updating Custom Crystal Reports on page 88. Then, if your customized reports still do not run, contact a Microsoft Certified Partner.

Guide for New Installations

51

Microsoft Dynamics SL Provider for Management Reporter ERP


A data provider acts as a bridge between the data source and Management Reporter for Microsoft Dynamics SL 2011. Information from the data source can be displayed and manipulated in financial reports that were created in Management Reporter without affecting the database where the Microsoft Dynamics SL data resides. Management Reporter can work with multiple data providers to meet the reporting needs of any organization. To use this feature, you must install the Microsoft Dynamics SL Provider for Management Reporter.

Overview of Management Reporter for Microsoft Dynamics SL installation


Install the server components of Management Reporter for Microsoft Dynamics SL 2011 from the Management Reporter installation package. Installation documentation and system requirements are included in the Management Reporter installation package. Install the Microsoft Dynamics SL Provider for Management Reporter from the Microsoft Dynamics SL installation package. Installation documentation is included in the Microsoft Dynamics SL Provider for Management Reporter users guide (DynamicsSLDataProvider.pdf). Install the client components of Management Reporter for Microsoft Dynamics SL 2011 from the Management Reporter installation package. Installation documentation is included in the Management Reporter installation package If you are moving from Microsoft FRx 6.7 to Microsoft Dynamics Management Reporter, use the Management Reporter Migration Wizard to migrate your reports. For detailed steps, download Migrating to Management Reporter for Microsoft Dynamics ERP from the Microsoft Dynamics File Exchange System. Note: If you will not be upgrading to Management Reporter for Microsoft Dynamics SL 2011 when you upgrade to Microsoft Dynamics SL 2011, you must apply Microsoft FRx 6.7 Service Pack 12 (SP12). Installation documentation is included in the Microsoft FRx installation package.

52

Installation Guide

Project Connector 2011 for Microsoft Project 2010


Integrating the Microsoft Dynamics SL and Microsoft Project Server 2010 databases involves installing components, running database scripts, and configuring options on the multiple computers (some computers might contain more than one application or service). For more information about how to install Project Connector 2011, see the Microsoft Project Connector Guide (MicrosoftProjectConnector.pdf) or help.

Guide for New Installations

53

Microsoft Dynamics SL Users Guides


Before you run the Setup program for the Users Guides, verify that Adobe Reader is installed.

To install the Users Guides:


1. Run Setup.exe in the root directory of the installation package by selecting Start|Run and browsing to the installation package.

Figure 49: Installation options window

54

Installation Guide

2. Click User Guides. The Welcome dialog box appears.

Figure 50: Welcome

3. Click Next. 4. License Agreement appears and asks you to accept or decline the software license agreement. Carefully read the license agreement. To print the agreement, click Print. Note: To read or print the license agreement details or the privacy statement after the software is installed, click Help | About Microsoft Dynamics SL in the Microsoft Dynamics SL window. Then click either View the Microsoft Software License Terms or Read our privacy statement. 5. 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 exit or resume installing. You can cancel the installation or accept the license agreement terms and continue.

Guide for New Installations

55

6. If you agree to the license agreement terms, Choose Destination Location appears that shows the default destination folder for the installation.

Figure 51: Choose Destination Location

7. Install the Microsoft Dynamics SL users guides in the default destination folder (\Microsoft Dynamics\SL\Applications\User Guides\) or select a different location. If you want to install the program files in the default destination folder, click Next to continue. If you want to override the default destination folder, click Browse and locate the folder to 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. This lets you confirm that you have selected the correct location. Click Next.

8. Install the Microsoft Dynamics SL users guides in the default destination folder (\Microsoft Dynamics\SL\Applications\User Guides\) or select a different location.

56

Installation Guide

9. Select Features appears and shows the list of users guides that will be installed.

Figure 52: Select Features

10. In this window, you can select module groups for which you can install users guides. Note: Select only those users guides you need to install. Do not automatically select all. 11. Click Next. 12. Start Copying Files appears and lists all current users guide selections.

Figure 53: Start Copying Files

Guide for New Installations

57

13. 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. 14. Review the selections to make sure that they are correct, and then click Next. InstallShield Wizard Complete appears.

Figure 54: InstallShield Wizard Complete

15. Click Finish. 16. Close the Installation Options window.

58

Installation Guide

Microsoft Dynamics SL SharePoint Web Service


The Doc Share, Print to SharePoint, and Attachments upload to SharePoint features are available to help you distribute documents on the web so that vendors, customers, or project teams can access them online. To use these features, you must install the Microsoft Dynamics SL SharePoint Web Service. Note: Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010 is required on the computer that will host the SharePoint site where the shared documents will reside. They must be configured before you install the Microsoft Dynamics SL SharePoint Web Service. For information about Windows Server or Microsoft SharePoint, see the Microsoft Dynamics SL Security Guide (securityguide.pdf) or contact a Microsoft Certified Partner. You must install the Microsoft Dynamics SL SharePoint Web Service on each computer that will host the SharePoint sites where your shared documents will reside. The SharePoint Web Service must be installed/configured for any site to which you want to publish. If you change your environment, you must uninstall the SharePoint Web Service, reinstall it, and then select the sites to which you want to publish.

To install the Microsoft Dynamics SL SharePoint Web Service:


1. Run Setup.exe in the root directory of the installation package by clicking Start Run and browsing to the installation package.

Figure 55: Installation options window

Guide for New Installations 2. Click Microsoft Dynamics SL SharePoint Web Service. License Agreement is displayed and asks you to accept or decline the software license agreement.

59

Note: If Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010 are not installed, a Doc Share message appears before License Agreement that reminds you to install them. When you click OK, the Microsoft Dynamics SL SharePoint Web Service installation process ends. For information about Windows Server or Microsoft SharePoint, see the Microsoft Dynamics SL Security Guide (securityguide.pdf) or contact a Microsoft Certified Partner. 3. Carefully read the license agreement. To print the agreement, click Print. 4. 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 exit or resume installing. You can cancel the installation or accept the license agreement terms and continue. A list of available SharePoint sites appears.

Figure 56: Select SharePoint Sites list

5. Click to select the site where you want to install the Web Service. You can select more than one site on the same computer by pressing CTRL as you left-click. 6. Click Next. The installation process starts.

60

Installation Guide

7. When the installation is almost complete, Installation Status appears and advises you that Setup is ready to reset the Internet Information Services (IIS).

Figure 57: Installation Status

8. Click Finish. The installation is completed.

Guide for New Installations

61

Microsoft Dynamics SL Web Services


The Web Services feature improves the extensibility of Microsoft Dynamics SL in two major areas. First, Web Services provides a set of programming interfaces that you can build upon to create web services that integrate with Microsoft Dynamics SL. Such web services are useful for those who want to develop solutions that integrate Microsoft Dynamics SL with other business systems on premise or in the cloud. In this manner, Web Services is suited for changing existing business systems that currently integrate with other ERP solutions so that the business systems now integrate with Microsoft Dynamics SL. Similarly, you can use Web Services to create a suite of new web services that contain logic that is equal to an existing third-party application. Second, Web Services provides out of the box web services that use business logic that is equal to the business logic used within the standard Microsoft Dynamics SL applications. These out of the box web services let third-party software interoperate with Microsoft Dynamics SL over a network, even from devices where the Microsoft Dynamics SL client is not installed. Additionally, web services that are built on Microsoft Dynamics SL Web Services can be customized, regardless of whether the web services originated as out of the box or third-party. To use this feature, you must install the Microsoft Dynamics SL Web Services. For information about how to install Microsoft Dynamics SL Web Services, see the Web Services users guide or help.

62

Installation Guide

Microsoft.Dynamics.SL.OutlookAddin
Microsoft Dynamics SL screens work with email through Microsoft Visual Studio Tools for Office (VSTO). VSTO lets Microsoft Dynamics SL screens to communicate with Microsoft Office Outlook through an add-in. This add-in is named Microsoft.Dynamics.SL.OutlookAddin and is installed with the Microsoft Dynamics SL client. When a user runs a screen that works with email for the first time, Microsoft Dynamics SL tries to install the add-in if you did not previously install the add-in manually for the user on the workstation computer. Depending on your computers configuration, you may see a window asking for permission to install the add-in. If Outlook is running while the add-in is installed, you must restart Outlook to finish installing the add-in. To avoid this automatic installation, use the installation steps shown here:

To manually install the Microsoft.Dynamics.SL.OutlookAddin, follow these steps:


1. Browse to the DynamicsSL\OutlookAddin folder in the installation package or to the MicrosoftDynamics\SL\Applications\OutlookAddin folder on the server. 2. Double-click the Microsoft.Dynamics.SL.OutlookAddin.vsto file. The Microsoft Office Customization Installer dialog box appears.

Figure 58: Microsoft Office Customization Installer

3. Click Install. 4. Click the Close button when the add-in is installed successfully. Note: If a cached copy of the Microsoft.Dynamics.SL.OutlookAddin.dll file remains from a previous uninstall of VSTO, you may be unable to reinstall VSTO. If this is the case, browse to the following location, and then delete the subfolder that contains the file: <SystemDrive>:\Users\[UserAlias]\AppData\Local\Apps\2.0\ Remember to uninstall the Microsoft Dynamics.SL.OutlookAddin every time that you uninstall Microsoft Dynamics SL. See the following steps.

Guide for New Installations

63

To uninstall the Microsoft Dynamics.SL.OutlookAddin, follow these steps:


1. Close Microsoft Office Outlook. 2. Open Control Panel, and then open Programs and Features. 3. Click the Microsoft.Dynamics.SL.OutlookAddin item in the list, and then click Uninstall. 4. Click OK when you are prompted Are you sure you want to remove this customization (Microsoft.Dynamics.SL.OutlookAddin) from this computer? 5. The Microsoft.Dynamics.SL.OutlookAddin will be removed from the list. Note: If you accidentally uninstall the add-in while Outlook is running, the add-in may remain on the computer.

To complete the uninstall of the add-in in this situation, follow these steps:
1. Open Add-Ins in Microsoft Office Outlook. In Outlook 2007, click Tools->Trust Center->Add-ins. In Outlook 2010, click File->Options->Add-Ins.

2. In the Manage box, select COM Add-ins, and then click Go. 3. The COM Add-Ins window appears. 4. Click Microsoft.Dynamics.SL.OutlookAddin. 5. Click Remove, and then click OK.

64

Installation Guide

.NET Framework 3.5 Service Pack 1 (SP1)


.NET Framework 3.5 Service Pack 1 (SP1) is required for the Microsoft Dynamics SL client installation. To prevent the Microsoft Dynamics SL client installation from being interrupted, install the .NET Framework before you try to install the Microsoft Dynamics SL client.

To install the .NET Framework 3.5 Service Pack 1 (SP1), follow these steps
1. Download .NET Framework 3.5 Service Pack 1 (SP1) from the following location: http://www.microsoft.com/downloads/details.aspx?FamilyID=ab99342f-5d1a-413d-831981da479ab0d7 2. When you are prompted, save the dotnetfx35setup.exe file to your computer. 3. Run dotnetfx35setup.exe. Note: Make sure not to restart the computer while the .NET Framework is being installed. 4. When installation is complete, you receive the following message.

Figure 59: Microsoft .NET Framework message

5. Click OK. 6. Open Control Panel, and then open Programs and Features. 7. On the left, click Turn Windows features on or off. Windows Features appears.

Figure 60: Windows Features

8. Click Microsoft .NET Framework 3.5.1, and then click OK. 9. After the feature is turned on, close Control Panel. 10. Restart the computer.

Guide for New Installations

65

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: Run Microsoft Dynamics SL from a shared directory on the server Run 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 3.5 Service Pack 1 is a required part of the client installation. The Microsoft Dynamics SL client installation will not install if it does not detect the .NET Framework (dotnetfx35.exe) in the \Program Files (Program Files x86 for an installation that uses WoW64---see Introduction)\Microsoft Dynamics\SL\Applications\WRKSTN folder on the client computer. The Microsoft .NET Framework 3.5 Service Pack 1 is available in the Microsoft Dynamics SL installation package.

Running Microsoft Dynamics SL from a Shared Directory on the Server


To set up a workstation to run 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 a workstation you will configure to use Microsoft Dynamics SL. Failure to do this causes problems in the setup. Note: If you are using Active Directory, you must log on as a member of the Domain Administrators group, that in turn must be part of the local Administrators group. 2. Map a network drive to the shared folder on the server where the Microsoft Dynamics SL programs are installed. For example, if the software is installed in C:\Program Files\Microsoft Dynamics\SL\Applications, you would map to the shared SL folder. 3. Run Setup.exe from the \WRKSTN folder to start Client Setup. Welcome appears and advises you to exit other Windows-based applications before you continue.

Figure 61: Welcome

66

Installation Guide

4. Click Next. Choose Destination Location appears.

Figure 62: Choose Destination Location

5. Click Next to accept the path that appears. If the appropriate path does not appear, click Browse and open by using the mapped network drive to the shared folder where the application files are located. Then click Next. Note: If Setup detects an existing Microsoft Dynamics SL client 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 2011, see Upgrading an Existing Installation on page 69. 6. Client Setup may prompt you to install the Visual Studio Tools for Office.

Figure 63: InstallShield Wizard, Visual Studio Tools for Office

Guide for New Installations 7. Click Install. For more information about Visual Studio Tools for Office, see Microsoft.Dynamics.SL.OutlookAddin on page 62. 8. Start Copying Files appears and displays the disk space that is required to complete the installation.

67

Figure 64: Start Copying Files

9. Click Next to start Setup. 10. After Setup copies all resources to the workstation computers hard disk and registers them where it is needed, InstallShield Wizard Complete appears.

Figure 65: InstallShield Wizard Complete

68

Installation Guide

11. Click Finish to restart immediately (strongly recommended). 12. Close the installation options window.

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

Upgrading an Existing Installation

69

Upgrading an Existing Installation


Overview
This section explains how to upgrade an existing Microsoft Dynamics SL installation. Before You Install on page 70 lists important tasks that you must do before you install release 2010. Included in this section are details on how to export customizations for safekeeping. Removing an Existing Installation on page 71 describes how to remove existing Microsoft Dynamics SL installations on servers and client workstations to prepare for installing. Installing Microsoft Dynamics SL on page 73 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 74 describes how to update existing Microsoft Dynamics SL databases. Updating Client Workstations on page 84 explains how to update Microsoft Dynamics SL client workstations to this release. Installing Supporting Applications on page 42 describes the procedure for installing applications that are included with this release. Be aware that, unless you have Crystal Reports 2008 already installed, you must remove the earlier version of Crystal Reports from the server and workstations in order to install Crystal Reports 2008. This section includes the following topics: Removing an Earlier Version of Crystal Reports on page 42 describes how to remove the previous installation of Crystal Reports in order to install Crystal Reports version 2008. Crystal Reports on page 42 describes how to install Crystal Reports 2008. Updating Custom Crystal Reports on page 88 describes how to update your existing Crystal reports from an earlier version to work with Crystal Reports version 2008. Microsoft Dynamics SL Users Guides on page 53 describes how to install the users guides for Microsoft Dynamics SL. Microsoft.Dynamics.SL.OutlookAddin on page 62 explains how to install and uninstall the Visual Studio Tools for Office add-in. .NET Framework 3.5 Service Pack 1 (SP1) on page 64 gives you the steps to install the .NET Framework required for Microsoft Dynamics SL client installation.

Using Database Update after Completing the Database Maintenance Scenario on page 82 explains how to update Microsoft Dynamics client workstations to this release. Adding Modules on page 90 gives you the steps that you will need if you want to add individual modules to the Microsoft Dynamics SL installation. Make sure that you grant access rights to enable users to access the added Microsoft Dynamics SL applications, screens, and reports. Contact a 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.

70

Installation Guide

Before You Install


Create a backup copy of the server where the Microsoft Dynamics SL applications are stored. This includes all custom Crystal Reports so that they can be restored after you are finished installing this release. In addition, export all screen customizations and store the export file in a safe location before you begin the installation. For more information, see Export Customizations in this topic. Important: Microsoft Dynamics SL (formerly Microsoft Business SolutionsSolomon) version 4.10 or a later version is required in order to update directly to release 2011. If you currently use a version that is earlier than 4.10, contact a Microsoft Certified Partner for information about how to upgrade your environment to version 4.10 so that you can install this release. To verify the Microsoft Dynamics SL version currently installed, see Which Microsoft Dynamics SL edition should I install? on page 7 of the Preinstallation Checklist.

Export Customizations
Always export your screen customizations before you upgrade to a new release of Microsoft Dynamics SL. This action is required before you upgrade. Before you remove your earlier Microsoft Dynamics SL installation, follow these steps: Use Customization Managers Export Customizations (91.500.00) to export all screen customizations (see the Customization Manager Help or users guide for more information). Export each customization to a separate export (.cst) file, and then save the export files for later use. Use the integrated development environment (VBA IDE) to export all Visual Basic for Applications (VBA) customizations. See the Customization Manager Help or users guide for more information.

Upgrading an Existing Installation

71

Removing an Existing Installation


Note: Make Sure That You perform a system backup before you follow these steps. In addition, remove the Microsoft Dynamics SL client from all workstations before you remove Microsoft Dynamics SL from the server. Also, if your Delta.mnu file is customized, create a backup folder that is not under the SL folder and put 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 Preinstallation Checklist on page 5, you were instructed to remove any earlier installation of Microsoft Dynamics SL (release 4.x or a later version) from all client workstations and from the server where it is installed before you start to install Microsoft Dynamics SL 2011. Otherwise, Setup will require you to do this but will start the removal only on the server before it starts the installation process. If you missed those steps, you can perform them now.

Removing Workstation Computer Components


To remove all Microsoft Dynamics SL client files from each workstation:
1. Close Microsoft Dynamics SL and all Windows-based applications. 2. Open Control Panel, and then open Programs and Features. 3. On the list of currently installed programs, click the entry for the Microsoft Dynamics SL client that is currently installed on the computer. The name of this entry depends on the release that is installed. Example: The name of the entry for a 7.0 installation is Microsoft Dynamics SL 7.0 Client. 4. Click Remove, Change/Remove, or Uninstall. 5. Click Yes to confirm that you want to completely remove the client and all its components. 6. Click Yes if you are prompted to remove Visual Basic for Applications. 7. Click Yes To All if you are prompted to remove shared components, and then click Yes if you are prompted to confirm your response. 8. Click OK to respond to the message that the client files were uninstalled successfully. 9. Click OK if you are prompted to restart your computer. Note: The following features are not automatically uninstalled and must be manually uninstalled. Microsoft Visual Studio Tools for Office (VSTO) See Microsoft.Dynamics.SL.OutlookAddin on page 62. SQL Server 2008 R2 Native Client Remove by using Programs and Features Microsoft SQL Server System CLR Types Remove by using Programs and Features

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:


1. Close Microsoft Dynamics SL and all Windows-based applications. 2. At the server where Microsoft Dynamics SL is installed, open Control Panel, and then open Programs and Features. 3. If you installed the client components for Microsoft Dynamics SL, Microsoft Business Solutions Solomon, or Solomon IV, you must remove them before uninstalling the server components. See Removing Workstation Computer Components earlier in this topic for instructions.

72

Installation Guide

4. After the client components are removed, select your installation of Microsoft Dynamics SL, Microsoft Business SolutionsSolomon, or Solomon IV from the list of currently installed programs, and then click Remove, Change/Remove, or Uninstall. The InstallShield Wizard Welcome window appears. 5. If you are prompted to remove Visual Basic for Applications, click Yes. 6. If you are prompted to remove a shared file, click Yes To All and confirm your selection if it is necessary. 7. When the uninstall process is complete, click Finish. 8. View your file system to make sure that the SL, Solomon, or SolIV folder (in the Program Files folder) was removed. If it still exists, delete it. 9. Restart your computer.

Removing Doc Share Web Service


If it is installed, uninstall Microsoft Dynamics SL Doc Share Web Service from the Windows SharePoint Services Server.

Upgrading an Existing Installation

73

Installing Microsoft Dynamics SL


The procedure for installing this release is the same for upgrade installations as it is for new installations. See Installing Microsoft Dynamics SL on page 14 for instructions. When the Microsoft Dynamics SL Setup program is finished, continue the upgrade process in the topics that follow.

74

Installation Guide

Updating Databases
Before you update databases for use with Microsoft Dynamics SL, make sure that you first upgrade your version of Microsoft SQL Server to SQL Server 2008 Standard or Enterprise Edition or SQL Server 2008 R2 Standard or Enterprise Edition. To obtain an upgrade, contact a Microsoft Certified Partner. Important Points: Back up the system and application databases. If you need help, see Knowledge Base article 916090 or see SQL Server Books Online for the SQL Server version that you are using. Do this before you begin the following procedure. Before upgrading your databases, export the Microsoft Dynamics SL customizations to a .cst file, and then import the file into the upgraded database. See the Customization Manager Help or users guide for information about how to export and importing .cst files. It is also a good idea to print the code associated with the customization by 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. Then it 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, you must verify that these changes are still in place after the update to Microsoft Dynamics SL 2011 is completed. 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 SLMenuItem records for use with the new menu system.

Database Maintenance (98.290.00) can update databases based on two scenarios: 6.5x, 7.x to 2011 4.1x/4.2x/4.5x/5.x/6.0x to 2011.

Upgrading an Existing Installation

75

To update Microsoft Dynamics SL databases:


1. Start SQL Server Services if they are stopped. See SQL Server Books Online for your SQL Server release for help. 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. If you need help, see Knowledge Base article 916090 or see SQL Server Books Online for the SQL Server version that you are using. 4. In Control Panel, select Administrative Tools, and then click Microsoft Dynamics SL Database Maintenance. Database Maintenance (98.290.00) appears.

Figure 66: Database Maintenance (98.290.00)

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

76

Installation Guide When the status bar at the bottom of the screen indicates that the instance of SQL Server connected successfully, click the Update Databases tab. Note: In Databases, the application databases are automatically selected for you.

Figure 67: Database Maintenance (98.290.00), Update Databases tab

8. Select the system database name from the System Database Name list. 9. In Update Scenario, notice that the correct scenario was selected by default based on the system database name that you selected. 10. Click Update Database to apply the update to the selected databases. The Authentication dialog box appears.

Figure 68: Authentication

Upgrading an Existing Installation 11. Select an authentication mode, and then click OK. We strongly recommend that you select Windows authentication to help provide the most secure system. For more information about authentication modes, see Considering whether to change the database authentication mode on page 106. If you selected SQL Server Authentication, Security appears.

77

Figure 69: Security

12. Click Yes to confirm your selection and continue. 13. Follow the steps that apply to the authentication method that you selected. If you selected Windows Authentication: a.) SYSADMIN Windows User Name appears and displays the domain and user name of the default system administrator.

Figure 70: SYSADMIN Windows User Name

b.) Make changes as needed. If you change the Windows user name and do not want to give the Windows user whom you designate the ability to create new SQL Server users and logins, clear the Grant this user permission to create SQL Server logins and users check box. By default, the check box is selected. Clearing the check box implies that the database administrator will generate SQL Server users and logins manually by using SQL Server tools. Note: If Microsoft Dynamics SL is running on a network, the user name that you enter here must be associated with the networks domain name. You can associate a Windows user name with a network domain name in Windows User Name in System Managers User Maintenance (95.260.00) screen to create an additional administrator. A user whom is defined as an administrator automatically has access to all screens and reports within Microsoft Dynamics SL. An administrator becomes a member of

78

Installation Guide the SQL Server SYSADMIN server role if the Grant this user permission to create SQL Server logins and users check box is selected. c.) Click Ok. The database update process starts. d.) Go to Step 14 to continue. If you selected SQL Server Authentication: a.) SQL Master80 Login appears if the Master80 user does not exist. If the Master80 user exists, Login appears. Go to Step b to continue.

Figure 71: SQL Master80 Login

Type a Password for the Master80 user that satisfies the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide. In Confirm Password, type the password again. b.) Click Ok. The SYSADMIN Login dialog box appears. See step c. c.) Login appears if the Master80 user exists.

Figure 72: Login

1. In the Password box, type the password that was created for the Master80 user when your databases were generated. 2. Click OK. Go to Step d to continue.

Upgrading an Existing Installation d.) Next, SYSADMIN Login appears.

79

Type a Password for the SYSADMIN user that satisfies the strong password requirements that are listed in the dialog box. For more information about strong passwords, see the Microsoft Dynamics SL Security Guide.

Figure 73: SYSADMIN Login

e.) In the Confirm box, type the password again. f.) Click OK. Default Password appears.

Figure 74: Default Password

g.) Follow the instructions to enter a default user password in the Password box. The password must satisfy the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide. h.) In Confirm Password, type the password again. i.) Click Ok. The database update process starts.

80

Installation Guide

14. When the update is complete, the 9829000 message box appears. Click OK.

Figure 75: 9829000 message

Note: If the update was unsuccessful, you will not see this message. Instead, a database update failure message appears. 15. In Database Maintenance (98.290.00), click Close. 16. Review the Dbbuild.log file. A successful database update results in a zero-byte Dbbuild.log file that contains only the start times and the end times for the process. If Dbbuild.log contains other text, contact Support Services for help. For more information about where you can find the Dbbuild.log, see Event Log Location Changes Required on page 23. For more information about how to contact Support Services, see Appendix D: Getting Support on page 113. 17. Follow the instructions in Using Database Update after Completing the Database Maintenance Scenario on page 82 to continue the database update process. 18. Repeat this process for each remaining system database and its related application databases.

Upgrading an Existing Installation

81

Prepare SQL Server 7.0 Databases to Run With The Latest Release
The Prepare SQL Server 7.0 Databases to Run With The Latest Release scenario is required to make sure that Microsoft Dynamics SL databases created in a SQL Server 7.0 environment are ready for use with the latest release of Microsoft SQL Server. Before you run a database update scenario, make sure that you have upgraded the computer that is running Microsoft SQL Server to a supported version of Microsoft SQL Server for use with Microsoft Dynamics SL. See Updating Databases on page 74 for more information. Note: Do not run the Prepare SQL Server 7.0 Databases to Run With The Latest Release scenario if you have not upgraded from SQL Server 7.0. If you have to use this scenario, run it after you have upgraded the SQL Server 7.0 databases to a supported version of Microsoft SQL Server for use with Microsoft Dynamics SL and after you have run the scenario to upgrade the databases for Microsoft Dynamics SL 2011. After you have upgraded the databases to a supported release of Microsoft SQL Server 2005 for use with Microsoft Dynamics SL and to Microsoft Dynamics SL 2011, prepare the databases. 1. In the Windows Control Panel, select Administrative Tools and then Microsoft Dynamics SL Database Maintenance. Database Maintenance (98.290.00) appears. 2. Click the Update Databases tab. 3. In Update Scenarios, click Prepare SQL Server 7.0 Databases to Run With The Latest Release. 4. Click Update Database. This process takes a short time and lets Microsoft Dynamics SL access the databases on the Microsoft SQL Server database server.

82

Installation Guide

Using Database Update after Completing the Database Maintenance Scenario


After you complete a database maintenance scenario (see Updating Databases on page 74), 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 by 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 as a user who has system administrator rights. 3. In the Microsoft Dynamics SL navigation pane, click Administration. 4. In the System Manager details pane, under Utilities, click Database Update. Database Update (98.100.00) appears. 5. In the Directory box, browse for \SL\DB\csvs. 6. In the Files box, select messages.msg, pvrec.csv, and rptcontrol.csv by clicking them. You do not have to hold down the CTRL key or SHIFT key. 7. Click Begin Processing. 8. Click OK when the process is completed. 9. Repeat step 1 through step 8 for each additional system and application database combination. 10. Close Database Update (98.100.00). 11. Back up the system and application databases. If you need help, see https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb$EN-US$916090 or see SQL Server Books Online for the SQL Server version that you are using. Your databases are ready to use. To install other applications that provide additional functionality to Microsoft Dynamics SL, see Installing Supporting Applications on page 42.

Upgrading an Existing Installation

83

Conversion Procedure for Order Management


The conversion procedure outlined here 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 improvement. If you do not perform the conversion procedure, existing open orders will be replanned incorrectly. This causes shipper creation to occur earlier than it should. Note: You only have to do this conversion one time. It does not have to be done with the next upgrade. If you do not perform the conversion before you run Process Manager (40.990.00), you must put the original sales orders on administrative hold and cancel the shippers that were created before you follow these steps. 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 before the upgrade. The back order visibility quantities on a shipper depend on snapshot information from the sales order at the time of shipper creation. Therefore, shippers that are created after the conversion will have accurate back order visibility quantities. Reports were changed to print the back order quantities. Therefore, back order quantities for open shippers created before 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. Click to 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. Close OM Integrity Check (40.990.00) after the process is completed. 5. Open Process Manager (40.400.00) and then 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 improvement, 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).

84

Installation Guide

Updating Client Workstations


To update Microsoft Dynamics SL client workstations:
On each workstation you update, you must log on as the local administrator or as a member of the local Administrators group. This is required. Failure to do this causes problems in the setup. Note: If you are using Active Directory, you must log on as a member of the Domain Administrators group, that in turn must be part of the local Administrators group. 1. Map a network drive to the shared folder on the server where the Microsoft Dynamics SL programs are installed. For example, if the software is installed in C:\Program Files\Microsoft Dynamics\SL\Applications, you would map to the shared SL folder. 2. To start the client setup, run Setup.exe from the \WRKSTN folder on the server where Microsoft Dynamics SL is installed. Note: If Setup detects an existing client installation, it requires you to remove it before continuing. If existing databases must be made compatible with this Microsoft Dynamics SL release, see Upgrading an Existing Installation on page 69.

3. Client Setup may prompt you to install the Visual Studio Tools for Office.

Figure 76: InstallShield Wizard, Visual Studio Tools for Office

Click Install. For more information about Visual Studio Tools for Office, see Microsoft.Dynamics.SL.OutlookAddin on page 62.

Upgrading an Existing Installation

85

Welcome appears and advises you to exit other Windows-based applications before you continue.

Figure 77: Welcome

4. Click Next. Choose Destination Location appears.

Figure 78: Choose Destination Location

5. Click Next to accept the path that appears. If no path appears, click Browse and open by using the mapped network drive to the shared folder where the Microsoft Dynamics SL application files are located.

86

Installation Guide Start Copying Files appears and displays the disk space that is required to complete the installation. If you selected to install the Microsoft Dynamics SL SDK, you see the SDK Information note.

Figure 79: Start Copying Files

6. Click Next to start Setup. 7. After the Setup program is finished installing files, View Readme File appears and asks whether you want to review the ReadMe.txt file. Click Yes. 8. Review the ReadMe.txt file on the screen, or click File | Print to print it.

Upgrading an Existing Installation Close the file by closing Notepad. InstallShield Wizard Complete appears and asks whether you want to restart the computer now.

87

Figure 80: InstallShield Wizard Complete

9. Click Finish to restart immediately (strongly recommended).

88

Installation Guide

Updating Custom Crystal Reports


Crystal Reports 2008 SP3 and Crystal Reports 2008 SP3 Fix Pack 3.1 are included with this release. Most of the standard reports for the application modules were created in this version of Crystal Reports. It is not always necessary to upgrade your Crystal report files. However, for optimal performance, we recommend that you upgrade your custom reports to Crystal Reports 2008. There are some instances where the implementation of custom reports must be upgraded to work with Microsoft Dynamics SL 2011 and Crystal Reports 2008. These instances involve the modification of the report's record selection criteria or "Where" clause outside the Report Designer. Modifications to the report's record selection criteria must now be in Crystal syntax and no longer in TSQL, as it was in versions earlier than Microsoft Dynamics SL 2011. The report files do not have to be changed, but how you run the files does have to change. There are three locations where the report's record selection criteria or "Where" clause can be changed outside the Report Designer. The ROI Command Line A TSQL Preprocess A Microsoft Dynamics SL SDK Preprocess

If your custom report implementation uses any of these three methods, you have to change the implementation so that the "Where" clause uses Crystal syntax. Before you update your reports, see the Appendix A: Converting Custom Reports to Crystal Reports 2008 section in the Reporting Guide users guide or Help (ReportingGuide.pdf). For help changing the syntax for custom reports, see the Additional Information topic in the same appendix.

Upgrading an Existing Installation

89

Updating Microsoft Dynamics SL Doc Share Web Service


Microsoft Dynamics SL SharePoint Web Service replaces Microsoft Dynamics SL Doc Share Web Service. If you have not uninstalled Microsoft Dynamics SL Doc Share Web Service, uninstall it from the Windows SharePoint Services Server. For detailed steps on installing Microsoft Dynamics SL SharePoint Web Service, see Microsoft Dynamics SL SharePoint Web Service on page 58.

90

Installation Guide

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:
1. Close Microsoft Dynamics SL and all Windows-based applications. 2. Open Control Panel, and then open Programs and Features. 3. On the list of currently installed programs, click the Microsoft Dynamics SL 2011 entry to select it, and then click Change. The InstallShield Wizard Modify, repair, or remove the program window appears.

Figure 81: InstallShield Wizard Modify, repair, or remove the program

Upgrading an Existing Installation 4. Select Modify, and then click Next. Select Microsoft Dynamics SL Applications appears.

91

Figure 82: InstallShield Wizard Select Microsoft Dynamics SL Applications

5. Select the modules that you want to install, and then click Next. 6. Continue with the installation steps. See Installing Microsoft Dynamics SL on page 73 if you need help.

92

Installation Guide

Troubleshooting

93

Troubleshooting
Repairing a Microsoft Dynamics SL Installation
You can 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 the General Ledger executable files and reports will be replaced with versions matching the executable files and reports from the installation package.

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


1. Close Microsoft Dynamics SL and all Windows-based applications. 2. Open Control Panel, and then open Programs and Features. 3. On the list of currently installed programs, click the entry for Microsoft Dynamics SL Client, and then click Change/Remove or Change. The InstallShield Wizard Modify, repair, or remove the program window appears.

Figure 83: InstallShield Wizard - Repair the Microsoft Dynamics SL client installation

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

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


1. Close Microsoft Dynamics SL and all Windows-based applications. 2. Open Control Panel, and then open Programs and Features.

94

Installation Guide

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

Figure 84: InstallShield Wizard - Repair the Microsoft Dynamics SL installation

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

Troubleshooting

95

Restoring System Database Table Views


Two issues 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 your database administrator.

To restore the system database table views:


1. Open the Windows Control Panel. 2. Double-click Administrative Tools, and then double-click Microsoft Dynamics SL Database Maintenance. Database Maintenance (98.290.00) appears.

Figure 85: Database Maintenance (98.290.00)

3. On the Connect Server tab, type the Destination SQL Server Name. 4. 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. 5. Click Connect to connect to the instance of SQL Server.

96

Installation Guide

6. Click the Update Databases tab. Be aware that in Databases, the application databases are automatically selected for you.

Figure 86: Database Maintenance (98.290.00), Update Databases tab

7. In the System Database Name list, click your system database name. 8. Click Update Views to update the views in the selected application databases. 9. Click OK. 10. Click Close.

Troubleshooting

97

Technical Resources
Section Contents
Terminology Definitions Key terms that are used in Microsoft Dynamics SL. Technology Tidbits Foundational changes appearing in this release. Backup and Restore Procedures Processes used to back up and restore to databases of the same or different names. Solomon.ini How the Solomon.ini file is used.

Terminology Definitions
View A view is an alternative way to examine data in one or more tables. Microsoft Dynamics SL uses database views in many reports to simplify the multi-company or inter-company implementation. To continue the company metaphor, we view the system databases 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 for user-declared variables, conditional execution, and other powerful programming features. The software uses stored procedures to perform tasks such as database navigation and possible values lookups. Proper Order of Rebuild If a view is incorrect or dropped because of an error, the proper order of rebuild is the correct way to re-create the view and the underlying components on which the view depends. Backup/Restore Backup/restore is the making a physical backup copy of a database and later restoring the database from the backup to the computer system. Backup/restore implements the standard Microsoft SQL Server Backup and Restore utility programs. 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 that is used by the server and workstation and is also the standard Internet Protocol (IP). 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 suitable protocols on the workstation and the server. The protocols on both computers 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 companys financial data is stored. Because companies can have

98

Installation Guide

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. Predefined companies exist within the demo databases included in the Microsoft Dynamics SL installation package. These databases are built from the \Microsoft Dynamics\SL\Applications\DB\demo folder that contains the following databases:
Company 0010 0020 0060 0070 0080 0051 Application Database Name SLDemoApp10 SLDemoApp10 SLDemoApp60 SLDemoApp60 SLDemoApp60 DemoStandardApp51

The system database Company table stores the relationship of the company to the application database. If you back up company records and then restore them by using a different database name, the records will no longer be available. Backup and restore procedures are discussed later.

AcctXRef Record
To simplify account, subaccount, and company information cross-referencing, the software uses a table named 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 alternative way to view records or multiple records in single or multiple databases. When you create custom reports, it is good practice to implement views to simplify reporting, advanced features, functionality, and performance. Consider how views are used: Reports Most Microsoft Dynamics SL reports are based on views. Therefore, if you want additional fields on a report, you must also make the modifications in the view used by that report. Advanced features and functionality Views are used by multi-company or inter-company implementations to simplify viewing the system database 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 run in the workspace on the computer that is running SQL Server. This saves significant time when you run lengthy processes. Processes can run from 10 to 100 times faster with using this methodology.

Note: If you must re-create database views, certain activities must occur to complete the process. This occurs because of the nature of the company metaphor throughout the database. For more information, see Appendix A: SQL Server Optimization Notes on page 103.

Backup and Restore Procedures


Regular database backups and periodic testing of the restore process are strongly recommended. Backing up databases and restoring them to their original names should not present problems or 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 it is not handled correctly. This results from the tracking of application databases by the Company table in the system database. For example, suppose that a company configuration looks as follows:

Troubleshooting

99

Company 0010 0020 0060 0070 0080 0051

Original application database name SLDemoApp10 SLDemoApp10 SLDemoApp60 SLDemoApp60 SLDemoApp60 DemoStandardApp51

New application database name NEWAPPDB NEWAPPDB

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 statement in SQL Server Management Studio against the system database:
UPDATE Company SET DatabaseName = 'NEWAPPDB' WHERE CpnyID IN ('0010','0020')

Problems result when views in a database no longer point to valid database names. For example, this can occur when a snapshot of a database is used for testing or reporting or if a system database backup is restored to a different system database name. 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, select the new system database (NEWSYSDB) from the database list. 4. Run 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 You select the correct database from the SQL Server Management Studio database list before you run these statements.

100

Installation Guide

If you are restoring to a different computer, use the following procedure.

To run the Synchronize All Ownership & Security update scenario in Database Maintenance (98.290.00) and rebuild the database views:
1. In Control Panel, select Administrative Tools and then Microsoft Dynamics SL Database Maintenance. Database Maintenance (98.290.00) appears.

Figure 87: Database Maintenance (98.290.00)

2. On 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. 4. Click Connect to connect to the instance of SQL Server.

Troubleshooting 5. Click Update Databases. Note: In Databases, the application databases are automatically selected for you.

101

Figure 88: Database Maintenance (98.290.00), Update Databases tab

6. In the Update Scenarios area, select Synchronize All Ownership & Security. Because this scenario processes all system and application databases on the connected server, you do not have to select system or application databases. 7. Click Update Database. This process will update each system databases 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, select your system database name. 10. Click Update Views. 11. Click OK, and then click Close.

Solomon.ini
Microsoft Dynamics SL uses the Solomon.ini file to save workstation-computer specific information, such as the last database to which the user logged on, printer preferences, and other settings. The Solomon.ini file is divided into sections, and the section headings are enclosed in double brackets [ ]. Each section performs its own characteristic functions. For example, the [Company] section stores local company logon information. Under each section are several settings that control the workstations options.
[Company] Company section CompanyID=0010 default CompanyID setting UserID=SYSADMlN default UserID setting

The Solomon.ini file is specific to the local workstation computer and Windows user. The file is stored in the local users application data directory. If a setting or section is not found in the Solomon.ini file, the program looks in alternative locations. The behavior occurs in the following order: 1. Microsoft Dynamics SL looks for the Solomon.ini file in \Users\<UserID>\AppData\Local\Microsoft Dynamics SL

102

Installation Guide

2. If the Solomon.ini file does not exist, Microsoft Dynamics SL creates the file with the basic sections. These sections are [System32 Database] and [Company]. 3. For sections that Microsoft Dynamics SL does not find locally, the program looks in the Solomon.ini file in Microsoft Dynamics SL installation folder on the server. 4. If a setting is not found in the local Solomon.ini file, it is obtained from the servers Solomon.ini file. Sections and settings in the local Solomon.ini override the same sections and detail settings 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 servers file. See Appendix A in the System Manager Help or users guide for more information about the Solomon.ini settings.

Appendixes

103

Appendixes
Appendix A: SQL Server Optimization Notes
This Appendix presents information about how to install and set up Microsoft SQL Server to operate with Microsoft Dynamics SL.

Supported Microsoft SQL Server Versions


This Microsoft Dynamics SL release supports the following versions of Microsoft SQL Server: Microsoft SQL Server 2008, Standard or Enterprise Edition Microsoft SQL Server 2008 R2, Standard or Enterprise Edition

Microsoft SQL Server must be purchased separately. Contact a Microsoft Certified Partner for help.

Microsoft SQL Server 2008


For an application user, the interface between SQL Server and Microsoft Dynamics SL remains unchanged. The underlying SQL server database is optimized for performance and usability. Microsoft SQL Server must be installed to run in SQL Server and Windows authentication mode. This setting can be made during or after you install SQL Server.

104

Installation Guide

To set SQL Server and Windows authentication mode after SQL Server installation:
1. In SQL Server Management Studio, connect to the database server. 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, and then click Properties. Server Properties appears.

Figure 89: Server Properties

3. Click Security. 4. Under Server authentication, click SQL Server and Windows Authentication mode. 5. Click OK, and then close SQL Server Management Studio.

Appendixes

105

To set dynamic and reserve memory:


1. In SQL Server Management Studio, connect to the database server. 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, and then click Properties. Server Properties appears.

Figure 90: Server Properties

3. Click Memory. 4. The default setting Minimum server memory (in MB) to zero MB. Do not change this setting. 5. Set Maximum server memory (in MB) based on the following guidelines:
Server Memory 128 MB 256 MB 512 MB 1 GB 1.5 GB 2 GB SQL Server Memory 100 MB 205 MB 410 MB 820 MB 1230 MB 1640 MB

6. Click OK. 7. Ask all SQL Server users to log off so that SQL Server services can be stopped and restarted safely. 8. Stop and restart the SQL Server services. 9. Close SQL Server Management Studio.

106

Installation Guide

Appendix B: Changing the Database Authentication Mode


Considering whether to change the database authentication mode
You may want to change the database authentication mode if you accidentally chose the wrong authentication mode originally or you are upgrading from previous release of Microsoft Dynamics SL that contained only the SQL Server Authentication option. Warning: If you move from SQL Server authentication to Windows authentication, you must open System Managers User Maintenance (95.260.00) and add a Windows domain\user name for each Microsoft Dynamics SL user. This authentication change does not affect groups.

To change the database authentication mode later


1. Start SQL Server Services if they are stopped. For more information, see SQL Server Books Online for your SQL Server release. Note: Because Microsoft Dynamics SL Setup may have to update files that are used by other programs or services, it is important to complete this step before you start the installation. Remember to restart the SQL Server Agent service when you restart SQL Server. If SQL Server Agent does not restart, any backups or other jobs scheduled in SQL Server will not run.

2. In SQL Server Management Studio, connect to the database server as an administrator (sa or a user who is a member of the SYSADMIN server role). 3. Back up the system and application databases. If you need help, see Knowledge Base article 916090 or see SQL Server Books Online for the SQL Server version that you are using. 4. In Control Panel, select Administrative Tools and then Microsoft Dynamics SL Database Maintenance. Database Maintenance (98.290.00) appears.

Figure 91: Database Maintenance (98.290.00), Connect Server tab

5. On the Connect Server tab, type the Destination SQL Server Name.

Appendixes

107

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. When the status bar at the bottom of the screen indicates that you are connected to the instance of SQL Server, click the Update Databases tab. Note: In Databases, the application databases are automatically selected for you.

Figure 92: Database Maintenance (98.290.00), Update Databases tab

8. In the System Database Name list, select the appropriate system database. 9. Click Set Authentication Type. Authentication appears.

Figure 93: Authentication

10. Select an authentication method, and then click Ok. Windows authentication is recommended. 11. Follow these steps that apply to the authentication method that you selected.

108

Installation Guide If you selected Windows Authentication: a.) SYSADMIN Windows User Name appears and displays the domain and user name of the default system administrator.

Figure 94: SYSADMIN Windows User Name

b.) Make changes as needed. If you change the Windows user name and do not want to give the individual you designate the ability to create new SQL Server users and logins, clear the Grant this user permission to create SQL Server logins and users check box. By default, the check box is selected. Clearing the check box implies that the database administrator will generate SQL Server users and logins manually by using SQL Server tools. See Appendix C: Creating SQL Server Users and Logins on page 111 for help setting up SQL Server users and logins manually. Note: A user whom is defined as an administrator automatically has access to all screens and reports within Microsoft Dynamics SL. An administrator becomes a member of the SQL Server SYSADMIN server role if the Grant this user permission to create SQL Server logins and users check box is selected. c.) Click OK. The authentication mode change process starts. If you selected SQL Server Authentication: a.) Security appears.

Figure 95: Security message

Appendixes b.) Click Yes to confirm your selection and continue. SQL Master80 Login appears if the Master80 user does not exist. If you have already created the Master80 user, see step f.

109

Figure 96: SQL Master80 Login

c.) Type a Password for the Master80 user that satisfies the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide. d.) In Confirm Password, type the password again. e.) Click Ok. SYSADMIN Login appears.

Figure 97: SYSADMIN Login

f.) In the SYSADMIN Login dialog box, type the password for the SYSADMIN user. This password must satisfy the strong password requirements that are listed in the dialog box. Note: For more information about strong passwords, see the Microsoft Dynamics SL Security Guide. g.) In Confirm, type the password again, and then click Ok.

110

Installation Guide If you created the Master80 user in Step b, the authentication mode change process starts. See step 12. Login appears if the Master80 user was created before you began these steps.

Figure 98: Login

h.) In the Password box, type the password that was created for the Master80 user when your databases were generated, and then click OK. The authentication mode change process starts. 12. When the process is complete, the 9829000 message box appears, and the status bar at the bottom of the Database Maintenance (98.290.00) window indicates that the authentication change was successful.

Figure 99: 9829000 - Process complete message

Note: When an authentication change is unsuccessful, you will not see this message. Instead, a failure message appears and directs you to view the Dbbuild.log file. For more information about where you can find the Dbbuild.log, see Event Log Location Changes Required on page 23. For more information about how to contact Support Services, see Appendix D: Getting Support on page 113. 13. Click OK. 14. Review the Dbbuild.log file.

Appendixes

111

Appendix C: Creating SQL Server Users and Logins


To create SQL Server users and logins manually, the database administrator must perform the following tasks by either by using the steps or by running the SQL statements that are provided. These procedures will help to ensure that the minimum database rights requirements are met and Microsoft Dynamics SL functions correctly.

To create SQL Server users and logins manually:


1. Create SQL Server security logins. a.) In SQL Server Management Studio, expand the Object Explorer tree. b.) Expand Security, and then right-click Logins. c.) Click New Login. Login New appears. d.) Add the Windows authenticated user or global domain security group. e.) Click OK. Or Type the following statement in a query window:
Create Login [domain\name] from windows

Replace Domain with the name of the domain where SQL Server exists. Replace Name with the user name or global domain security group name that is granted the permissions. 2. Grant database connect permissions. a.) In the Object Explorer tree, expand Databases. b.) Expand the Microsoft Dynamics SL database node. c.) Expand Security. d.) Right-click Users, and then click New User. e.) Type the User Name and Login Name of the new user or global domain security group. f.) Click OK Or Type the following statement in a query window:
Create User [domain\name] for login [domain\name]

Replace Domain with the name of the domain where SQL Server exists. Replace Name with the user name or global domain security group name to which you will grant database access permissions. This only grants access to view objects in the database, not to access the objects or data. 3. Grant database pre-login permissions. a.) In the Object Explorer tree, expand Databases. b.) Expand the Microsoft Dynamics SL system database node. c.) Expand Security, expand Roles, and then expand Database Roles. d.) Right-click MSDynamicsSL, and then click Properties. e.) On the General tab, under Members of this role, click Add. f.) In Select Database User or Role, type the name of the user or global domain security group, or click Browse to find it. g.) Click OK. Or Type the following statement in a query window:
sp_addrolemember 'MSDynamicsSL', 'domain\name'

112

Installation Guide Replace Domain with the name of the domain where SQL Server exists. Replace Name with the user name or global domain security group name to add as a member of this role. Add to this role the name of the group that holds the Microsoft Dynamics SL users or each Windows user name to grant access to select or run required objects in the database during the Microsoft Dynamics SL pre-login process.

4. To grant Microsoft Dynamics SL administrators permission to access the databases and perform administrative tasks, enter the following statement in a query window:
sp_addrolemember 'db_owner', 'domain\name'

Run the command for each Microsoft Dynamics SL system database and application database. Example:
use SLSystemDatabase GO sp_addrolemember 'db_owner', 'domain\name' GO use SLApplicationDatabase GO sp_addrolemember 'db_owner', 'domain\name' GO

Appendixes

113

Appendix D: Getting Support


Various support plans are available that provide the exact product support that you want for your Microsoft Dynamics SL installation: Local support through a Microsoft Certified Partner Support by mail from Support Services Electronic Microsoft Support access (fax, email, web-based) Telephone support, including priority telephone support plans CustomerSource at www.microsoft.com/dynamics/CustomerSource Visit www.microsoft.com/dynamics/support for the latest details on these professional support services

Important Telephone Numbers and Internet Addresses


Microsoft Dynamics Fax Microsoft Support Telephone Internet Training/Seminars 800-456-0025 U.S. and Canada 701-281-6500 Worldwide 425-936-7329 include email alias of addressee Guaranteed and Premium Support clients only 888-477-7877 www.microsoft.com/dynamics Telephone 800-476-5666 Fax 425-936-7329 include ATTN: Microsoft Dynamics University, mbsuniv@microsoft.com Telephone 800-476-5666 Fax 425-936-7329 To view your software registration information, visit the CustomerSource Product and Service Summary webpage. To submit an order inquiry or request information about your account, visit the CustomerSource New Service Request webpage.

Product Registration

114

Installation Guide

Index

115

Index
A
Active Directory 84

M
messages file location 23 messages file location, Windows 23 Microsoft Dynamics SL application files location 24 Microsoft Dynamics SL event log location 23 Microsoft Dynamics SL installation package contents 7 Microsoft SL SDK 9 Microsoft SQL Server installing 25 optimizing 98 recommended protocols 97 version 9, 103 Microsoft Support telephone numbers 113 website URL 113

C
Company record 97 computer name 6

D
database demo 8 updating, important points 74

E
edition Advanced Management 7 Business Essentials 7 determining whicdecidenstalled 7 Professional 7 Standard, Multi-User 7 Standard, Single-User 7

O
operating systems 1 optimizing Microsoft SQL Server 98 options, installation setup 11

G
getting ready to install 6

P
protocols for Microsoft SQL Server 97

I
Installashows youalling from 14 Installation package contents 7 installing Crystal Reports 43 Microsoft SL SDK 9 Microsoft SQL Server 25 new Microsoft Dynamics SL installations 13

R
record Company 97 removing Crystal Reports earlier version 42

S
setting SQL Server and Windows Authentication mode 104 setting up client workstations from a shared directory 65 Microsoft Dynamics SL on a singleuser workstation 68 Microsoft Dynamics SL options 11 signing in 39 Solomon.ini and other profile locations 23 SQL Server version 9 supported environments 1

K
key terms 97

L
logging on 39

116

Installation Guide

T
technical resources foundational changes 97

U
uninstalling Crystal Reports earlier version 42 update prerequisites 70 updating databases, important points 74

V
version, Microsoft SQL Server 9

W
Windows messages file location 23 Microsoft Dynamics SL application files location 24 Microsoft Dynamics SL event log location 23 Solomon.ini location 23 workstation setting up the client from a shared directory 65 single-user Microsoft Dynamics SL client 68