Game Issues (access, TP, Gem Store) 10-03/04 [merged]

[BakBakaa.2453]

Just wanted to update you guys on some changes. This morning, everything seems to be working fine, thus far. I am in game and playing story missions, map changes seem to be working and no disconnects yet (knock on elder wood logs). Will report back if anything changes.

[Gaile Gray.6029]

Thanks for the update, BakBakaa. I will pass that along to the server team!

[pema.7834]

Here is the result of my trace report from command prompt:

 

```

Tracing route to 64.25.38-51.ncsoft.com [64.25.38.51]

over a maximum of 30 hops:

 

1 1 ms <1 ms 1 ms www.routerlogin.com [192.168.1.1]

2 10 ms 9 ms 8 ms 96.120.102.233

3 9 ms 9 ms 16 ms po-117-rur102.bellevue.wa.seattle.comcast.net [68.87.206.141]

4 11 ms 9 ms 11 ms 69.139.164.77

5 * * * Request timed out.

6 * * * Request timed out.

7 50 ms 62 ms 49 ms 4.59.197.34

8 48 ms 50 ms 49 ms 64.25.32-9.ncsoft.com [64.25.32.9]

9 48 ms 48 ms 50 ms 64.25.32-26.ncsoft.com [64.25.32.26]

10 51 ms 51 ms 51 ms 64.25.32-82.ncsoft.com [64.25.32.82]

11 49 ms 49 ms 52 ms 64.25.38-51.ncsoft.com [64.25.38.51]

 

Trace complete.

```

 

And the diagnostic result from -diag:

 

