Problem With Tournament Client
#1
Posted 26 May 2016 - 04:49 PM
Wonder if im the only one that have trouble with the tournament client. It install with no error but as soon as i try to launch it crash! OS language problem!!? begin to wonder.
System running windows 10 in french...
any help will be appreciated.
Alderic Marsden [NTCR]
#2
Posted 26 May 2016 - 05:08 PM
#3
Posted 26 May 2016 - 05:45 PM
#4
Posted 26 May 2016 - 05:52 PM
I have the same issue as Max
#5
Posted 26 May 2016 - 06:11 PM
Max Vebaneta, on 26 May 2016 - 05:45 PM, said:
JDH4mm3r, on 26 May 2016 - 05:52 PM, said:
I have the same issue as Max
Same issue here as well
#6
Posted 26 May 2016 - 07:01 PM
Already tried adding a windows firewall exception. Win8.1.
#7
Posted 26 May 2016 - 07:08 PM
#8
Posted 26 May 2016 - 07:20 PM
#9
Posted 26 May 2016 - 07:33 PM
Max Vebaneta, on 26 May 2016 - 05:45 PM, said:
I get the same network error issue as a couple other people reported.
It would be nice to hear if someone has successfully logged in.
#10
Posted 26 May 2016 - 08:12 PM
We get the client, then will only be able to log in to it when the tournament server is running.
I'm gonna go out on a limb and say.... Tournament server is not live yet. Makes a whole lot of sense.
Edited by Dirk Le Daring, 26 May 2016 - 08:12 PM.
#11
Posted 26 May 2016 - 08:14 PM
As for the problems running the client, that might actually take some back-and-forth to figure out. First question is a simple one, though: are you able to run the normal "main" version of MWO?
Also, just going to toss this out because it's probably going to be asked: the most common problem with the MWO Portal not running is likely to be that you don't have the correct version of .NET installed. Sorry about that, I'll be fixing the installer along the way to install all the prerequisites. For now, though, here's the link to the correct .NET installer:
https://www.microsof...s.aspx?id=42643
The proper version is 4.5.2. If you already have this (or a higher version of .NET 4.x) installed, then there must be something else going on, and I'd greatly appreciate it if you could provide some details about your issue.
Sorry, for the Tournament release we're kinda taking advantage of the fact that the user base is a smaller subset and testing out the new Portal, so I truly apologize if it's causing you any issues. Rest assured, we will get you up and running well before the actual MWO Tournament starts. And, if you're already up and running, feel free to launch some matches, we want to be sure everything is in place and working as soon as we can. (Yes, we did test everything in-house, but that's a very limited test).
#12
Posted 26 May 2016 - 08:17 PM
#13
Posted 26 May 2016 - 08:31 PM
Running Win 10 professional german. Got the right version of .net and normal mwo client is running.
cid:FEFBE7BA1AFE4BB58819D45FD974A59E@dns
Edited by JayKay17, 26 May 2016 - 08:39 PM.
#14
Posted 26 May 2016 - 09:12 PM
JayKay17, on 26 May 2016 - 08:31 PM, said:
[...]
Ok, so you're in the "Portal issues" pool. I'm going to try an update shortly to see if I can narrow things down a bit. I'm going to add in a very crude exception reader so that I can get a little more information about what's going on.
This raises a new point - the Portal auto-updates. So I guess we'll also be testing that on your system. As always, let me know if there are any problems with that.
#15
Posted 26 May 2016 - 10:33 PM
mwo runs normal.
edit (good point McAllister): i have not installed in the default folder, too.
error description:
No chance to click anything. the portal-screen shows up and crashes immediately.
Quote
Problemereignisname: CLR20r3
Problemsignatur 01: MWO Portal.exe
Problemsignatur 02: 1.0.0.0
Problemsignatur 03: 5747d8cf
Problemsignatur 04: System
Problemsignatur 05: 4.6.1055.0
Problemsignatur 06: 563c0ff8
Problemsignatur 07: 363
Problemsignatur 08: 73
Problemsignatur 09: System.UriFormatException
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 0a9e
Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789
Zusatzinformation 3: 0a9e
Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789
second:
why is pgi using the members of the world championship as beta-testers for a new development?
at least i as a team captain have my hands full with all the regular (trainings, tactics) and irregular (private match schedule rearrangements) issues.
and i am sure, pgi has enough other things to sort out than having to hurriedly fix beta-software issues last minute.
i am not pleased that i, additionally, have to sort out "portal" software issues with my teammates.
instead i would want to train with my team in the final championship environment.
lets hope this issue is a one-time problem and fixed quickly.
Edited by AngelusDD, 26 May 2016 - 10:50 PM.
#16
Posted 26 May 2016 - 10:46 PM
What additional information will be helpful to you?
#17
Posted 26 May 2016 - 11:10 PM
AngelusDD, on 26 May 2016 - 10:33 PM, said:
I have a new build I will be deploying shortly that should help narrow down the issue. The reason the Tournament build is being released this early is primarily for setup issues just like this. I'm sorry if it's an inconvenience, if you would prefer to wait until this gets sorted out, we should be done by this weekend, at the latest. (Please don't take that as a snotty answer, I just mean that helping us out at this point is purely optional).
#18
Posted 26 May 2016 - 11:21 PM
It also told me to tell you this ^^
Edited by Zarock, 26 May 2016 - 11:25 PM.
#19
Posted 26 May 2016 - 11:21 PM
Quincy McAllister, on 26 May 2016 - 10:46 PM, said:
We've tested installing to various directories, on various drives, with and without "special" characters and not seen this particular problem. I have no advice, but I am curious if the auto-update is working. Have you gotten any of the updates I've published? I've published two tonight in the last hour or so.
#20
Posted 26 May 2016 - 11:26 PM
vs2015 debugger> UnhandledException System.Security.Principal.IdentityNotMappedException
occured in call System.Security.Principal.NTAccount.Translate(bla.bla.IdentityRefferenceCollection,bool)
upd: > .net upgraded to 4.6.1, portal autoupgraded. Exception is present
Edited by Alex Razorblade, 26 May 2016 - 11:42 PM.
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users