Page 1 of 1

Server failed to identify my details.

Posted: Tue May 02, 2023 10:47 pm
by AlexDetrojan
The header above is the message I get when trying to connect today(may 2) to my multiplayer game with KiwiWarlord for the Pike and Shot tournament. Not sure what's going on. This has never happened in all the years I've been playing multiplayer. Any insights tech support? Thanks in advance.
Alex

Re: Server failed to identify my details.

Posted: Wed May 03, 2023 9:18 am
by awesum4
Alex,

thats happened to me a couple of times in the last week, it comes right a few hours later. Happened again this morning at 9am (be 9pm in England) it came right this evening.

Re: Server failed to identify my details.

Posted: Wed May 03, 2023 4:43 pm
by AlexDetrojan
awesum4 wrote: Wed May 03, 2023 9:18 am Alex,

thats happened to me a couple of times in the last week, it comes right a few hours later. Happened again this morning at 9am (be 9pm in England) it came right this evening.
Ok, thanks will check in the morning.

Re: Server failed to identify my details.

Posted: Wed May 03, 2023 8:13 pm
by pipfromslitherine
The team say they have stamped out the issue. Please let us know if you have any more recurring issues.

Cheers

Pip

Re: Server failed to identify my details.

Posted: Sun Jun 04, 2023 6:30 am
by Okie
The same thing is happening to me with all 4, ancient, medevil,Pike&shot and Mandate of heaven.Why does this happen so often??? How can this be prevented and how to fix it now???

Re: Server failed to identify my details.

Posted: Sun Oct 08, 2023 9:10 am
by KiwiWarlord
10pm October 8th and it is happening again on Pike & Shot, Sengoku Jidai, FoGM & FoGII.
Been like this for several hours now.
Rebooted and virus scanned to no avail.

Re: Server failed to identify my details.

Posted: Sun Oct 08, 2023 9:30 am
by rbodleyscott
KiwiWarlord wrote: Sun Oct 08, 2023 9:10 am 10pm October 8th and it is happening again on Pike & Shot, Sengoku Jidai, FoGM & FoGII.
Been like this for several hours now.
Rebooted and virus scanned to no avail.
Most likely the server was down. Still seems to be down currently.