ImageNow Support‎ > ‎

ImageNow News

New Java Update Causes WebNow Crash

posted Jul 28, 2017, 7:38 AM by Stephen Blaylock

The new or latest Java update is incompatible with the WebNow portal.  Java 8.141 causes a WebNow security issue and can not verify a resource.  Short answer, WebNow can not connect to the ImageNow server. 

Resolution
 
There is an unintentional breaking change with the jar signing and verification that was introduced by Oracle in the Java 8 patch 141 released July 18, 2017.

This issue effects all versions of WebNow. This issue may also impact the Java based Forms Server client on pre 7.1.2 versions of Perceptive Content before the HTML based Forms Server client was introduced.

The issue is resolved by updating the client JRE to Java 8 patch 144 on workstations where WebNow is being accessed.

Java™ SE Development Kit 8, Update 144 (JDK 8u144)
http://www.oracle.com/technetwork/java/javase/8u144-relnotes-3838694.html

Image Now Printer Crashes

posted Jan 23, 2017, 7:49 AM by Stephen Blaylock   [ updated Jan 23, 2017, 8:28 AM ]

ImageNow Printer Crashes

After the July 2016 upgrade to the Imaging System, the ImageNow printer may intermittently break. Lexmark, the company that provides the Imaging System), is aware of the issue and working on a fix; unfortunately we do not have a timeline for the fix. This document will provide steps to minimize printer issues and resolve them should they occur.

Nature of the issue

The issue can Manifest itself in two ways:

  1. The program that is sending a document to the ImageNow Printer (e.g. Microsoft Word, Excel, Adobe Reader, etc) stops responding.
  2. Nothing happens when a printing a document. Perceptive Content never receives the document and the prompt to choose a capture profile does not appear.

Troubleshooting steps

Removing previous versions of the PEERNET Spooler Service may reduce the frequency of the issues. This does require administrative privileges for the workstation. See ECMS - Removing previous versions of PEERNET Spooler Service for instructions.

Should the printer break, the only working resolution currently available is to reinstall the ImageNow printer. See ECMS - Reinstalling the ImageNow Printer for instructions. Note that it is important to follow each of the steps to reinstall the printer carefully, as omitting certain steps (such as restarting the machine) will interfere with the installation. It is recommended that these steps be performed with assistance from local desktop support.

A future resolution

Lexmark acknowledges the issue, but they have not provided a timeline for when a fix will be implemented. We are hopeful that a fix will be introduced by the time that we patch the system in February 2017, but cannot guarantee that this will be the case.

WebNow and eForms Unsupported in Google Chrome v42 and Higher

posted Apr 17, 2015, 1:08 PM by John Brown   [ updated Apr 17, 2015, 1:16 PM ]

Google has moved to disable certain older browser plug-ins, including Java, from its Chrome browser. This change means that WebNow and eForms will no longer work in Google Chrome if you are using Chrome version 42 or higher. Google will not be bringing back support for the plug-ins used by these applications, so our current recommendation is to use an alternative browser, such as Firefox or Internet Explorer, to access these applications. 

ImageNow Patch Notes - Summer 2014

posted Aug 12, 2014, 7:00 AM by John Brown   [ updated Aug 20, 2014, 5:51 AM ]

The following are key items that will be resolved with the patching of ImageNow/WebNow on 8/22/14 - 8/23/14:

WebNow
  • Full support for Java 7
  • Updates to handle security settings introduced in Java version 1.7.0.45 (Known Issue Link)
  • Updates to the Trusted Application Certificate (Will prevent a future occurrence of the issue here: Known Issue Link)
  • Document properties now display properly in Safari or Firefox on a Mac
eForms
  • Full support for Java 7
  • Updates to handle security settings introduced in Java version 1.7.0.45 (Known Issue Link)
  • Updates to the Trusted Application Certificate (Will prevent a future occurrence of the issue here: Known Issue Link)
ImageNow Client
  • Resolved an issue with the incorrect creation time being set on batch scanned documents, resulting in incorrect sorting (Known Issue Link) *
  • Support for Java 7 when linking in certain application plans *
  • The ImageNow Printer now installs correctly and has the same settings available as in ImageNow version 6.6. (Known Issue Link) **
  • Improvements to how batches are processed when scanning *
ImageNow Server
  • Mail Agent now correctly reconnects to the server after a server restart/outage
  • Improved speed performance when capturing documents