```

ArenaNet diagnostic utility [82762]

 

Windows version: 6.2

Build 9200

 

 

Section completed in 0.00 seconds

 

 

==============================================================================

= Gathering adapter settings

==============================================================================

*--> ipconfig /all <--*

 

Windows IP Configuration

 

Host Name . . . . . . . . . . . . : DESKTOP-N7Q83GO

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

 

Wireless LAN adapter Local Area Connection* 10:

 

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter

Physical Address. . . . . . . . . : BA-E8-56-2D-CD-F2

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

 

Wireless LAN adapter Wi-Fi:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Broadcom 802.11ac Network Adapter

Physical Address. . . . . . . . . : B8-E8-56-2D-CD-F2

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::3843:e411:c32f:6f4c%6(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.20(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Tuesday, October 3, 2017 10:28:59 PM

Lease Expires . . . . . . . . . . : Thursday, October 5, 2017 8:50:54 AM

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DHCPv6 IAID . . . . . . . . . . . : 146335830

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-FA-21-60-B8-E8-56-2D-CD-F2

DNS Servers . . . . . . . . . . . : 192.168.1.1

NetBIOS over Tcpip. . . . . . . . : Enabled

 

Ethernet adapter Bluetooth Network Connection:

 

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)

Physical Address. . . . . . . . . : B8-E8-56-2D-CD-F3

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter Local Area Connection* 11:

 

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:14ca:cd5:3f57:feeb(Preferred)

Link-local IPv6 Address . . . . . : fe80::14ca:cd5:3f57:feeb%2(Preferred)

Default Gateway . . . . . . . . . : ::

DHCPv6 IAID . . . . . . . . . . . : 33554432

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-FA-21-60-B8-E8-56-2D-CD-F2

NetBIOS over Tcpip. . . . . . . . : Disabled

Section completed in 0.08 seconds

 

 

==============================================================================

= Detecting network connections

==============================================================================

*--> netstat -n <--*

 

Active Connections

 

Proto Local Address Foreign Address State

TCP 192.168.1.20:61539 65.52.108.222:443 ESTABLISHED

TCP 192.168.1.20:61542 108.177.98.188:5228 ESTABLISHED

TCP 192.168.1.20:61578 216.58.216.165:443 ESTABLISHED

TCP 192.168.1.20:61588 151.101.53.140:443 ESTABLISHED

TCP 192.168.1.20:61589 151.101.1.140:443 ESTABLISHED

TCP 192.168.1.20:61590 151.101.53.140:443 ESTABLISHED

TCP 192.168.1.20:61762 199.96.57.6:443 ESTABLISHED

TCP 192.168.1.20:61798 198.183.167.119:443 TIME_WAIT

TCP 192.168.1.20:61801 104.16.136.245:443 ESTABLISHED

TCP 192.168.1.20:61802 104.16.135.249:443 ESTABLISHED

TCP 192.168.1.20:61808 104.19.193.102:443 ESTABLISHED

TCP 192.168.1.20:61863 172.217.3.195:443 ESTABLISHED

TCP 192.168.1.20:61868 216.58.216.174:443 ESTABLISHED

TCP 192.168.1.20:61869 104.31.74.54:443 ESTABLISHED

TCP 192.168.1.20:61871 192.0.77.2:443 ESTABLISHED

TCP 192.168.1.20:61872 52.84.16.235:443 ESTABLISHED

TCP 192.168.1.20:61873 52.84.16.235:443 ESTABLISHED

TCP 192.168.1.20:61875 64.4.54.253:443 TIME_WAIT

TCP 192.168.1.20:61885 52.84.25.227:443 ESTABLISHED

TCP 192.168.1.20:61886 64.25.40.51:443 ESTABLISHED

TCP 192.168.1.20:61889 52.84.16.166:443 ESTABLISHED

TCP 192.168.1.20:61890 52.84.16.140:443 ESTABLISHED

TCP 192.168.1.20:61891 52.84.16.166:443 ESTABLISHED

TCP 192.168.1.20:61893 13.107.21.200:443 ESTABLISHED

TCP 192.168.1.20:61899 104.154.127.47:80 TIME_WAIT

TCP 192.168.1.20:61900 104.154.127.50:4070 ESTABLISHED

TCP 192.168.1.20:61911 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61912 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61913 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61914 172.217.3.194:443 ESTABLISHED

TCP 192.168.1.20:61915 172.217.3.162:443 ESTABLISHED

TCP 192.168.1.20:61916 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61917 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61918 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61919 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61920 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61921 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61922 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61923 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61924 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61925 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61926 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61927 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61928 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61929 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61930 151.101.52.246:443 ESTABLISHED

TCP 192.168.1.20:61931 172.217.3.193:443 ESTABLISHED

TCP 192.168.1.20:61932 151.101.52.246:80 ESTABLISHED

TCP 192.168.1.20:61933 151.101.52.249:443 ESTABLISHED

TCP 192.168.1.20:61934 151.101.52.249:443 ESTABLISHED

TCP 192.168.1.20:61935 23.32.46.16:80 ESTABLISHED

TCP 192.168.1.20:61936 151.101.52.249:443 ESTABLISHED

TCP 192.168.1.20:61937 151.101.52.249:443 ESTABLISHED

TCP 192.168.1.20:61938 151.101.52.249:443 ESTABLISHED

TCP 192.168.1.20:61939 151.101.52.249:443 ESTABLISHED

TCP 192.168.1.20:61940 216.58.216.174:443 ESTABLISHED

TCP 192.168.1.20:61952 151.101.52.193:443 ESTABLISHED

TCP 192.168.1.20:61953 151.101.40.193:443 ESTABLISHED

TCP 192.168.1.20:61955 151.101.52.193:443 ESTABLISHED

TCP 192.168.1.20:61956 216.58.216.163:443 ESTABLISHED

TCP 192.168.1.20:61959 54.83.156.61:80 ESTABLISHED

TCP 192.168.1.20:61960 52.206.103.170:443 ESTABLISHED

Section completed in 0.06 seconds

 

 

==============================================================================

= Discovering external address

==============================================================================

Current IP Address: 24.18.160.215

 

Section completed in 0.41 seconds

 

 

==============================================================================

= Checking server connectivity

==============================================================================

Section completed in 0.00 seconds

 

Diag.ArenaNetworks.com

64.25.38.172:80 - connect succeeded

64.25.38.51:80 - connect succeeded

64.25.38.172:6112 - connect succeeded

64.25.38.171:80 - connect succeeded

64.25.38.171:6112 - connect succeeded

64.25.38.185:80 - connect succeeded

64.25.38.54:80 - connect succeeded

64.25.38.54:6112 - connect succeeded

64.25.38.51:6112 - connect succeeded

64.25.38.185:6112 - connect succeeded

 

Section completed in 0.09 seconds

 

assetcdn.101.ArenaNetworks.com.

52.84.25.96:80 - connect succeeded

52.84.25.122:80 - connect succeeded

52.84.25.180:80 - connect succeeded

52.84.25.151:80 - connect succeeded

52.84.25.215:80 - connect succeeded

52.84.25.238:80 - connect succeeded

52.84.25.137:80 - connect succeeded

52.84.25.14:80 - connect succeeded

 

Section completed in 0.05 seconds

 

auth1.101.ArenaNetworks.com.

64.25.38.172:6112 - connect succeeded

64.25.38.51:6112 - connect succeeded

64.25.38.54:6112 - connect succeeded

64.25.38.185:6112 - connect succeeded

64.25.38.171:6112 - connect succeeded

 

Section completed in 0.06 seconds

 

auth2.101.ArenaNetworks.com.

206.127.159.109:6112 - connect succeeded

206.127.159.107:6112 - connect succeeded

206.127.146.74:6112 - connect succeeded

206.127.146.67:6112 - connect succeeded

206.127.146.73:6112 - connect succeeded

 

Section completed in 0.20 seconds

 

cligate.101.NCPlatform.net.

64.25.40.115:6112 - connect succeeded

64.25.40.114:6112 - connect succeeded

64.25.40.112:6112 - connect succeeded

64.25.40.110:6112 - connect succeeded

64.25.40.113:6112 - connect succeeded

64.25.40.122:6112 - connect succeeded

64.25.40.123:6112 - connect succeeded

 

Section completed in 0.08 seconds

 

 

==============================================================================

= Tracing network paths (about 10 mins)

==============================================================================

*--> pathping -w 500 -q 50 -4 64.25.39.1 <--*

 

Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1]

over a maximum of 30 hops:

0 DESKTOP-N7Q83GO [192.168.1.20]

1 www.routerlogin.com [192.168.1.1]

2 96.120.102.233

3 po-117-rur101.bellevue.wa.seattle.comcast.net [68.86.113.149]

4 po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]

5 69.139.164.77

6 * * *

Computing statistics for 62 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 DESKTOP-N7Q83GO [192.168.1.20]

0/ 50 = 0% |

1 0ms 0/ 50 = 0% 0/ 50 = 0% www.routerlogin.com [192.168.1.1]

1/ 50 = 2% |

2 9ms 2/ 50 = 4% 1/ 50 = 2% 96.120.102.233

0/ 50 = 0% |

3 9ms 1/ 50 = 2% 0/ 50 = 0% po-117-rur101.bellevue.wa.seattle.comcast.net [68.86.113.149]

0/ 50 = 0% |

4 9ms 1/ 50 = 2% 0/ 50 = 0% po-2-rur102.bellevue.wa.seattle.comcast.net [69.139.160.26]

0/ 50 = 0% |

5 11ms 1/ 50 = 2% 0/ 50 = 0% 69.139.164.77

 

Trace complete.

*--> pathping -w 500 -q 50 -4 206.127.158.1 <--*

 

Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1]

over a maximum of 30 hops:

0 DESKTOP-N7Q83GO [192.168.1.20]

1 www.routerlogin.com [192.168.1.1]

2 96.120.102.233

3 po-117-rur102.bellevue.wa.seattle.comcast.net [68.87.206.141]

4 69.139.164.77

5 * * *

Computing statistics for 50 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 DESKTOP-N7Q83GO [192.168.1.20]

0/ 50 = 0% |

1 1ms 0/ 50 = 0% 0/ 50 = 0% www.routerlogin.com [192.168.1.1]

0/ 50 = 0% |

2 9ms 0/ 50 = 0% 0/ 50 = 0% 96.120.102.233

0/ 50 = 0% |

3 9ms 0/ 50 = 0% 0/ 50 = 0% po-117-rur102.bellevue.wa.seattle.comcast.net [68.87.206.141]

50/ 50 =100% |

4 --- 50/ 50 =100% 0/ 50 = 0% 69.139.164.77

 

Trace complete.

*--> pathping -w 500 -q 50 -4 52.84.25.122 <--*

 

Tracing route to server-52-84-25-122.sea32.r.cloudfront.net [52.84.25.122]

over a maximum of 30 hops:

0 DESKTOP-N7Q83GO [192.168.1.20]

1 www.routerlogin.com [192.168.1.1]

2 96.120.102.233

3 po-117-rur102.bellevue.wa.seattle.comcast.net [68.87.206.141]

4 69.139.164.77

5 be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]

6 be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]

7 50.248.116.34

8 * * *

Computing statistics for 87 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 DESKTOP-N7Q83GO [192.168.1.20]

0/ 50 = 0% |

1 1ms 1/ 50 = 2% 1/ 50 = 2% www.routerlogin.com [192.168.1.1]

0/ 50 = 0% |

2 12ms 0/ 50 = 0% 0/ 50 = 0% 96.120.102.233

1/ 50 = 2% |

3 11ms 1/ 50 = 2% 0/ 50 = 0% po-117-rur102.bellevue.wa.seattle.comcast.net [68.87.206.141]

0/ 50 = 0% |

4 11ms 2/ 50 = 4% 1/ 50 = 2% 69.139.164.77

0/ 50 = 0% |

5 14ms 1/ 50 = 2% 0/ 50 = 0% be-33650-cr01.seattle.wa.ibone.comcast.net [68.86.93.165]

0/ 50 = 0% |

6 12ms 1/ 50 = 2% 0/ 50 = 0% be-10847-pe02.seattle.wa.ibone.comcast.net [68.86.86.226]

1/ 50 = 2% |

7 13ms 2/ 50 = 4% 0/ 50 = 0% 50.248.116.34

 

Trace complete.

Section completed in 201.89 seconds

```

