Page 5 of 9

Posted: Wed Aug 13, 2014 5:21 am
by hockey1015
8/13/2014 5:14:50 AM UTC: Allegiance process was not found, this is normal. The message was: System.InvalidOperationException: Cannot process request because the process (4440) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle()
at System.Diagnostics.Process.get_Handle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessMonitor.<.ctor>b__0(Object param) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessMonitor.cs:line 54

8/13/2014 5:14:50 AM UTC: System.Exception: An error occurred trying to kill allegiance. This usually happens when Allegiance is shutting down and the process killer also tries to clean it up at the same time. This error is safe to ignore. ---> System.InvalidOperationException: Cannot process request because the process (4440) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.WaitForInputIdle(Int32 milliseconds)
at System.Diagnostics.Process.WaitForInputIdle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessHandler.ForceClose(
) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessHandler.cs:line 92
--- End of inner exception stack trace ---

8/13/2014 5:14:51 AM UTC: Allegiance process was not found, this is normal. The message was: System.InvalidOperationException: Cannot process request because the process (4440) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle()
at System.Diagnostics.Process.get_Handle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessMonitor.<.ctor>b__0(Object param) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessMonitor.cs:line 54

8/13/2014 5:14:51 AM UTC: System.Exception: An error occurred trying to kill allegiance. This usually happens when Allegiance is shutting down and the process killer also tries to clean it up at the same time. This error is safe to ignore. ---> System.InvalidOperationException: Cannot process request because the process (4440) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.WaitForInputIdle(Int32 milliseconds)
at System.Diagnostics.Process.WaitForInputIdle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessHandler.ForceClose(
) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessHandler.cs:line 92
--- End of inner exception stack trace ---

8/13/2014 5:14:52 AM UTC: ProcessHandler()::Debugger - Sending on exit task().

8/13/2014 5:14:52 AM UTC: ProcessHandler()::Debugger - Calling OnExiting().

8/13/2014 5:14:52 AM UTC: AllegianceLoader::process_OnExiting - Called!

8/13/2014 5:14:52 AM UTC: AllegianceLoader::process_OnExiting - System Watcher Closed.

8/13/2014 5:14:52 AM UTC: AllegianceLoader::process_OnExiting - Calling Allegiance Exit.

8/13/2014 5:14:52 AM UTC: PlayControl::AllegianceProcess_OnExiting - Logout.

8/13/2014 5:14:52 AM UTC: PlayControl::AllegianceProcess_OnExiting - AllegianceExited called.

Posted: Wed Aug 13, 2014 5:49 am
by BackTrak
It seems like every thing around the acss server is very slow, even just remoting into it was slow. I'll continue to dig on it.

Posted: Wed Aug 13, 2014 2:15 pm
by MagisterXF94
Credentials timeout error while first starting the launcher at 16.07 pm (GMT+1)
log:

Code: Select all

System.Net.WebException: Timeout dell'operazione.
   in System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   in System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   in System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   in Allegiance.CommunitySecuritySystem.Client.ClientService.ClientService.CheckIn(CheckInData data) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Web References\ClientService\Reference.cs:riga 260
   in Allegiance.CommunitySecuritySystem.Client.Service.SessionNegotiator.CheckIn(Byte[] encryptedData, String& message, String& ticket) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Service\SessionNegotiator.cs:riga 157
   in Allegiance.CommunitySecuritySystem.Client.PlayControl.CheckInTimer_Tick(Object sender, EventArgs e) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Controls\PlayControl.cs:riga 96
   in System.Windows.Forms.Timer.OnTick(EventArgs e)
   in System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Posted: Thu Aug 14, 2014 1:47 am
by MrChaos
BackTrak wrote:QUOTE (BackTrak @ Aug 12 2014, 03:23 PM) waaaaah someone stole my trucker cap of infinity ability to see the details from random posts again

Thanks,
-BT
Ffs dude again?!?

edit: gah.... *nervously makes circles in the dirt with the toe of his shoe*.... *clears throst*... "ahhhh".... *nervous titter*... my inability to spool is legeundiary and all... *clears throat* and duly noted but *high pitched insane witchy cackle*

ffs it is lose

not loose

unless of course that is Aussie spelling of the word :unsure:


MrChaos <--- got schooled on to, too, and two by *hangs head in perpetual shame* lexaal

Posted: Fri Aug 15, 2014 3:08 am
by hockey1015
Sigh. Another crash, I believe.

8/15/2014 3:02:21 AM UTC: System.Net.WebException: The operation has timed out
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Allegiance.CommunitySecuritySystem.Client.ClientService.ClientService.CheckIn(Ch
eckInData data) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Web References\ClientService\Reference.cs:line 260
at Allegiance.CommunitySecuritySystem.Client.Service.SessionNegotiator.CheckIn(Byte
[] encryptedData, String& message, String& ticket) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Service\SessionNegotiator.cs:line 157
at Allegiance.CommunitySecuritySystem.Client.Service.SessionNegotiator.ValidateLogi
n(Byte[] blackboxData, String& message, String& ticket) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Service\SessionNegotiator.cs:line 144
at Allegiance.CommunitySecuritySystem.Client.Service.SessionNegotiator.<>c__DisplayClass3.<Login>b__2(Object input) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Service\SessionNegotiator.cs:line 62





