[SOLVED] Root Type is Mandatory ErpNext Error

When setting up Erpnext after installing it in a site I get the following message on the web page:
Adding System Manager to this User as there must be atleast one System Manager Setting this Address Template as default as there is no other default Root Type is mandatory There were errors.

Checking inside frappe-bench/logs/web.error.logIjust see this:
[2016-05-17 03:47:38 +0000] [2561] [INFO] Shutting down: Master [2016-05-17 03:47:47 +0000] [5919] [INFO] Starting gunicorn 19.5.0 [2016-05-17 03:47:47 +0000] [5919] [INFO] Listening at: http://127.0.0.1:8000 (5919) [2016-05-17 03:47:47 +0000] [5919] [INFO] Using worker: sync [2016-05-17 03:47:47 +0000] [5934] [INFO] Booting worker with pid: 5934 [2016-05-17 03:47:47 +0000] [5935] [INFO] Booting worker with pid: 5935 [2016-05-17 03:47:47 +0000] [5937] [INFO] Booting worker with pid: 5937 [2016-05-17 03:47:47 +0000] [5939] [INFO] Booting worker with pid: 5939 [2016-05-17 03:50:05 +0000] [5919] [INFO] Handling signal: term [2016-05-17 03:50:05 +0000] [5939] [INFO] Worker exiting (pid: 5939) [2016-05-17 03:50:05 +0000] [5937] [INFO] Worker exiting (pid: 5937) [2016-05-17 03:50:05 +0000] [5935] [INFO] Worker exiting (pid: 5935) [2016-05-17 03:50:05 +0000] [5934] [INFO] Worker exiting (pid: 5934) [2016-05-17 03:50:05 +0000] [5919] [INFO] Shutting down: Master [2016-05-17 03:50:14 +0000] [6367] [INFO] Starting gunicorn 19.5.0 [2016-05-17 03:50:14 +0000] [6367] [INFO] Listening at: http://127.0.0.1:8000 (6367) [2016-05-17 03:50:14 +0000] [6367] [INFO] Using worker: sync [2016-05-17 03:50:14 +0000] [6382] [INFO] Booting worker with pid: 6382 [2016-05-17 03:50:14 +0000] [6383] [INFO] Booting worker with pid: 6383 [2016-05-17 03:50:14 +0000] [6385] [INFO] Booting worker with pid: 6385 [2016-05-17 03:50:14 +0000] [6386] [INFO] Booting worker with pid: 6386

But nothing related to my issue.
I suspect it is just an oversight within the Account creation code, but I am not a python programmer.
So any help would be appreciated.

@samjaninf, the issue is fixed in ERPNext develop branch.