Maintenance for the week of April 6:
• [IN PROGRESS] ESO Store and Account System for maintenance – April 8, 9:00AM EDT (13:00 UTC) - 6:00PM EDT (22:00 UTC)
Booted from Server because of delivering Master Writs
To level up my new Necro rapidly, I prepared a lot of Master Writs for Alchemy and Provisioning.
To do this, I've bought Skyshards packs in the Crown Store to get skill points,
levelled the Alchemy and Food skills up and prepared all necessary delivery items.
However, while handing the items in to fulfil the Master Writs, sometimes I receive the error "booted from server".
I had the same exact issue, for the same exact reason; I had to simply wait 10-15 minutes before the game let me back on. Actual bots can run rampant for hours on end, but when real players do something repetitive we get booted...
First, with regard to the OP: on which platform and megaserver do you play TESO? ZOS cannot investigate without that information. Please review the Guidelines For Bug Report Forum.
Second, during the past 4+ years I have observed that I can be "booted from the server" at any time. Whether I am is rarely related to any particular activity in which I am engaged.
The one and only time that I can recall in which the "Booted from Server" message specified a cause, it was "too many searches in rapid succession". Whether I, personally, was making too many searches in rapid succession, however, was doubtful. Much more likely, the "megaserver" system was simply unable to process the number of search requests that it was receiving from all of the players who were currently logged-in to play the game and searching for items in the Guild Stores. So the system just responded by disconnecting players to reduce the overload.
In other words, in my experience, "Booted from Server" has been coincidental, not incidental to what I've been doing -- albeit, what I did is, of course, always a possible cause. Regardless, the only remedy is to wait a few minutes and attempt to log-in to resume playing the game.
Unfortunately, though, the rude disconnect does not always occur without damaging a player's access to their game account and/or their character's position in the game. When it does, we need Customer Support to assist in finding the cause and resolving the issue. They really should not be referring players to the Technical Support or Bug Report forum for advice to recover from the situation (for which ZOS/Bethesda is responsible, not the player!).
NOTE:
After I am "booted from the server" and the game client displays the primary game/account log-in dialog, usually it is only a matter of logging-in to resume playing the game. Sometimes the response is that I am still logged-in to the game, so I must wait for the megaserver to terminate the log-in. The game client has not crashed, so it is still running.
However, if the outcome returns me to the Windows desktop instead, then I always run Launcher and choose Repair Files from its Game Options menu, before I attempt to log-in again. This recognizes the possibility that the game installation has become corrupted by the incident, because the game client might not have had an opportunity to close any files that it had open (on my computer) before it exited.
Edited by Shadowshire on June 5, 2019 3:09AM
--- Shadowshire .......... ESO Plus on PC NA with Windows 7 Pro SP1
I play on PS4 EU, but this does not matter, people also report this issue on PC. I have never seen this issue before or after, I see it only delivering Master Writs.
Alcast also mentions this issue when delivering Master Writs in one of his last videos: https://www.youtube.com/watch?v=ECoPEdnZ3-w
I have received the, “Error 307: Booted from Server” on a handful of occasions, always when either doing parsing or crafting for an hour or more. I have never received this particular error (at least not to my recollection) for a different reason.
I’ve been kicked with the “Too Many Messages” error as well but that has always been during a heavy lag spike where an influx of my controller movements (seemingly) sent through to the servers at once upon regaining a solid connection.
In either case, I leveled a Necromancer via Master Writs and received Error 307. It isn’t causal evidence, but it’s certainly worth investigating.