Connecting to account server it just never connects.
Any1 else experiencing the same issue can confirm this?
Tried a few times, no problems here. It could be several items for you, including aftermarket antivirus/antispyware/application firewall or a crash you will find in your sto logs.
Gameclient.exe has a Feb 26th version now, you might have something blocking this new version.
Check my FAQ, if your logs show nothing we might need to do a packet capture to find out what is happening on your client server communication.
Also check your router logs for drops/denys to/from 208. addresses
100301 14:22:07 68 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/fmod_event_netL.dll!
100301 14:22:08 75 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/nvtt.dll!
100301 14:22:10 82 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/NxCooking.dll!
100301 14:22:07 68 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/fmod_event_netL.dll!
100301 14:22:08 75 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/nvtt.dll!
100301 14:22:10 82 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/NxCooking.dll!
Close STO completely and try deleting the file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/NxCooking.dll.
I did so on my system and when I restarted STO it was replaced automatically. Check to see if you still receive the dll error in your log file. This is a known issue for STO and CO players according to forum postings.
Note to others looking at this thread, the date stamps were off in the logs because the PC time was off by that much. That was corrected on his side.
Comments
Tried a few times, no problems here. It could be several items for you, including aftermarket antivirus/antispyware/application firewall or a crash you will find in your sto logs.
Gameclient.exe has a Feb 26th version now, you might have something blocking this new version.
Check my FAQ, if your logs show nothing we might need to do a packet capture to find out what is happening on your client server communication.
Also check your router logs for drops/denys to/from 208. addresses
http://forums.startrekonline.com/showthread.php?p=2104036#post2104036
100228 14:54:59 2 Client[0]: gServerLink disconnected
100228 15:19:06 3 Client[0]: Server Link disconnected. Reason: bytes_xferred == 0 && !link->listening in netiocp
100228 15:19:06 4 Client[0]: gServerLink disconnected
100301 14:22:08 75 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/nvtt.dll!
100301 14:22:10 82 [1] ESC : The patchclientlib is internally recording error code : 36\nA file was locked that could not be open for writing. - Unable to read back file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/NxCooking.dll!
Close STO completely and try deleting the file C:/Users/Public/Games/Cryptic Studios/Star Trek Online/Live/NxCooking.dll.
I did so on my system and when I restarted STO it was replaced automatically. Check to see if you still receive the dll error in your log file. This is a known issue for STO and CO players according to forum postings.
Note to others looking at this thread, the date stamps were off in the logs because the PC time was off by that much. That was corrected on his side.