Network error again

Warhammer 40K Bug Report

By blitz666

Bastard2k replied

blitz666

1 26

Hey,

after the Hotfix 0.6.3b i'm getting NETWORK ERROR again.

logfile says:

2017-09-21 20:29:56.956 ( 13.152s) [ 11D8] SparksManager.cpp:685 0| Backend connection timed out

2017-09-21 20:29:56.956 ( 13.152s) [ 11D8] SparksManager.cpp:489 0| Disconnected from the backend

so its probably a Database Problem on Serverside?!

anyway...

I tried the usual stuff:

Registry Key

redownloading

verifying files

Kinda annoying

This post was edited by blitz666

Store Page

11 comments

Network error again
Your Thoughts? Please login to place your opinion. Not a member yet? Register here and now!

Calida

0 3

blitz666

I am suffering the same problem, thx for creating the bugreport!

BTW: Where do you find the log file?

This comment was edited by Calida

blitz666

1 26

Posted by Calida

I am suffering the same problem, thx for creating the bugreport!

BTW: Where do you find the log file?

Hey, its found in:

C:\Users\[username]\Documents\NeocoreGames\Warhammer Martyr\log.txt

Bastard2k

0 1

I've got the same problem at the same time. Sent every logfile to the support months ago. Still the bug remains... I can't enter the game from september 2017.

blitz666

1 26

So, one day later. Still the same problem.

2017-09-22 19:19:08.811 ( 41.742s) [ 134] MenuMainWindow.cpp:1147 0| User reconnecting to backend.
2017-09-22 19:19:14.167 ( 47.103s) [ E64] SparksManager.cpp:685 0| Backend connection timed out
2017-09-22 19:19:14.167 ( 47.103s) [ E64] SparksManager.cpp:489 0| Disconnected from the backend

Guess that means i will give it a rest for some days/weeks now.

Catskinner

2 4

Have you logged the issue with support? More likely to get a response...

blitz666

1 26

yeah, well, and here i thought writing in the bug report section on the developers site was exactly the right place to put it.

blitz666

1 26

well i did open a mantis issue

http://old.neocoregames.com/mantisbt/view.php?id=2104

turns out that at least one other guy got the same problem and we probably narrowed it down to a dead route somewhere to the login-server thats hosted in the amazon cloud.