Installation Guide: Release 2018 CU1

Installation Guide
Release 2018 CU1

Disclaimer
This document is provided “as-is”. Information and views expressed in this document, including
URL and other Internet Web site references, may change without notice. You bear the risk of
using it.
Some examples are for illustration only and are fictitious. No real association is intended or
inferred.
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.
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.
License agreement
Use of this software is covered by a license agreement provided with it. 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.
Copyright
© 2018 Microsoft Corporation. All rights reserved.
Publication Date
November 2018
Contents iii
Contents
Introduction 1
Audience ................................................................................................................................... 2
Installation Preparation 3
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 .......................................................................................... 15
Changes Needed for User Account Control .......................................................................... 18
Microsoft SQL Server Installation.......................................................................................... 20
Creating Databases ............................................................................................................... 21
Creating an Empty Database .................................................................................. 24
Creating a Demo Database ..................................................................................... 29
Creating an Additional Empty Application Database ............................................. 33
Logging On ............................................................................................................... 33
Preparing the Demo System and Application Databases ..................................... 35
Preparing the Empty System and Application Databases ..................................... 35
Installing Supporting Applications ......................................................................................... 37
Microsoft Dynamics SL Software Development Kit (SDK)..................................... 37
Microsoft Dynamics SL Legacy Controls ................................................................ 38
Microsoft Dynamics SL User’s Guides .................................................................... 38
Microsoft Dynamics SL Web Services and Web Apps ........................................... 39
Microsoft Dynamics Business Analyzer for Microsoft Dynamics SL ..................... 40
Microsoft Dynamics SL Data Mart Adapter for Management Reporter ................ 40
Microsoft Dynamics SL Outlook Add-in .................................................................. 41
.NET Framework....................................................................................................... 43
Setting Up Microsoft Dynamics SL on Workstations ............................................................ 44
Running Microsoft Dynamics SL from a Shared Directory on the Server ............. 44
Running Microsoft Dynamics SL from the Local Client Workstation .................... 44
Upgrading an Existing Installation 47

Overview ................................................................................................................................. 47
Before You Install ................................................................................................................... 49
Export Customizations ............................................................................................. 49
Removing an Existing Installation ......................................................................................... 50
Removing Doc Share Web Service ......................................................................... 50
Installing Microsoft Dynamics SL .......................................................................................... 51
Updating Databases .............................................................................................................. 51
Using Database Update after Completing the Database Maintenance Scenario 57
Updating Client Workstations ................................................................................................ 59
Updating Custom Crystal Reports ......................................................................................... 60
Updating Microsoft Dynamics SL SharePoint Web Service ................................................. 60
Adding Modules ..................................................................................................................... 60
Troubleshooting 61
Repairing a Microsoft Dynamics SL Installation .................................................................. 61
Restoring System Database Table Views ............................................................................. 62
Technical Resources .............................................................................................................. 64
Section Contents ..................................................................................................... 64
iv Installation Guide
Terminology Definitions ........................................................................................... 64

Technology Tidbits.................................................................................................... 64
Backup and Restore Procedures ............................................................................ 66
Solomon.ini ............................................................................................................... 69
Appendixes 71
Appendix A: SQL Server Optimization Notes ......................................................................... 71
Supported Microsoft SQL Server Versions ............................................................. 71
Microsoft SQL Server ............................................................................................... 71
Appendix B: Changing the Database Authentication Mode ................................................. 73
Considering whether to change the database authentication mode .................... 73
To change the database authentication mode later .............................................. 73
Appendix C: Creating SQL Server Users and Logins ............................................................. 78
Appendix D: Getting Support ................................................................................................. 80
Important Telephone Numbers and Internet Addresses ....................................... 80
Index 81
Introduction 1
Introduction
This guide provides instructions for installing Microsoft Dynamics® SL in the following
environments:
Operating System
• Microsoft Windows® 10 or later versions
• Windows Server® 2012 R2 or later versions
• Windows Server® 2016 or later versions
Microsoft SQL Server

• Microsoft SQL Server® 2014 or later versions, Standard or Enterprise Edition
Note:
• See the System Requirements for Microsoft Dynamics® SL 2018 CU1 and the System
Requirements for Microsoft Dynamics® SL 2018 Web Applications that are 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 Remote Desktop for Windows Server 2012 R2 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 or Microsoft® SharePoint® Server 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 user’s guide for information about Doc Share.
The following sections are included:
• 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.
2 Installation Guide
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.
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
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. UAC is enabled automatically, and implements a
protection level to help eliminate unwanted access by users and programs.
UAC does not affect the Microsoft Dynamics SL installation process. However, setup changes are
required when you use this security feature with Microsoft Dynamics SL. See “Changes Needed for
User Account Control” on page 18 for topics that explain how to set up a user’s 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 Upgrading an existing installation
❑ Perform the tasks on the Preinstallation ❑ Perform the tasks on the Preinstallation
Checklist. Some are optional, whereas other Checklist. Some are optional, whereas other
tasks are required. tasks are required.
❑ Perform a system backup of the server on which ❑ Export all screen customizations from the
you will install Microsoft Dynamics SL. earlier version.
❑ Perform a system backup of the database ❑ Perform a system backup of the server that
server. holds the Microsoft Dynamics SL applications.
❑ Install Microsoft Dynamics SL on the server that ❑ If your installation includes a customized
you have selected to hold the program files. Delta.mnu file, save a copy so that you can refer
to it after the installation is finished. The
Delta.mnu file was used in Microsoft Business
Solutions – Solomon 6.x and earlier versions.
❑ If you do not have Microsoft SQL Server and the ❑ Perform a database backup of the system and
required service packs already installed, install application databases.
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 ❑ Remove all existing Microsoft Dynamics SL
loading them with system data. clients from workstation computers.

❑ Install Management Reporter 2012 as follows: ❑ Remove Microsoft Dynamics SL Outlook Add-in
• MR 2012 server components from workstation computers.
• Configure the data integration
• MR 2012 client components
Installation documentation is included at the
following location:
https://mbs.microsoft.com/customersource/no
rthamerica/MR/downloads/service-
packs/MROverview
❑ Install Microsoft .NET Framework 4.5 on each ❑ Remove the existing Microsoft Dynamics SL
workstation computer. After the installation is installation from the server where it currently
complete, you must restart the computer before resides.
you install the Microsoft Dynamics SL client on
workstation computers.
To install the .NET Framework, see “.NET

