Shoutbox

Problem With .net Passport :( Error #81000303 - Printable Version

-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Skype & Technology (/forumdisplay.php?fid=9)
+---- Forum: Skype & Live Messenger (/forumdisplay.php?fid=10)
+----- Thread: Problem With .net Passport :( Error #81000303 (/showthread.php?tid=35554)

Problem With .net Passport :( Error #81000303 by banky on 12-12-2004 at 11:07 PM

Ok today I was useing my .net passport to sign into msn messenger but then when I signed out to clean up my room and house. I came back about 30 or so mins later wich is now and when trying to login it gives me this.

We could not sign you in to MSN messenger because there is a problem with your passport.

Click ok to learn more at the .Net Passport Web Site.  81000303.

ok thats the error then when I click ok I get this.

Microsoft® .NET Passport was temporarily unable to complete your request. Please try again later.


Any help would be appericated.


RE: Problem With .net Passport :( Error #81000303 by Ash_ on 12-13-2004 at 02:51 AM

yeah i had this problem about 20 mins ago but it looks alright now. maybe try again now?


RE: Problem With .net Passport :( Error #81000303 by Hank on 12-13-2004 at 02:56 AM


MSN Messenger Sign-in Problems

MSN Messenger users using non @hotmail.com/@msn.com email address's for their MSN Messenger logins maybe experiencing problems with the service this evening. The common error message is :

We could not sign you in to MSN Messenger because there is a problem with your .NET Passport. Click OK to learn more at the .NET Passport Web site. 81000303. Clicking ok results in another error message, Microsoft® .NET Passport was temporarily unable to complete your request. Please try again later. Although the messenger status page hasn't been updated to reflect this problem we've spoken to sources close to MSN Support who have confirmed outage for many customers.

Update: Microsoft have confirmed this is a problem with the .NET Passport Service rather than the MSN Messenger Service, engineers are currently working on a solution.


RE: Problem With .net Passport :( Error #81000303 by RaceProUK on 12-13-2004 at 12:33 PM

Quoted from www.mess.be by any chance? :P


RE: Problem With .net Passport :( Error #81000303 by Underlord on 12-13-2004 at 12:46 PM

It is originally from Neowin :).


RE: Problem With .net Passport :( Error #81000303 by Pr0xY on 12-13-2004 at 01:09 PM

quote:
Originally posted by raceprouk
Quoted from www.mess.be by any chance? :P
quote:
Originally posted by Underlord
It is originally from Neowin :).

Nope... it actually came from here...
http://messenger.msn.com/Status.aspx

Thats where mess.be and Neowin find out this kind of stuff. 


RE: Problem With .net Passport :( Error #81000303 by Hank on 12-13-2004 at 01:11 PM

quote:
Originally posted by Pr0xY
quote:
Originally posted by raceprouk
Quoted from www.mess.be by any chance? :P
quote:
Originally posted by Underlord
It is originally from Neowin :).

Nope... it actually came from here...
http://messenger.msn.com/Status.aspx

Thats where mess.be and Neowin find out this kind of stuff.

  true Pr0x, but i originally got it from Neowin :)
RE: Problem With .net Passport :( Error #81000303 by Pr0xY on 12-13-2004 at 05:20 PM

quote:
Originally posted by Demandred
quote:
Originally posted by Pr0xY
quote:
Originally posted by raceprouk
Quoted from www.mess.be by any chance? :P
quote:
Originally posted by Underlord
It is originally from Neowin :).

Nope... it actually came from here...
http://messenger.msn.com/Status.aspx

Thats where mess.be and Neowin find out this kind of stuff.

  true Pr0x, but i originally got it from Neowin :)
O_o umm alright, thats cool.  I never said you didn't, I thought I would just inform people of where they can go if mess.be or neowin does not have info about a sign in problem. 

RE: Problem With .net Passport :( Error #81000303 by kangie on 12-14-2004 at 04:08 AM

ummm... well i was helping a couple of million people witht this the other day, and there is no solution other than to just wait till its fixed by mircosoft...