Skip to main content

Solving HCL 7.1.59 installation error

By
I was encounter below error message when I tried to install HP Comware simulator (H3C cloud Lab).

"The virtualbox version is lower than the HCL needed."

My PC was installed with Virtualbox Version 5.0.16 and it is latest when I am writing this post.

Below is the resolve method to skip this error.

You just open registry editor and go to HKEY_LOCAL_MACHINE>SOFTWARE>Oracle>Virtualbox.
Then change the Data Value of Version and VersionExt to 4.2.18 and try to reinstall Simulator.
You will see no more error while installing it.
Do not forget to revert to correct version data value in registry value after Simulator installation done.

Have a good time.
(Be knowledgeable, pass it on then)
Labels:

Comments

  1. UnknownDecember 20, 2016 at 12:32 PM

    Thank you for the solution. Installed it without any errors and reverted the registry back to its default values.

    ReplyDelete
  2. WillianMay 6, 2018 at 12:09 AM

    Help!!!! Error Failed to create device msr36-20_1

    ReplyDelete
  3. ScottJuly 19, 2019 at 6:19 AM

    Mee to facing the same error how to fix

    hp printer setup

    ReplyDelete
  4. IndahAugust 29, 2020 at 9:14 AM

    How to fix this

    123.hp.com setup

    ReplyDelete
  5. kaloyanmmOctober 10, 2020 at 2:46 PM

    That did it, thank you!

    ReplyDelete

Post a Comment

Popular posts from this blog

Fortigate guide for Begineer - 6

By
I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...
Post a Comment
Read more

Why do we need network virtualization?

By
We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...
144 comments
Read more

Solving "WSUS administration console was unable to connect to the WSUS Server via the remote API" error

By
Today, I've got below when I try to connect my WSUS Server via WSUS Console. Below logs are display in Event Logs too. The WSUS administration console was unable to connect to the WSUS Server via the remote API.  Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 172.16.99.98:80 Source System Stack Trace:    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Soc...
7 comments
Read more