Error: Failed to send authorization request (Account Not Found)

[Stallion Free]

ISSUE
After having my friend log into his account on my PC and add my PC to his list of authorized devices I am able to see his whole library of games when I log back into my account and install and play them (as long as the library isn't in use).

Two days in a row now Steam seems to forget that my PC is authorized forcing me to request access again (and only showing the games installed, not his entire list). Once I send the request I am always given the error: "Error: Failed to send authorization request (Account Not Found)."

If I try to check the achievement page for a game I have played on my friends shared library it throws up a community page error as well: "There was a failure loading user game stats." This is despite the actual Steam application showing achievement progress on the Detail View.

The only way we have found to fix it is to have him re-login on my PC after getting rid of the previous authorization entry and re-add my PC to the authorized devices list.


OS
Windows 7 64-bit


STEPS
-Authorize PC
-Play game from friends library
-Attempt again the following day
-Forced authorization request pop-up
-Attempt request


RESULTS
-Error: Failed to send authorization request (Account Not Found)
-Broken Achievement Steam Community page: "There was a failure loading user game stats."


EXPECTED
My friend has yet to need to send a request to reauthorize from using my library on his PC so I suspect I shouldn't be seeing this request authorization pop-up and it shouldn't always fail the authorization request if I should be seeing it.


THANKS
Hopefully I included all the necessary details. If any further information is needed I'll try to supply it. When family sharing is working it has really blown me away (the pop-up "friend's library is available again" is a really great touch).

[Scratch]

Okay, so I've been trying regularly to test to see if steam would let me play shared games.
Today I tried and it returned a message saying that 'I have access to this library already.... you're all set'

This is the second time I've had this luck in a week

I also decided to take a screencap of my familysharing settings
http://i.imgur.com/QCuQFdf.png

I think there is something out of the ordinary with the 'used by' entries

[KaziArmada]

Also having this problem on my secondary machine. No hardware changes and while it DOES have a 'virtual' adapter, from VirtualBox, it's been disabled since before the sharing function was implimented.

The other two machines in my house work fine, it's just that one machine. It's also the only 'Wireless' machine in the house, not being hard-wired into our network.

Said machine is also in the Steam Beta Client. I haven't tried having the person request authorization again, but am in the process of doing so.

Bit of an odd issue given this literally popped up out of nowhere with no hardware or software changes that I remember implementing.

Edit: Also as a note, I logged into that machine, reauthorized it..apparently it assumed it was a *different machine than I had authorized*...and the logged my girlfriend in.

Keep in mind, not a minute before real time I had authorized this machine.

Steam reports, on her account now, that it is not authorized. Checking my steamshare reports that nobody has logged into that machine.

I'm really wondering what would make steam forget it was authorized inside of a minute....

[WonderGamer]

I do not know that the virtual network allegations is at all accurate. As you can see from here, I re-authorized his computer & we immediately got the same issue.

http://steamcommunity.com/groups/familysharing/discussions/0/846964363934331891/?tscn=1384797183#c648811852578727378

[KaziArmada]

引用自 Xfire WonderGamer：

I do not know that the virtual network allegations is at all accurate. As you can see from here, I re-authorized his computer & we immediately go the same issue.

http://steamcommunity.com/groups/familysharing/discussions/0/846964363934331891/?tscn=1384797183#c648811852578727378

Yeah, same thing. Even if the Virtual Network WAS an issue..which I doubt as it's been on there in my case, and disabled, I had the same 'Instant re-authorize with no recgonition'.

I kept reauthorizing and deauthoririzng it and it stuck eveuntelly....god only knows why Steam keeps forgetting itself though...

[WonderGamer]

Seems to be working now after the update.

[Kasin]

no, after relogging in my authorization was gone. my friend has not deauthorized me and we have gone through the reauthorization progress many times now, that means requesting authorization again by pressing the library play button just gives the account not found error

[Esca]

引用自 JKX：

no, after relogging in my authorization was gone. my friend has not deauthorized me and we have gone through the reauthorization progress many times now, that means requesting authorization again by pressing the library play button just gives the account not found error

The usual problem is that authorizations become invalid if Steam thinks your hardware has changed. You probably have frequently-changing virtual hardware, an unusual operating system configuration, a built-in graphics processor with incompatible settings, or some other recurring issue.

There are several threads about this (including this one) that suggest possible solutions. Try disabling things like Hamachi or other VPN software, virtual machines, drive-freezing security software, etc.

[WonderGamer]

That wouldn't be the problem, however. An "account not found" error is a lot different than a simple de-authorization based on changed hardware.

[KaziArmada]

The other thing that makes this weird is that while the excuse..and I call it that for reasons I'll explain..is 'Steam thinks the hardware changed', following that logic you should be unable to retain your Steamguard code to use the machine.

Yet that function works fine while the Steamshare loses it's mind. Whats different between the two.

[Esca]

引用自 Xfire WonderGamer：

That wouldn't be the problem, however. An "account not found" error is a lot different than a simple de-authorization based on changed hardware.

After my authorization broke, I tried to request it again without having it removed first; it gave me the "account not found" error. It could appear for other reasons, of course, but it does apply to that bug.

引用自 KaziArmada：

The other thing that makes this weird is that while the excuse..and I call it that for reasons I'll explain..is 'Steam thinks the hardware changed', following that logic you should be unable to retain your Steamguard code to use the machine.

Yet that function works fine while the Steamshare loses it's mind. Whats different between the two.

I don't know why, but they're apparently not the same identification system, or at least not used the same way. The Valve staff member who answered early bug reports, martino, mentioned that SFS authorization has unresolved issues with virtual hardware.

[WonderGamer]

Apparently it's happening again... >.<

引用自 martino：

Are you guys in the Steam Client Beta ?

Yes, Beta client. My co-worker also opted into it when he started running into this problem.

[Cam]

Just got this issue, the other computer couldn't authorize after a GPU upgrade. Had to do the full authorization process to get them back.

[KaziArmada]

引用自 Wohlfe：

Just got this issue, the other computer couldn't authorize after a GPU upgrade. Had to do the full authorization process to get them back.

That at least makes minor sense as it was an actual hardware change. IIf it happens again without you swapping hardware again, then you need to be worried.

[WonderGamer]

引用自 KaziArmada：

If it happens again without you swapping hardware again, then you need to be worried.

Which seems to be the case every time it happens to my co-worker as far as I know... >.<

[Bard]

I've had the same problem a couple of times now with the library of my brother-in-law and when I try to play an already installed game I get the Account-not-found-error. Not sure if this a just a coincidence or not, but it seems that I can get access again if I close Steam and before restarting it also close Origin.
This worked for me three times in a row now. Still might just be coincidental but maybe you guys can test it further.