Dr. Alan Grant: Well, on the trailer, they used frog DNA to fill in the dinosaurs gene sequence gaps. They mutated the dinosaur genetic code and blended it with that of a frog's. Now, some updates for the game sometimes came with problems, and it's a bad idea put it on holodeck before testing or make corrections. Malcolm was right.
Dr. Ian Malcolm: You've heard of chaos theory? Taking dinosaurs off Jurassic island is the worst idea in the long, sad history of bad ideas. And i can't be there when you learn that, because my game crashes.
Genetic power is the most awesome force the planet's ever seen, but you wield it on this faster-carelessly update like a kid that's found his dad's gun.
(somebody remember this movie quotes?)
you want to know something really creepy. there is an element of truth in this, they are already cloning extinct species and as of this year they are using frog DNA!
and what's worse (for all you batman and DC fans out there) its called the
"The meaning of victory is not to merely defeat your enemy but to destroy him, to completely eradicate him from living memory, to leave no remnant of his endeavours, to crush utterly his achievement and remove from all record his every trace of existence. From that defeat no enemy can ever recover. That is the meaning of victory."
-Lord Commander Solar Macharius
Don't bet on them being at home. Programmers HATE having a bug in something and can be pretty OC about finding the why. (So they are possibly working at least Saturday to find a solution.)
That said, can someone figure out what is the fault in common? Maybe if we spend sometime on the weekend helping out, we can get the team closer to a solution.
Damn it, raven, I'm a Doctor, not a Programmer!
j/k xD But I agree, how can we go about helping these guys? I know I can't speak for everyone but I'm sure that pretty much everyone on this thread would agree to help out if asked to do something to help the situation. If the guys need me to keep crashing every 2 minutes or learn how to make a .dmp file (I think the crash report handles that though) and read it, I'd be happy to volunteer. I'd even feed and water the Hamsters that run the servers, though I hear they've upgraded to Guinea Pigs xD
Let's squish these bugs together, people! Or at least not berate these poor guys until after they fix it ^^
j/k xD But I agree, how can we go about helping these guys? I know I can't speak for everyone but I'm sure that pretty much everyone on this thread would agree to help out if asked to do something to help the situation. If the guys need me to keep crashing every 2 minutes or learn how to make a .dmp file (I think the crash report handles that though) and read it, I'd be happy to volunteer. I'd even feed and water the Hamsters that run the servers, though I hear they've upgraded to Guinea Pigs xD
Let's squish these bugs together, people! Or at least not berate these poor guys until after they fix it ^^
+1.............
(future refarance the full stops are to fill the gap for the "minimum requirement of 10 letters)
j/k xD But I agree, how can we go about helping these guys? I know I can't speak for everyone but I'm sure that pretty much everyone on this thread would agree to help out if asked to do something to help the situation. If the guys need me to keep crashing every 2 minutes or learn how to make a .dmp file (I think the crash report handles that though) and read it, I'd be happy to volunteer. I'd even feed and water the Hamsters that run the servers, though I hear they've upgraded to Guinea Pigs xD
Let's squish these bugs together, people! Or at least not berate these poor guys until after they fix it ^^
First, the servers here at the Holodeck have always run on Tribbles. Never anything else. Hamsters run the Gravity servers at Ragnarok Online. The Guinea Pigs handle Turbine. Rats and Mice for Blizzard.
Second, anything has to be better than nothing right? O_o I've got 2300 Zen and I want a new Fed character to play!
What I'm going to suggest might be a bit inconvenient for players who have got on.
This is an idea on crushing these bugs and errors could be squashed
Close the server, we'd understand if you did Cryptic but the bugs need squashing, zero server strain means the programmers have free reign to swat them.
Cryptic need to do a Sony, I'll elaborate on that
When Sony got TRIBBLE they brought down the entire Playstation network and compensated the players when the network came back online, a happy customer is a loyal customer.
If only Cryptic went along the same lines as Sony, they would keep that customer base happy.
We've all lost lobi and possibly the tribble as well, Gold players and life timers pay for this game monthly and they are not too happy about it.
I'm only a silver F2P but I've put money into this game with purchases and I enjoy this game immensely, it's sad to see how much the errors and bugs have broken it.
Cryptic please kill these bugs so we can all get back online.
"The meaning of victory is not to merely defeat your enemy but to destroy him, to completely eradicate him from living memory, to leave no remnant of his endeavours, to crush utterly his achievement and remove from all record his every trace of existence. From that defeat no enemy can ever recover. That is the meaning of victory."
-Lord Commander Solar Macharius
I don't have any updates to provide at this time -- wanted to let you know before I head out for the weekend. I will be watching email, and if there is an update that arises that I can provide, I'll post here.
Cheers,
Brandon =/\=
Thanks for keeping us in the loop. have a great weekend Brandon.
At this point I'd even be willing to spell the tribbles (Hamsters, whatever...) for a while and run the wheel myself if it would get me back in the game...
"If you can't take a little bloody nose, maybe you ought to go back home and crawl under your bed. It's not safe out here. It's wondrous, with treasures to satiate desires both subtle and gross; but it's not for the timid." -- Q, TNG: "Q-Who?"
^Words that every player should keep in mind, especially whenever there's a problem with the game...
At this point I'd even be willing to spell the tribbles (Hamsters, whatever...) for a while and run the wheel myself if it would get me back in the game...
I'll take second shift....
Proud Member of the Order of persistence, Chief of Investigations"Persistent Officer"since 11/12/13...:P 600 strong and growing...all phages, vidians, other outcasts welcome, note: all new members BYOC (bring your own chair) please and thank you! Five time winner in 1st and 2nd annual last 500 tied for top 2000 @halfpint71ky
Cryptic knew about these client glitches back when they were beta testing S8. So just why would they apply this to the Holodeck server if they knew there were problems with it?
possibilitiesare a thing of hope,sometimes it drives us toward something better
Cryptic knew about these client glitches back when they were beta testing S8. So just why would they apply this to the Holodeck server if they knew there were problems with it?
They are probably having a hard time replicating it in their systems. Just look at the number of ticket numbers shows how complicated it is.
Having crashing problems while loading Holodeck. Previously had problems on Tribble (but no problems on Hololdeck, prior to Season 8 rollout). So, whatever the issue is seems to have to do with some changes made on Tribble beta test, and that got rolled out to Holodeck.
Trying some troubleshooting steps.
Let's start with basics, though.
HP Pavilion PW526AA-ABA a1007w
AMD Athlon64 3200+ (2.21GHz) w/1GB RAM.
XP Pro SP3 (32-bit?). Currently running some windows updates.
DirectX 9.0c (4.09.000.0904)
ATI Radeon HD 3450 (512MB) AGP. Some of the details in DirectX or Catalyst Control Center appear to indicate it's a VisionTek. (Driver packaging 8.723-1004069-099558E-VisionTek).
HP vs15 flat panel.
Have tried "force verify." No joy.
Tried deleting PIGGs & HOGGs & horses. (oh myyyy!) And making STO re-patch 12GB, with no joy.
Now a friend is remote assisting me.
We copied the old .log files, and re-nameed them so they'd get recreated the next time there was a crash. Strangely, only 2 out of the 4 got recreated. Debug.log & Clientservercomm.log. But Crash.log & error.log were NOT recreated durign the crash. Is that normal? Seems odd, given, y'know, the "crash," that crash.log wouldn't be recreated.
Not sure whether those are specific to the CRASH, or just generic errors?
As to the crash itself, launcher works fine. It updates. I close it, re-open it. Launcher patch seemed to take. Patched client. Clicked engage. It gets through the loading screen with the Legacy of Romulus logo, then right before the character selection screen would come up, it crashes to desktop with no error message, just a box asking what happened. That's what I'D LIKE TO KNOW!
[1115/221727:ERROR:backend_impl.cc(2083)] Corrupt Index file
[1115/221727:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[1115/221727:ERROR:backend_impl.cc(134)] Unable to move cache folder C:\Program Files\Perfect World Entertainment\Star Trek Online_en\cef_cache to C:\Program Files\Perfect World Entertainment\Star Trek Online_en\old_cef_cache_000
[1115/221727:ERROR:backend_impl.cc(221)] Unable to create cache
[1115/221815:ERROR:backend_impl.cc(2083)] Corrupt Index file
[1115/221815:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[1115/221815:ERROR:backend_impl.cc(134)] Unable to move cache folder C:\Program Files\Perfect World Entertainment\Star Trek Online_en\cef_cache to C:\Program Files\Perfect World Entertainment\Star Trek Online_en\old_cef_cache_000
[1115/221815:ERROR:backend_impl.cc(221)] Unable to create cache
[1115/221825:INFO:CONSOLE(0)] "Select shard: 0," source: http://launcher.startrekonline.com/static/all/js/api.js(96)
My system is WinXp pro SP3
AMD athlon 64 3800+
2.40Ghz 1.5gb ram
Nvidia 9400gt
From the old crash.log (not recreated upon the current crop of crashes today after renaming the old file):
131106 23:02:20 62 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 01:35:20 22 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 05:12:51 18 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 06:40:56 89 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 11:24:18 54 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 22:15:01 88 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131108 04:23:56 149 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 01:55:13 47 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 04:08:03 24 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 06:16:14 18 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 11:50:28 74 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 22:19:02 15 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131110 04:27:13 48 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131110 10:20:37 33 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131110 22:43:53 33 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131111 04:07:06 93 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131111 11:02:49 64 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131112 00:08:16 69 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131113 23:50:48 14 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
Not sure whether those are related to this issue. Perhaps? Or somethign else?
In the old clientservercomm.log, there's a lot of this kind of stuff:
131111 23:59:24 61 Client[0 [NOENT]]: GameServer link connected (208.95.186.43:7266).
131112 00:04:49 62 Client[0 [NOENT]]: GameServer link being forcibly disconnected by client (208.95.186.43:7266): Entered gclLogin
131112 00:04:49 63 Client[0 [NOENT]]: GameServer link disconnected (208.95.186.43:7266). Reason: Entered gclLogin(997:Unknown socket error) (socket error 997: Unknown socket error)
131112 00:04:50 64 Client[0 [NOENT]]: ChatRelay link disconnected (208.95.186.12:7403). Reason: socket was shutdown(10054:Connection reset by remote host) (socket error 10054: Connection reset by remote host)
131112 00:04:53 65 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7422
131112 00:05:43 66 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.12:7422). Reason: socket was shutdown(0:No error) (socket error 0: No error)
131112 00:05:43 67 Client[0 [NOENT]]: GameServer link attempting connect (208.95.186.45:7219).
131112 00:05:44 68 Client[0 [NOENT]]: GameServer link connected (208.95.186.45:7219).
131112 22:29:19 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131112 22:29:19 15 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.11:7422). Reason: gclLoginFail(0:No error) (socket error 0: No error)
131112 22:31:19 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131112 22:32:56 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7422
131112 22:51:12 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7001
131113 01:33:12 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7001
131113 02:03:04 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7001
131113 05:20:14 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7422
131113 12:29:04 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7001
131113 12:29:05 15 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.13:7001). Reason: gclLoginFail(0:No error) (socket error 0: No error)
131113 12:47:29 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131113 23:54:16 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.184.129:7001
131114 02:54:44 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7001
131114 08:11:00 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131114 19:09:12 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7422
131115 09:42:57 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.32:7422
131115 16:21:59 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131115 16:22:00 15 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.11:7422). Reason: gclLoginFail(0:No error) (socket error 0: No error)
Don't know if that's germane or not. May or may not indicate a connectivity issue?
Are others getting these same kinds of error messages in their logs...?
Hmm...your's looks like mine. Same error message number (188 whatever) by chance?
Everyone, check the files msot recent (as in the last four days) in the Star Trek Online Logs folder...let's see what we got going on here?
This looks like my version of the file. Maybe a key to solving the problem for the Dev Team helping us lies in what ever is similar between the files. Namely let's stick to people who have not had the same Ticket Number as me or this guy.
Having nothing better to do, I loaded up my STO client to try again to get into game. First thing I notice is my launcher gets a patch, this is before it loads the log-in screen. So, just curious, was I the only one to get this launcher patch? What got changed this time? Could this all be because of a glitch in the launcher coding?
As of while I'm typing this, got the last game patch being applied....soo...fingers crossed.
Having nothing better to do, I loaded up my STO client to try again to get into game. First thing I notice is my launcher gets a patch, this is before it loads the log-in screen. So, just curious, was I the only one to get this launcher patch? What got changed this time? Could this all be because of a glitch in the launcher coding?
As of while I'm typing this, got the last game patch being applied....soo...fingers crossed.
If it is what I think it is...nope. I got it as well.
Uhm....got through the load screens and am now sitting looking at the 'in-game' log-in screen. Got an 'account ticket authentication failure', but I see the animated planet in the background. Am trying the log-in from here now....*keeps fingers crossed.*
EDIT: *Picks jaw up off floor.*
Am now on character select screen.
EDIT #2: Am now in-game in my ship. Earlier, someone posted about getting this far and not being able to do anything....*still has fingers crossed.*
Having nothing better to do, I loaded up my STO client to try again to get into game. First thing I notice is my launcher gets a patch, this is before it loads the log-in screen. So, just curious, was I the only one to get this launcher patch? What got changed this time? Could this all be because of a glitch in the launcher coding?
As of while I'm typing this, got the last game patch being applied....soo...fingers crossed.
Ours patched as well. But the patch seemed to go fine for the LAUNCHER. But, in our case it's the GAME CLIENT that crashes, not the launcher. So, to me at least, that seems to rule out a launcher issue? Dunno. Something about whatever goes on RIGHT BEFORE hitting the character selection screen. As that seems to be right when the crashing is happening, consistently...
Before, it was ONLY doing it on Tribble, but NOT on Holodeck. Now it's doing it both places (after Season 8 rolled out). So, pretty clearly something changed on the Tribble version, and that change then propagated when it rolled out live to Holodeck.
I'm helping out my friend Everton2003 remotely. I'm hoping that we can, by getting specs & log file reports maybe narrow down what's up. Interesting that someone else was running XP SP3 on an Athlon 64, as that's what my friend is running (different GHz, but same basic architecture). May be nothing? Dunno. Don't know if there's any weird issue with XP 32-bit OS running on Athlon 64-bit processor? One would hope not... But y'never know. Just a "left field" "logical leap." I'm sure others with different setups will probably rule out that theory?
Could it be an issue with the account servers? I know I was getting a lot of those 'account ticket authentication failures' of late instead of just being taken right to the character select screen and having to re-log-in every time.
Comments
Parallels: my second mission for Fed aligned Romulans.
first characters come up then crash
id#26340348
you want to know something really creepy. there is an element of truth in this, they are already cloning extinct species and as of this year they are using frog DNA!
and what's worse (for all you batman and DC fans out there) its called the
LAZARUS PROJECT!!!!
.
.
apparently its been going on since 2003
http://ngm.nationalgeographic.com/2013/04/125-species-revival/zimmer-text
-Lord Commander Solar Macharius
Damn it, raven, I'm a Doctor, not a Programmer!
j/k xD But I agree, how can we go about helping these guys? I know I can't speak for everyone but I'm sure that pretty much everyone on this thread would agree to help out if asked to do something to help the situation. If the guys need me to keep crashing every 2 minutes or learn how to make a .dmp file (I think the crash report handles that though) and read it, I'd be happy to volunteer. I'd even feed and water the Hamsters that run the servers, though I hear they've upgraded to Guinea Pigs xD
Let's squish these bugs together, people! Or at least not berate these poor guys until after they fix it ^^
+1.............
(future refarance the full stops are to fill the gap for the "minimum requirement of 10 letters)
First, the servers here at the Holodeck have always run on Tribbles. Never anything else. Hamsters run the Gravity servers at Ragnarok Online. The Guinea Pigs handle Turbine. Rats and Mice for Blizzard.
Second, anything has to be better than nothing right? O_o I've got 2300 Zen and I want a new Fed character to play!
This is an idea on crushing these bugs and errors could be squashed
Close the server, we'd understand if you did Cryptic but the bugs need squashing, zero server strain means the programmers have free reign to swat them.
Cryptic need to do a Sony, I'll elaborate on that
When Sony got TRIBBLE they brought down the entire Playstation network and compensated the players when the network came back online, a happy customer is a loyal customer.
If only Cryptic went along the same lines as Sony, they would keep that customer base happy.
We've all lost lobi and possibly the tribble as well, Gold players and life timers pay for this game monthly and they are not too happy about it.
I'm only a silver F2P but I've put money into this game with purchases and I enjoy this game immensely, it's sad to see how much the errors and bugs have broken it.
Cryptic please kill these bugs so we can all get back online.
-Lord Commander Solar Macharius
^Words that every player should keep in mind, especially whenever there's a problem with the game...
I'll take second shift....
I call Third shift!
...or I call shotgun.
Didn't work for me. I tried Safe Mode.
They are probably having a hard time replicating it in their systems. Just look at the number of ticket numbers shows how complicated it is.
Trying some troubleshooting steps.
Let's start with basics, though.
HP Pavilion PW526AA-ABA a1007w
AMD Athlon64 3200+ (2.21GHz) w/1GB RAM.
XP Pro SP3 (32-bit?). Currently running some windows updates.
DirectX 9.0c (4.09.000.0904)
ATI Radeon HD 3450 (512MB) AGP. Some of the details in DirectX or Catalyst Control Center appear to indicate it's a VisionTek. (Driver packaging 8.723-1004069-099558E-VisionTek).
HP vs15 flat panel.
Have tried "force verify." No joy.
Tried deleting PIGGs & HOGGs & horses. (oh myyyy!) And making STO re-patch 12GB, with no joy.
Now a friend is remote assisting me.
We copied the old .log files, and re-nameed them so they'd get recreated the next time there was a crash. Strangely, only 2 out of the 4 got recreated. Debug.log & Clientservercomm.log. But Crash.log & error.log were NOT recreated durign the crash. Is that normal? Seems odd, given, y'know, the "crash," that crash.log wouldn't be recreated.
clinetservercomm.log:
"131116 05:01:14 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7001"
debug.log:
[1115/215809:WARNING:dns_config_service_win.cc(520)] Failed to read DnsHosts.
[1115/215840:INFO:CONSOLE(0)] "Select shard: 0," source: http://launcher.startrekonline.com/static/all/js/api.js(96)
Not sure whether those are specific to the CRASH, or just generic errors?
As to the crash itself, launcher works fine. It updates. I close it, re-open it. Launcher patch seemed to take. Patched client. Clicked engage. It gets through the loading screen with the Legacy of Romulus logo, then right before the character selection screen would come up, it crashes to desktop with no error message, just a box asking what happened. That's what I'D LIKE TO KNOW!
Any thoughts?
131106 23:02:20 62 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 01:35:20 22 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 05:12:51 18 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 06:40:56 89 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 11:24:18 54 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131107 22:15:01 88 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131108 04:23:56 149 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 01:55:13 47 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 04:08:03 24 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 06:16:14 18 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 11:50:28 74 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131109 22:19:02 15 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131110 04:27:13 48 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131110 10:20:37 33 Client[0 P[4401876@4969180 James Redding@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131110 22:43:53 33 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131111 04:07:06 93 Client[0 P[2982071@4969180 Arwen Liadrin@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131111 11:02:49 64 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131112 00:08:16 69 Client[0 P[2819331@4969180 Douglas Everton@everton2003]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
131113 23:50:48 14 Client[0 [NOENT]]: GSM_Quit(). Reason: emEditorMain or utilitiesLibShouldQuit()
Not sure whether those are related to this issue. Perhaps? Or somethign else?
In the old clientservercomm.log, there's a lot of this kind of stuff:
131111 23:59:24 61 Client[0 [NOENT]]: GameServer link connected (208.95.186.43:7266).
131112 00:04:49 62 Client[0 [NOENT]]: GameServer link being forcibly disconnected by client (208.95.186.43:7266): Entered gclLogin
131112 00:04:49 63 Client[0 [NOENT]]: GameServer link disconnected (208.95.186.43:7266). Reason: Entered gclLogin(997:Unknown socket error) (socket error 997: Unknown socket error)
131112 00:04:50 64 Client[0 [NOENT]]: ChatRelay link disconnected (208.95.186.12:7403). Reason: socket was shutdown(10054:Connection reset by remote host) (socket error 10054: Connection reset by remote host)
131112 00:04:53 65 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7422
131112 00:05:43 66 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.12:7422). Reason: socket was shutdown(0:No error) (socket error 0: No error)
131112 00:05:43 67 Client[0 [NOENT]]: GameServer link attempting connect (208.95.186.45:7219).
131112 00:05:44 68 Client[0 [NOENT]]: GameServer link connected (208.95.186.45:7219).
131112 22:29:19 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131112 22:29:19 15 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.11:7422). Reason: gclLoginFail(0:No error) (socket error 0: No error)
131112 22:31:19 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131112 22:32:56 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7422
131112 22:51:12 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7001
131113 01:33:12 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7001
131113 02:03:04 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7001
131113 05:20:14 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7422
131113 12:29:04 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7001
131113 12:29:05 15 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.13:7001). Reason: gclLoginFail(0:No error) (socket error 0: No error)
131113 12:47:29 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131113 23:54:16 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.184.129:7001
131114 02:54:44 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.13:7001
131114 08:11:00 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131114 19:09:12 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.12:7422
131115 09:42:57 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.32:7422
131115 16:21:59 14 Client[0 [NOENT]]: LoginServer link attempting connect: 208.95.186.11:7422
131115 16:22:00 15 Client[0 [NOENT]]: LoginServer link disconnected (208.95.186.11:7422). Reason: gclLoginFail(0:No error) (socket error 0: No error)
Don't know if that's germane or not. May or may not indicate a connectivity issue?
Are others getting these same kinds of error messages in their logs...?
[1115/221727:ERROR:backend_impl.cc(2083)] Corrupt Index file
[1115/221727:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[1115/221727:ERROR:backend_impl.cc(134)] Unable to move cache folder C:\Program Files\Perfect World Entertainment\Star Trek Online_en\cef_cache to C:\Program Files\Perfect World Entertainment\Star Trek Online_en\old_cef_cache_000
[1115/221727:ERROR:backend_impl.cc(221)] Unable to create cache
[1115/221815:ERROR:backend_impl.cc(2083)] Corrupt Index file
[1115/221815:ERROR:cache_util_win.cc(43)] Unable to move the cache: 0
[1115/221815:ERROR:backend_impl.cc(134)] Unable to move cache folder C:\Program Files\Perfect World Entertainment\Star Trek Online_en\cef_cache to C:\Program Files\Perfect World Entertainment\Star Trek Online_en\old_cef_cache_000
[1115/221815:ERROR:backend_impl.cc(221)] Unable to create cache
[1115/221825:INFO:CONSOLE(0)] "Select shard: 0," source: http://launcher.startrekonline.com/static/all/js/api.js(96)
My system is WinXp pro SP3
AMD athlon 64 3800+
2.40Ghz 1.5gb ram
Nvidia 9400gt
Hmm...your's looks like mine. Same error message number (188 whatever) by chance?
Everyone, check the files msot recent (as in the last four days) in the Star Trek Online Logs folder...let's see what we got going on here?
This looks like my version of the file. Maybe a key to solving the problem for the Dev Team helping us lies in what ever is similar between the files. Namely let's stick to people who have not had the same Ticket Number as me or this guy.
Having nothing better to do, I loaded up my STO client to try again to get into game. First thing I notice is my launcher gets a patch, this is before it loads the log-in screen. So, just curious, was I the only one to get this launcher patch? What got changed this time? Could this all be because of a glitch in the launcher coding?
As of while I'm typing this, got the last game patch being applied....soo...fingers crossed.
If it is what I think it is...nope. I got it as well.
EDIT: *Picks jaw up off floor.*
Am now on character select screen.
EDIT #2: Am now in-game in my ship. Earlier, someone posted about getting this far and not being able to do anything....*still has fingers crossed.*
Ours patched as well. But the patch seemed to go fine for the LAUNCHER. But, in our case it's the GAME CLIENT that crashes, not the launcher. So, to me at least, that seems to rule out a launcher issue? Dunno. Something about whatever goes on RIGHT BEFORE hitting the character selection screen. As that seems to be right when the crashing is happening, consistently...
Before, it was ONLY doing it on Tribble, but NOT on Holodeck. Now it's doing it both places (after Season 8 rolled out). So, pretty clearly something changed on the Tribble version, and that change then propagated when it rolled out live to Holodeck.
I'm helping out my friend Everton2003 remotely. I'm hoping that we can, by getting specs & log file reports maybe narrow down what's up. Interesting that someone else was running XP SP3 on an Athlon 64, as that's what my friend is running (different GHz, but same basic architecture). May be nothing? Dunno. Don't know if there's any weird issue with XP 32-bit OS running on Athlon 64-bit processor? One would hope not... But y'never know. Just a "left field" "logical leap." I'm sure others with different setups will probably rule out that theory?
~MG
meanwhile back at cryptic someone gets upset
This is from the ClientServercomm file. Looking for Debug File