Wiki Home TROUBLESHOOTS Check the server error log

Check the server error log

There are two ways for checking the error logs.

Check the log in the main interface

  1. Click the “View” tab and click the “View fatal log” option (Figure 1).

Figure 1

  1. If there is any error,  it will pop up the log which records the errors.

Check the log in the installation folder

You can find the log folder in the CCBootCloud installation folder (Figure 1).

Figure 1

Common error logs

  1.  *** ERROR *** servicecontrol client server to client disconnect process mem 11M threads 2

This error indicates the error log of the RAM, which belongs to the procedure bug. The dump files shall be submitted to the development personnel according to the fifth procedure.

  1.  *** ERROR *** open write-back file? false process mem 50m threads 10

Error log of the write-back disk, possible reasons:

  1. If the file of the writeback disk has error, for example, a blackout of power will cause the error of the writeback files. If the service needs to be stopped, reformat the write-back disk and restart the service.

  1. If the write-back disk brakes, a new one shall take the place of it...

  1. If the room of the write-back memory is not enough, a bigger one shall take the place of it.

3.  *** ERROR *** open image D: xp.vmdk failed: A file was not found process mem 82m threads 10.

The image package reads the error log of the data. Possible reasons:

  1.  According to the log, check whether the image package exists .

  1.  If the image package is broken, the images shall be restored from the spare images and shall be remade.

4. Registered Failed

Checking failed error log. Possible reasons: the serial number of purchase is problematic, contact the seller.

5. There is a dump folder in the installation folder of CCBoot, if the dump folder has the *.dmp files, please compress the dump folder and send the zip file to support@youngzsoft.net. For details, please refer to "Solutions for Program Crash".

Note: In CCBoot recent builds, most of the dump files are related to the write-back disk problems, it may be due to the write-back disk error, or because the write-back disk is full.

6. *** ERROR *** file_read error 38 process mem 683M threads 41 getlasterror=38: Reached the end of the file

Normally, it indicates the writeback disk is full at that time.

7. 14:06:00 Cannot connect to the control service

If this error is logged, then please re-install CCBootCloud once and make sure to reboot when CCBootCloud asks you to reboot.

8.  "getlasterror=1392: The file or directory is corrupted and unreadable."

This error may be because the disk is broken, please chkdsk or reformat the disk. Or it may because the disk is full at that time.

9. 13:15:01 *** ERROR *** file_write error process mem 443M threads 19 getlasterror=112: (null)

13:15:01 *** ERROR *** file_read error 38 process mem 443M threads 19 getlasterror=38: (null)

This problem may be related to write-back disk problems. Maybe the write-back disk is small or broken. Please replace a new larger HDD for the write-back disk and try again.

10. 13:24:36 *** ERROR *** file_write 1 error 112 reason: 0x70 Insufficient disk space.

11. 13:24:36 *** ERROR *** file_read 1 error 38 reason: 0x26 has reached the end of the file.

This error is caused when the writeback disk is full. To solve this, increase the size of the writeback disk or delete writeback files

12. 07:25:29 *** ERROR *** file_open E:\Win7.vhd error 3 reason: 0x3 The system cannot find the path specified.

07:25:29 *** ERROR *** Open E:\Win7.vhd failed

07:25:29 *** ERROR *** file_open E:\Window10.vhd error 3 reason: 0x3 The system cannot find the path specified.

07:25:29 *** ERROR *** Open E:\Window10.vhd failed

This error means that the mentioned image file is not present in the path. This happens when you have changed server and settings are not set correctly. Set the image path correctly to resolve this issue.

13. 07:43:57 *** ERROR *** file_open E:\Win7.vhd.Super.vhd error 3 reason: 0x3 The system cannot find the path specified.

07:43:57 *** ERROR *** Create image E:\Win7.vhd.Super.vhd failed

This error occurs when the image file is not located on the image path and you try to super client that image on a client. To resolve this, set the image path correctly.

