poweruser

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-11
18:30
1738 views
iManager-Iprint Plugin broken - After OES2015 SP1 Patch
After applying the Feb 6th 2018 OES 2015 SP1 Mandatory patch and the latest SLES 11 SP4 patches,
I can't no longer manage iprint manager or printers through iManager. It will be prompted with " Internal error, a page has performed an illegal action" message. I have several servers with iManager and they all had the same issue after the patches. Though I can't manage or create new printer from imanager, Print service behaves normally.
The last time I updated was Jan, 2018.
I have tried to update imanager framework plugin, and update iprint plugin with no help. I have even reinstalled iprint plugin followed this TID
https://www.novell.com/support/kb/doc.php?id=7014466
I can't be alone on this issue. Any body ran into or confirmed this bug?
I can't no longer manage iprint manager or printers through iManager. It will be prompted with " Internal error, a page has performed an illegal action" message. I have several servers with iManager and they all had the same issue after the patches. Though I can't manage or create new printer from imanager, Print service behaves normally.
The last time I updated was Jan, 2018.
I have tried to update imanager framework plugin, and update iprint plugin with no help. I have even reinstalled iprint plugin followed this TID
https://www.novell.com/support/kb/doc.php?id=7014466
I can't be alone on this issue. Any body ran into or confirmed this bug?
6 Replies
lca25

Captain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-12
12:38
Same here.
laurabuckley

Micro Focus Expert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-12
12:43
Hi,
Check to see if your server has this version of Java installed (ps -ef | grep java) :
java-1_7_1-ibm-1.7.1_sr4.20-26.13.1
If so I recommend you backrev it to the previous version (zypper in -f java-1_7_1-ibm=1.7.1_sr4.15-26.8.1). Restart novell-tomcat6 and let us know if this makes a difference.
Cheers,
Check to see if your server has this version of Java installed (ps -ef | grep java) :
java-1_7_1-ibm-1.7.1_sr4.20-26.13.1
If so I recommend you backrev it to the previous version (zypper in -f java-1_7_1-ibm=1.7.1_sr4.15-26.8.1). Restart novell-tomcat6 and let us know if this makes a difference.
Cheers,
Laura Buckley
Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
lca25

Captain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-12
12:49
It was the SLES patch that broke it for us as we were managing iprint from oes server-based iManagers (servers that did not have iprint installed), up until the most recent patching on Sunday. These servers were patched about 2 weeks earlier.
lca25

Captain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-12
12:57
That fixed it for us.
poweruser

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-12
13:32
Backrev to version 1.7.1_sr4.15-26.8.1 works. This exact Sles SP4 patch released on March 7th, 2018 is the issue.
- slessp4-java-1_7_1-ibm-13500-1
I don't think they're going to pull it.
Thanks,
- slessp4-java-1_7_1-ibm-13500-1
I don't think they're going to pull it.
Thanks,
Mjedlicka1

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-03-13
07:37
There is a solution other than Backrev ing the java update. The problem is links in /etc/alternatives to the policy jar files for java. This can be fixed by running:
update-alternatives --auto jce_1.7.1_ibm_local_policy
After the update and restarting tomcat.
update-alternatives --auto jce_1.7.1_ibm_local_policy
After the update and restarting tomcat.