[BakBakaa.2453]

Seems my last report was a bit premature. Since my last post I played through three story missions and then got hung up loading into Timberline Falls with a disconnect soon to follow. Here are the details of this recent crash:

 

> Error: The game client lost its connection to the server. Please wait a few minutes before restarting the client and trying again.

> Error Code: 7:0:0:1026:101

 

Trace Route just after crashing:

> Tracing route to 64.25.38-51.ncsoft.com [64.25.38.51] over a maximum of 30 hops:

> 1 3 ms 2 ms 3 ms router.asus.com [192.168.1.1]

> 2 10 ms 10 ms 10 ms 96.120.14.53

> 3 10 ms 18 ms 20 ms ae-204-sur01.chico.ca.ccal.comcast.net [69.139.197.197]

> 4 18 ms 22 ms 13 ms ae-5-ar01.sacramento.ca.ccal.comcast.net [68.85.196.165]

> 5 * * * Request timed out.

> 6 * * * Request timed out.

> 7 60 ms 63 ms 63 ms 4.59.197.34

> 8 56 ms 55 ms 58 ms 64.25.32-9.ncsoft.com [64.25.32.9]

> 9 56 ms 57 ms 60 ms 64.25.32-26.ncsoft.com [64.25.32.26]

> 10 63 ms 58 ms 160 ms 64.25.32-82.ncsoft.com [64.25.32.82]