14. 15:06:38 *** ERROR *** Open image E:\Win7 failed: The file is already in use

For these errors, please check if the image is mounted on windows or not. if the files are mounted then unmount them from the windows.

15.         07:38:52 ERROR lock volume \\.\G: failed reason: 0x9e The segment is already unlocked.

07:38:52 ERROR Open \\.\G: failed

Solution:

1. Make sure the Game disk is not the same as Image.

2. When you update the game disk with super client mode please do not run icafemenu

16. 10:12:44 *** ERROR *** file_read 0 error 6 reason: 0x6 The handle is invalid.

The above error occurs when you enable super client to game disk when you have client running from the CCBoot.

Solution: To solve this, turn of all the other client before enabling super client to the game disk.

17. 17:22:33 *** ERROR *** file_open \\.\D: error 2 reason: 0x2 The system cannot find the file specified.

17:22:33 *** ERROR *** Open \\.\D: failed

17:22:33 *** ERROR *** 192.168.1.241:52117 disconnect: InitDisk (E:\win764ru_vip.vhd;\\.\D:;)failed

This error meant that the drive D: is not working in the system or is uninitialized or broken

Solution: format the drive again and add to the CCBoot, if the error repeats again, then better to replace the disk that the drive belongs to.

18. 16:19:07 *** ERROR *** file_read 0 Unknown error 6 [F:] 150.53G(free)/232.37G(total) [H:] 131.09G(free)/232.37G(total) reason: 0x6 The handle is invalid

This error denotes that the writeback disk has corrupt data and is not able to overwrite it with new writeback data from the client.

Solution:

Stop CCBoot service, then delete all the writeback data from the writeback disk. If any writeback data is not deleted that means there is corrupt data. To fix it, format the writeback disk to clear the corrupted data from the writeback disk.

19.  14:16:14 ** Error ** Set game cache failed. drive: J ram: 1024 ssd: 0 reason: 0x1f A device attached to the system is not functioning.

14:16:14 ** Error ** Start game cache failed. drive: J ram: 1024 ssd: 0 reason: 0x1f A device attached to the system is not functioning.

This error occurs when the disk is unallocated or inaccessible due to few reasons.1

1. disk disconnected from the server.

2. disk has bad sector and cannot read/write to the disk

To fix this you need to do the following:

1. first turn off the system

2. secure the power cable and SATA cable to the disks

3. turn on the computer, then check in disk management if the disks are detected or not

4. Check the disk for bad sectors using chkdsk command

5. And make sure you have not set any rules in system to prevent access to the disks

20. *** ERROR *** Current memory used: 32002048/5897347072, lack of memory process mem 5654M threads 11

If you encounter this error then this means that CCBoot was not able to use the system RAM for RAM cache

To resolve this, follow the instructions below.

a. Check of your RAM modules are working properly - run a memcheck

b. If RAM is working fine, then uninstall CCBoot, and delete all configuration files from the installation directory, then re-install CCBoot and configure it.

c. If reinstall is still not fixing the issue, then please remove any blockage for CCBoot in the system like in firewall or in hosts files as if CCBoot cannot activate properly.

21. "DHCP socket error in getsockname: 10055 reason: 0x2747 an operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full."

With a large number of clients (100 or more) on one server, can see the following in the logs of critical errors as above.

This error occurs because of the large number of concurrent connections (by default, win server 2008 is set to 5000). Due to this error, your clients will not receive IP addresses from DHCP and any PC can randomly lose connection from CCBoot and reboot.

To fix this, you need to add more slots, this can be done using the registry editor.

1. Start Registry Editor.

2. Locate the following subkey in the registry, and then click Parameters:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

3. On the Edit menu, click New, and then add the following registry entry:

  Value Name: MaxUserPort

  Value Type: DWORD

  Value data: 65534

  Valid Range: 5000-65534 (decimal)

  Default: 0x1388 (5000 decimal)

4. Close the registry editor and restart the CCBoot server.

5. Now, clients will not such issue again

Related: