KNOWN ISSUE: Backend Error

Still got this issue after update

750mb update this morning, still getting the same backend error, using a VPN did not resolve the issue for me

aaaaaand nothing changed, still getting backend errors and so far haven’t been able to play at all.

Hello,

I have to sadly say that I did not have the error bevor the latest update and was able to play yesterday.

Since the latest update launched, I now have the Backend Error when signing in.

I have had my dns server set to googles’ (8.8.8.8) even during the Closed Beta Test.

So to recap:

Closed Beta Test: had the Backend Error but was able to get around it by disabling my fire wall fully, dns server set to googles’ (8.8.8.8)

Pre-Order Beta 1.0.6: was able to play, dns server set to googles’ (8.8.8.8)

Pre-Order Beta 1.0.7: getting the Backend Error again, dns server set to googles’ (8.8.8.8)

Steps to Reproduce:

  • Launch game from steam.
  • Press play from launcher
  • Press “space” to log in.
  • Game shows backend error message on “processing inquisitorial clearance”.

Platform: Steam

Player ID: Steam Community :: Rechet

Approx. Time of Issue & Timezone: 11/22/2022, 06:00PM UTC+2

Note: I am also uploading the log from yesterday when I was able to play

Backend Error
console-2022-11-22-16.39.02-c115034c-c777-4445-9cf2-10d74cd1f455.log (29.4 KB)
console-2022-11-22-17.03.25-a1f1da34-39c6-4d7b-83e5-caf789a8a24d.log (30.2 KB)
console-2022-11-22-17.05.14-23f6c556-d983-4bdd-8e29-b869dc9b6606.log (20.1 KB)

No Backend Error
console-2022-11-21-16.58.13-73ebfb72-73b5-4133-8015-ab5c658a2b0d.log (1.1 MB)

Had this issue since the 17th
Steps to Reproduce:

  1. Launch game from steam.
  2. Press play from launcher
  3. Press “space” to log in.
  4. Game crashes at “processing inquisitorial clearance” with backend error message.

Platform:
Steam

Player ID:
SteamID:76561198042279838

Consol logs
console-2022-11-21-18.42.57-8658b0b7-2eed-4400-9d13-f5a25bc3e9da.log (30.8 KB)
console-2022-11-21-21.38.49-a60229dd-a7d8-4724-9df0-ea8cd2198d1b.log (20.4 KB)
console-2022-11-22-06.32.06-afd308cf-d1be-45d1-a4c6-8415b2b775b9.log (20.4 KB)
console-2022-11-22-17.32.09-b60ab058-f84e-4864-91cc-29d9e543c4e9.log (31.1 KB)
console-2022-11-19-23.11.37-8894bec5-7406-44ab-aa66-4485715bc19a.log (21.2 KB)

We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.


Issue Description:
Game never loads past the “checking inquisitor orders” so I am unable to play at all

Error Displayed (If Applicable):
given backend error everytime it trys to load in. Never even seen the prologe
Steps to Reproduce:

  1. turn the game on
  2. try to load

Platform:
Steam

Player ID:
MustardTiger20

Approx. Time of Issue & Timezone:
11/18/2022 Eastern Standard

Reproduction Rate:

Constant (100%)

Upload Console Log:
console-2022-11-22-19.48.18-08000e24-43e9-4b1a-8b7e-1d3a7be38ea4.log (18.5 KB)
console-2022-11-21-21.57.09-12e7f214-a3ec-43e9-bd65-717bc85a27af.log (20.4 KB)
console-2022-11-21-22.05.36-a2e44afc-fdfd-428c-a415-ce68a3a7ce28.log (20.4 KB)
console-2022-11-21-22.19.46-dfeda298-8f0b-4271-ae9d-fe63723dd330.log (28.9 KB)

Upload darktide_launcher.log:
darktide_launcher.log (322.2 KB)

Crash Report :
console-2022-11-23-03.01.03-7c49051e-cbdb-4c90-9b9f-611e9db7dbf9.log (33.8 KB)

Steps to Reproduce:

  1. Turn on game
  2. Observe error after waiting for the inquisitorial authorization

I have reproduced this with and without VPN, & while installed on C: as well as installed on D:

Platform:
Steam

Player ID:

Approx. Time of Issue & Timezone:
11/22/2022 at ~1900 PST

Found a solution to my problem, changed DNS from my ISP (Mediacom) to googles 8.8.8.8 & 8.8.4.4