Framework” on page 43.
❑ Install the Microsoft Dynamics SL client on ❑ Install Microsoft Dynamics SL on the server that
workstation computers. you have selected to hold the program files.
❑ If you currently run a version of Microsoft SQL
Server earlier than Microsoft SQL Server 2014,
perform the upgrade to a SQL Server version
that is supported for this release.
Update databases and prepare them for use by
loading them with system data.
❑ If a release of Management Reporter that is
earlier than version 2012 is installed, remove it
from the server and workstation computers.
Uninstallation documentation is included at the
following location:
packs/MROverview
❑ Install Management Reporter 2012 as follows:
• MR 2012 server components
• Configure the data integration
• MR 2012 client components
Installation documentation is included at the
following location:
packs/MROverview
Note: If you are moving from Microsoft FRx 6.7

to Management Reporter, you must install MR
2012 and then MR 2012 SP1. Use the
Management Reporter Migration Wizard to
migrate your reports. For detailed steps, see the
Migration Guide and Migration Best Practices
documents at the following location:
packs/MROverview
Note: Microsoft FRx 6.7 is not supported for use

with Microsoft Dynamics SL 2018 CU1.

❑ Install Microsoft .NET Framework 4.5 on each
workstation computer. After the installation is
complete, you must restart the computer before
you install the Microsoft Dynamics SL client on
To install the .NET Framework, see “.NET

Framework” on page 43.
❑ Install the Microsoft Dynamics SL client on
❑ If you have the Microsoft Dynamics SL Doc
Share Web Service installed, uninstall that from
the Windows SharePoint Services Server.
The Microsoft Dynamics SL SharePoint Web

Service (Microsoft.Dynamics.SL.Docshare.vb) is
replaced by the
Microsoft.Dynamics.SL.SharepointClient.dll
assembly. This DLL is installed automatically by
the Microsoft Dynamics SL client installation.
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:
• Microsoft .NET Framework 4.5 is a prerequisite for the Microsoft Dynamics SL client
installation. 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”
on page 43.
• Make sure that you determine whether your system meets the minimum configuration needs
before you install this release. The System Requirements for Microsoft Dynamics® SL 2018
CU1 and the System Requirements for Microsoft Dynamics® SL 2018 Web Applications that
are available for download from the CustomerSource website or the PartnerSource website.
They provide 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 must
have 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 Outlook Add-in
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 computer’s 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 Outlook
Add-in” on page 41.
Note: The add-in must be installed one time on each workstation computer by each user who
runs a screen on the workstation computer 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 Outlook Add-in” on page
41.
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.
❑ (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 you need
more space.
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
❑ Locate the Microsoft Dynamics SL 2018 CU1 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 Web Services, the Microsoft Dynamics SL user’s 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://mbs2.microsoft.com/voice/ 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 21 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 120 is the default for new and upgraded Microsoft
Dynamics SL databases.
• 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.
Empty Databases
_________________________________________ ❑ System ❑ Application
_________________________________________ Server (include path)
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.
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.
_____________________________________________
Which Microsoft SQL Server version do I have?

Microsoft Dynamics SL 2018 CU1 supports the versions of SQL Server listed in “Microsoft
SQL Server” on page 1. You must buy SQL Server separately. Contact a Microsoft Certified
Partner for help.
If you already have SQL Server installed, determine your version by using the SQL 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:
Software release
Supported products Product version and product level
SQL Server 2014 12.00.2000.8 SQL Server 2014
For more information about how to determine the Microsoft SQL Server version, see “How to
determine the version and edition of SQL Server and its components” at
http://support.microsoft.com/kb/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 60 for more information.
❑ You must log on as an 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.
❑ 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, 7.x, 2011, or
2015), you must export all screen customizations. The Export Customizations (91.500.00)
screen helps you to perform this task (see the Customization Manager Help or user's guide).
Make sure that you store the export file in a safe location.
You can also use the VBA Code window to export the customization’s Visual Basic code for
safekeeping (for more information, see “Export Customizations” on page 49). 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, 7.x, 2011,
2015), 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.
3. 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 50.
2. Click Remove or Uninstall.
❑ Uninstalling/Installing the Microsoft Dynamics SL Outlook add-in. If you installed an earlier
version of the Microsoft Dynamics SL Outlook Add-in, 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: Different from the client that must be uninstalled one time on each computer; each
user who ran a screen that works with email in the client must uninstall the add-in one time.
Before uninstalling the add-in, make sure that neither Outlook nor the Microsoft Dynamics SL
client are running. For information about how to uninstall the add-in, see ”Microsoft Dynamics
SL Outlook Add-in” on page 41.
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 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 2018 CU1 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 2018 CU1 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
2018 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 2018
CU1 in .pdf file format.
• View Readme — Opens the ReadMe.txt file.
Install
• Microsoft Dynamics® SL — Starts the installation process.
• Microsoft Dynamics® SL SDK — Starts the installation of CodeInspector, project templates,
Visual Basic DH files, and adds controls to the toolbox in Visual Studio.
• Microsoft Dynamics® SL Legacy Controls — Starts the installation of the previously used VB6
controls, the 2011 to 2015 code converter, Visual Basic DH files for the server, and adds the
legacy controls to the toolbox in Visual Studio. This is useful for developers upgrading projects
that used the VB6 controls and for clients who need the VB6 controls to run a custom screen
that has not been upgraded to use newer controls.
• User Guides — Installs the application user’s guides. This includes the Microsoft Dynamics SL
Software Development Kit and the Visual Basic .NET Conversion Toolkit for Microsoft
Dynamics SL.
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 Business Objects Crystal Reports installation process.
• Business Analyzer – Opens the Business Analyzer submenu
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 upgrading an earlier release, see “Upgrading an Existing Installation” on page 47.
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 15 guides you through installing the application
files on your company’s server. These steps apply to both new and upgrade installations.
• “Changes Needed for User Account Control” on page 18 discusses actions that you must take
if you have User Account Control (UAC) enabled in Windows.
• “Microsoft SQL Server Installation” on page 20 discusses installing the Microsoft SQL Server
database software on your company’s database server.
• “Creating Databases” on page 21 describes the various databases that you can create and
explains how to create them.
• “Installing Supporting Applications” on page 37 guides you through the installation of
programs that provide additional functionality to Microsoft Dynamics SL.
• “Microsoft Dynamics SL Legacy Controls
Before you run the Setup program for the Legacy Controls, make sure that you have installed
Visual Studio and opened it at least one time.
To install the Legacy Controls:
1. Run Setup.exe in the root directory of the installation package by selecting Start | Run and
browsing to the installation package.
2. Click Microsoft Dynamics SL® Legacy Controls. The Welcome dialog box appears.
3. Click Next.
4. End-User 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.
To agree to the terms of the license agreement and continue with the installation, click I
accept the terms in the License Agreement, and then click Next. If you do not accept the
terms in the License Agreement, click Cancel. The installation closes.
If you agreed to the license agreement terms, Custom Setup appears.
5. By default, all SDK features are selected. If you do not want to install a specific feature, you
can change the setting for each.
• 2011 to 2015 Code Converter – This utility can assist developers to convert an
application that uses the Microsoft Dynamics SL 2011 SDK to use the Microsoft
Dynamics SL 2018 CU1 SDK.
• 2011 Toolbox Controls – Installs the controls used by the Microsoft Dynamics SL 2011
SDK into the Visual Studio Toolbox.
• 2011 Runtime Controls – Installs the controls used by the Microsoft Dynamics SL 2011
SDK.
• Server VB Files – Installs the Solomon.VBTools.vb file that is needed for Microsoft
Dynamics SL 2011 SDK applications.
Note: We recommend that you install all of these features.