> 11 58 ms 58 ms 56 ms 64.25.38-51.ncsoft.com [64.25.38.51]

> Trace complete.

 

Was able to successfully reconnect to server after game crashed, log in, but upon selecting the same character I crashed with received a another error message. Here are the details of that message:

 

> Error: The game client lost its connection to the server. Please wait a few minutes before restarting the client and trying again.

> Error Code: 7:11:3:191:101

 

Decided to log in with a different character after this crash. Was able to connect to server, log in, and play that character without issues. Ported to the Frostland way-point I was having issues with on the first character and was able to traverse to the new map without issue. This got me thinking. I then logged out to the character select screen, loaded up the original character that received the error and tried to walk across the map load barrier and was again stuck at another waiting screen followed by a disconnect. Here are the details of that error:

 

> Error: The game client lost its connection to the server. Please wait a few minutes before restarting the client and trying again.

> Error Code: 7:0:0:1026:101

 

Upon loading the game back up I was again unable to get passed the log-in screen (same issue as yesterday). It simply attempts to connect and after a wait of about 2 - 3 minutes presents an error:

 

> Error: The game client was unable to connect to the log-in server. Please restart your client and try again. If the problem persists, contact Customer Support for assistance at http://support.guildwars2.com.

> Build: 82762

> Error Code: 58:11:5:535

 

