The LEADTOOLS services are WCF service classes.
Microsoft Visual C++ 2010 SP1 Redistributables are required for .NET 4.0.
By default, the LEADTOOLS configuration demos configure the LEADTOOLS Windows services and web services to run as the LocalSystem (NT Authority\System) identity. This is a special built-in account that has full access to the local system. SQL Server 2008 R2 and earlier included this account as a login with full access to SQL Server. Microsoft considered this a security flaw and the login removed from the default installations of newer versions of SQL Server.
Review: SQL Server – “Create a Login” documentation: https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/create-a-login?view=sql-server-2017
If enabled in SQL Server, SQL Server authentication may be used. If using SQL authentication, before running the LEADTOOLS Database Configuration demo, the SQL login must already exist. When adding the SQL login, make sure the option “Must change password” is unchecked. Once the SQL login and user is created, connect to the database engine in Visual Studio or SQL Server Management Studio to test.
If using Windows authentication, create a service user account, SQL log in and user with appropriate permissions to access the server and databases. Ignore the following dialog when it appears:
Using either Windows or SQL authentication to login to SQL Server,
the mapped user must have the correct permissions to perform the
functions required by the configuration tools and demos. For
development, associating the user with
sysadmin server role and
dbowner database role is the quickest, but not recommended for
production per the obvious security concerns.
If Windows authentication is used to connect to the database, the LEADTOOLS DICOM Windows services should be configured to run as the same Windows user.
Ensure the Windows user account can
Access the database provider (SQL Server, Oracle, etc.) for creating, reading, writing, and removing a database.
Access to shared folders and files
TypeScript is included with Visual Studio 2013 Update 2 and newer. Get TypeScript for Visual Studio 2012: https://www.microsoft.com/en-us/download/details.aspx?id=34790
1) Do either (a) or (b) below:
2) From the LEADTOOLS Medical Menu, click the link for the “Utility to create required databases”, or click the link for “HTML5 Medical Web Viewer (Configure and Run).A dialog stating that databases are not configured may be displayed. Tap **Yes** to configure the database.
3) The Database Configuration Demo will attempt to enumerate the SQL Servers available on the network. If the demo was unable to enumerate the SQL Servers, it may present the following message box:
1. Tap OK.
2. Enter the server/instance name to connect and tap Validate.
3. A "Warning" or "Connection String Validation" message box will be presented.
Tap OK. If “Warning”, see "Troubleshoot SQL Server" else continue.
4. Choose the default options for all settings including “Create New Databases”. Take note of the User Name and Password entered as they will be needed in future steps. Tap Configure.
A summary for the databases that are about to be created will be presented. Tap OK.
Once the databases have been created, a success message will be displayed in the Status Box.
If running the Medical Web Viewer setup, the PACS Configuration demo will start automatically. Otherwise, you will need to navigate to the “Utility to create DICOM Listening Services” link in the LEADTOOLS Medical Menu. Certain features of the HTML5 Medical Web Viewer requires the Storage Server Windows service to be running.
4) Leave all options as default and tap Configure to install the LEADTOOLS DICOM Windows services.
5) Once all services are installed the demo then tries to communicate with the SQL Server instance through each service. If any of the services have failed this test, follow the steps detailed in the SQL Server with Window Authentication section
To complete the configuration, click the “HTML5 Medical Web Viewer (Configure and Run) ” link from the LEADTOOLS Medical Menu.
6) Tap Fix Problems to complete the configuration. If the demo presents with an IIS warning,1. Review the IIS prerequisites 2. Restart Medical Web Viewer demo and try again.
7) The LEADTOOLS Service Host Manager will start. Accept the default
settings and tap Next through all of the steps.
8) The LEADTOOLS Service Host Manager will next create an Application Pool named LEADTOOLS20_DOTNET_v40 and two IIS applications. The MedicalViewerServiceWcf20 application hosts the LEADTOOLS WCF service classes as web services. The MedicalViewer20 application hosts the LEADTOOLS HTML5 Medical Web Viewer demo application files.
9) Tap Test All. Follow any troubleshooting links and make any required
adjustments. Tap Test All until all issues are resolved.
10) If you are using SQL Server with Window Authentication you’ll also need to follow the steps outlined in the Update Application Pool Identity section in order to login to the demo.
1) If you are using SQL Server 2012 or newer and opted to use Windows Authentication, you may see an error message indicating that the Listening Service can’t access the database.
2) This error message occurs because LEADTOOLS will install the
services to run as
LocalSystem. Change the run-as user using the
Services applet found in the Administrative Settings under the
Windows Control Panel to a user that can login to SQL Server and has
appropriate permissions to the LEADTOOLS databases.
1) Open IIS Manager. Expand and select Application Pools. In
Application Pools select LEADTOOLS_DOTNET_v40 or
LEADTOOLS_DOTNET_v20, and click the Advanced Settings… action.
2) In the Advanced Settings dialog, change the Identity to be the
Windows user that has access to SQL Server. Tap the ellipsis in
Identity property setting.
3) Select the “Custom account” option and tap Set… :
4) Enter the login information and tap OK for all dialogs:
5) You should now see the Application Pool running under your user.
Depending on the order that the prerequisite steps were completed, it is possible that handlers for WCF are not installed correctly. To correct this, start an elevated cmd prompt and run the following commands:
%SYSTEMROOT%\\Microsoft.NET\\Framework\\v3.0\\"Windows Communication Foundation"\\ServiceModelReg –i
%SYSTEMROOT%\\Microsoft.NET\\Framework64\\v3.0\\"Windows Communication Foundation"\\ServiceModelReg –i