6. Click Next.
7. Ready to install appears. Click Install.
8. When the installation is complete, Completed appears. Click Finish.
• Microsoft Dynamics SL User’s Guides” on page 38 describes the steps that you must follow to
install the user’s guides.
• “Setting Up Microsoft Dynamics SL on Workstations” on page 44 explains how to configure
workstations that will connect to the new environment.
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 an 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. Make sure that you have .NET Framework 4.5 installed to prevent an interruption in the
Microsoft Dynamics SL installation. See “.NET Framework” on page 43.
3. 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
4. Click Microsoft Dynamics SL.
If Setup detects an existing installation, Setup prompts you to repair or uninstall the existing
installation before you continue. If existing Microsoft Dynamics SL databases must be made
compatible with Microsoft Dynamics SL 2018 CU1, see “Upgrading an Existing Installation” on
page 47.
5. Microsoft Software License Terms appears. Carefully read the license agreement.
6. (Optional) Click Print to print the license agreement.
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.
7. To agree to the terms of the license agreement and continue with the installation, select I
agree to the license terms and conditions, and then click Next.
If you do not select I agree to the license terms and conditions agreement, and then click
Cancel, Exit Setup appears, prompting you to quit or resume installing.
If you agree to the license agreement terms, Select Edition and Installation Location appears.
Figure 3: Select Edition and Installation Location
8. In Select Edition, choose 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.
9. Install the Microsoft Dynamics SL program files in the default Installation Location (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\). The folder in
which you install the program files —the SL folder in the example—must 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 Installation Location, click Install to
continue.
• If you want to override the default Installation Location, click the ellipses (…) 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 Install.
10. Installation In Progress appears and installs both the server and client components. If any
prerequisites are needed, Setup installs them, displaying a status bar message in the window
as it does so.
11. 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.
12. Review the ReadMe.txt file on the screen, or select File | Print to print it.
13. After reviewing or printing, close the file by closing Notepad. Install Succeeded appears.
Figure 4: InstallShield Wizard Complete
14. Click Close.
If you use User Account Control (UAC) in Windows, see “Changes Needed for User Account
Control” on page 18 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 21.
• If you are upgrading an existing installation, see “Updating Databases” on page 51.
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 unwanted access by 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 user’s 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 user’s 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 user’s
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: C:\Program Files\Microsoft Dynamics\SL\Applications\
• Copy to: C:\Users\Public\Documents\Microsoft Dynamics SL\
• 64-bit
• Copy from: C:\Program Files (x86)\Microsoft Dynamics\SL\Applications\
• Copy to: C:\Users\Public\Documents\Microsoft Dynamics SL\
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 UAC’s 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 user’s guide). In the following example, the Public
folder lets several users share the same file location:
[Event Log]
Directory=C:\Users\Public\Documents\Microsoft Dynamics SL
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 user’s 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 Manager’s Transaction Import (98.500.00), Control Macro Generator (98.510.00),
and Export Customizations (91.500.00)
• General Ledger’s Generate Consolidation (01.500.00)
• Application Server
• Tax updates
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 buy 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 21.
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 71 to set up
SQL Server for use with Microsoft Dynamics SL.
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 begin to create 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.
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 5: 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 occurs in the status bar that indicates that you are connected to
the instance of SQL Server.
6. Click the Create Databases tab.
Figure 6: 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 24
• “Creating a Demo Database” on page 29
• “Creating an Additional Empty Application Database” on page 33
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 7: 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
4. In the Application Database Definition area, change the following settings if it is necessary:
• Database Name
• Size
• Database Path
• Transaction Log Path
5. Click Ok. The Create Databases tab reappears.
6. Click Create. The Authentication dialog box appears.
Figure 8: Authentication
7. 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 73.
8. Verify that you selected the correct authentication mode, and then click OK. If you selected
SQL Server Authentication, go to Step 12. If you selected Windows Authentication, SYSADMIN
Windows User Name appears.
Figure 9: 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 who is 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 specify here
must be associated with the network’s domain name. You can associate a Windows user
name with a network domain name in Windows User Name in System Manager’s User
Maintenance (95.260.00) to create an additional administrator.
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. 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.
For more information about this check box, see “Appendix C: Creating SQL Server Users and
Logins” on page 78
11. Click OK.
12. If you selected Windows Authentication in the Authentication window, go to Step 0.
If you selected SQL Server Authentication, Security appears.
Figure 10: 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.
Note: If you have already created the Master80 user, see step 17.
Figure 11: SQL Master80 Login
14. In Password, type a password for the Master80 user which 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 12: SYSADMIN Login
17. In the Password box, type a password for the SYSADMIN user which satisfies the strong
password requirements that are listed in the dialog box.
Guide (securityguide.pdf).
18. In the Confirm box, type the password again.
19. Click OK.
20. The “Database creation process complete” message occurs.
Figure 13: 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 18. For more information about how to
contact Support Services, see “Appendix D: Getting Support” on page 80.
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 32.
If you are finished creating databases, see “Preparing the Demo System and Application
Databases” on page 35.
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
are created based on the edition that you chose when you installed Microsoft Dynamics SL.
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 you can.
• 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
6. Click Create. The Authentication dialog box appears.
Windows Authentication. For more information about authentication modes, see “Considering
whether to change the database authentication mode” on page 73.
If you selected SQL Server Authentication, go to Step 11.
If you selected Windows Authentication, SYSADMIN Windows User Name appears.
8. In Windows User Name, type the identifier of the Windows user who will be the Microsoft
Dynamics SL administrator for this database. Type the information 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 network’s domain name. You can associate a Windows user
name with a network domain name in Windows User Name in System Manager’s 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.)
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 78 for help with setting up SQL Server users and logins manually.
Note: A user who 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.
10. Click OK.

