Reepete's client crashes on startup

User-to-user help and troubleshooting.
Post Reply
MagisterXF94
Posts: 1935
Joined: Fri Aug 23, 2013 9:46 am
Location: Trieste, Italy

Post by MagisterXF94 »

Code: Select all

-------------- Log Start 12/13/15 at 2:54 PM UTC --------------

12/13/2015 2:54:52 PM UTC:     Using: Software\Microsoft\Microsoft Games\Allegiance\ for registry root.
            
12/13/2015 2:54:56 PM UTC:     ServiceHandler::LauncherSignIn() - Data received for: reepete, data length: 9216
            
12/13/2015 2:54:56 PM UTC:     AssemblyLoader::ValidateEntryAssembly() - data length: 9216
            
12/13/2015 2:54:56 PM UTC:     opened: HARDWARE\DEVICEMAP\Scsi
            
12/13/2015 2:54:56 PM UTC:     Scsi Port 0
            
12/13/2015 2:54:56 PM UTC:     Scsi Bus 0
            
12/13/2015 2:54:56 PM UTC:     Initiator Id 255
            
12/13/2015 2:54:56 PM UTC:     Target Id 0
            
12/13/2015 2:54:56 PM UTC:     Logical Unit Id 0
            
12/13/2015 2:54:56 PM UTC:     value: ST2000DMST2000DM001-1ER1HP51, cleanValue: ST2000DMST2000DM001 1ER1HP51
            
12/13/2015 2:54:56 PM UTC:     Scsi Bus 1
            
12/13/2015 2:54:56 PM UTC:     Initiator Id 255
            
12/13/2015 2:54:56 PM UTC:     Scsi Bus 2
            
12/13/2015 2:54:56 PM UTC:     Initiator Id 255
            
12/13/2015 2:54:56 PM UTC:     Target Id 0
            
12/13/2015 2:54:56 PM UTC:     Logical Unit Id 0
            
12/13/2015 2:54:56 PM UTC:     value: hp      DVD-RAM GHC0N   RL04, cleanValue: hp      DVD RAM GHC0N   RL04
            
12/13/2015 2:54:56 PM UTC:     Scsi Bus 3
            
12/13/2015 2:54:56 PM UTC:     Initiator Id 255
            
12/13/2015 2:54:56 PM UTC:     Scsi Bus 4
            
12/13/2015 2:54:56 PM UTC:     Initiator Id 255
            
12/13/2015 2:54:56 PM UTC:     Scsi Bus 5
            
12/13/2015 2:54:56 PM UTC:     Initiator Id 255
            
12/13/2015 2:54:56 PM UTC:     AssemblyLoader::ValidateEntryAssembly() loaded assembly: System.Reflection.Assembly
            
12/13/2015 2:54:56 PM UTC:     AssemblyLoader::ValidateEntryAssembly() machine info created.
            
12/13/2015 2:54:56 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
12/13/2015 2:54:56 PM UTC:     AssemblyLoader::ValidateEntryAssembly() calling checkin.
            
12/13/2015 2:55:00 PM UTC:     Using: C:\Program Files (x86)\Microsoft Games\Allegiance 1.2\Production\Allegiance.exe -authenticated -callsign= -debug -windowed -nomovies to launch...
            
12/13/2015 2:55:14 PM UTC:     ProcessHandler()::Debugger - Sending on exit task().
            
12/13/2015 2:55:14 PM UTC:     ProcessHandler()::Debugger - Calling OnExiting().
            
12/13/2015 2:55:14 PM UTC:     AllegianceLoader::process_OnExiting - Called!
            
12/13/2015 2:55:14 PM UTC:     AllegianceLoader::process_OnExiting - System Watcher Closed.
            
12/13/2015 2:55:14 PM UTC:     AllegianceLoader::process_OnExiting - Calling Allegiance Exit.
            
12/13/2015 2:55:14 PM UTC:     Allegiance process has ended, forcing processHandler to close.
            
12/13/2015 2:55:14 PM UTC:     Allegiance process was not found, this is normal. The message was: System.ArgumentException: Process with an Id of 5004 is not running.
            at System.Diagnostics.Process.GetProcessById(Int32 processId, String machineName)
            at System.Diagnostics.Process.GetProcessById(Int32 processId)
            at Allegiance.CommunitySecuritySystem.Client.Integration.ProcessMonitor.<.ctor>b__0(Object param)
QUOTE ^cashto@Elem (all): yeah, i imagine if you're rusty, you could build op short for no reason, build a naked ref, then go two techpaths even though your mining is by all objective standards $#@!ed[/quote]
Image
Wasp
Posts: 1084
Joined: Sun Aug 17, 2003 7:00 am

Post by Wasp »

He could try running it under Server 2003 mode, or vista mode, or even Win 7 mode.

I was able to get a client crash on launch fixed by changing the client to run in Win XP mode, I launched it and it crashed, I then changed it to run normally but I then deleted it before running it so that CSS would download a replacement client...which was able to run without crashing.

weird, I know... I had already tried to run the game once before after switching to xp mode and then back, but it crashed when running normally so the next time I changed the compatibility mode and deleted it before running the client. When CSS downloaded a replacement client, I think windows assigned the client a "normal mode" or reset something to make the client run properly.

I found that crashes on start up usually involve artwork issues. Many were corrected by uninstalling, cleaning the registry , rebooting and re-installing.

Another trick is to install the game in a compatibility mode. * Right click the installer, select Troubleshoot Compatibility, select The Program Worked in a Previous Version of Windows, then select a mode to install it.
Last edited by Wasp on Sun Dec 13, 2015 4:06 pm, edited 1 time in total.
MagisterXF94
Posts: 1935
Joined: Fri Aug 23, 2013 9:46 am
Location: Trieste, Italy

Post by MagisterXF94 »

fixed
QUOTE ^cashto@Elem (all): yeah, i imagine if you're rusty, you could build op short for no reason, build a naked ref, then go two techpaths even though your mining is by all objective standards $#@!ed[/quote]
Image
Post Reply