Ethereum node connection error:'(

[unitedcryptos]

Version: Ethereum-Wallet-installer-0-8-10.exe Windows 7

Hi, please support with the wallet below! Your help is greatly needed! All the best.

System information

Version: `0.0.0`
OS & Version: windows/linux/osx
Node type: `eth/geth(default)`
![screenshot 2017-05-28 23 26 11](https://cloud.githubusercontent.com/assets/29031969/26538719/52dd89e4-43fd-11e7-8b4a-be1aff9f5ed9.png)
![screenshot 2017-05-28 23 26 20](https://cloud.githubusercontent.com/assets/29031969/26538720/52e60dda-43fd-11e7-9f3a-2554052d9255.png)
![screenshot 2017-05-28 23 28 04](https://cloud.githubusercontent.com/assets/29031969/26538721/52e63f58-43fd-11e7-8cf3-31bf062a381c.png)

Please check the already existing issues to keep duplicates at a minimum.

Furthermore several work-arounds have been collected in the Mist-Troubleshooting-Guide.

If possible add the following to your report:

• Screenshots

• Check the console, of Mist (CTRL/CMD + ALT + i) and take a screenshot

• Log files

  • go to menu -> accounts -> backup -> application data
  • zip and upload node.log and all other node.log.X files

[unitedcryptos]

[kiahmed]

seems to me geth isnt running . try running geth individually first and you can create a new user account from geth command line as well. Once geth is running and start syncing then run wallet/mist

[dmsalsman]

If you run geth with administrator privileges you must also open Mist/Wallet with administrator privileges.

Just found out the hard way on my own after hours of googling while syncing without success.

[curator999]

Hi dmsalsman. What that mean to run "run geth with administrator privileges you must also open Mist/Wallet with administrator privileges". I try to solve issue - same here, it my second night, i am reading but not really understand. Please advice

[sujithcmohan]

I am getting similar error on Windows 10, 64 bit machine. Unable to solve. Any solutions?

[mcna72]

Okay I solved the problem but not the easy way. It is not possible to solve it via any back door. This is clearly a software bug. One advise: don't try to use the testnetwork. It will make your wallet software crash!

Solution: You have to make a backup of the C:\users\user\appsdata\roaming\ and there you select the ethereum and the ethereum wallet folder (which may be hidden). Back-up them to an external disk or somewhere you feel save. Then completely delete the folders from the appdata folder. Then unstall the ethereum wallet. Restart your pc and install the latest ethereum wallet download. Then you have to wait again for the wallet will download all the blocks in the blockchain once again to your hard disk (which might take 24 hours). After this you can enter your wallet again. But ofcourse your key has to be filled out again, but you can find this key in your backup folders. You find the key in the ehtereum/keystore/ folder. Replace the saved one with the one that was generated by the installation.

[kiahmed]

doesnt sound like an actual solution to me..glad that it worked for you. I keep m eth folders on a different drive anyway. I did by overwriting exciting chain with fast mode, it was upto date for a while then falls back again.. doh :(

[darocha]

Solved by running both programs as an administrator (Windows 10 and Ethereum Wallet 0.9.3). I was getting a similar error as shown on the screenshots provided by unitedcryptos.

The problem started after I switched the network to Ropsten on Ethereum Wallet.

To run the apps follow these steps.

1. Open a command prompt or a powershell window as an adminstrator and run Geth (type geth then press enter).
2. Run Ethereum Wallet as an administrator. Right click on the icon and select the command: Run as adminstrator.

These steps worked well for me.

[ddanh85]

@darocha I face this problem with Windows 10 and Ethereum Wallet 0.9.3 too. Your solution helps me alot, now I can continue to sync without any problem.

[micrin]

Hi, it works indeed, however if you want to start ethereum wallet again without running geth first, the problem still exists

[alexvandesande]

The issue occurs when geth fails to close in the background. Killing the process manually, or just restarting the computer, should do it. Does it keep occurring after that?