Avocent Dsview Error
Contents |
- click to join Wikis - Page
Avocent Dsview 3 Manual
Java VM Error when installing DSView 4 Environment:DSView 4.0Issue:When installing DSView 4.0, user encountered a Java VM error.Cause:User was trying to avocent dsview 4 manual install DSView 4 on a Win2003 32 bit virtual machine, which is not supported.Supported Operating Systems for DSView 4Microsoft® Windows Server 2003 (x64), 2003 R2 (x64), 2008 (x64), 2008 R2 (x64)SuSe® Linux Enterprise Server 10 (x64), 11(x64)RedHat® Enterprise Server 4 (x64), 5.4 (x64)Sun™ Solaris SPARC® 9, 10Attached is the DSView 4 Management Software Transition Technical Bulletin.Attachment: http://community.emerson.com/networkpower/support/avocent/dcsoft/dsview_4/m/mediagallery/1153.aspx Share History More Cancel
- click to join Wikis - Page DSView3: Unable to Communicate with Device Error DSView3:
Avocent Dsview 3 Firefox Plugin
Unable to Communicate with Device errorMessage: Unable to Communicate dsview download with DeviceIssue:The message was received when adding a device to DSView3Cause:The firmware version of an avocent viewer plugin appliance and supporting DSView3 Plug-in are not compatible either too new or older version; for instance, DSR8035 firmware version 3.7.1.9 (which is too http://community.emerson.com/networkpower/support/avocent/dcsoft/dsview_4/w/wiki/1029.java-vm-error-when-installing-dsview-4 new) will not communicate with DSView3 DSR Support Plug-in version 1.0.0.354 (which is quite older) due to DSView3 software 3.6.0.127 version. Every DSView3 installation package includes with different version of the appliance’s plug-ins. A few plug-ins can be upgraded from DSView3, but mostly there are not available. It http://community.emerson.com/networkpower/support/avocent/dcsoft/dsview/w/wiki/943.dsview3-unable-to-communicate-with-device-error has to be upgraded or fresh installed the DSView3. (Hint: Checking Plug-in supporting version; DSView3 >> System >> Plug-in)Resolution:1. Check your installed DSView3 version.2. Check the DSView3 Plug-in version of the appliance going to be added.3. Check the firmware version of the appliance.4. Compare the appliance’s firmware version to the DSView3 Release Note (Note: It is listed in the ‘Appliance Compatibility/Plug-in Information’ section).5. Perform one of the following options:a. Downgrade the appliance firmware.Note: When downgrading a firmware, please make sure to ‘Clear a Certificate’ from the serial console of the appliance before adding it back to the DSView3 software.b. Upgrade the appliance’s firmware.c. Upgrade the appliance’s firmware and DSView3 Software. 6. Readd the appliance to DSView3 using 'Type' such as DSR8035. Resources:Current Product Updateshttp://www.avocent.com/Services_and_Support/Technical_Support/Product_Updates/Product_Updates.aspxLegacy Product Updateshttp://www.avocent.com/Services_and_Support/Technical_Support/Product_Updates/Product_Updates-Legacy.aspxDSView3 Download: Installers, Release Notes, and Plug-inshttp://www.avocent.com/Services_and_Support/Technical_Support/Product_Updates/Treeview_Updates/DSView_3_Downloads.aspxI hope it helps.Chakkrit Wattananusit unable_to_communicate_with_device_error Share History More Cancel
Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug471413 - https://bugzilla.redhat.com/show_bug.cgi?id=471413 Avocent KVM viewer doesn't work with IcedTea plugin Summary: Avocent KVM viewer doesn't work with IcedTea plugin Status: CLOSED CURRENTRELEASE Aliases: None Product: Fedora Classification: Fedora Component: java-1.6.0-openjdk (Show other bugs) Sub Component: --- Version: 13 Hardware: All Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Deepak Bhole QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: avocent dsview Show dependency tree /graph Reported: 2008-11-13 10:36 EST by Charles R. Anderson Modified: 2011-12-12 02:41 EST (History) CC List: 20 users (show) adam820 antillon.maurizio apevec chrisw clalance csimpson cyrusyzgtt fabrice lkundrak mark mburns mike.stefanelli nelg npatil paulds rderooy redhat rkhadgar rruss wesley See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2011-06-02 16:34:47 EDT avocent dsview 3 Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) java.stdout (334 bytes, text/plain) 2008-11-17 12:20 EST, Charles R. Anderson no flags Details java.stderr (16.45 KB, text/plain) 2008-11-17 12:20 EST, Charles R. Anderson no flags Details firefox terminal output (6.38 KB, text/plain) 2008-11-17 12:23 EST, Charles R. Anderson no flags Details java.stderr for comment #10 (31.87 KB, application/octet-stream) 2009-02-24 15:08 EST, Stefan Neufeind no flags Details stderr-output when run via http (to comment #15) (7.49 KB, application/x-compressed) 2009-02-26 17:35 EST, Stefan Neufeind no flags Details Avocent KVM java.stdout (5.40 KB, text/plain) 2009-02-26 18:27 EST, Charles R. Anderson no flags Details Avocent KVM java.stderr (1.03 MB, text/plain) 2009-02-26 18:29 EST, Charles R. Anderson no flags Details Avocent KVM firefox terminal output (1.17 MB, text/plain) 2009-02-26 18:31 EST, Charles R. Anderson no flags Details Avocent KVM java.stdout (4.58 KB, text/plain) 2009-05-13 19:23 EDT, Charles R. Anderson no flags Details Avocent KVM java.stderr (136.35 KB, text/plain) 2009-05-13 19:23 EDT, Charles R. Anderson no flags Details Avocent KVM firefox stdout (142.31 KB, text/plain) 2009-05-13 19:26 EDT, Charles R. Anderson no