These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Test Server Feedback

 
  • Topic is locked indefinitely.
 

Launcher Bug since last Sissi's DT ?

First post
Author
Previous Topic Next Topic
Fantome
The Scope
Gallente Federation
#1 - 2013-10-28 16:02:05 UTC
When i try to log since the last DT on Sissi i get this msg on the launcher after entering login/pw :

Sorry, but an error occured while processing your request.

Error code: CDD340BF-B17F-43AD-BDD9-E067617F62E4


Worked fine just before dt this afternoom.
Flying Apocalypse
#2 - 2013-10-28 16:07:32 UTC
Same here:
Error code: 0DC1E20D-0A0C-4BD2-ADC0-5576330A7AC9

For some reason I can't delete my signature o.o
Vinyl 41
AdVictis
#3 - 2013-10-28 16:09:39 UTC
sadly same junk here error codes differ every time i try to log in Ugh
D17D4D85-7738-4524-A186-33B859D825D3
CCP Habakuk
C C P
C C P Alliance
#4 - 2013-10-28 16:19:59 UTC
Hi,

This is a known issue and we working on fixing it.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
Fantome
The Scope
Gallente Federation
#5 - 2013-10-28 16:23:10 UTC
Thx for update.
Ahnn
Space Zombiez
#6 - 2013-10-28 17:16:28 UTC  |  Edited by: Ahnn
You can work around this by using the old log in window.

Open the folder named "bin" in your Singularity installation. Find the file named "exefile". Make a shortcut to the "exefile". Right click the shortcut and select Properties. In the Target field, click after the last quotation mark. Hit the spacebar one time, then type /server:Singularity

Hit the Apply button, then double click the shortcut. If you did it right, you'll soon find yourself at the old (and still reliable) log in screen.
Maruk Ihnati
Coreli Corporation
Pandemic Legion
#7 - 2013-10-28 17:42:13 UTC  |  Edited by: Maruk Ihnati
nvm
Johan Botha
Aliastra
Gallente Federation
#8 - 2013-10-28 17:50:35 UTC
Ahnn wrote:
You can work around this by using the old log in window.

Open the folder named "bin" in your Singularity installation. Find the file named "exefile". Make a shortcut to the "exefile". Right click the shortcut and select Properties. In the Target field, click after the last quotation mark. Hit the spacebar one time, then type /server:Singularity

Hit the Apply button, then double click the shortcut. If you did it right, you'll soon find yourself at the old (and still reliable) log in screen.



I can confirm, this does work.
BravoFoxtrot
Basgerin Pirate
#9 - 2013-10-28 17:58:11 UTC
Johan Botha wrote:
Ahnn wrote:
You can work around this by using the old log in window.

Open the folder named "bin" in your Singularity installation. Find the file named "exefile". Make a shortcut to the "exefile". Right click the shortcut and select Properties. In the Target field, click after the last quotation mark. Hit the spacebar one time, then type /server:Singularity

Hit the Apply button, then double click the shortcut. If you did it right, you'll soon find yourself at the old (and still reliable) log in screen.



I can confirm, this does work.




Not working for me. Client is saying incompatible. :(
Ahnn
Space Zombiez
#10 - 2013-10-28 18:00:10 UTC  |  Edited by: Ahnn
BravoFoxtrot wrote:
Johan Botha wrote:
Ahnn wrote:
You can work around this by using the old log in window.

Open the folder named "bin" in your Singularity installation. Find the file named "exefile". Make a shortcut to the "exefile". Right click the shortcut and select Properties. In the Target field, click after the last quotation mark. Hit the spacebar one time, then type /server:Singularity

Hit the Apply button, then double click the shortcut. If you did it right, you'll soon find yourself at the old (and still reliable) log in screen.



I can confirm, this does work.




Not working for me. Client is saying incompatible. :(


You must have an up-to-date client to log on, whether or not you're logging in through the new system or old, you *always* have to have the current build.

Open the launcher and let it update. After it has updated, you can then use the above method.
BravoFoxtrot
Basgerin Pirate
#11 - 2013-10-28 18:02:21 UTC
Ahnn wrote:
BravoFoxtrot wrote:
Johan Botha wrote:
Ahnn wrote:
You can work around this by using the old log in window.

Open the folder named "bin" in your Singularity installation. Find the file named "exefile". Make a shortcut to the "exefile". Right click the shortcut and select Properties. In the Target field, click after the last quotation mark. Hit the spacebar one time, then type /server:Singularity

Hit the Apply button, then double click the shortcut. If you did it right, you'll soon find yourself at the old (and still reliable) log in screen.



I can confirm, this does work.




Not working for me. Client is saying incompatible. :(


You must have an up-to-date client to log on, whether or not you're logging in through the new system or old, you *always* have to have the current build.



Yes, I just noticed the launcher was not updating the client either. Also I had to use the exe file in the installation folder not the bin folder to get it to update.
CCP Habakuk
C C P
C C P Alliance
#12 - 2013-10-28 18:34:23 UTC
This launcher error should be fixed now.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
Fantome
The Scope
Gallente Federation
#13 - 2013-10-28 18:37:55 UTC
Yes work fine now for me.
Thx
Kane Boirelle
Antimatter Ruins You
Esports Petopia
#14 - 2013-10-29 11:06:51 UTC
I get a "Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index"

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Whenever I try and load the SiSi launcher, worked fine yesterday afternoon and I haven't changed anything since. I would copy and paste the Source Error and Stack trace but the forums won't let me as it contains HTML (Anywhere I can submit this?)