Project

General

Profile

Support #123

Unkown bundle setup error: 0x5

Added by Backer cidgjosu about 3 years ago. Updated almost 3 years ago.

Status:
Investigating
Priority:
Normal

Description

I´m having this problem when trying to install the game

b9bf5613afa7be33d30ab8b549ea4403.png (282 KB) Backer cidgjosu, 03/24/2016 08:04 PM

GameLauncher_20160418_154841_8990590.log Magnifier (3.31 KB) Backer cidgjosu, 04/18/2016 04:01 PM

KCD_Beta_Access_20160418154943.log Magnifier (11.5 KB) Backer cidgjosu, 04/18/2016 05:29 PM

KCD_Beta_Access_20160324174453.log Magnifier (11.5 KB) Backer cidgjosu, 06/23/2016 06:12 PM

History

#1 Updated by Daniel Zadák about 3 years ago

  • Assignee set to Miroslav Louma

#2 Updated by Daniel Zadák about 3 years ago

  • Status changed from New to Investigating

#3 Updated by Miroslav Louma about 3 years ago

Hi, it is difficult to determine cause of this issue with only having error message itself. Could you please upload installation log file and launcher log file?

The launcher log file is created in system temporary directory (accessible via putting %TEMP% in File Explorer address bar), within subdirectory called GameLauncher. These files are not readable in text editor, so it's pointless to try doing so.

The installation log file is created in system temporary directory as well, the filename looks like this: KCD_Beta_Access_<date_and_time>.log

#4 Updated by Backer cidgjosu about 3 years ago

Miroslav Louma wrote:

Hi, it is difficult to determine cause of this issue with only having error message itself. Could you please upload installation log file and launcher log file?

The launcher log file is created in system temporary directory (accessible via putting %TEMP% in File Explorer address bar), within subdirectory called GameLauncher. These files are not readable in text editor, so it's pointless to try doing so.

The installation log file is created in system temporary directory as well, the filename looks like this: KCD_Beta_Access_<date_and_time>.log

Here you have the log

#5 Updated by Miroslav Louma about 3 years ago

Thank you very much. The log indicates, that the installation subsystem is trying to download one file over and over again.

However, in order to determine underlying cause of this behavior, we also need the log file from the installation subsystem itself. The log file that you've uploaded previously is created by the launcher itself.

The log file created by the installation subsystem should have name like this: KCD_Beta_Access_<date_and_time>.log

#6 Updated by Backer cidgjosu about 3 years ago

Miroslav Louma wrote:

Thank you very much. The log indicates, that the installation subsystem is trying to download one file over and over again.

However, in order to determine underlying cause of this behavior, we also need the log file from the installation subsystem itself. The log file that you've uploaded previously is created by the launcher itself.

The log file created by the installation subsystem should have name like this: KCD_Beta_Access_<date_and_time>.log

#7 Updated by Miroslav Louma about 3 years ago

Thank you very much for the additional log file.

Unfortunately, we still don't have a clear idea, what's causing the installation to fail. However, thanks to the log file, we do have a general idea, what went wrong.

We've updated installation subsystem to create additional diagnostic messages in the log file related to the issue you're experiencing. This will help us better understand, what's the underlying cause of the issue. Could you please try installing the beta again and then upload new installation log file (KCD_Beta_Access file)?

#8 Updated by Backer cidgjosu almost 3 years ago

Miroslav Louma wrote:

Thank you very much for the additional log file.

Unfortunately, we still don't have a clear idea, what's causing the installation to fail. However, thanks to the log file, we do have a general idea, what went wrong.

We've updated installation subsystem to create additional diagnostic messages in the log file related to the issue you're experiencing. This will help us better understand, what's the underlying cause of the issue. Could you please try installing the beta again and then upload new installation log file (KCD_Beta_Access file)?

#9 Updated by Miroslav Louma almost 3 years ago

Unfortunately, you have uploaded log file that is rather old (it's from 24th March). It does not give us any more clues as to what is happening, because it basically contains same information as the previous log file (KCD_Beta_Access_20160418154943.log).

In order for us to determine exact cause of this issue, we need to have a look at a log file generated by the (updated) installation subsystem, that puts more diagnostic information into log file related to this issue.

Also available in: Atom PDF