Allegiance crashes at Step 6!

Djole88 · Post by **Djole88** » Sat Feb 01, 2014 6:22 pm

I suspect you have an issue with network adapters order. .net TCP Client only tries to connect to the internet via the default adapter (the first one). That was an issue with .net2.0 though and they have maybe fixed it.

muddywaters · Post by **muddywaters** » Sat Feb 01, 2014 9:33 pm

Plugged ethernet straight into router and put VM into Bridged ethernet mode and still no cigar, even though it definitely had a wired connection to the net. Also tried changing the 'allsrvbox.alleg.net' in my allegiance.txt to 204.14.17.27, as AEM suggested. My VM definitely has access to internet. Every other internet function works. I do use the program "Little Snitch" on my macbook and it hasn't prompted me or blocked any of the connections from allegiance. Djole88: I should have .net 4.0. Any ideas?

Exception Log:

System.Net.WebException: The remote name could not be resolved: 'allsrvbox.alleg.net'
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Allegiance.CommunitySecuritySystem.Client.ClientService.ClientService.CheckAvail
ableLobbies() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Web References\ClientService\Reference.cs:line 638
at Allegiance.CommunitySecuritySystem.Client.Service.AutoUpdate.GetPendingUpdateQue
ues(ClientService service) in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Service\AutoUpdate.cs:line 58
at Allegiance.CommunitySecuritySystem.Client.Controls.UpdateCheckControl.get_Pendin
gUpdates() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Controls\UpdateCheckControl.cs:line 28
at Allegiance.CommunitySecuritySystem.Client.Controls.UpdateCheckControl.get_HasPen
dingUpdates() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Controls\UpdateCheckControl.cs:line 38
at Allegiance.CommunitySecuritySystem.Client.UpdateCheckForm.get_HasPendingUpdates(
) in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\UpdateCheckForm.cs:line 45
at Allegiance.CommunitySecuritySystem.Client.Program.Initialize() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Program.cs:line 152
at Allegiance.CommunitySecuritySystem.Client.Program.Main() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Program.cs:line 27

Post by **aem** » Sat Feb 01, 2014 9:54 pm

Shouldn't need to plug into router.

If you are still getting the same error after changing allsrvbox.alleg.net to the IP in the allegiance.txt file, ACSS is pulling allsrvbox.alleg.net from somewhere else. As I said before the other place you could change to the IP in the registry as well (back at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.2). Not sure if there might be any config files for CSS that have allsrvbox.alleg.net listed to.

Really odd that you would be able to access allsrvbox.alleg.net in a VM web browser but Alleg/CSS are failing to resolve.

edit: Also make sure you are completely closing ACSS after changing to the IP. It may be loading it when starting up and storing in memory.

muddywaters · Post by **muddywaters** » Sat Feb 01, 2014 10:26 pm

AEM wrote:QUOTE (AEM @ Feb 1 2014, 01:54 PM) Shouldn't need to plug into router.

If you are still getting the same error after changing allsrvbox.alleg.net to the IP in the allegiance.txt file, ACSS is pulling allsrvbox.alleg.net from somewhere else. As I said before the other place you could change to the IP in the registry as well (back at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Allegiance\1.2). Not sure if there might be any config files for CSS that have allsrvbox.alleg.net listed to.

Really odd that you would be able to access allsrvbox.alleg.net in a VM web browser but Alleg/CSS are failing to resolve.

edit: Also make sure you are completely closing ACSS after changing to the IP. It may be loading it when starting up and storing in memory.

So I set the key on the registry ProductionCfgFile to http://204.14.17.27/allegiance.txt. And it still crashes. I'm pretty sure ACSS was completed closed...I started up the VM and changed the registry key to that before I opened ACSS. allsrvbox.alleg.net definitely has no problem on my VM web browser.

I also noticed in the same registry folder, the file "ManagementWebRoot" was also set to 'allsrvbox.alleg.net,' so I just tried setting it to http://204.14.17.27 instead. Still no luck

Post by **aem** » Sat Feb 01, 2014 10:34 pm

muddywaters wrote:QUOTE (muddywaters @ Feb 1 2014, 03:26 PM) So I set the key on the registry ProductionCfgFile to http://204.14.17.27/allegiance.txt. And it still crashes. I'm pretty sure ACSS was completed closed...I started up the VM and changed the registry key to that before I opened ACSS. allsrvbox.alleg.net definitely has no problem on my VM web browser.

I also noticed in the same registry folder, the file "ManagementWebRoot" was also set to 'allsrvbox.alleg.net,' so I just tried setting it to http://204.14.17.27 instead. Still no luck

