search

msndevs / msnp-sharp

Automatically exported from code.google.com/p/msnp-sharp
5 stars 2 forks source link

Authentification Exception on connect #332

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I get an authentification error right at the start. (It's not a wrong password 
MS Account. Every account affected. Worked just fine yesterday and the past 2 
years.)
This is a very important problem as my bot can't even connect to the service 
anymore.

What steps will reproduce the problem?
1. Messenger.Credentials = New MSNPSharp.Credentials(id, pw)
2. Messenger.Connect()

What is the expected output? What do you see instead?
Nameserver_AuthenticationError gets fired with exception (see below).

What version of the product are you using? (MSNPSharp, OS, Mono etc.)
MSNPSharp: newest, OS: Server 2008, .NET 4.0

Is your code clone from GIT or download from our download page?
download

Please provide any additional information below:

Exception Details of e.Exception.InnerException
System.Web.Services.Protocols.SoapException: Invalid Request
   bei System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   bei System.Web.Services.Protocols.SoapHttpClientProtocol.InvokeAsyncCallback(IAsyncResult result)

Original issue reported on code.google.com by matti_ko...@msn.com on 18 Apr 2013 at 11:24

GoogleCodeExporter commented 9 years ago 
Verified, I am checking to see if there is any solutions.

Original comment by freezing...@gmail.com on 19 Apr 2013 at 5:00

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I got this error as well in the last 18 hours. Still isn't working. Does it 
have something to do with Microsoft and Skype/MSN platform merge?

Original comment by stian.lo...@gmail.com on 19 Apr 2013 at 4:43

GoogleCodeExporter commented 9 years ago 
The Problem seems to have disappeared now. But still I hope this won't happen 
again.

Original comment by matti_ko...@msn.com on 23 Apr 2013 at 4:22

GoogleCodeExporter commented 9 years ago 
Sometimes M$ upgrade their service will cause this issue. I tried to switch 
back to the old 2.5 API lib at that time and everything works fine. Glad it 
goes...

Original comment by freezing...@gmail.com on 24 Apr 2013 at 1:17