How to resolve Failed to connect to IPC Port Error - c#-4.0

I am getting one issue in my application Setup USING wix
When i run my setup i got the below exception message:-
Failed to connect to IPC Port System cannot find the file specified:mscorlib.dll
After getting this message i got a windows message
There is a problem with this installer setup.
A program run as a part of system did not finish as expected.
Is there any way to resolve it.

Get to Dos command line then type in
Netsh winhttp show proxy ( Press Enter )
then type in
Reset proxy ( Press Enter )
This will release the Internet Proxy IP settings, restart the PC if needed.

Related

Virtual-box failed to start VM VERR_INTNET_FLT_IF_NOT_FOUND

When I run vagrant up I get this error
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "3ae7b70c-8ea1-417a-ab67-99aef96624f8", "--type", "headless"]
Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
I found the solution here: https://www.howtoforge.com/setup-a-local-wordpress-development-environment-with-vagrant/ which is to update the driver of VirtualBox Host-Only Ethernet Adapter
But the problem is I am remotely connected to the machine. So I am afraid that the network settings may lose my remote connection. Also, I cannot reboot the machine.
Is it safe to follow the steps mentioned in the link above which should not disconnect me? If not, is there any alternative way?
Recently I have struggled with this issue. I tried many times to solve the issue. Sometimes I was able to run my vagrant machines successfully but how I did was not sure because I was trying lot of options. But finally, I found a way to solve it. It's pretty simple and tricky.
Solution:
Once you get this error on your terminal, just open your computer network adaptors from the control panel. Select the adaptor which was created for that virtual box. simply disable once and enable again. then run vagrant up command. That's it. the problem is gone.
- Start --> Network status --> Change adaptor options --> (select the Ethernet adaptor - In my case it is Ethernet4)
- Right click --> Disable and right click --> Enable
- vagrant up
I faced the same issue and could not resolve it by changing properties in Network Adapters.
Then i reinstalled Virtual Machine by below command and it worked fine:
V:\softwares>VirtualBox-6.0.4-128413-Win.exe -msiparams NETWORKTYPE=NDIS5

Emulator is not detected automatically unable to connect to device

