Anyone else still getting the "Missing required configuration value for [Url.DownloadFilesList]" message?
Anyone else still getting the "Missing required configuration value for [Url.DownloadFilesList]" message?
Yup patching now
Just started to work! :)
Edit: its working again
Yup, getting the same thing, was getting fearful something broke locally needing a reinstall..hoping its just waiting for the update to become available to download etc
Yes, that is the message shown to me also.
Had the same, but now downloading.
updating right now
I guess that file list needed some time to propagate. I was getting that error, but now patching is working.
No patch download, just this message:
https://dl.dropboxusercontent.com/s/...0%20A.JPG?dl=0
Clicking through generates this:
https://dl.dropboxusercontent.com/s/...0%20B.JPG?dl=0
Clicking through that presents me with the normal login screen requesting my user name and password. But I didn't proceed to learn if I could log in successfully because we were told there is supposed to be a patch today and if I did end up logging in I didn't want my client to fail to match the server's expectations.
Its working now
Just tried again after reading your message and yes, my client is now patching itself as I write this.
edit: Well, at least it's trying. Getting server timeouts, but I assume it will get connected and then work itself out eventually.
edit: Yup, all patched and ready to play now.
Last time I did a packet capture on this, I saw the client getting an HTTP redirect back from the server, to a nice spiffy LOTRO/DDO "we're down for maintenance" page (http://content.turbine.com/maintenance/), but the client just ignores that redirect and seemingly plows into some code path that ultimately results in the cryptic "missing required configuration value" nonsense.
So, it seems like someone is trying to provide a professional-looking customer communication mechanism, but the client-code deficiencies/misconfigurations are tripping it up.
I haven't been able to diagnose the "unexpected end of line" cryptic message, because I haven't seen that one for a while.
P.S. Before anyone chimes in with "capturing packets is against the CoC", a) it's not "deciphering" because it's not "ciphered" to begin with, and b) the CoC only applies while "playing" LOTRO -- a failed attempt to connect and/or login is not "playing".
You people really should go outdoors more often lol
like real life outdoors
I was able to (re-)confirm the broken/ignored redirect that ultimately results in "missing required configuration file" misleading error message.
I'll see if I can diagnose the "end of input" cryptic error message, when maintenance gets to that phase, but my gut says that's fundamentally a server-side thing (sending back a malformed response to an authentication request). This is not to say the client-side message couldn't use some improvement: even something generic like "authentication failed" would be better than debug-looking gibberish.
I am a gamer not a techie. To me the message means the log-in server is still down. That information more than suffices.
Folks...this thread was started LAST week. Today's downtime is until 1:00. Cord has NOT posted the servers are up yet today......
Egarthur knew that - as witness
"when maintenance gets to that phase"
But the error message is the same and his or her point was to discuss the error message.
If maintenance were every day, would you be complaining about thread necro? This thread continues across multiple weeks because maintenance only happens about once a week.. I didn't put the Cord reference in the original subject line, and I can't change it. If I created a separate thread, then folks would complain about thread proliferation. There's always something to complain about.
Was that your reaction the first you saw the message, though? Or just because you've seen it enough times to know it's not a catastrophic/critical error? Many people freak out the first time they see it. I'm sure there have been a few that saw that error and decided it's a broken game and they don't want to have anything to do with it. That's why I'm saying it should be improved.
Some people are resistant to change, even when it's clearly a change for the better. Keeping around broken stuff just because it's familiar. But frankly I'm surprised anyone would defend an "end of input" error message for a routine operational condition. And this is from someone who started their IT career diagnosing errors by looking up hex codes displayed on a front panel. I thought UI had moved beyond that.
The worlds are up. The usual cause of this is if I push the announcement too quickly after the worlds have technically opened but before they are opened to the public. There's a difference re: things being in an unavailable state and them being open, technically. So, usually due to miscommunication or someone forgetting to toggle a thing before opening the worlds.