(OLD) KNOWN ISSUE: internal_error / Error Code: 2007

Warhammer 40,000: Darktide Technical Support
735

Gonna copy here the logs with vpn with the ones from before for if it helps, still, just got a crash
GUID: e9e7b7d3-eceb-4611-b15b-b1d30673c22d
Log File:
Info Type:

LOG WITH VPN (WITH NO ERROR 2007)
console-2022-11-28-14.53.38-e9e7b7d3-eceb-4611-b15b-b1d30673c22d.log (395.6 KB)
WITHOUT VPN ( WITH ERROR 2007)
console-2022-11-28-10.15.07-18eee55b-86c8-4b64-9599-00392ac7b5a6.log (60.4 KB)
console-2022-11-28-11.58.16-ae737358-4160-4fd3-8762-001458d3a11f.log (68.4 KB)
console-2022-11-28-14.25.40-e4d332bb-0f8b-46af-8bdd-9494cf86120e.log (59.5 KB)
ALSO AFTER THIS SMALL 7.6MB UPDATE NOT WORKING
console-2022-11-28-16.13.36-52d76f5a-f10b-4b17-9339-9b1f5876be14.log (98.1 KB)

736

still getting same error 2007

737

Ok now itā€™s fixed FOR ME just got a crash a the end of a mission but itā€™s ok since now i can play !

my log
console-2022-11-28-15.53.47-926977c2-ea2e-48f2-aef6-43ef5308d0e9.log (162.2 KB)

1 Like
738

Holy macaroni Julia! This one sees progress, I got to the big ship. No crashing yet, will post a log if it happens, but hey that is a great sign of progress!

Okay it did end up crashing but only after the mission was complete. Far more progress than I expected, but no error code for this one. Still, very good progress on the updates.

console-2022-11-28-16.24.54-75b5115d-0b42-4609-a760-8380b6d18241.log (150.1 KB)

2 Likes
739

Very exciting!!

I cant fully test it because I am at work. But right off the bat I was able to actually log in for the first time which I am really excited about. I even walked around the whole dome for 15 mins and didnt get booted out.

I will keep you posted with more details when I can more completely test it.

1 Like
740

The experimental branch appears to have fixed the issue for me. Able to log in and vibe in the Mourningstar. Will try out a few matches. Log for the devs.

darktide_launcher.log (169.2 KB)
console-2022-11-28-16.21.01-3cb11ce4-d742-458d-b37d-dffb8d549329.log (45.2 KB)

1 Like
741

Based on people saying the last experimental fixed things for them, it seems that one of the two problems (Read Error, ssl error 2) was fixed. Sadly, the other one (In client listen: remote peer graciously disconnected, ssl error: 6) is still there.

742

Where are you getting those details? In the logs? My 2007 errors were not associated to those Iirc from what Iā€™ve read in the files, but mainly error in transport layer or something like that

743

Only experimental branch logs have this (see Juliaā€™s post here on how to switch to experimental). Usual game logs come without such details.

744

I should add that I DISABLED STEAM OVERLAY. I havenā€™t tried it with it on yet but maybe that will help others? Worth a shot.

745

Nice, I didnā€™t thought about reading the new logs. Didnā€™t know they contained that much more detail! Thanks

@FatsharkJulia Updating on the situation:

Latest fix totally solved my issues on the primary desktop computer.
Unfortunately the secondary laptop computer started to see error 2001 when connected to the wifi router and error 2003 when connected to smartphoneā€™s hotspot.
Since I donā€™t know if this is the same issue under a different mis-label (we already experinced a change of error names when switching connections) Iā€™m reporting this here and also in the topic dedicated to 2001 error.
Details here: KNOWN ISSUE: nonexisting_channel / Error Code: 2001 - #79 by GRAAK85

Thanks so much for your efforts!

746

Something changed (until now I had Error Code 2007 directly in the loading screen, but now I saw the start of a cutscene or so), still not able to play.
First try it loaded for a long time, then I saw the beginning of a cutscene for a second and then crash.
Second try, it loaded (faster now), I saw the beginning of the cutscene and than I got my gold old friend ā€œError Code 2007ā€ and was back in loading screen (still hearing the sound of the cutscenen).

Reproduce:

  • Still just try to login from char select

1st try crash

2nd try (Error 2007) console.log

Iā€™m on the beta experimental branch.

747

Thanks everyone for still working so hard on this and I hope it gets fixed before full release.

Unfortunately it didnā€™t work and I had an error 2007 disconnect almost immediately upon entering the Mourningstar.

Disconnect happened at 2022-11-28 18:05 UTC
console-2022-11-28-18.03.28-030ef8e9-33d1-47c6-bb75-07ca24a9aab0.log (43.4 KB)

748

No error codes but this is the log I received when I crashed just finishing a match

GUID: 425d1548-3637-42de-b848-1863324b38b9
Log File:
Info Type:

749

So some crashes here and Error Code 2007 still. Last night I was able to play to full matches out of the 3; the first one had a lot of problems. Today during the two I kept DCā€™ing and crashed twice.

750

crashed on end game screen counting rewards, experimental build.

GUID: 1de84578-5b9e-4e54-9db8-7f740622b977
Log File:
Info Type:

2 Likes
751

Yeah i had same issue 1 hour ago, but only once.

752

Played through a whole match with no Error Code: 2007 DCinā€™ me and having to reconnect. Do we know when the experimental build goes live?

753

Tried again with the third experimental build but still the same issue, I get error 2007 as soon as Iā€™ve gotten past character screen and connect to a game server.

754

This actually worked for meā€¦and then it crashed in the end of mission screen, right as plasteel was being shown.