11. If you selected Windows Authentication in the Authentication window, go to Step 19.
Figure 17: 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.
13. Type a Password for the Master80 user which satisfies the strong password requirements
that are listed in the dialog box
Guide (securityguide.pdf) in the User Guides.
14. In Confirm Password, type the password again.

15. Click Ok. The SYSADMIN Login dialog box appears.
16. Type a Password for the SYSADMIN user which satisfies the strong password requirements
that are listed in the dialog box.
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
occurs.
Figure 20: 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
“Event Log Location Changes Required” on page 18. For more information about how to
contact Support Services, see “Appendix D: Getting Support” on page 80.
22. See “Logging On” on page 33.
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.
3. In the System Database Definition area, do not type any information.

• Database Name
• Database Path
6. Click Create. Identify System Database (98.290.40) appears.
Figure 22: 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. 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
“Event Log Location Changes Required” on page 18.
Logging On
When you first open Microsoft Dynamics SL after you install and create 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 and 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 Manager’s 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, point to All Programs, and then click Microsoft Dynamics SL. Find Database
(98.000.01) appears.
Figure 23: Find Database (98.000.01)
2. In Server Name, select the name of the instance of SQL Server or type the name if it does not
appear on the list.
3. In Database Name, 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 24: Microsoft Dynamics SL Login (98.000.00) – Windows authentication, password required
5. Type the Company, User ID, and Password, and then click OK.
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)
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 Application databases, select the application database(s) that you want to update.
4. Click Browse for Files. The default location in the Select files to import box is Microsoft
Dynamics\SL\Applications\DB\csvs.
5. In the Select files to import box, select messages.msg and pvrec.csv by clicking them. Use the
CTRL key or the SHIFT key to select more than one file, and then click Open.
6. Click Begin Processing.
7. Click OK when the process is finished.
8. 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 37.
Preparing the Empty 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)
To prepare the empty system and application databases:
(98.100.00) appears.
7. When the process is complete, click OK to finish preparing the production system and
application databases.
9. If you installed the Multi-Company module, complete this step. Otherwise, go to the next step.
a) In the Microsoft Dynamics SL navigation pane, click Foundation, and then click Multi-
Company.
b) In the Multi-Company details pane, under Setup, click Multi-Company Setup. Multi-
Company Setup (13.950.00) appears.
c) Click to select the Activate Multi-Company with Inter-Company Processing check box.
d) Click Save, and then close Multi-Company Setup (13.950.00).
10. In the Microsoft Dynamics SL navigation pane, click Financials, and then click General Ledger.
11. 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).
12. Under Setup, click GL Setup. GL Setup (01.950.00) appears.
13. Define the appropriate setup information on the Options, Fiscal Info, and Currency Info tabs.
Note: This step is required. However, you cannot complete all fields on the tabs until you first
define retained earnings and year-to-date net income accounts, subaccounts, and ledgers.
See step 11.
14. Click Save, and then close GL Setup (01.950.00).

15. Register Microsoft Dynamics SL. For more information, see the System Manager Help or
user’s 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.
Installing Supporting Applications

Microsoft Dynamics SL Software Development Kit (SDK)
Before you run the Setup program for the Software Development Kit, make sure that you have
installed Visual Studio and opened it at least one time.
To install the Software Development Kit:
2. Click Microsoft Dynamics SL® SDK. The Welcome dialog box appears.
3. Click Next.
statement.
• Code Inspector – This utility can be used to inspect your SDK application code for known
issues. When installed, you can find it in Visual Studio, on the XX menu.
• VB Project Templates – These templates are installed and attached to Visual Studio.
When installed, you can find them in Visual Studio, on the XX menu.
• Toolbox Controls – This contains the .NET controls needed for SDK applications. When
installed, you can find them in Visual Studio, on the XX menu.
• VB Files – This contains the Microsoft.Dynamics.SL.SDK.vb and DH files needed to create
SDK applications
6. Install the SDK in the default destination folder (\Microsoft Dynamics\SL\SDK\) or click
Browse to select a different location.
• If you want to install the files in the default destination folder, click Next to continue.
• If you want to override the default destination folder for each feature, click Browse and
locate the folder to which you want to install the 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.
Microsoft Dynamics SL Legacy Controls

3. Click Next.
statement.
SDK.
6. Click Next.
Microsoft Dynamics SL User’s Guides

Before you run the Setup program for the User’s Guides, verify that Adobe Reader is installed.
To install the User’s Guides:
2. Click User Guides. The Welcome dialog box appears.
3. Click Next.
software is installed, click Help | About Microsoft Dynamics® SL in the Microsoft
If you agree to the license agreement terms, Custom Setup appears.
5. By default, all user’s guides are selected. If you do not want to install specific user’s guides,
you can change the setting for each.
6. Install the Microsoft Dynamics SL user’s guides in the default destination folder (\Microsoft
Dynamics\SL\Applications\User Guides\) or click Browse to 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.
Microsoft Dynamics SL Web Services and Web Apps

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.
Building upon the Microsoft Dynamics SL Web Services, the prebuilt Web Apps provides access to
specific functions from a web browser on many devices and desktop computers.
To use these features, you must install the Microsoft Dynamics SL Web Services or both Web
Services and Web Apps. For information about how to install one or both of these features, see
the Microsoft Dynamics SL Web Apps Deployment user’s guide. This user’s guide is available
within the Microsoft Dynamics SL Web Apps delivery.
Microsoft Dynamics Business Analyzer for Microsoft Dynamics SL

