Known Issues

Aside from the unsupported platforms implied in Support and the issues outlined in Limitations, this release includes the following additional known issues:

 

5391	Description: squirt-server receives a corrupted source.info from squirtcopy. Workaround: On the VMWare‑hosted PNs, switch the NIC type from E1000E to E1000.
5823/6012/6063	Description: On Windows Server 2012 R2, it is possible that the mouse may not be activated when an RN is running in test mode via Java console. Workaround: Uninstall the Intel(R2) 82371SB PCI to USB Host Controller. To uninstall Intel(R2) 82371SB PCI to USB Host Controller: 1. Start the RN. 2. Bring up a Java console, then connect to it via VNC. 3. Use a keyboard to start the Device Manager, then uninstall Intel(R2) 82371SB PCI to USB Host Controller. a. From the Xen Center console, press the Windows key (Send Ctrl-Esc). b. Launch the command prompt: type "cmd", then press Enter. c. Start the Device Manager: type "devmgmt.msc", then press Enter. d. Use tab and keyboard keys to uninstall the Intel(R2) 82371SB PCI to USB Host Controller from the Driver tab. 4. Reboot the RN to rescan the hardware. After the Intel(R2) 82371SB PCI to USB Host Controller drivers are working, the mouse should work. a. Launch the command prompt: Start > type "cmd", then press Enter. b. Reboot the machine: type "shutdown /r /t 0", then press Enter. 5. Repeat Step 1 thru Step 4 if mouse still does not work.
5868	Description: When onQ event log reports 3010 code for any Windows PNs, the auto-upgrade fails. Workaround: Perform one of the following workarounds in the order that they are listed: • Restart onQ Service on the PN. • Reboot the PN. • Uninstall and reinstall the last msi package at C:\Program Files\Quorum\installer.
5916	Description: BSOD occurs when booting win2k12R2 RN in production mode. The RN stays disconnected. Workaround: If an RN boots to BSOD, verify that the PN has all the latest critical Windows updates installed. If it doesn’t, install them on the PN. Then, back up and build the RN. The RN should boot successfully.

 

v3.6 SP1 HF1