I have a Dell device and suddenly I cannot connect the Android studio to the emulator. I get the following error message:
unable to open connection to: localhost/127.0.0.1:5037, due to:
java.net.connectexception: connection refused: connect
Any Idea how to fix it ?
Try Manually Starting the Server.
Location to your ADB.exe Android\Sdk\platform-tools\adb.exe start-server
I had the same problem after some unknown operations with my Windows 10. I tried many different ways, and finally solved it with the following steps:
open Command Prompt with Adminstrator privilege. (If you don't know how to, please google.)
"netstat -ao" to find which process takes the port of 127.0.0.1:5037. FOr example, something like
TCP 127.0.0.1:5037 mypcname:0 LISTENING 15752
Here the culprit PID is 15752.
"taskkill /PID /F PID" to kill the process. Replace PID with your number, e.g., 15752.
retry adb. If it works, you may sometimes have to proceed with the following steps.
If it is a Windows service that is using the port, it may start automatically, and blocks adb subsequently. You could specify another adb server port for environment variable ANDROID_ADB_SERVER_PORT.
If the Windows service is LogsAndAlerts (which is the common case for many), you can disable or delete it with:
sc config "LogsAndAlerts" start= disabled
sc delete "LogsAndAlerts"
Download this and extract it to in my case
C:\Users\Dev\AppData\Local\Android\Sdk\platform-tools.
It worked for me.

gitkraken failed to connect to gitlab invalid argument

I want to connect to my school gitlab (self-hosted) with gitkraken.
It create the repo when i try to init but a few second later i get this error :
failed to connect to (school.gitlab.url) invalid argument
I'm on win7 x64
gitkraken v4.0.5
I'm connected to the gitlab on gitkraken and my SSH key is good.
I also try to desactivate my firewall but no change.
Can someone help me please?
I would set up a proxy, that fixed it for me.
On windows:
Press win key
Type proxy settings
Turn on use a proxy server
Type in IP and port (google free proxies to find one)
Press save
GitKraken should detect the proxy

Cygwin Error : tcp_peer_send_blocking: send() to socket

My Cygwin installed on Windows 7 was working properly till I try to install a new package. The package installation failed. Then I keep getting this error every time I want to run my Open MPI program. I can successfully compile the program but cannot run it. I even remove and make a new installation without success.
Thanks for any hints. Below is the sample error message.
[Reloaded-PC:03900] [[3921,1],0] tcp_peer_send_blocking: send() to socket 13 failed: Transport endpoint is not connected (128)
[Reloaded-PC:03900] [[3921,1],0] tcp_peer_send_blocking: send() to socket 13 failed: Transport endpoint is not connected (128)
[Reloaded-PC:04676] [[3921,1],2] tcp_peer_send_blocking: send() to socket 13 failed: Transport endpoint is not connected (128)
[Reloaded-PC:04676] [[3921,1],2] tcp_peer_send_blocking: send() to socket 13 failed: Transport endpoint is not connected (128)
The problem is solved by disabling the unused network adapter in "Control Panel->Network and Internet->Network Connections".
It turned out the unused network adapter tried to get configured by DHCP and an IP address started with "169.254.X.X" was assigned to this adapter when DHCP fails. Somehow openmpi on Cygwin use that invalid IP address for establishing communication between processes.
I figured it out by looking at /tmp/openmpi-sessions-{username}/{PID of orterun}/contact.txt.
I had this same problem on Cygwin with OpenMPI 1.10.4.
Try adding "-report-uri -" to your mpirun command to see what IP address it's trying to use for connection:
mpirun -report-uri - -np 2 a.exe
It should print out a line that looks something like this:
568328192.0;tcp://192.168.10.103,169.254.247.11,0.0.0.0,0.0.0.0,0.0.0.0:55600
If the first IP address after the "tcp://" is not a current valid address for your machine, that's the problem and things are likely to break (even if the correct IP appears later in the list). Apparently ORTE is not smart enough to order the interfaces based on what is actually enabled and online.
If the wrong IP corresponds to an old/disabled interface, uninstall it (if possible) using the windows network connections control panel.
In my case, the first address was a DHCP address for an old hardware adapter I'd removed and thrown away long ago (but apparently not uninstalled in software). Windows normally hides such removed-but-not-uninstalled interfaces in the control panel, but the settings remain in the registry under:
HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\
Search in that registry subkey for the bogus IP address and you are likely to find the problematic interface. I fixed mine by changing the IP address in that registry key to match my current static IP, but uninstalling the interface entirely would probably also work.
I had the same problem with openmpi v 1.8.8 (which is the default version of the package installed by cygwin). Manually going back to version 1.8.6 fixed the issue for me.
I just encountered this problem and in my case I had to disable the "VirtualBox Host-Only Network" adapter (I recently installed virtualbox and have not used openmpi in cygwin after that until today).
1. Open the Cygwin terminal.
mpicc --version
mpirun --version
If not execute, follow the document below and reinstall everything. Document
2. Try turning off Bluetooth and test your program again.
3. Try closing the Wifi and test your program again (you can connect to the wired internete)
4. Open C:\Windows\System32\drivers\etc\hosts
add line
127.0.0.1 localhost cygdrive wpad
and test your program again.
5. If you have a virtual network like VirtualBox or similar, turn off the control panel and test your program again.
6. If possible, uninstall VirtualBox completely. Restart your computer and test your program again.
7. Try turning off the Windows Firewall and test your program again.
The above steps solved both the "tcp_peer_send_blocking: send () to socket 12 failed: transport endpoint is not connected" error and the slowness problem in MPI for Windows 10 - Cygwin.

Guacamole internal error

So I followed a bunch of tutorials and installed tomcat7 and guacamole (http://guac-dev.org/) on an ubuntu server (virtual machine).
I managed to set everything up...tomcat is running perfectly.But whenever I try to connect via localhost:8080/guacamole/ and log in..I get this error saying:
Internal error... with a countdown that reloads the page
I used guacd -f to and found out that apparently it is "Unable to bind socket to any addresses."
Looking at the manual (http://guac-dev.org/doc/gug/troubleshooting.html) I found this error and followed the instructions on how to fix it and changed the port information.
Didn't work! And I didn't find anything after hours of google searches.
Do you have an idea what I can do?

Resources