Recently because of a error my Windows unexpectingly restarted.
I was using a virtual machine at that time, and after the restart the configuration file went missing (.vmx) I managed to rebuild this file using the vmware log.
After this, I wanted to start the machine again but it gives a error.
"Could not open virtual machine: /path/pc.vmx Encryption libraries
problem."
I have used the Encryption function in vmware to encrypt the machine.
At this point I cant find any answers to fix this problem, I have the decryption key etc.
Any help is appreciated!
Here is document from Workstation 11 Documentation Center. Hope it can help.
Remove Encryption from a Virtual Machine
You can remove encryption from a virtual machine.
Prerequisites
■ Power off the virtual machine.
■ Remove any sensitive information from the virtual machine.
Procedure
1 Select the virtual machine and select VM > Settings.
2 On the Options tab, select Encryption.
3 Click Remove Encryption.
4 Type the encryption password.
5 Click Remove Encryption.
Related
I've tried looking at other questions here with similar problems, but unfortunately I haven't been able to solve this issue.
For some basic background info, I'm currently using a PC in a lab and the lab has GPU servers somewhere in the institution. I'm attempting to connect the Atom Editor to the remote host. My PC uses Windows 10 and the remote server is Ubuntu 16.04.
I've looked at thie remote-atom guide but for some reason the "Start Server" option is not working. I've also tried to do what this answer has stated, but unfortunately I don't have sudo permission.
Would there be another way that I can connect Atom remotely? Thank you.
You can easily connect to remote FTP using atom even if you do not have any sudo permission on the sudo server.
On Remote server:
- Create a rsa key (ssh-keygen -t rsa)
- add the public key to .ssh/authorized_keys file
- download the private key to you local desktop
On local machine > open Atom editor:
- press ctrl+space to open the 'ftp-remote-edit'
- add the server if not present already
Atom editor: remote server configs
That's it, you are ready to connect and edit files.
Other viable option is using VS code using winScp.
Is there any way to install OpenStack without using virtual box in a single machine?
You can install all openstack services(controller, compute, network) in a single node. But it's not recommended.
If you don't want to install virtualbox you can try VMware
You may also try LXC or XEN if you are using linux. Then create 3 virtual machines and install openstack 3 node configuration.
Yes, of course. Just make sure you have enough resources on the system (single machine) to bare OpenStack. You may use packstack do the All-in-One
deployment. Check out RDO.
There is a possibility of installing openstack(both 2 and 3 node architectures) in a single system. But, things are to be considered. Like the performance of the system used, the primary memory associated with it, the secondary memory that is available, e.t.c
If you're talking about development environment, sure! You don't need a VM at all, and can just install it on your laptop directly! Note that this is not a desirable configuration :)
Other ways are to use a different virtualization tool than VirtualBox, like KVM, or VMware stuff.
Virtual machine is nothing but a system with shared resources. Whatever we do on a VM can be replicated to an individual system.
Make sure you have VT enabled on the hardware , else you may have issues in creating instance on the Compute node.
Regards,
Amit Manel
Whatever you can install in single virtual machine , can also be installed on your machine directly.
After all your machine is much more powerful and stable than your virtual machine.
We use virtual machine just to leave our system intact in case something goes wrong. Just compare the time it would take you to delete and create another virtual machine with time and effort for formatting your entire laptop.
Also, we sometimes use virtual machine if we need to make a network of 2-3 computers for some functionality and we have got only one hardware.
I created with kvm virtual machünes on Ubuntu 14.04
If you create the virtual machines and the virtual networks you can use it.
For the easiest way if you use an orchestration/deployment tool e.g. Mirantis Fuel
Surprising no body talked about Dockers. You can run openstack in a docker container.
According to my experience, always try to install openstack on a fresh system( either on a freshly created VM or on a newly installed OS). I have installed openstack many times, and trust me no error will come just follow this link on a newly setup machine. For old system, I was stuck for 3 days, and only GOD knows where from the hell those errors were showing up.
PS: I have always tried ubuntu system.
When I try to start debugging my windows phone 8 app in Emulator WVGA 512MB the following error message is showing
The Windows Phone Emulator wasn't able to connect to the Windows Phone operating system:
The emulator couldn't determine the host IP address, which is used to communicate with the guest virtual machine.
Some functionality may be disabled.
and the emulator is always showing The Windows Phone OS is starting...
Can't understand what's the problem. Please advice.
This worked for me (found here):
follow the following steps to solve this problem
1.go to network and sharing center
2.go to change adapter setting
3.go to v Ethernet (internal Ethernet port windows phone emulator internal switch)
4.right click it and enable it(if already enabled then disable and enable it again).
At last the problem is solved.
Open Hyper V Manager
Delete all installed Virtual Machines
Delete all Virtual Switches
Restart system
Rerun visual studio
Thanks to Shiv Kumar Ganesh
I had the same problem. After a long investigation and checking the event log, learned that windows firewall is blocking the emulator connecting to the virtual machine. With that information it is simple to fix the problem.
Yes! Just navigate to Control Panel -> System and Security -> Windows Firewall -> Allow app or feature through Windows Firewall. And click on Add another app button and browse the emulator's path (typically "C:\Program Files (x86)\Microsoft XDE\8.0\XDE.exe" but may vary based on your installation location). Choose the appropriate network type that you want and add the new item.
Now go back to VS and run your application (close any emulator instance that you have opened already), everything should work fine now!
the solution that worked for me :
open Hyper V
Select ur VM and go to Virtual Switch Manager.
Select Windows Phone Emulator Internal
if your connection is Internal then , check the Enable VLAN Identification option
press F5 from VS .
good luck!
Just reboot
No magic needed. Just reboot your development machine after installing Windows Phone SDK.
what your describing is usually due to a Firewall of a third party Anti-virus.
If your using Symantec follow this procedure https://stackoverflow.com/a/26326528/4446346
If your using Windows Firewall follow this procedure https://stackoverflow.com/a/27685167/4446346
and If you'r using AVG do the following procedure:
open AVG and go to-->Options-->Firewall Settings-->Expert mode-->Advanced Settings.
Check the "Allow any traffic from/to virtual machines supported by firewall"
and click "OK".
One more thing you must do is go to the "Windows Phone Emulator Internal Switch" and uncheck "AVG network filter driver"
open Network and Sharing Center-->Change Adapter Settings-->Properties
Uncheck "AVG network filter driver"
If you are loading the emulator for the first time, it behaves just like the phone (on first boot) where it will install the initial set of apps and configure them. Which is why the first start will take a long time. You can actually open Hyper-V manager and connect to the VM you had selected at the time of initiating debug - to see the actual progress of what is happening.
Hope this helps.
You can disable Hyper-V from Program and Features and reboot your machine twice. Everything will be default. Enable Hyper-V and reboot twice and everything should be working again.
Also you can check if your vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) in Network and Sharing Center is enabled (mine was not, and I got same error like you).
Check that you have enough free space in your hard drive.
If you have a computer with a touch-screen and get this error, it can be because Hyper-V is trying to port over the touchscreen-fx to the virtual device.
This is (when found) easily corrected:
Shut down all attempt at launching virtual devices.
Go to: Hyper-V Manager->Hyper-V-settings->Physical GPU:s // Uncheck box "use this GPU with RemoteFX"
Try uninstalling vmware player 12 if you have ,I have tried several ways but nothing works until I remove it.
Hope it could help you.
I am having difficulty connecting to a existing Informix database. I am attempting to mimic the configuration that is present on another machine which currently works. By the way, that other machine is on the same network and it is accessing the DB through a tunnel, so I am pretty sure the issue isn't related to the network configuration.
Regardless, here are the steps that I took to try and make the connection
Downloaded clientsdk.3.50.TC9DE and installed this. The working machine uses 3.50.TC2DE, but I couldn't find the installer for that version. (Note that at first I tried using 3.50TC9, not sure if that makes a difference)
Matched the ODBC config in the new machine to the working machine
The working machine has a host name in the Host Name field. I assume this was allowed because the host was set to an IP in the hosts file. Regardless, I am using the IP.
Also I am using C:\Windows\SysWOW64\odbcad32.exe to create the DSN
Made sure that the INFORMIXDIR and PATH directory were correct. as per http://www.dbforums.com/informix/694408-odbc-test-connection-not-successful.html#post2633932 I don't think the locales are the issue because they aren't set in the working machine's Setnet32. Also, I made sure that the locales matched in the ODBC environment settings.
Also, since my INFORMIXDIR is in C:\Program Files (x86)\IBM\Informix\Client-SDK\bin I tried replacing Program Files (x86) with PROGRAM~2 and Client-SDK with CLIENT~1 to no avail.
Tried setting INFORMIXDIR directly in my system environment variables (outside of Setnet32)
Set DBPATH to match the working system in both the user and system environment variables.
Set INFORMIXSERVER to the server in both Setnet and the system environment variables.
Completely lowered the firewall on my machine.
I can ping and telnet into the server.
I have also tried..
Tried this on Windows XP
Tested the ILogin demo. The result was a popup that stated Customer Records Found in the title bar with an empty text area field.
Reinstalled into C:\informix instead of C:\Program Files(x86)...
Rebooted after various steps.
At this point I am at a loss. Has anyone run into this? The only other things I can think of is that I am using Win7 64-bit (with 32 bit drivers) and that the driver is 9DE not 2DE.
Alright so half of the battle is over. I was able to get a "Test connection was successful" on my Win7 machine. We had a copy of the 2.90.TC6 driver available in our file server from way back. I installed it and it worked. So my guess is that the database I am working with isn't compatible with 3.50.TC9DE.
I guess my next course of action is to try and find an installer for 3.50.TC2DE so that I can match the production system.
When I try to connect to local ports, Computer -> Connect local, using Portmon v. 3.02, I'm getting an error message, Error 2, in a small error dialog box:
I run the tool as an administrator (if not, I get error 6).
By the way this is a Windows 7 x64. On 32-bit, in Windows 7 x86, it works fine. How can I fix this problem?
Sysinternals' Portmon works only on 32-bit versions of Windows. It does not support 64-bit (probably its driver is not signed).
From the Portmon homepage:
Runs on:
Client: Windows XP (32-bit) and higher (32-bit).
Server: Windows Server 2003 (32-bit) and higher (32-bit).
In Windows Explorer, right click on portmon.exe --> select Properties --> click the Compatibility tab, and Run in Windows XP compatibility mode. It works fine like that in Windows 7 64-bit.
"Error 2" is "Cannot find the file specified", that is, cannot find a required DLL file.
Originally, you got this error when you tried to run Portmon from a network location: that broke the security trust, causing Portmon to be untrusted (or perhaps just messing up the search path somehow).
On my copy of Windows 7 64 bit, Microsoft Dependency Walker (depends.exe) tells me that PORTMSYS.SYS (the file created/loaded by Portmon.exe), has unresolved dependencies on ci.dll, clfs.sys, hal.dll and kdcom.dll.
Those are the
code integrity
common log file system
hardware abstraction layer
kernel debugger com
libraries, and they aren't actually missing: if they were, Windows wouldn't boot. However, I don't see a copy of those files in SysWow64. This suggests to me that the problem is not with portman.sys: the problem is with the win32 compatibility layer in Windows 7/64 bit: It doesn't support debug properly.
It is now 2018. There is no 64-bit version of Portmon. Serial ports are a legacy standard. The Windows 7 problem was fixed by the release of Windows 8.1. However, there is a faint chance that some Visual Studio utility or security update back-ported to Windows 7 will fix the problem. Perhaps someone who is familiar with SysWow and debugging will comment.
Instead of portmon for Windows x64, you can use an emulator of a pair of virtual COM ports and a simple program that will connect the physical port and one of the virtual ones, as well as perform the logging function.
To create a pair of virtual COM ports you can use:
com0com (preferably version "com0com-2.2.2.0-x64-fre-signed", because it contains signed x64 driver)
Virtual Serial Ports Emulator (VSPE), every time it starts on x64 it asks to purchase a driver, but it works even if you refuse.
Simple mapping and logging program can be found e.g. here or you can write it yourself, it is simple.
The sequence of actions is follows:
Сreate a pair of virtual COM ports using emulator (for example, COM28 and COM29)
Let the external device be connected to the computer COM1 port. In the program, whose exchange with external device we want to listen to, we set up a port COM28 (instead of СОМ1) for communication.
In the mapping program, we set up that we want to bind and log ports COM1 and COM29 (don't forget to set the port baud rate).
I haven't tried it yet, but this question mentions com0com. It creates two virtual serial ports and emulates a null modem cable between them. It claims to be able to run on 64 bit Windows. I'm not sure whether it comes with software that lets you just pipe input from a real port into one of the virtual ports. One of the FAQ's says that you can turn on logging.
I guess in the worst case, you could write your own small program that pipes data from a real port to one of the virtual ports and logs it all.
There's also this question on open-source alternatives that mentions a couple of projects.
I've used AccessPort
http://sudt.com/en/ap/download.htm and it works great. Very similar to Portmon
Don't start Portmon from a network drive/path or something else.
Copy on to the hard disk drive, e.g. on the desktop, restart and try again!
If you run Portmon in compatibility mode, it will work.
Check Make older programs run in this version of Windows.
It says:
To run the Program Compatibility troubleshooter:
Open the Program Compatibility troubleshooter by clicking the Start button Picture of the Start button, and then clicking Control Panel. In the search box, type troubleshooter, and then click Troubleshooting. Under Programs, click Run programs made for previous versions of Windows.
Follow the instructions in the troubleshooter.
The above is a public explanation from Microsoft for a common situation when running older applications in Windows.
But, I can say it briefly;
Right click on portmon.exe
Select menu about "troubleshooting compatibility problem" or something like that (I'm using a foreign version of Windows, so I don't see correct name of that menu in English.)
Select automatic mode
It will detect the problem and recommend Windows XP (SP2) mode
Select it and execute Portmon again.
I hope it works!
Instead of Portmon you can also use the IO Ninja program with the "Serial Monitor" plugin.
It gives a little less information than Portmon, but in a more understandable form. The main thing is, just like a Portmon, it allows you to see the data that is transmitted between a third-party application and an external device via a serial port. The program works under modern versions of Windows (I tried it myself on Windows 10 x64). The aforementioned plugin "Serial Monitor" is paid (but has an evaluation period).
Note: the port that you want to monitor must first be connected to the "IO Ninja" program, and then opened in a third-party application whose exchange with an external device you want to track.
Just to test that the hardware is working, you could perhaps boot a Linux live CD and run the statserial and/or minicom program to verify that it works. The Knoppix distribution seems to contain both those programs.
Serial ports on Linux are named /dev/ttyS0 for COM1, /dev/ttyS1 for COM2, etc.