The Microsoft Dynamics Business Analyzer feature provides a client dashboard into SQL Server
Report Services (SSRS) reports, Management Reporter reports, and Microsoft Excel files stored in
a network location, without requiring that Microsoft Dynamics SL be installed locally. It provides
business decision makers with a desktop dashboard or a mobile app that they can use to gain
contextual business intelligence by viewing up-to-date reports pulled from Microsoft Dynamics SL.
To use this feature, you must install the Microsoft Dynamics Business Analyzer and other
prerequisites. For information about how to install and configure Microsoft Dynamics Business
Analyzer for use with Microsoft Dynamics SL, see the Business Analyzer user’s guide
(BusinessAnalyzer.pdf).
Microsoft Dynamics SL Data Mart Adapter for Management Reporter

A data mart adapter acts as a bridge between the data source and Management Reporter for
Microsoft Dynamics SL 2018 CU1. 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 mart adapters to meet the reporting needs of any organization.
Installation documentation is available as follows:
1. Browse to the following location:
https://mbs.microsoft.com/customersource/northamerica/MR/downloads/service-packs/MROverview
2. Click Microsoft Dynamics SL 2015 Guide.
3. When you are prompted, download the Management Reporter Integration Guide for Microsoft
Dynamics® SL (DynSLDataMartAdapterInstGuide_ENUS.pdf).
Note:
• If you are moving from Microsoft FRx 6.7 to Management Reporter, you must install
Management Reporter 2012 and then Management Reporter 2012 Service Pack 1. Use the
Management Reporter Migration Wizard to migrate your reports. For detailed steps, see the
Migration Guide and Migration Best Practices documents at the following location:
https://mbs.microsoft.com/customersource/northamerica/MR/downloads/service-packs/MROverview
• Microsoft FRx 6.7 is not supported for use with Microsoft Dynamics SL 2018 CU1.
Microsoft Dynamics SL Outlook Add-in

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 Outlook Add-in 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 computer’s 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:
Uninstall the Microsoft Dynamics SL Outlook Add-in:
1. Close Microsoft Office Outlook.
3. Locate the Microsoft Dynamics SL Outlook Add-in item in the list.
4. If it exists in the list, click Uninstall.
5. Click OK when prompted “Are you sure you want to remove this customization (Microsoft
Dynamics SL Outlook Add-in) from this computer?”
6. The Microsoft Dynamics SL Outlook Add-in is removed from the list.
Verify that the add-in no longer appears in Outlook:

1. Open Microsoft Office Outlook.
2. Open Add-Ins in Microsoft Office Outlook.
• In Outlook 2007, click Tools->Trust Center->Add-ins.
• In Outlook 2010, Outlook 2013 and Outlook 2016 click File->Options->Add-Ins.
3. In the Manage box, select COM Add-ins, and then click Go.
4. The COM Add-Ins window appears.
5. Locate Microsoft Dynamics SL Outlook Add-in.
6. If it exists in the list, click Remove, and then click OK.
7. Close Microsoft Office Outlook.
Remove any cached copies of the of the Microsoft.Dynamics.SL.OutlookAddin.dll file:

1. Browse to the following location:
<SystemDrive>:\Users\[UserAlias]\AppData\Local
2. Search this location for “outlook”.
3. You may find the Microsoft.Dynamics.SL.OutlookAddin.dll file within the following locations:
<SystemDrive>:\Users\[UserAlias]\AppData\Local\Apps\2.0\
<SystemDrive>:\Users\[UserAlias]\AppData\Local\assembly\dl3\
4. Delete the entire subfolder that contains the Microsoft.Dynamics.SL.OutlookAddin.dll file.
Example: If you find the Microsoft.DynamicsSL.OutlookAddin.dll file in the following locations:

<SystemDrive>:\Users\[UserAlias]\AppData\Local\Apps\2.0\2DG0N50O.V1Z\
--Delete the 2DG0N50O.V1Z folder and all of its contents.
<SystemDrive>:\Users\[UserAlias]\AppData\Local\assembly\dl3\M3AAR91W.8TL\
--Delete the M3AAR91W.8TL folder and all of its contents.
To manually install the Microsoft Dynamics SL Outlook Add-in, follow these steps:
1. Make sure that Microsoft Office Outlook is closed.
2. Browse to the Program Files\Microsoft Dynamics\SL\Applications\OutlookAddin\ folder on
the client workstation.
Or, browse to either the DynamicsSL\OutlookAddin folder in the installation package or to the
\Microsoft Dynamics\SL\Applications\OutlookAddin folder on the server.
3. Double-click the Microsoft.Dynamics.SL.OutlookAddin.vsto file.
The Microsoft Office Customization Installer dialog box appears.
Figure 25: Microsoft Office Customization Installer
4. Click Install.
5. Click Close when installation is complete.
Note: Remember to uninstall the Microsoft Dynamics SL Outlook Add-in every time that you
uninstall Microsoft Dynamics SL. See the following steps.
.NET Framework
Microsoft.NET Framework 4.5 is required for the Microsoft Dynamics SL client installation.
To install the .NET Framework, follow these steps:
1. Download .NET Framework from the following location:
http://www.microsoft.com/en-us/download/details.aspx?id=30653
2. When prompted, save the dotNetFx45_Full_setup.exe file to your computer.
3. Run dotNetFx45_Full_setup.exe.
Note: Make sure not to restart the computer while the .NET Framework is installing.
4. When installation is complete, you receive the following message.
Figure 26: Microsoft .NET Framework message
5. Click Finish.
6. Restart the computer.
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.
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 an administrator or as a member of the local Administrators group at a workstation
computer that 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.
3. 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.
4. Open a command prompt using “Run as Administrator”. Map a network drive to the shared
folder on the server where Microsoft Dynamics SL programs are installed using the same
drive letter as specified in Step 3.
5. Run ClientSetup.exe from the shared \Microsoft Dynamics\SL\Applications folder to start
Client Setup. Do not execute the program as “Run as Administrator”.
7. (Optional) Click Print to print the license terms.
8. To agree to the terms of the license agreement and continue with the installation, click I agree
to the license terms and conditions, and then click Next.
If you do not click I agree to the license terms and conditions, and then click Cancel, the
installation will end.
If you agree to the license agreement terms, Installation In Progress appears and installs the
client components. If any prerequisites are needed, Setup installs them, displaying a status
bar message in the window as it does so.
9. After Setup has installed the selected files, Install Succeeded appears.
10. Click Close.
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 15.
Upgrading an Existing Installation