I would suspect the registry value that needs changed is ClientService. Did you try changing that? It is set to https://allsrvbox.alleg.net/CSSServer/ClientService.svc for me. The error references ClientService so I assume it is related.

muddywaters · Post by **muddywaters** » Sun Feb 02, 2014 12:09 am

Just tried replacing ClientService from https://allsrvbox.alleg.net/CSSServer/ClientService.svc to:

https://204.14.17.27/CSSServer/ClientService.svc

I also tried without the 's' in https, so: http://204.14.17.27/CSSServer/ClientService.svc

and it actually prompted me once I opened ACSS that it wasn't connected to the internet (and asked if I wanted to play single-player). So internet actually didn't work with ACSS with that incorrect key.

So with the default Key (allsrvbox.alleg.net) AND the '204.14.17.27' key ACSS has no problem connecting to the net. It's once the ACSS is signed in and the Allegiance game is already launched and I click "Free Games" that it crashes...

Post by **Dome** » Sun Feb 02, 2014 12:29 am

Are you sure your direct x is up to date?

The only time I've had crashes on pushing free games is when I have out of date dx.

I'm using dx11.

Post by **aem** » Sun Feb 02, 2014 1:03 am

muddywaters wrote:QUOTE (muddywaters @ Feb 1 2014, 05:09 PM) Just tried replacing ClientService from https://allsrvbox.alleg.net/CSSServer/ClientService.svc to:

https://204.14.17.27/CSSServer/ClientService.svc

I also tried without the 's' in https, so: http://204.14.17.27/CSSServer/ClientService.svc

and it actually prompted me once I opened ACSS that it wasn't connected to the internet (and asked if I wanted to play single-player). So internet actually didn't work with ACSS with that incorrect key.

So with the default Key (allsrvbox.alleg.net) AND the '204.14.17.27' key ACSS has no problem connecting to the net. It's once the ACSS is signed in and the Allegiance game is already launched and I click "Free Games" that it crashes...

I am about out of ideas other than you could try updating directx as Dome suggests (http://www.microsoft.com/en-us/download/details.aspx?id=35). Looks like a .Net exception though.

When you have the IP set for ClientService, is the exception still the same?

muddywaters · Post by **muddywaters** » Sun Feb 02, 2014 1:29 am

I have Windows XP here with DirectX 9C, (They never made 10 or 11 for XP) on my Virtual machine. I just updated it with that link anyways, and no cigar. .NET is version 4.0...maybe i should try and update?

New Exception with IP set for ClientService in registry:

Exception Log: C:\Program Files\Microsoft Games\Allegiance 1.2\ExceptionLog.txt
===============================================================================
System.Net.WebException: The request failed with HTTP status 404: Not Found.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMess
age message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Allegiance.CommunitySecuritySystem.Client.ClientService.ClientService.CheckAvail
ableLobbies() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Web References\ClientService\Reference.cs:line 638
at Allegiance.CommunitySecuritySystem.Client.Service.AutoUpdate.GetPendingUpdateQue
ues(ClientService service) in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Service\AutoUpdate.cs:line 58
at Allegiance.CommunitySecuritySystem.Client.Controls.UpdateCheckControl.get_Pendin
gUpdates() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Controls\UpdateCheckControl.cs:line 28
at Allegiance.CommunitySecuritySystem.Client.Controls.UpdateCheckControl.get_HasPen
dingUpdates() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Controls\UpdateCheckControl.cs:line 38
at Allegiance.CommunitySecuritySystem.Client.UpdateCheckForm.get_HasPendingUpdates(
) in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\UpdateCheckForm.cs:line 45
at Allegiance.CommunitySecuritySystem.Client.Program.Initialize() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Program.cs:line 152
at Allegiance.CommunitySecuritySystem.Client.Program.Main() in C:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Program.cs:line 27

Post by **aem** » Sun Feb 02, 2014 2:03 am

Hm, I wonder if it is possible it is SSL related since I think it is only failing on the https link. May be possible it is getting blocked because it does not have a valid/trusted SSL certificate. Not sure the proper workaround if it may be getting blocked due to this.

Maybe try Control Panel -> Internet Options. Go to Advanced and scroll down to the bottom. Uncheck "Warn about invalid site certificates". Also go to the Security tab and add https://allsrvbox.alleg.net to the Trusted Sites. You might also try opening https://allsrvbox.alleg.net/CSSServer/ClientService.svc in Internet Explorer and making sure it loads there fine with no warning/error (shouldn't after doing the last couple steps).

Change the ClientService URL back to https://allsrvbox.alleg.net/CSSServer/ClientService.svc instead of the IP before trying this.

Be sure Windows is fully up to date as well.