We kindly ask that you complete the questions below. With this information, we can investigate your issue properly.


As soon as I am through the first cutscene and hit the spacebar to launch I get an error loading “backend error.” I’ve tried reinstalling, verifying files, updating my drivers and restarting.

Player ID:
[Steam ID karliclark27

Approx. Time of Issue & Timezone:
[11/22/22, all day] [EST]

Reproduction Rate:
Constant (100%)

Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. 10:53:39.469 [Launcher] LOGGER OPEN
    10:53:39.469 [Launcher] Launcher version: Launcher: 1.0.248.0
    10:53:39.474 [Launcher] Local time: 11/21/2022 5:53:39 PM
    10:53:39.808 [Launcher] Steam name: Garbage Garbanzo
    10:53:39.810 [Launcher] [Main Window] Launcher Directory (AppDomain.CurrentDomain.BaseDirectory): C:\Program Files (x86)\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\launcher
    10:53:39.810 [Launcher] [Main Window] Base Directory: C:\Program Files (x86)\Steam\steamapps\common\Warhammer 40,000 DARKTIDE
    10:53:39.812 [Launcher] [Main Window] [Parse Arguments] Steam is initialized.
    10:53:39.813 [Launcher] [Main Window] [Parse Arguments] Retrieving backend settings for Steam application ‘1361210’ (branch=‘default’)
    10:53:39.820 [Launcher] [Main Window] [Parse Arguments] Using backend ‘prod’
    10:53:39.821 [Launcher] [Main Window] [Parse Arguments] Bundle dir: C:\Program Files (x86)\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\bundle
    10:53:39.821 [Launcher] [Main Window] [Parse Arguments] Common Ini-file: C:\Program Files (x86)\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\settings_common.ini
    10:53:39.821 [Launcher] [Main Window] [Parse Arguments] Win32 Ini-file: C:\Program Files (x86)\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\bundle\application_settings\win32_settings.ini
    10:53:39.823 [Launcher] [Main Window] OS Version: Microsoft Windows 10.0.19044
    10:53:39.823 [Launcher] [Main Window] OS Architecture: X64
    10:53:39.823 [Launcher] [Main Window] Framework Version: .NET Framework 4.8.4515.0
    10:53:39.952 [Launcher] [Main Window] Launcher was started by: steam(6568)
    10:53:39.954 [Launcher] [Main Window] [Load Settings] Load settings from: C:\Users\karli\AppData\Roaming\Fatshark\Darktide\launcher.config
    10:53:41.375 [Launcher] [Main Window] [SysInfo] AdapterId: 0 (NVIDIA GeForce GTX 1660 SUPER) OutputId: 0 CurrentResolution: 1920x1080
    | Processor
    | Manufacturer: AuthenticAMD
    | Name: AMD Ryzen 5 2600 Six-Core Processor
    | Caption: AMD64 Family 23 Model 8 Stepping 2
    | Maxclock: 3400
    | Total Memory: 0
    | Available Memory:0

Hi!

I’m constantly getting backend error after starting up the game and getting to “waiting for inquisitorial clearance”. When i press space button, the backend error instantly pops up. No way around it it seems. Please unlock my account, I’d like to create content with it and promote.

time: 22/11/2022 around 7pm
console-2022-11-22-19.03.11-89beba04-cdfc-459d-b4b7-4cc1b71f5466.log (21.9 KB)

I’m getting the Back error too. Wh nyou have to press space and wait for “inquisitorial clearance” it loads for a couple of minutes then the error pops up.

Been playing fine early today without any issue.

I also had backend error after I finished a mission, NO EXP or Rewards.

console-2022-11-23-16.56.09-759f8972-1320-4e72-8566-70455c945b3a.log (185.1 KB)

Got my first Backend Error today.

I was playing a lot over the weekend 34hr with the newest AMD Graphics Driver and had some stuttering, artefacts and also 3 crashes. (Also a lot of server
kickouts and server conection issures)

Then I was playing V2 and also had stuttering so I downgraded the driver to 22.10.1 (stable for me).
No more stuttering, but first time I tried to log in I got my first Backend error after waiting in the queue.
Restart, still the same.
After verifying the game data, it seems to work but at the end of the mission I got the Error Code 2001.
After trying to relog I got the backend Error again.

I hope that helps a bit.

(I also attached Tuesday log, where it worked ok 22.11)

console-2022-11-23-16.30.37-5406026f-bb36-4bb1-a06c-19db21f31a33.log (27.7 KB)
console-2022-11-23-16.34.18-1b1878b1-c818-497e-b3aa-f65f00d97562.log (14.8 KB)
console-2022-11-23-16.38.08-c5df03fd-0316-4238-ba0f-3e0b1adf7b2e.log (162.3 KB)
console-2022-11-22-14.22.55-24f20ae5-f952-4a0d-93bf-a860b234edc1.log (580.6 KB)
console-2022-11-22-16.10.39-3488267c-cdf3-41cb-a6a8-b2800bdede70.log (305.1 KB)

We’re looking for somebody that is encountering the Backend Error and has Deadline exceeded in their console logs to help us with our investigation. You would need to be quite confident in working with your PC and willing to set a Windows Environment Variable though. Please reach out!

Crash Report :
console-2022-11-23-22.29.18-0d34a0f8-9a03-4a5a-a95d-fa7774569ac3.log (20.4 KB)

Steps to Reproduce:

  1. Turn on game
  2. Observe error after waiting for the inquisitorial authorization

I have reproduced this with and without VPN, & while installed on C: as well as installed on D:

Platform:
Steam

Player ID:

steamcommunity.com

Steam Community :: Harbinger

Approx. Time of Issue & Timezone:
11/23/2022 at ~1433 PST

I’m happy to help.

Issue Description:
Unable to log into the beta after hitting play on the launcher. I am able to get past the cinematic but as soon as I hit space to sign in I get an error. Seems like others in the community have been experiencing this issue as well and a way around it seems to be using a VPN.

Steps to Reproduce:

  1. Launch Warhammer Darktide launcher
  2. Click Play button to launch darktide

Platform:
[Steam]

Player ID:
Steam ID/Steam Profile URL/GamerTag]