Trace Route just after crashing the second time:

> Tracing route to 64.25.38-51.ncsoft.com [64.25.38.51] over a maximum of 30 hops:

> 1 7 ms 10 ms 9 ms router.asus.com [192.168.1.1]

> 2 12 ms 10 ms 15 ms 96.120.14.53

> 3 10 ms 12 ms 16 ms ae-204-sur01.chico.ca.ccal.comcast.net [69.139.197.197]

> 4 13 ms 18 ms 19 ms ae-5-ar01.sacramento.ca.ccal.comcast.net [68.85.196.165]

> 5 * * * Request timed out.

> 6 * * * Request timed out.

> 7 59 ms 56 ms 59 ms 4.59.197.34

> 8 59 ms 56 ms 56 ms 64.25.32-9.ncsoft.com [64.25.32.9]

> 9 55 ms 55 ms 62 ms 64.25.32-26.ncsoft.com [64.25.32.26]

> 10 58 ms 57 ms 64 ms 64.25.32-82.ncsoft.com [64.25.32.82]

> 11 56 ms 56 ms 57 ms 64.25.38-51.ncsoft.com [64.25.38.51]

> Trace complete.

 

If I remember right, I was having this issue when loading into one of the maps that contained a story way-point before as well (on another character the day before yesterday). I know the sample size is too small for any real conclusion, but could it be tied to story events or map loads into story areas periodically? Each character became stuck at a loading screen after attempting to go to load into a map where the next story objective was placed (different story objectives, different expansions, different characters, different maps each time).

 

Hope this helps you guys/gals.

 

 

EDIT to add log after unsuccessful reconnect attempt:

> 00000734: Perf: Build 82762

> 00000734: Perf: 2017-10-05T18:31:42Z

> 00000734: Perf: Platform 1

> 00000750: Perf: Archive has version 1 header

> 00001069: Perf: Archive has version 1 header

> 00002597: Perf: Deleted 0 old files.

> 00002678: Debug: WebBrowser: Skipping file CoherentUI_Host.exe

> 00002678: Debug: WebBrowser: Skipping file CoherentUI64.dll

> 00003361: Debug: Coherent Warning: PID: 9956 | 10400 18:31:44.634904 [9956:10400:ERROR:resource_bundle.cc(528)] Failed to load C:\Program Files\Guild Wars 2\bin64\ui_resources_100_percent.pak

> Some features may not be available.

> 00003361: Debug: Coherent Warning: PID: 9956 | 10400 18:31:44.635907 [9956:10400:WARNING:resource_bundle.cc(252)] locale_file_path.empty()

> 00004303: Debug: Coherent Warning: PID: 9956 | 6996 18:31:45.679182 [3384:10476:ERROR:resource_bundle.cc(528)] Failed to load C:\Program Files\Guild Wars 2\bin64\ui_resources_100_percent.pak

> Some features may not be available.

> 00004303: Debug: Coherent Warning: PID: 9956 | 6996 18:31:45.679182 [3384:10476:WARNING:resource_bundle.cc(252)] locale_file_path.empty()

> 00004478: Debug: Web Message (launcher.js:2): onShowLauncher

> 00004478: Debug: Web Message (launcher.js:2): onSetPreferences

> 00004478: Debug: Web Message (launcher.js:2): onSetLanguage

> 00004528: Debug: Web Message (launcher.js:2): onPasswordHash

