Help For You: Trouble shooting starting the new version (can't get it started)

[jabo38]

A lot of people have a hard time when updating.

Here are some tips that might help you.

1- If you are syncing but an your machine says something like “NIS is synchronizing. At block 221896, est. 126 days behind. (at block 221896)” and doesn’t move and sync but seems stuck, please try to delete your database and start a new chain. You can speed up this process by just downloading a new chain and inserting it manually. Here are some tutorials with step by step instructions.

How to Delete Your Local Copy of the Blockchain

How to Import the Database File Provided by Developers

2- If there is a major problem, you might have to delete all NEM software on the computer and start over from scratch installing. Here is a tutorial for that. http://blog.nem.io/how-to-remove-old-nem-software-versions/

Generally speaking the installer is the most buggy. Most people that have a problem with the installer find that using the stand alone works. Instructions for the stand alone are here. http://blog.nem.io/nem-tutorial-list/

If you have your private key backed up, or want to make a new wallet with a pass phrase, the Lightwallet is also very safe and easy to use. http://nem.io/install.html

At some point NEM will fully transition away from NCC to Lightwallet and mobile apps for iOS and Android and there will no longer be any of these problems.

3- If you are having trouble logging in.

Go to C:\Users\yourname\nem\ncc and delete the ncc.cfg file and the accounts_cache_mainnet.json file.
.
4. If NIS wont start. Go to C:\Users\yourname\nem and delete the nis.lock file.

5- If you are having a problem with Java, please try to update your Java.

[jabo38]

If you are getting this Java error when trying to install the NEM installer, then you will need to delete and reinstall Java.

Doing the automated reinstall won’t fix the problem. Please go to Control Panel -> Programs -> Java -> Delete Java

Also go to C:\Program Files (x86) and look for any old Java programs there and delete them.

You will need to download the 64 bit version of java as the installer only works on 64 bit OS and 64 bit Java. Please go to http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html and download a 64 bit version exe and install it.

That should work and you can now install the NEM installer.

If it doesn’t, you might want to look at your Java pathway and edit it as described here.

[jabo38]

Some people are having problems with their node being unresponsive. This can be because of RAM settings. For the short term to help minimize this problem please do the following.

Go to package -> NIS -> logalpha.properties

Then change the level on the first and third entry from “INFO” to “WARNING” and restart NEM.

The logalpha.properties should look like this.

[titan20]

Hi Jabo38,
I want to use the lightwallet. It asks for a few things:

1. wallet name
2. account address
3. private key
4. password

i know 2 en 4.
I have a wallet file like: london.wlt.
is the wallet name the same as london? and is there a way to retreive the private key from the wallet file?

t

[jabo38]

More tips from Pat.

Troubleshooting guide

This post will be extended over time, hopefully not only by me but others as well. It's suppused to give newcomers a guide on how to troubleshoot commong problems.

NIS needs to be booted
Create a wallet and log into it. That should boot NIS automatically.
If it's a remote NIS then you need to enable autoboot in the file named config.properties.

NIS is not available
If you have been using a remote NIS check if that NIS is still available. You can do that by opening your browser and visit <ip-of-remote-nis>:7890/node/info
If you have not beeing using a remote NIS check if your local NIS is running. You can either use the same method as for a remote NIS or check the icon in the system tray.

NCC isn't accepting my password. Says a parameter is missing
Check if your wallet name contains dots or spaces. If so create a new wallet with a different name.

ERROR 699 - Maximum number of harvesters allowed on server has been reached
This means that that someone is already harvesting on the NIS you are connected to. Default limit is 1 but it can be raised by editing config.properties. However raising the limit shouldn't be necessary.
Harvesting locally and delegated is harvesting with 2 different accounts so it's likely that you are already harvesting on your NIS and are trying to activate the other harvesting method.
If you're using a remote NIS that isn't hosted by you it's likely that the maximum is reached and you can't do anything about that.

I'm on a Mac and trying to update
If you are on Mac and are using an installer and trying to update, it is very important that you uninstall the previous version first.  If you messed up and didn't do this, than uninstall both versions you have in your applications menu, and then install the latest version again.

[jabo38]

Some people who run a Supernode for an extended time will have log files build up. If you want to auto-delete your log files to save space, you can follow the advice from Rev in the Telegram chat.

you can always add to the startup script or a cron find ~/nem/logs -ctime +10 -delete

[jabo38]

Here is the answer to that 699 problem.

How to Raise the Amount of Harvesters. Fix Error 699

Many people get the error ERROR 699. NIS: HARVESTING LIMIT HIT. This happens because a person can by default only harvest on one account and some people's configuration settings take up this account automatically, which confuses many people. The easiest way to fix this problem is to raise the default limit. If you are running the Stand Alone version of NEM. You need to locate the folder called package that you made when unzipping the NEM download. Then open it and go to the NIS folde…

[jabo38]

Sometimes people update and they have a problem with NCC starting. If that is so then do the following:

Delete the file accounts_cache_mainnet.json in the folder c:\users\ < your_user > \nem\ncc.

Then start ncc again.