How do I set up the v19 Medical Web Viewer?

The latest guide for setting up the Medical Web Viewer can be found here: https://www.leadtools.co...-medical-web-viewer.html

In this post, you will see how to set up the LEADTOOLS 19 HTML5 Medical Web Viewer. The LEADTOOLS HTML5 Medical Web Viewer is comprised of:

1. Front end HTML5/JS code developed in AngularJS.
2. Backend WCF web services for providing the images and other necessary information to the front end viewer.
3. SQL Server Database to store all the DICOM information

Prerequisites:

Supported Operating System(s):

• Windows 7 and newer
  
• Server 2008 and newer
  

.NET Framework:
The LEADTOOLS services are WCF service classes.
Microsoft .NET Framework 3.5 or newer is installed

Microsoft Visual C++ Redistributables:
Microsoft Visual C++ 2008 SP1 Redistributables are required for .NET 3.5.
Microsoft Visual C++ 2010 SP1 Redistributables are required for .NET 4.0.

IIS Features:
IIS with at least the following features is required (Check all options under each section):
Internet Information Services

• Web Management Tools
  
• World Wide Web Services
  

If Windows 8 or newer
.NET Framework 4.5 Advanced Services

• ASP.NET 4.5
  
• WCF Services
  

* In Windows 8 / Server 2015 and newer, be sure to check both 3.5 and 4.5
versions.

Below is a screen shot from Windows 10 showing the features to check (This window's layout can change based on your operating system):



SQL Server:
At least SQL Server Express 2005 or newer is required.

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.c...on-access/create-a-login

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.

Windows Services
If using Windows authentication, you need a Windows user account, SQL log-in for the Windows user account, and SQL user that is mapped to the SQL log-in associated with the Windows user account. The SQL user must have appropriate permissions to access the databases.

Ensure the Windows user account can:

• Access the web service site
  
• Access the database provider (SQL Server) for creating, reading, writing, and removing a database.
  
• Access to shared folders and files:
  
  
  
  • GlobalPacs.config
    
  • Storage Server Directory
    
  • Image Storage Directory
    
  • Image Overwrite Directory
    
  
  

Microsoft's Typescript
TypeScript is not required to run the LEADTOOLS HTML5 Medical Web Viewer demo. However, TypeScript is highly recommended if you wish to make any modifications to the JavaScript code that calls the LEADTOOLS web services. TypeScript is included with Visual Studio 2013 Update 2 and newer. Get TypeScript for Visual Studio 2012:
https://www.microsoft.co...etails.aspx%3Fid%3D34790

Configure the HTML5 Medical Web Viewer:

1. Browse to the “{LEADTOOLS Install}\Shortcuts\Medical Viewers\JavaScript\Medical Web Viewer” folder
   
2. Run the “Run This First To Config 32-bit Demos” shortcut. (Run the 64-bit version if you are setting this up as 64-bit)
   
3. A dialog stating that databases are not configured may be displayed. Tap Yes to configure the database.
   
   
   
   
4. 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:
   
   
   
   
5. Tap OK.
   
6. Enter the server/instance name to connect and tap Validate.
   
   
   
   
7. A “Warning” or “Connection String Validation” message box will be presented.
   
   
   
   If you receive a 'Named Pipes Provider, error: 40' see the document (error_40.docx) in the follow-up post below for directions on how to resolve.
   
   
   
   Tap OK. If "Warning", see "Troubleshoot SQL Server" else continue.
   
8. 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 Apply Configuration Options.
   
   
   
   
9. A summary for the databases that are about to be created will be presented. Tap OK.
   
10. Once the databases have been created, a success messagebox will be displayed.
    
    
    
    
11. The PACS Configuration demo will start automatically to complete the configuration. Certain features of the HTML5 Medical Web Viewer requires the Storage Server Windows service to be running. Leave all options as default and tap Configure to install the LEADTOOLS DICOM Windows services.
    
    
    
    
12. 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, run the “Run This Second to Run the Medical Web Viewer 32-bit Demo” (Run 64-bit if you are setting up for 64-bit) in the “{LEADTOOLS Install}\Shortcuts\ Medical Viewers\JavaScript\Medical Web Viewer” folder.
    
    
    
    
13. Tap Fix Problems to complete the configuration. If the demo presents with an IIS warning, either Review the IIS Prerequisites or Restart Medical Web Viewer demo and try again.
    
14. The LEADTOOLS Service Host Manager will start. Accept the default settings and tap Next through all of the steps.
    
    
    
    
    
    
15. The LEADTOOLS Service Host Manager will next create an Application Pool named LEADTOOLS_DOTNET_v40 and two IIS applications. The MedicalViewerService19 application hosts the LEADTOOLS WCF service classes as web services. The MedicalViewer19 application hosts the LEADTOOLS HTML5 Medical Web Viewer demo application files.
    
16. Tap Test All. Follow any troubleshooting links and make any required adjustments. Tap Test All until all issues are resolved.
    
    
    
    
17. 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.
    

You should now be able to navigate to the link to the demo in the screen shot above and log in using the credentials provided in Step 8. At this point the LEADTOOLS HTML5 Medical Web Viewer demo is fully functional and you can begin your testing.

Troubleshoot LEADTOOLS Service Host Manager - Remote Server Returns 500 Error
WCF features not installed properly in IIS
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:

32-Bit
%SYSTEMROOT%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i
%SYSTEMROOT%\Microsoft.NET\Framework\v3.0\”Windows Communication Foundation”\ServiceModelReg –i

64-Bit
%SYSTEMROOT%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i
%SYSTEMROOT%\Microsoft.NET\Framework64\v3.0\”Windows Communication Foundation”\ServiceModelReg –i

Attached is a complete downloadable PDF document containing the steps above.

Edited by moderator Wednesday, December 27, 2023 4:00:08 PM(UTC)  | Reason: Updated

In the event that you receive a 'Named Pipes Provider, error: 40' you can follow the attached document to resolve.