Overview
This section explains how to upgrade an existing Microsoft Dynamics SL installation.
• “Before You Install” on page 49 lists important tasks that you must do before you install this
release. Included in this section are details on how to export customizations for safekeeping.
• “Removing an Existing Installation” on page 50 describes how to remove existing Microsoft
Dynamics SL installations on servers and client workstations to prepare for installing.
• “Installing Microsoft Dynamics SL” on page 51 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 51 describes how to update existing Microsoft Dynamics SL
databases. This includes entering the registration keys for this version. For more information
about registration keys, see “Entering Registration Information and Unlocking Modules” in the
System Manager Help or user’s guide.
• “Updating Client Workstations” on page 59 explains how to update Microsoft Dynamics SL
client workstations to this release.
• “Installing Supporting Applications” on page 37 describes the procedure for installing
applications that are included with this release.
– “Updating Custom Crystal Reports” on page 60 describes how to update your existing
Crystal reports from an earlier version to work with Crystal Reports version 2008.
– “Microsoft Dynamics SL Legacy Controls
3. Click Next.
statement.
SDK.
6. Click Next.
– Microsoft Dynamics SL User’s Guides” on page 38 describes how to install the user’s
guides for Microsoft Dynamics SL.
– “Microsoft Dynamics SL Outlook Add-in” on page 41 explains how to install and uninstall
the Visual Studio Tools for Office add-in.
– “.NET Framework” on page 43 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 57
explains how to update Microsoft Dynamics client workstations to this release.
• “Adding Modules” on page 60 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.
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 you can restore them after you finish 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 version 6.5 or a later version is required in order to update
directly to this release. If you currently use a version that is earlier than 6.5, contact a Microsoft
Certified Partner for information about how to upgrade your environment to version 6.5 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 Manager’s Export Customizations (91.500.00) to export all screen
customizations (for more information, see the Customization Manager Help or user’s guide).
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. For more information, see the Customization Manager
Help or user’s guide.
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 you have a customized Delta.mnu file, create a backup
folder that is not under the \Microsoft Dynamics\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. The Delta.mnu file
was used in Microsoft Business Solutions – Solomon 6.x and earlier versions.
On the “Preinstallation Checklist” on page 6, you were instructed to remove any earlier installation
of Microsoft Dynamics SL (release 6.5 or a later version) from all client workstations and from the
server where it is installed before you start to install Microsoft Dynamics SL 2018 CU1. Otherwise,
Setup will require you to do this but starts the removal only on the server before it starts the
installation process.
If you missed those steps, you can perform them now.
To remove all Microsoft Dynamics SL files from a workstation or server:
1. Close Microsoft Dynamics SL and all Windows-based applications.
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 2011 installation is Microsoft Dynamics SL 2011 Client
or Microsoft Dynamics SL 2011 Server.
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. 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.
Note: The following features are not automatically uninstalled and must be manually uninstalled.
• Microsoft Dynamics SL Outlook Add-in (VSTO) – See “Microsoft Dynamics SL Outlook Add-in”
on page 41.
• Microsoft SQL Server System CLR Types or Microsoft System CLR Types for SQL Server –
Remove by using Programs and Features
Removing Doc Share Web Service

If it is installed, uninstall Microsoft Dynamics SL Doc Share Web Service from the Windows
SharePoint Services Server.
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 15 for instructions. When the
Microsoft Dynamics SL Setup program is finished, continue the upgrade process in the topics that
follow.
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 one of the versions listed in “Microsoft SQL
Server” on page 1. 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 user’s guide for information about how to export and import .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 2018 CU1 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 the current version as
follows:
• 6.5x, 7.x, 2011.x, 2015.x to 2018 CU1
• 2018.x to 2018 CU1
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
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 the instance of SQL Server
connected successfully, click the Update Databases tab.
Note: In Databases, the application databases are automatically selected for you.
Figure 28: 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.
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 73.
Figure 30: 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.
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 specify
here must be associated with the network’s domain name. You can
associate a Windows user name with a network domain name in Windows
User Name in System Manager’s 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 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.
Type a Password for the Master80 user which satisfies the strong password
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 33: 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.
d.) Next, SYSADMIN Login appears.

Type a Password for the SYSADMIN user which 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.
e.) In the Confirm box, type the password again.

f.) Click OK. Default Password appears.
Figure 35: 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.
Security Guide.
h.) In Confirm Password, type the password again and then click Ok. The database
update process starts.
14. When the update is complete, the 9829000 message box appears. Click OK.
Figure 36: 9829000 message
Note: If the update was unsuccessful, you will not see this message. Instead, a database
update failure message occurs.
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 18. For more
information about how to contact Support Services, see “Appendix D: Getting Support” on
page 80.
17. Follow the instructions in ”Using Database Update after Completing the Database
Maintenance Scenario” on page 57 to continue the database update process.
18. Repeat this process for each remaining system database and its related application
databases.
19. For each system database that you upgraded, log on to Microsoft Dynamics SL and enter the
new registration keys for this version. For more information about registration keys, see
“Entering Registration Information and Unlocking Modules” in the System Manager Help or
user’s guide.
Using Database Update after Completing the Database Maintenance

Scenario
After you complete a database maintenance scenario (see “Updating Databases” on page 51),
you must use Database Update (98.100.00) to populate the system database with current system
data.
Note: Populating the Screen table and the RPTControl table occurs during database creation
(databases are created by using Database Maintenance (98.290.00)). The Screen.csv file and the
rptcontrol.csv file are 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.
(98.100.00) appears.
9. Click OK when the process is complete.
10. Repeat step 1 through step 8 for each additional system and application database
combination.
Your databases are ready to use. To install other applications that provide additional functionality
to Microsoft Dynamics SL, see “Installing Supporting Applications” on page 37.
Updating Client Workstations

To update Microsoft Dynamics SL client workstations:
1. Log on as an administrator or as a member of the local Administrators group at a workstation
that you will configure to use Microsoft Dynamics SL. Failure to do this will cause 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. Open a command prompt using “Run as Administrator”. Map a network drive to the shared
folder on the server where Microsoft Dynamics SL programs are installed using the same
drive letter as specified in Step 2.
5. Run ClientSetup.exe from the shared \Microsoft Dynamics\SL\Applications folder to start
Client Setup. Do not execute the program as “Run as Administrator”.
7. (Optional) Click Print to print the license terms.
8. To agree to the terms of the license agreement and continue with the installation, click I agree
to the license terms and conditions, and then click Next.
If you do not click I agree to the license terms and conditions, and then click Cancel, the
installation will end.
If you agree to the license agreement terms, Installation In Progress appears and installs the
client components. If any prerequisites are needed, Setup installs them, displaying a status
bar message in the window as it does so.
9. After Setup has installed the selected files, Install Succeeded appears.
10. Click Close.
Updating Custom Crystal Reports