Exception Log: D:\Program Files\Allegiance 1.2\ExceptionLog.txt
===============================================================================
System.Net.WebException: The operation has timed out
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Allegiance.CommunitySecuritySystem.Client.ClientService.ClientService.CheckIn(Ch
eckInData data) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Web References\ClientService\Reference.cs:line 260
at Allegiance.CommunitySecuritySystem.Client.Service.SessionNegotiator.CheckIn(Byte
[] encryptedData, String& message, String& ticket) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Service\SessionNegotiator.cs:line 157
at Allegiance.CommunitySecuritySystem.Client.PlayControl.CheckInTimer_Tick(Object sender, EventArgs e) in C:\Source\Allegiance\CSS-BT-AutoUpdateFix\Client\Allegiance.CommunitySecuritySystem.Client\Controls\PlayControl.cs:line 96
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Posted: Fri Aug 15, 2014 3:20 am
by BackTrak
Hi Guys,

I updated some of the timeout limits in the launcher, so you'll get a fresh one starting tonight. Let me know if you see improvements (or lack thereof).

Thanks,
-BT

Posted: Fri Aug 15, 2014 3:31 am
by hockey1015
BackTrak wrote:QUOTE (BackTrak @ Aug 14 2014, 11:20 PM) Hi Guys,

I updated some of the timeout limits in the launcher, so you'll get a fresh one starting tonight. Let me know if you see improvements (or lack thereof).

Thanks,
-BT
Was that the 2 updates? Appreciate the help with trying to solve this. I'll do my best to keep you updated.

Posted: Fri Aug 15, 2014 3:44 am
by BackTrak
Yep, that was them... One more update coming, missed a spot... :D

Posted: Fri Aug 15, 2014 3:57 am
by hockey1015
BackTrak wrote:QUOTE (BackTrak @ Aug 14 2014, 11:44 PM) Yep, that was them... One more update coming, missed a spot... :D

Ya, just had another crash.

8/15/2014 3:49:06 AM UTC: Allegiance process was not found, this is normal. The message was: System.InvalidOperationException: Cannot process request because the process (668) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle()
at System.Diagnostics.Process.get_Handle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessMonitor.<.ctor>b__0(Object param) in c:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessMonitor.cs:line 54

8/15/2014 3:49:06 AM UTC: System.Exception: An error occurred trying to kill allegiance. This usually happens when Allegiance is shutting down and the process killer also tries to clean it up at the same time. This error is safe to ignore. ---> System.InvalidOperationException: Cannot process request because the process (668) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.WaitForInputIdle(Int32 milliseconds)
at System.Diagnostics.Process.WaitForInputIdle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessHandler.ForceClose(
) in c:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessHandler.cs:line 92
--- End of inner exception stack trace ---

8/15/2014 3:49:07 AM UTC: Allegiance process was not found, this is normal. The message was: System.InvalidOperationException: Cannot process request because the process (668) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.OpenProcessHandle()
at System.Diagnostics.Process.get_Handle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessMonitor.<.ctor>b__0(Object param) in c:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessMonitor.cs:line 54

8/15/2014 3:49:07 AM UTC: System.Exception: An error occurred trying to kill allegiance. This usually happens when Allegiance is shutting down and the process killer also tries to clean it up at the same time. This error is safe to ignore. ---> System.InvalidOperationException: Cannot process request because the process (668) has exited.
at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited)
at System.Diagnostics.Process.WaitForInputIdle(Int32 milliseconds)
at System.Diagnostics.Process.WaitForInputIdle()
at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessHandler.ForceClose(
) in c:\Source\Allegiance\CSS\Client\Allegiance.CommunitySecuritySystem.Client\Integration\ProcessHandler.cs:line 92
--- End of inner exception stack trace ---

8/15/2014 3:49:08 AM UTC: ProcessHandler()::Debugger - Sending on exit task().

8/15/2014 3:49:08 AM UTC: ProcessHandler()::Debugger - Calling OnExiting().

8/15/2014 3:49:08 AM UTC: AllegianceLoader::process_OnExiting - Called!

8/15/2014 3:49:08 AM UTC: AllegianceLoader::process_OnExiting - System Watcher Closed.

8/15/2014 3:49:08 AM UTC: AllegianceLoader::process_OnExiting - Calling Allegiance Exit.

8/15/2014 3:49:08 AM UTC: PlayControl::AllegianceProcess_OnExiting - Logout.

8/15/2014 3:49:08 AM UTC: PlayControl::AllegianceProcess_OnExiting - AllegianceExited called.

Posted: Fri Aug 15, 2014 4:02 am
by cashto
I can't log in. After d/ling the two updates, I receive 'machine hash not valid' when starting the launcher.