This post is more than 5 years old
31 Posts
0
19612
Update for Windows Server 2008 R2 x64 Edition (KB3161608)
It seems that Update for Windows Server 2008 R2 x64 Edition (KB3161608) caused a Secure Channel error on OpenManage, anyone else see this today?
Running Windows 2008 R2
Servers PE 840 Domain and a PE 2900 General Server
Removing KB3161608 from both server fixes the issue but then I do have my servers updated.
The following fatal alert was generated: 40. The internal error state is 808 (On my Domain)
The following fatal alert was generated: 10. The internal error state is 1203. (On General Server)
Dell OpenManage Systems Management Software (64-Bit) Version 7.4.0
Copyright (C) Dell Inc. 1995-2014. All rights reserved.
Details
Broadcom SNMP Agent Version 17.6.4
Common Storage Module Version 4.4.0
Data Engine Version 7.4.0
Hardware Application Programming Interface Version 7.4.0
Instrumentation Service Version 7.4.0
Intel SNMP Agent Version 1.118.0
Apache Tomcat Webserver Version 7.0.39
Oracle Java Runtime Environment Version 1.7.0_21
Server Administrator Core files Version 7.4.0 (866)
OMACS Version 7.4.0
Instrumentation Service Integration Layer Version 7.4.0
Server Administrator Instrumentation files Version 7.4.0
Inventory Collector Version 7.4.0
Storage Management Version 4.4.0
Server Administrator Common Framework Version 7.4.0
Operating System Logging Version 7.4.0
Remote Access Controller Managed Node Version 7.4.0
Server Instrumentation SNMP Module Version 7.4.0
Agent for Remote Access Version 2.0.0
Server Instrumentation WMI Module Version 7.4.0
bcavnaugh
31 Posts
1
June 24th, 2016 18:00
Installing OSMA 8.3 and will re-install KB3161608
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=TK61C
General Server PE 2900
Looks like this IS THE FIX.
Now Testing OSMA 8.3 on my Domain Controller.
Domain PE 840
Looks like this IS THE FIX.
Make sure you run Windows Update after you restart the server from installing KB3161608
rsenio
8 Posts
0
June 22nd, 2016 15:00
I am seeing the same thing running OSMA 8.1. I'm going to update to 8.2 and check again
rsenio
8 Posts
0
June 22nd, 2016 16:00
That didn't fix it....hmm....
mbodo
1 Message
0
June 24th, 2016 09:00
We had something similar happen with this KB ... it blew up how Tomcat 6/7 handled security certs.
These MS patches introduced some new ciphers to Windows and with that they have also changed the default cipher order preference. This last change is confusing Tomcat as its standard configuration is set to accept all ciphers, but these new ciphers are not known to Tomcat 6 and Tomcat 7. The solution is to restrict Tomcat configuration to only accept the ciphers it fully supports. This is easily done by adding one line to the Tomcat configuration file and restarting Tomcat service.
bcavnaugh
31 Posts
0
June 24th, 2016 15:00
What is this One Line? Can you Post this One Line for us?
rsenio
8 Posts
0
June 24th, 2016 18:00
Don't waste your time. I've already tried that as well. I've got an open case will dell now
bcavnaugh
31 Posts
0
June 25th, 2016 20:00
Did you Install OSMA 8.3? Above you show 8.2
www.dell.com/.../DriversDetails
rsenio
8 Posts
0
June 25th, 2016 21:00
Yes, it was 8.3. Feel free to try, it won't work. As I said, this is now in the hands of the team that does the osma stuff.
rsenio
8 Posts
0
August 16th, 2016 14:00
Use 8.3, if you have issues make sure to uninstall any previous version first. That was my issue, the upgrade left remnants of a the previous version.
ojnik76
4 Posts
0
August 16th, 2016 14:00
hi,,
do we have any updates on this issue?
bcavnaugh
31 Posts
1
August 16th, 2016 16:00
As I said above on 24 Jun 2016 18:06 8.3 Fixed this Issue.