* These fixes require a new version of the ImageNow Client to be installed
** This fix requires a new version of the ImageNow Client to be installed and the ImageNow Printer to be uninstalled and then re-installed with the new client.

Update on Document Capturing Issues - 2/20/14

posted Feb 20, 2014, 12:35 PM by John Brown

As you are likely aware, since the upgrade to ImageNow 6.7 last August, we have been experiencing intermittent issues with documents being captured but failing to actually enter workflow. In these cases, documents would be scanned or printed into ImageNow, but would get stuck in what is known as the "Batch Processing Agent." With this issue, we have been able to correct it by restarting this agent and resubmitting the documents to the system. This prevented any data loss, but still caused an inconvenience to users expecting to see their documents enter workflow right away.

We are happy to report that after nearly six months of working with the vendor, Perceptive Software, we have finally found the cause for this problem. The Batch Agent mentioned above is failing to correctly "clean up" after itself, leaving a large number of temporary folders on the server. Once we reach a threshold of folders, the process starts to fail. This bug has been identified and the vendor is working on a solution that will be presented in a future update. In the interim, we here in UMS ITS are putting into place a plan to prevent this from happening again. Now that we know what the issue is, we can proactively track what is going on and take the necessary steps to prevent the failures we have been seeing.

We appreciate your patience as we have worked through this issue and are quite happy that we finally have a solution in place for you. Please let us know if you have any questions or concerns about this going forward.

MaineStreet ImageNow Linking Page Change

posted Jan 21, 2014, 11:18 AM by John Brown

The linking pages for ImageNow found in Campus Community under University of Maine System > ImageNow Home have undergone a slight change to correct an issue that was found. It will now be necessary to click on the Clear Displayed Data button in between searches. The Search For Student button will be disabled after the initial search, until the Clear button is clicked. This is to prevent an issue that was found with some fields not clearing data in the case where a new search result does not have any data to report (e.g. the field is blank). Please let us know if you have any questions or concerns.

Update to Java/WebNow Issue

posted Jan 17, 2014, 7:47 AM by John Brown   [ updated Jan 17, 2014, 7:48 AM ]

The support article posted at the link below has been updated with some additional steps. Please review before configuring any security settings for users with Java and WebNow issues. In addition, here are a few key points about this issue:
  • Users should not be advised to lower their Java security level to correct the issue. Doing so could expose that user to potential security threats. The steps provided at the linked article provide a targeted workaround that only gives the security exception to WebNow.
  • If a user does not have the security options outlined in the linked article, they most likely do not have Java 7 Release 51 installed yet. We have had some reports of users on Release 45 also having this issue, although it is unclear why this would happen. Additionally, if a user has the Java Runtime Environment installed for development purposes, the Java JRE will also need to be updated to Release 51 to get the newest Java Control Panel.
  • The additional directions in the article will add a second exception for the MaineStreet WebNow link. The address used for this feature is slightly different than what is used when logging into WebNow directly, so both addresses need to be on the exception list.
The support article can be found here:

Known Issue with WebNow and Java 7 Release 51

posted Jan 15, 2014, 1:06 PM by John Brown

Java has released an update for Java 7 (Release 51) that will cause WebNow to not load for anyone with the update installed. This is a known issue and we have developed a workaround for the problem. The directions for this workaround can be found in the article below:


A future update to WebNow will also correct this issue, but the best interim solution is to follow the steps outlined at the link above. Please let us know if you have any questions or concerns.

ImageNow Emergency Maintenance - 12/10/13 - 11 AM

posted Dec 10, 2013, 7:59 AM by John Brown

In order to repair our authentication issues, we will be doing an emergency restart of ImageNow services at 11 AM. We expect the outage to be brief, but the system will be unavailable during this restart. We will send confirmation once the system is back up and available. We appreciate your patience as we work through this issue.

ImageNow Authentication Issues - 12/10/13

posted Dec 10, 2013, 6:58 AM by John Brown   [ updated Feb 14, 2014, 9:47 AM ]

ImageNow is currently being affected by back end authentication issues that is preventing users from logging in. This is an issue affecting a few different systems, including ImageNow. We are working on resolving the root cause and hope to have the issue resolved shortly. If you are currently logged into ImageNow, you will continue to have access, as long as you do not sign out.

1-10 of 26