Chronicle of events:
-
Error formally confirmed
-
The issue has been fully resolved.
We are aware of an issue that is causing some users to be unable to send/receive messages and see presence of contacts. Our engineers are actively investigating the issue and we hope to resolve it as soon as possible.
10 comments
+5), #+1214), # ↑+5), # ↑+1214), # ↑+5), # ↑MSNP: Connection Data (MSNP24):* Status: NetStateConnected
* Server Current: db5-s.gateway.messenger.live.com
* Server Saved: db5-s.gateway.messenger.live.com
* Login: (Don't want to show it here) (Token) IMPL: 0 PMN_SET
* Login State: CUR:0 LAST:0 LEND:0 ERRC:0
* Skypename: (Don't want to show it here) [linked]
* EPID: 0becdad3-ae7b-0840-4a3f-8d56eba10738
* ClientVersion: 0/7.40.0.103//
* OSVersion: Windows 6.3 (build
* Time: TZ: UTC+1, Server: 1504269894, Local: 1504269922
* Connection: IF: 0 DC: 0 RC: direct
* B:0 CS:[B:1 S:1] MO:yes CWB:1 Q:0[F:0 I:0] PMN:ATH
* Recent connect: db5-s.gateway.messenger.live.com @ 2017-09-01T12:30:16Z
* Recent connect: db5-s.gateway.messenger.live.com @ 2017-09-01T10:54:27Z
* Recent connect: db5-s.gateway.messenger.live.com @ 2017-09-01T10:50:13Z
* Recent connect: db5-s.gateway.messenger.live.com @ 2017-08-31T23:51:26Z
* Recent connect: db5-s.gateway.messenger.live.com @ 2017-08-31T23:41:53Z
* Push: None (Unregistered)
* Build conf: RELEASE
* CLC: cc9e3d6110a4f3b41bf4f300c4b75d55a8743c08
* CL: 64e33b8c6a326a5c44db051c538cad359bbc8c8a
* ML: 499671deea5bab8f2a60e4cde42f06cca5081f53
* CoreLib: releases/CL2017.R15 @ 124be529ca72960084742c42495b3953271e4b79
(I cut out my login and skype name)
[Updated ]
i accidentally posted it in a new post, sorry. Did I send the correct information
+1214), # ↑If this did not help, open file
%appdata%\Skype\skype_login\config.xmland copy here all information between<MSNPCore></MSNPCore>tags.+5), # ↑<MSNPCore><AgentsSupportRequested>1</AgentsSupportRequested>
<AnnotationsSupportRequested>1</AnnotationsSupportRequested>
<HighlightsSupportRequested>0</HighlightsSupportRequested>
<HomeServer>db5-s.gateway.messenger.live.com</HomeServer>
<P2PMigrationAllowed>0</P2PMigrationAllowed>
<ReactionThreadsSupportRequested>1</ReactionThreadsSupportRequested>
<ReadReceiptsSupportRequested>0</ReadReceiptsSupportRequested>
<RecentConnectionInfo>***</RecentConnectionInfo>
<RecentConversationsSyncState>***</RecentConversationsSyncState>
</MSNPCore>
+1214), # ↑<MSNPCore>and select information before</MSNPCore>). Anyway, please do not worry; I never use the information for malicious purposes.About your issue. As I understand updating time does not fixed it? Is so it seems it occurs because your account does not use the MSNP24 protocol. To activate it, execute /msnp24 command (you should receive the “Restart and be a happy MSNP24 user” message) and restart Skype. Even if this did not solve the issue, execute the following commands one by one then restart Skype:
/setupkey Lib/MSNPCore/HomeServer s.gateway.messenger.live.com/setupkey Lib/MSNPCore/PrimaryServer s.gateway.messenger.live.com/setupkey Lib/MSNPCore/ProtocolToUse 24Please let me know if it solved your issue.
+5), # ↑[Updated ]
I have also completly re-installed skype from scratch (deleteing all skype files on my comp). Will I have to redo all this?
[Updated ]
(UPDATE on the issue)
So I set my online status to Online instead or away like it normaly is, and so far it has yet to give me the errors. Did I accidentally fix it? In my mind it makes sense since when they bring out the new skype, you'll only ever be either online or offline so maybe my away symbol was messing with things...? I'm not sure...it may just be a coincidence and still break.
What do you think...?
[Updated ]
Disregard all my messages, it still happens. It only fixes when i close skype and then re-open it. Do you have any suggestions?
+1214), # ↑If this is a global problem, they will certainly fix it in the coming days. In any case, try to contact Skype support.