Approx. Time of Issue & Timezone:
Start: Pre-Order Beta Launch
End: On-going

Reproduction Rate:
100%

Upload Supporting Evidence:
[


.]

Upload Console Log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names

console-2022-11-19-21.24.24-d916147d-52ff-4d49-b1e3-fbf4a20da1e4.log (16.5 KB)
console-2022-11-20-02.14.08-d5e4046a-2881-4b74-b021-5e6230b14194.log (23.2 KB)
console-2022-11-21-16.01.08-3efc6265-f42b-4a1b-9e34-8bd55efa039b.log (19.2 KB)
console-2022-11-21-16.06.13-9dfab8c1-5436-4547-8996-06ee714bedb1.log (18.4 KB)
console-2022-11-22-20.42.13-648dcd30-4afb-43da-af98-00be7ff03a3e.log (6.4 KB)

Upload darktide_launcher.log:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Darktide
  4. Locate the darktide_launcher.log in this directory

darktide_launcher.log (537.0 KB)

Issue Description: Can not get past the title screen in the pre order beta. Was able to play no problem before the new 1.08 patch, but now stuck with this backend error.

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

  1. Launch Warhammer Darktide
  2. Press Space to Continue on title Screen
  3. Observe Backend Error

Platform:
[Steam]

Player ID:
[Steam Community :: talavisto]

Approx. Time of Issue & Timezone:
Start: 11/24/2022, 11:54AM PST
End: Ongoing

Upload Supporting Evidence:

Upload Console Log:

console-2022-11-24-19.54.13-3d50e885-618a-4421-81d0-60b8c1a8e34e.log (21.3 KB)

Upload darktide_launcher.log:

darktide_launcher.log (579.2 KB)

23.11.2022

Server error, code 2004

24.11.2022

Update on, error 2007

23.11
console-2022-11-23-17.11.30-e6844359-924a-46b9-b4d0-bc250223d695.log (77.3 KB)
24.11
console-2022-11-24-20.20.40-c97dd40d-25c0-4e0a-af07-e9ea45a5e2d9.log (53.1 KB)

darktide_launcher.log (229.0 KB)

It continues with update 1.8

console-2022-11-24-14.27.34-af6abdb6-f8dc-4ebb-8f0a-f3b5b0fb45c6.log (20.5 KB)
console-2022-11-24-22.24.47-b38c85f5-c7d5-4ffd-ac9d-422b45cd9674.log (35.4 KB)

still cant play the game without a VPN its ridiculous that i need a 3rd party service to just play your game. i get internal errors and backend errors over and over if i dont use a VPN and even then i can sometimes get multiple backend errors using a VPN.