> 00004653: Debug: Web Message (launcher.js:2): onDownloadComplete

> 00076915: Debug: Web Message (launcher.js:2): onLoginError

> 00119982: Perf: Counter; 30d.1m.socket inet msgs processed; 3

> 00119982: Perf: Counter; 30d.1m.socket inet msgs processed (ms); 2

> 00119982: Perf: Counter; 30d.1m.socket inet msgs sent; 6

> 00119982: Perf: Counter; 30d.1m.transactions (peak); 1

> 00119982: Perf: Counter; 30d.1m.transactions (total); 3

 

 

Edit #2:

Oddly enough, an IPCONFIG -release and IPCONFIG -renew seems to get me back into the game after issues with the login screen. It doesn't solve the disconnect issues though.

[Katiekaboom.1980]

Gaile is the human story where you choose Hospital or Orphanage bugged or disabled? For 3 days now I have not been able to do my story because I chose Hospital and the door is bugged. I keep trying to do it every day since there is no way to tell Logan Thackeray that I change my mind and want to do Orphanage instead... The door breaks but it is like the door isn't broken because as if an invisible door still remains you cannot attack the enemies and you cannot enter the Hospital to complete the instance. You can't go in because it is like you are running into the door as if it is still closed. I went today to do Kryta Miner in my home just to be reminded that I can't even do that because to go into my home it wants me to do the Story Instance. :( So I thought I would ask is it disabled or bugged and is it known when it will be working again?

 


 

[Azraehl.4156]

> @ZeroHour.2418 said:

> Got Kicked out from game. Managed to log back in again, but could not get past character select screen. Happened twice. Now can't even log into client.

>

> Looks like the log in server is broken again.

 

Yes it's the same for me too :( Cannot get past charcter screen. Tried several times but I get kicked back to login screen every time.

[Azraehl.4156]

> @Azraehl.4156 said:

> > @ZeroHour.2418 said:

> > Got Kicked out from game. Managed to log back in again, but could not get past character select screen. Happened twice. Now can't even log into client.

> >

> > Looks like the log in server is broken again.

>

> Yes it's the same for me too :( Cannot get past charcter screen. Tried several times but I get kicked back to login screen every time.

 

However, the second after I wrote the above, I tried again, and like a miracle IT WORKED!!!! :D

[Springlz.5780]

High ping, a lot of DC

[Katiekaboom.1980]

> @Katiekaboom.1980 said:

> Gaile is the human story where you choose Hospital or Orphanage bugged or disabled? For 3 days now I have not been able to do my story because I chose Hospital and the door is bugged. I keep trying to do it every day since there is no way to tell Logan Thackeray that I change my mind and want to do Orphanage instead... The door breaks but it is like the door isn't broken because as if an invisible door still remains you cannot attack the enemies and you cannot enter the Hospital to complete the instance. You can't go in because it is like you are running into the door as if it is still closed. I went today to do Kryta Miner in my home just to be reminded that I can't even do that because to go into my home it wants me to do the Story Instance. :( So I thought I would ask is it disabled or bugged and is it known when it will be working again?

>

> 

>

 

Still cannot do story. So I checked to see if this issue is being looked into or is even known .. and I found out it is:

 

[Known Issue Tracker ](https://help.guildwars2.com/hc/en-us/articles/231272908?input_string=cannot+complete+level+10+human+story "Known Issue Tracker ")

 

**Divinity's Reach:** Invisible wall inside a house in the Human home instance, blocks progression to "Hospital in Jeopardy" mission.

**Status:** Investigating

[Katiekaboom.1980]

They say on reddit that the DR Hospital bug has been fixed but that is misleading. When they have a fix but have not yet implemented once again it leads players to be frustrated and feel the lack of proper communication.

 

http://uploads.im/fXa1B.png

[Katiekaboom.1980]

Here is where Anet said on Reddit that it is fixed when the fix has not YET been implemented in game. Saying it is fixed on Reddit is misleading players and only adding to the frustration. I wish Anet would not say on Reddit that it is fixed until the fix has been successfully implemented and tested for a few days by real players in live instances.