Unable to print or view final report within Client/Server Network Environment
LIMS Administrators, Lab Analysts, Lab Supervisors
After installing a clean copy of the LIMS-plus client on my workstation, I am unable to print final reports
I can view a final report when connected to LIMS-plus via terminal services but cannot when accessing the application using a localized installation
Our Laboratory recently upgraded the LIMS client on all workstations. However, workstations used by Supervisors and Document Control Specialists are unable to print/view final reports
I am unable to print final report on one workstation but all other workstations are ok.
Our LIMS server experienced a catastrophic failure. Our LIMS network share was restored using a backup. However, we are unable to view final reports
The application is prompting me to specify a path when attempting to print/view final reports. What is going on?
When viewing final reports associated to a case, LIMS-plus 3.x has code instructions to look for a registry entry for Adobe Acrobat Reader. This application is bundled within the LIMS-plus client installer. Laboratories may use the client installer to install Adobe Acrobat reader or they may choose to install it by obtaining the adobe acrobat setup file directly from www.adobe.com.
For all versions of LIMS-plus 3.x, the following registry entry is referenced when a user right clicks on a request and selects "Print Final Report>>Print Destination=Screen".
Segment of LIMS-plus 3.x Application Code: .
= RegOpenKey(HKEY_LOCAL_MACHINE, "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\AcroRd32.exe", @nSubKey)
NOTE: For users experiencing the following error: “Error 76 - Path not found” Click Here
The Quincy County Crime Lab uses a Terminal Services environment for all users. During a department review, the LIMS Administrator (Frank Hart) felt that 3 users needed to be excluded from Terminal Services with respect to accessing LIMS-plus.
Frank installs the LIMS-plus client application on the workstations used by the excluded individuals. These workstations connect to the database using a typical client/server configuration (i.e ODBC connections configured on each workstation).
All three users serve as Documentation specialists within the laboratory. They create, manage, and review standard operating procedures. For these users, Frank made sure that Adobe Acrobat Professional 9.0 was installed on the target workstations. The installation takes place on a Friday afternoon during non-business hours.
On Monday morning, a supervisor (Violet Newstead) is called upon to review a final report for a given case. Violet is one of the three individuals who received a client installation of LIMS-plus to her local workstation. She logs into LIMS using her locally installed client and proceeds to view the final report by right clicking on the completed request. She notices that instead of the application opening the final report, it opens a dialog box asking her to specify a location. To her, it looks as if the system is attempting to locate the final report.
Recognizing that her workstation recently received a local client installation of LIMS-plus, she decides to access LIMS-plus via Terminal Services. Low and behold, she is able to view the final report for the case when accessing LIMS-plus via a terminal Service connection. She contacts Frank Hart.
Frank receives the call from the Violet and begins his analysis. He asks Violet if she is able to create or view PDF documents on her local workstation. Violet indicates that that she is able to open up non-LIMS PDF documents using Adobe Acrobat Professional 9.0. The problem appears to be isolated when final reports are called upon via LIMS-plus. Frank contacts JusticeTrax Support for assistance.
In order to print/view final reports, Adobe Acrobat reader must be installed on the workstation that LIMS-plus is being accessed from. LIMS-plus 3.x is dependent on a registry key that installed during the client installation. If the adobe acrobat is not installed, users will not be able to view final reports.
It was found that when Frank installed the LIMS-plus client on the 3 workstations, he unchecked the “Adobe Acrobat Reader” option within the installer. The three workstations in question were brand new and had only received an installation of Adobe Professional 9.0. When Adobe Acrobat Professional 9.0 is installed the executable of the application is Acrobat.exe. Windows installed the correct registry key for Acrobat.exe. Frank made the assumption that since Adobe Acrobat Professional 9.0 was installed, there was no need for Adobe Acrobat Reader (stripped down free version of the viewer).
The terminal server already had Adobe Acrobat reader installed to it. This was the reason why Violet was able to view the report within Terminal Services whereas her local machine failed.
After installing Adobe Acrobat Reader on the machines that had Adobe Acrobat 9.0 Professional, the 3 users could view and print final reports. The application code has an explicit instruction to look for a registry key tied to AcroRd32.exe. LIMS-plus 3.x does not take into consideration Acrobat.exe (Adobe Acrobat Professional 9.0). This exclusion is by software design. This behavior has been in effect for releases of the application dating back to January 2002.
LIMS-plus is also dependent on the UNC path that configured within system administration. The LIMS database holds the fully qualified UNC path for images, casedocs, final reports and report templates within the following database tables:
dbo.Imaging / dbo.casedocs / dbo.Requests / dbo.Report_Setup
For Client/Server or Mixed Environments, the use of drive letters should be avoided when configuring system default paths for images, case docs, final reports and report templates.
If all users access LIMS via Terminal services, using a drive letter in the system defaults will have no effect if the LIMS network share directory resides solely on the Terminal Server itself.
It is recommended by JusticeTrax that fully qualified UNC paths are specified within system defaults since Mapped Drive letters may not be the same across all workstations.