Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
ipconfig /release [hit enter]
ipconfig /renew [hit enter]
Steam will then magically work....for a while. Resetting your router also does this. Forwarding ports however, does nothing.
So, mystery. But that's your temporary band aid fix.
"An error occurred while processing your request. Reference #97"
http://steamcommunity.com/discussions/forum/search/?gidforum=882959061466924237&include_deleted=1&q=%22An+error+occurred+while+processing+your+request.+Reference+%2397%22
Because I used my phone (without wifi) to come to the realisation that it isn't steam servers. Something's ♥♥♥♥♥ with the home network, but I cannot work out what. My 'solution' only fixes it temporarily. I did also search both in Google and Steam, without any luck whatsoever.
And I saw this in your post........
The first, and usually considered the main step, in troubleshooting network connectivity issues with Steam, even if you can use the internet fine otherwise, is to bypass all wireless connectivity and hardware (routers) and use ethernet only directly to the modem.
Covered here, as well as other helpful info about connectivity troubleshooting...
https://support.steampowered.com/kb_article.php?ref=1456-EUDN-2493
As to the latter suggestion, I am wired through ethernet. Only the phone uses wifi, which I disabled just to check if it was different with the cellular network.
Surely enough, it was.
Suspiciously, my friend also has the same problem and in the same vein as myself, it's very sporatic and only happened this week.
Also, topkek at the link you posted being a steam link, thus requiring me to renew my IP just to read the link. *sigh* what a quirky network bug.
For example....
If you are having connectivity issues, try this.....
Boot your PC into safe mode with networking. Again, it is safe mode with networking. Stay connected to the modem directly, and see if you can log into your Steam account using the client in that safe boot.
If you can, then that means that software is probably presenting a conflict in a normal boot. This list is a good start, but there can be other culprits.
https://support.steampowered.com/kb_article.php?ref=9828-SFLZ-9289
If you cannot, then that leaves pretty much only the following.
1. NIC(LAN) device driver not installed or updated to the latest one, especially under Windows 10
2. NIC(LAN) device itself is having issues...seen it happen before here.
3. modem (try resetting it)
4. Windows firewall. Make sure Steam is fully allowed through.
5. ISP...seen that happen also, the ISP started limiting traffic for the user or user was at a school
6. Steam network. If this was the cause, there would be many other threads right now about it also, surely.
EDIT..Forgive my posting here, but connectivity does not seem to be what this thread is about. The OP seems to only have issues when doing anything not involving his or her library.
In that case, I would suggest this...
Steam in the top left of the client, then settings, then Web Browser. Delete Web Browser Cache. Allow Steam to refresh...wait, please. Now, see if that helps the problem.
Thanks for your help too, though it's unfortunately not yeilding any results (yet)
LAN drivers are reinstalled, only thing I can't really check is the ISP.
I don't see where you tried safe mode with networking. You can post here while still in safe mode with networking and using ethernet only. More info about your system there would be maybe helpful also.
Such as...
Operating system (Windows and if it is 32 or 64 bit)
Network info (school/home network ?)
Computer model and model number exactly. If custom built, the exact motherboard instead. And if you reinstalled the drivers for the NIC, where did you get them ?
Edit: As to routers, I can't see any correlation there either. My friend is over in the US using a Linksys router. Mine is....something. It's not Linksys though.
You seem to be making many assumptions as to what is or is not causing the problem. That is the last thing you should ever do in troubleshooting something. Just troubleshoot it, using process of elimination and not make any assumptions, no matter what you think is or is not relevant, please.
Step by step method, using process of elimination is all there is to troubleshooting connectivity issues. Eliminate or go around one possibile cause and move on to the next.
I can even shut my PC down and have the phone generate the exact same error and when I renew my IP from the PC, Steam works again. There's just too much that's screaming "NETWORK". Had I not seen this thread and talked to my friend, I'd probably be updating the router's firmware right about now.
You know what WOULD be handy? Actually knowing what Ref #97 is.
Why the comments about the phone ? Are we not talking about Steam here and troubleshooting an issue with Steam, as in network connectivity problems ?
And I thought you said you use ethernet only anyway.
So why does the router keep coming up here, please ? I am sorry for my confusion, if so.
Then you have the browser version of Steam, which also throws the same error.
Then you have the mobile version of Steam, (basically the browser version) throwing the same error.
Thus, multiple ways to access Steam are reacting identically.
Now, on the offchance that Steam, using a chrome webkit is ♥♥♥♥♥♥♥ with me via cached data, I have completely obliterated the caches in both the client and my browser. The phone also has a cache, so I'm in the process of obliterating that too.
Should this not be the case, the only other thing these devices have in common is where they connect: The router.
Hence why I bring up the router.