Crystal Reports runtime only is included with this release. This allows you to print the standard
Crystal Reports.
If you need the full version of Crystal Designer to customize a crystal report or maintain a
previously customized crystal report, contact the software developer at www.crystalreports.com.
There are some instances where the implementation of custom reports must be upgraded to work
with Microsoft Dynamics SL 2018 CU1 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 user’s guide or Help (ReportingGuide.pdf). For help
changing the syntax for custom reports, see the “Additional Information” topic in the same
appendix.
Updating Microsoft Dynamics SL SharePoint Web

Service
The Microsoft.Dynamics.SL.SharepointClient.dll assembly replaces the Microsoft Dynamics SL
SharePoint Web Service (Microsoft.Dynamics.SL.Docshare.vb). The Microsoft Dynamics SL client
installation installs this .dll file automatically. If you have not uninstalled Microsoft Dynamics SL
SharePoint Web Service, uninstall it from the Windows SharePoint Services Server to free up
resources.
For more information about the new Microsoft.Dynamics.SL.SharepointClient.dll assembly, see
the “Modifying a SharePoint Site” topic in the Software Development Kit Help or user’s guide.
Adding Modules
After you install Microsoft Dynamics SL, it is easy to add modules. During the initial installation, all
modules are installed. To begin to use a module that you have not previously used, you must
register the module. For more information about registering modules, see the System Manager
Help or user’s guide.
Troubleshooting 61
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. All files and reports are replaced with versions matching the executable files
and reports from the installation package.
To repair all Microsoft Dynamics SL on a workstation or on a server:
1. Close Microsoft Dynamics SL and all Windows-based applications.
3. On the list of currently installed programs, click the entry for Microsoft Dynamics SL 2018
CU1 (this includes both the server and client), Microsoft Dynamics SL 2018 CU1 Server or
Microsoft Dynamics SL 2018 CU1 Client, and then click Change/Remove or Change. The
Microsoft Dynamics SL 2018 CU1 Setup window appears.
4. Click Repair.
5. When the process finishes, click Close.
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
to use it, and then type the SQL Server “sa” Login ID and Password.
Troubleshooting 63
6. Click the Update Databases tab.

Be aware that in Databases, the application databases are automatically selected for you.
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.
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 that are 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
database’s Company table.
• Index — An index is a set of pointers that are logically ordered by the values of a key. Indexes
provide quick access to data and can enforce uniqueness on the rows in a table. Indexes are
used everywhere in Microsoft Dynamics SL. They are foundational to the performance of a
database structure.
• Stored Procedure — A stored procedure is a multi-statement compiled Transact-SQL query
with control-of-flow language that can take parameters and allows 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
then 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 company’s financial data is stored. Because
companies can have a one-to-one or a one-to-many relationship of company to application
database, the Company table is the central cross-reference for all companies.
Troubleshooting 65
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 Application Database Name

0010 SLDemoApp10
0020 SLDemoApp10
0060 SLDemoApp60
0070 SLDemoApp60
0080 SLDemoApp60
0051 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 71.
Backup and Restore Procedures

We strongly recommend regular database backups and periodic testing of the restore process.
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:
Company Original application database name New application database name

0010 SLDemoApp10 NEWAPPDB
0020 SLDemoApp10 NEWAPPDB
0060 SLDemoApp60
0070 SLDemoApp60
0080 SLDemoApp60
0051 DemoStandardApp51
If restored to a different database name, company 0010, stored in the system database, is still
pointing to SLDemoApp10, not the new database name. To correct this, issue the following
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.
Troubleshooting 67
If you are restoring to a different computer, follow these steps.

To run the Synchronize All Database 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
Server where the databases will be created.
5. Click Update Databases.

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 specific system or application databases.
6. Click Update Database. This process will update each system database’s domain table with
the correct server name and update SQL Server logins and permissions for the Microsoft
Dynamics SL databases.
7. After the process is complete, click OK.
8. In the System Database Name list, select your system database name.
9. Click Update Views.
10. Click OK, and then click Close.
Troubleshooting 69
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 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 workstation’s 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 user’s 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
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 server’s
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 server’s file. See Appendix A in the System Manager Help or user’s
guide for more information about the Solomon.ini settings.
Appendixes 71
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 versions of Microsoft SQL Server listed in
“Microsoft SQL Server” on page 1. Microsoft SQL Server must be purchased separately. Contact a
Microsoft Certified Partner for help.
Microsoft SQL Server

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.
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.
3. Click Security.
4. Under Server authentication, click SQL Server and Windows Authentication mode.
5. Click OK, and then close SQL Server Management Studio.
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 41: Server Properties
3. Click Memory.
4. The default setting Minimum server memory (in MB) is zero (0) MB. Do not change this
setting.
5. Set Maximum server memory (in MB) to approximately 80% of the total server memory. For
example, if your total server memory is 32 GB, set the maximum server memory to 26 GB.
6. Click OK.
7. Ask all SQL Server users to log off so that you can stop and then restart SQL Server services
safely.
8. Stop and restart the SQL Server services.
9. Close SQL Server Management Studio.
Appendixes 73
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 Manager’s 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).
4. In Control Panel, select Administrative Tools and then Microsoft Dynamics SL Database
Figure 42: Database Maintenance (98.290.00), Connect Server tab
Server where the databases are located.
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.
6. In System Database Name, select the appropriate system database.

7. Click Set Authentication Type. Authentication appears.
8. Select an authentication method, and then click Ok. We recommend Windows authentication.
9. 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.
Appendixes 75
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 78 for help setting up SQL Server
users and logins manually.
Note: A user who 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 you select the Grant this user
permission to create SQL Server logins and users check box .
c.) Click OK. The authentication mode change process starts.
• If you selected SQL Server Authentication:
a.) Security appears.
Figure 46: Security message

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.
c.) Type a Password for the Master80 user which satisfies the strong password
Security Guide.
d.) In Confirm Password, type the password again.
e.) Click Ok. SYSADMIN Login appears.
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.
Appendixes 77
Security Guide.
g.) In Confirm, type the password again, and then click Ok.
If you created the Master80 user in Step b, the authentication mode change process
starts. See step 10.
Login appears if the Master80 user was created before you began these steps.
Figure 49: 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.
10. 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 50: 9829000 - Process complete message
Note: When an authentication change is unsuccessful, you will not see this message. Instead,
a failure message occurs 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 18. For more information about how to contact Support Services, see “Appendix D:
Getting Support” on page 80.
11. Click OK.

