Error processing SSI file
Show in webframe

Restoring the Viewer to its Original State

Step 1: Restore the original Leadtools.Medical.WebViewer.Addins.dll assembly

·         Start Visual Studio

·         Open the Leadtools.Medical.WebViewer.Addins project

·         Open the properties page

·         Remove the reference to My.Medical.Storage.DataAccessLayer

·         Remove TUTORIAL_CUSTOM_DATABASE from the Conditional compilation symbols

·         Rebuild Leadtools.Medical.WebViewer.Addins.dll

·         Copy Leadtools.Medical.WebViewer.Addins.dll to the Medical Viewer Service Bin folder

·         The default bin location for the medical web viewer services is here:

·         C:\LEADTOOLS 19\Examples\PACSFramework\MedicalWebViewer\Leadtools.Medical.WebViewer.WCF\Bin

·         If you cannot copy the assembly

·         start a command box

·         type iisreset and hit the enter key

·         try again to copy the Leadtools.Medical.WebViewer.Addins.dll to the Medical Viewer Service Bin folder 

Step 2: Restore the original Leadtools.Medical.WebViewer.WCF.dll assembly

·         Follow steps in Step 1 using the Leadtools.Medical.WebViewer.WCF project

 Step 3: Restore the web.config file

<?xml version="1.0" encoding="utf-8"?>

<configuration>

  <!--<configSections>

    <section name="xmlStorageCatalogSettings" type="Leadtools.Medical.Storage.DataAccessLayer.XmlStorageCatalogSettings, Leadtools.Medical.Storage.DataAccessLayer" />

  </configSections>

  <xmlStorageCatalogSettings catalogPath="C:\LEADTOOLS 19\Bin\Dotnet4\Win32\MyCatalog.xml"/>-->

  <system.web>

      <compilation debug="true" />

      <authentication mode="None"/>

      <httpRuntime maxRequestLength="2097151" />

      <hostingEnvironment shadowCopyBinAssemblies="false"/>

      <pages compilationMode="Never"/>

   </system.web>

   <!-- When deploying the service library project, the content of the config file must be added to the host's

  app.config file. System.Configuration does not support config files for libraries. -->

   <system.serviceModel>

      <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />

 

      <services>

         <service name="Leadtools.Medical.WebViewer.Wcf.StoreService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IStoreService" behaviorConfiguration="WebViewerServiceBehavior" bindingConfiguration="HandleLargeData">

            </endpoint>

         </service>

 

         <service name="Leadtools.Medical.WebViewer.Wcf.ObjectQueryService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IObjectQueryService" behaviorConfiguration="WebViewerServiceBehavior">

            </endpoint>

            <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

         </service>

         <service name="Leadtools.Medical.WebViewer.Wcf.ObjectRetrieveService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IObjectRetrieveService" behaviorConfiguration="WebViewerServiceBehavior">

            </endpoint>

         </service>

         <service name="Leadtools.Medical.WebViewer.Wcf.PacsQueryService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IPACSQueryService" behaviorConfiguration="WebViewerServiceBehavior">

            </endpoint>

            <!-- Metadata Endpoints -->

            <!-- The Metadata Exchange endpoint is used by the service to describe itself to clients. -->

            <!-- This endpoint does not use a secure binding and should be secured or removed before deployment -->

            <endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange" />

         </service>

         <service name="Leadtools.Medical.WebViewer.Wcf.PACSRetrieveService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IPACSRetrieveService" behaviorConfiguration="WebViewerServiceBehavior">

            </endpoint>

         </service>

         <service name="Leadtools.Medical.WebViewer.Wcf.AuthenticationService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IAuthenticationService" behaviorConfiguration="WebViewerServiceBehavior">

            </endpoint>

         </service>

         <service name="Leadtools.Medical.WebViewer.Wcf.PatientAccessRightsService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IPatientAccessRightsService" behaviorConfiguration="WebViewerServiceBehavior">

            </endpoint>

         </service>

         <service name="Leadtools.Medical.WebViewer.Wcf.AnnotationsService" behaviorConfiguration="WebViewerServiceBehavior">

            <endpoint address="" binding="webHttpBinding" contract="Leadtools.Medical.WebViewer.ServiceContracts.IAnnotationsService" behaviorConfiguration="WebViewerServiceBehavior" bindingConfiguration="HandleLargeData">

            </endpoint>

         </service>

      </services>

      <extensions>

         <behaviorExtensions>

            <add name="jsonWebHttp" type="Leadtools.Dicom.Services.ErrorHandler.JsonErrorWebHttpBehaviorElement, Leadtools.Medical.WebViewer.WCF, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />

         </behaviorExtensions>

      </extensions>

      <bindings>

         <webHttpBinding>

            <binding name="HandleLargeData" maxReceivedMessageSize="2147483647">

              

               <readerQuotas maxDepth="2147483647"

                  maxStringContentLength="2147483647"

                  maxArrayLength="2147483647"

                  maxBytesPerRead="2147483647"

                  maxNameTableCharCount="2147483647" />

            </binding>

         </webHttpBinding>

      </bindings>

      <behaviors>

         <serviceBehaviors>

            <behavior name="WebViewerServiceBehavior">

               <!-- To avoid disclosing metadata information,

          set the value below to false and remove the metadata endpoint above before deployment -->

               <serviceMetadata httpGetEnabled="True" />

               <!-- To receive exception details in faults for debugging purposes,

          set the value below to true.  Set to false before deployment

          to avoid disclosing exception information -->

               <serviceDebug includeExceptionDetailInFaults="True" />

            </behavior>

         </serviceBehaviors>

         <endpointBehaviors>

            <behavior name="WebViewerServiceBehavior">

               <webHttp />

               <jsonWebHttp />

            </behavior>

         </endpointBehaviors>

      </behaviors>

   </system.serviceModel>

   <connectionStrings>

   </connectionStrings>

   <appSettings>

      <add key="license" />

      <add key="key" />

      <add key="ClientAe" value="L19_CLIENT32" />

      <add key="ClientIP" value="192.168.0.181" />

      <add key="ClientPort" value="1000" />

      <add key="ServerAe" value="L19_PACS_SCP32" />

      <add key="ServerIP" value="192.168.0.181" />

      <add key="ServerPort" value="504" />

      <add key="globalConfigPath" value="C:\LEADTOOLS 19\Bin\Dotnet4\Win32\GlobalPacs.config" />

      <add key="storageServerServicePath" value="c:\LEADTOOLS 19\bin\dotnet4\win32\L19_PACS_SCP32\" />

     <!--<add key="DataSetSchema" value="C:\LEADTOOLS 19\Bin\Dotnet4\Win32\MyDataSet.xsd"/>-->

   </appSettings>

</configuration> 

 

Step 4: Verify the HTML5 Medical Web Viewer Demo is using the Shipping Database

§         Login with the Username and Password credentials that you defined during database configuration

§         Click the Search button to display the existing studies in the original shipping database

§         You will see a patient from the original shipping database (JONES^JR^JOHN^L)

 

Error processing SSI file