Then I went to C:\Users\username\AppData\LocalLow and deleted the Firestorm folder also. I went to C:\Users\username\AppData\Roaming and deleted the Firestorm圆4 folder. It turns out it was an issue with the firestorm AO in the latest version of firestorm. My firestorm was working this morning then I double click it to log on again and it crashes every time. I worked through several areas to troubleshoot with the firestorm rep. And I was assisted by a firestorm rep on the official firestorm site. We need to replace the download location in your client, so your WoW 4.3.4 Cataclysm Client downloads it from a location that is accessible. I did contact FIRESTORM on google and had an official 'fix it' ticket.
0 ms SQL(p): DELETE FROM ipbanned WHERE unbandate<>bandate AND unbandateHere's the solution to: Cannot stream required archive data / WoW Error 134 Updating realm 'F0xs Server' at 90.91.92.93:8085. This means that your WoW Cataclysm Client is unable to download the necessary files, which results in the: " Cannot stream required archive data" error, and the WoW Error 134 on your Cataclysm 4.3.4 client, and in some rare occasions: the WoW Error 132. Until recently, they were public for everyone to download, but recently Blizzard has closed the access to it. This means that the client downloads from Blizzard's CDN Servers (Streaming Servers). The reason is that the Cataclysm mini-client (fast client) depend on Blizzard's servers. Why does the Cannot stream required archive data / WoW Error 134 Error even happen?
Today's Cataclysm tutorial explains how to get rid of the frustrating Cannot stream required archive data, and in other cases, you might experience WoW Error 134, for Cataclysm 4.3.4 Fixing Cannot Stream required archive Data / WoW Error 134, on Cataclysm 4.3.4