12. Review the Dbbuild.log file.
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.
Expand Security, and then right-click Logins.
Click New Login. Login – New appears.
Add the Windows authenticated user or global domain security group.
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.
Expand the Microsoft Dynamics SL database node.
Expand Security.
Right-click Users, and then click New User.
Type the User Name and Login Name of the new user or global domain security
group.
Click OK
– Or –
Create User [domain\name] for login [domain\name]
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.
Expand the Microsoft Dynamics SL system database node.
Expand Security, expand Roles, and then expand Database Roles.
Right-click MSDynamicsSL, and then click Properties.
On the General tab, under Members of this role, click Add.
In Select Database User or Role, type the name of the user or global domain security
group, or click Browse to find it.
Click OK.
– Or –
sp_addrolemember 'MSDynamicsSL', 'domain\name'
Appendixes 79
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
GO
use SLApplicationDatabase
GO
GO
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
• Telephone Microsoft support
• Electronic Microsoft support
• Go to https://mbs.microsoft.com/customersource/northamerica/SLfor the latest details on
these professional support services
Important Telephone Numbers and Internet Addresses

Microsoft Dynamics
Country Phone Number Hours
(All times in local time
Zone)
Canada 1-800-668-7975 Monday - Wednesday
& Friday:
1-800-936-4900 08:00 – 20:00
Thursday:
United States 1-888-477-7877 10:00 – 20:00
Worldwide: https://www.microsoft.com/en-us/dynamics365/support
Training/Seminars https://mbs.microsoft.com/customersource/northamerica/SL/learning
Product Registration Telephone — 800-476-5666

To view your software registration information, go to the CustomerSource
Product and Service Summary at
https://mbs.microsoft.com/CustomerSourceApp/myprofile/product_service_
summary.aspx.
If you have questions about your licenses, registration keys or service plans,
please start a service request by clicking Operations Support at
https://mbs.microsoft.com/CustomerSource/northamerica/Help/Help/Conta
ctUs
Index 81
Index
recommended protocols 64
version 9, 71
C
Company record 64
computer name 6
O
operating systems 1
optimizing Microsoft SQL Server 65
D options, installation setup 11
database
demo 8
updating, important points 51
P
preparing to install 6
protocols for Microsoft SQL Server 64
E
edition
Advanced Management 7
R
Business Essentials 7 record
determining which edition Company 64
installed 7
Professional 7
Standard, Multi-User 7
Standard, Single-User 7
S
setting
SQL Server and Windows
I Authentication mode 71
setting up
Installation 15 Microsoft Dynamics SL on a single-
Installation package user workstation 44
contents 7 Microsoft Dynamics SL options 11
installing signing in 33
Microsoft SL SDK 9 Solomon.ini and other profile locations 18
Microsoft SQL Server 20 SQL Server version 9
new Microsoft Dynamics SL supported environments 1
installations 13
K T
technical resources
key terms 64 foundational changes 64
L U
logging on 33 update prerequisites 49
updating
databases, important points 51
M
messages file location 18
messages file location, Windows 18
V
Microsoft Dynamics SL application files version, Microsoft SQL Server 9
location 19
Microsoft Dynamics SL event log
location 18
Microsoft Dynamics SL installation
W
package contents 7 Windows
Microsoft SL SDK 9 messages file location 18
Microsoft SQL Server Microsoft Dynamics SL application
installing 20 files location 19
optimizing 65
Microsoft Dynamics SL event log

location 18
Solomon.ini location 18
workstation
single-user Microsoft Dynamics SL
client 44

Installation Guide: Release 2018 CU1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Guide: Release 2018 CU1

Uploaded by

Copyright:

Available Formats

Installation Guide

Release 2018 CU1

Guide for New Installations 13

Upgrading an Existing Installation 47

Terminology Definitions ........................................................................................... 64

Microsoft SQL Server

What You Must Know about User Account Control

Summary of Tasks for New and Existing Installations

First-time installation Upgrading an existing installation

To install the .NET Framework, see “.NET

Note: If you are moving from Microsoft FRx 6.7

Note: Microsoft FRx 6.7 is not supported for use

First-time installation Upgrading an existing installation

To install the .NET Framework, see “.NET

The Microsoft Dynamics SL SharePoint Web

To complete the preinstallation checklist:

Which Microsoft SQL Server version do I have?

SQL Server 2014 12.00.2000.8 SQL Server 2014

SQL Server 2016 13.00.1601.5 SQL Server 2016

SQL Server 2017 14.0.1000.169 SQL Server 2017

Figure 1: Installation options window

The installation options include the following:

If an earlier release of Microsoft Dynamics SL is not installed on your workstation computers or

Guide for New Installations

Note: We recommend that you install all of these features.

Installing Microsoft Dynamics SL

Figure 2: Installation options window

4. Click Microsoft Dynamics SL.

Figure 3: Select Edition and Installation Location

Figure 4: InstallShield Wizard Complete

14. Click Close.

Changes Needed for User Account Control

Locating Solomon.ini and Other Profiles

Making Required Messages File Location Changes

Event Log Location Changes Required

Selecting Program File Locations

Microsoft SQL Server Installation

Note: Your database administrator must perform these procedures.

Figure 5: Database Maintenance (98.290.00)

6. Click the Create Databases tab.

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

Creating an Empty Database

Figure 7: Advanced Configuration Settings

6. Click Create. The Authentication dialog box appears.

Figure 9: SYSADMIN Windows User Name

Figure 10: Security

Figure 11: SQL Master80 Login

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

Figure 12: SYSADMIN Login

Figure 13: Database creation process complete

21. Click OK. Database Maintenance (98.290.00) reappears. Click Close.

Creating a Demo Database

2. Click Advanced. Advanced Configuration Settings appears.

Figure 14: Advanced Configuration Settings

• SLDemoApp10 (companies 0010 and 0020)

6. Click Create. The Authentication dialog box appears.

Figure 15: Authentication

Figure 16: SYSADMIN Windows User Name

10. Click OK.

Figure 17: Security

Figure 18: SQL Master80 Login

14. In Confirm Password, type the password again.

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