Restoring the LEAD Storage Server

Note: If you have already worked through the Changing the LEAD HTML5 Medical Viewer to use a Different Database Schema  tutorial, then you should first work through the Restoring the LEAD HTML5 Medical Viewer to its Original State topic of that tutorial.

Step 1: Restore the Storage Server Manager so that it no Longer Uses MyQueryIOD.xml

Step 2: Restore the Application Configuration Files to use the Default Storage Catalog and Default DataSet Schema

<?xml version="1.0"?> 
<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"/> 
 
  <runtime> 
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> 
         <dependentAssembly> 
            <assemblyIdentity name="System.Data.SqlServerCe" publicKeyToken="89845DCD8080CC91" culture="neutral"/> 
            <bindingRedirect oldVersion="0.0.0.0-3.5.1.0" newVersion="3.5.1.0"/> 
         </dependentAssembly> 
         <dependentAssembly> 
            <assemblyIdentity name="Microsoft.Practices.ObjectBuilder2" publicKeyToken="31BF3856AD364E35" culture="neutral"/> 
            <bindingRedirect oldVersion="0.0.0.0-2.2.0.0" newVersion="2.2.0.0"/> 
         </dependentAssembly> 
         <dependentAssembly> 
            <assemblyIdentity name="Microsoft.Practices.Unity" publicKeyToken="31BF3856AD364E35" culture="neutral"/> 
            <bindingRedirect oldVersion="0.0.0.0-1.2.0.0" newVersion="1.2.0.0"/> 
         </dependentAssembly>       
      </assemblyBinding> 
   </runtime> 
  <appSettings> 
    <!--<add key="DataSetSchema" value=" C:\LEADTOOLS 19\Bin\Dotnet4\Win32\MyDataSet.xsd"/>--> 
  </appSettings> 
</configuration> 

Step 3: Rebuild the CSStorageServerManagerDemo.exe with Modifications

Note that you can skip this step completely, and just run the precompiled version of the demo (CSStorageServerManagerDemo_original.exe)

Step 4: Delete the Following Files from {LEAD Installation BIN}

Step 5: Restore GlobalPacs.config to use the Original Shipping Database

<section name="storageDataAccessConfiguration175" type="Leadtools.Medical.DataAccessLayer.Configuration.DataAccessSettings, Leadtools.Medical.DataAccessLayer, Version=19.0.4.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907" /> 
 
<!--<section name="myStorageDataAccessConfiguration175" type="Leadtools.Medical.DataAccessLayer.Configuration.DataAccessSettings, Leadtools.Medical.DataAccessLayer, Version=19.0.4.0, Culture=neutral, PublicKeyToken=9cf889f53ea9b907" />--> 

<storageDataAccessConfiguration175 connectionName="LeadStorageServer19_32"> 
    <add productName="StorageServer" serviceName="L19_PACS_SCP32" 
       connectionName="LeadStorageServer19_32" /> 
    <add productName="Workstation" serviceName="L19_WS_SERVER32" connectionName="MedicalWorkstation19_32" /> 
  </storageDataAccessConfiguration175> 
 
  <!--<myStorageDataAccessConfiguration175 connectionName="MyDicomDb"> 
    <add productName="StorageServer" serviceName=" L19_PACS_SCP32" connectionName="MyDicomDb" /gt; 
  </myStorageDataAccessConfiguration175>--> 

<forwardConfiguration175> 
    <add productName="StorageServer" serviceName="L19_PACS_SCP32" connectionName="LeadStorageServer19_32" /> 
    <!--<add productName="StorageServer" serviceName="L19_PACS_SCP32" connectionName="MyDicomDb" />--> 
  </forwardConfiguration175> 

Step 6: Restore the Forwarding Data Access Layer (Leadtools.Medical.Forward.DataAccessLayer ) to its original state:

Step 7: Remove the Configuration Assembly (My.Medical.Storage.Configuration.dll ) from the Configuration folder

Step 8: Verify that the Storage Server Manager is using the Shipping Database

Products | Support | Contact Us | Copyright Notices
© 1991-2017 LEAD Technologies, Inc. All Rights Reserved.
LEADTOOLS Imaging, Medical, and Document
Click or drag to resize