0.7.0 issue

[sasp_sasp]

Here my problem is. I have updated my 0.6.6 eqemu to 0.7.0 , then I started "eqlauhch.exe" and get the message below
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_01, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_02, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_03, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_04, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_05, but it is already running.
Does anyone know what's wrong with it? and how to fix it?
Thanks in advance.

[daemonreaver]

Here my problem is. I have updated my 0.6.6 eqemu to 0.7.0 , then I started "eqlauhch.exe" and get the message below
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_01, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_02, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_03, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_04, but it is already running.
[04.21. - 09:25:37] [LAUNCHER__ERROR] World told us to start zone dynamic_05, but it is already running.
Does anyone know what's wrong with it? and how to fix it?
Thanks in advance.

I would not worry about it. It's caused by the launcher reading the SQL launcher table and booting the zones, then when it connects to world, world tells it to do the same.

NOT a critical/crash error.

[klinzhai]

Apparently this is 'normal'. I've chatted with Caveman a bit and he says that all the Windows (maybe even the Linux) servers do this, so don't worry about it.