Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IllegalArgumentException on save: Name and ID cannot both be blank #347

Closed
mibby opened this issue Jun 20, 2016 · 4 comments
Closed

IllegalArgumentException on save: Name and ID cannot both be blank #347

mibby opened this issue Jun 20, 2016 · 4 comments

Comments

@mibby
Copy link

mibby commented Jun 20, 2016

Paper 791

Got this exception every time the world auto-saved.

[16:20:13] [Server thread/INFO]: Saving...
[16:20:13] [Server thread/WARN]: java.lang.IllegalArgumentException: Name and ID cannot both be blank
[16:20:13] [Server thread/WARN]:    at com.mojang.authlib.GameProfile.<init>(GameProfile.java:25)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.UserCache.a(UserCache.java:90)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.UserCache.getProfile(UserCache.java:158)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.Village.b(Village.java:444)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.PersistentVillage.b(PersistentVillage.java:256)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.PersistentCollection.a(PersistentCollection.java:99)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.PersistentCollection.a(PersistentCollection.java:84)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.WorldServer.a(WorldServer.java:1083)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.WorldServer.save(WorldServer.java:1024)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.CommandSaveAll.execute(SourceFile:36)
[16:20:13] [Server thread/WARN]:    at org.bukkit.craftbukkit.v1_10_R1.command.VanillaCommandWrapper.dispatchVanillaCommand(VanillaCommandWrapper.java:122)
[16:20:13] [Server thread/WARN]:    at org.bukkit.craftbukkit.v1_10_R1.command.VanillaCommandWrapper.execute(VanillaCommandWrapper.java:44)
[16:20:13] [Server thread/WARN]:    at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:152)
[16:20:13] [Server thread/WARN]:    at org.bukkit.craftbukkit.v1_10_R1.CraftServer.dispatchCommand(CraftServer.java:665)
[16:20:13] [Server thread/WARN]:    at org.bukkit.craftbukkit.v1_10_R1.CraftServer.dispatchServerCommand(CraftServer.java:628)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.DedicatedServer.aL(DedicatedServer.java:441)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.DedicatedServer.D(DedicatedServer.java:404)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.MinecraftServer.C(MinecraftServer.java:730)
[16:20:13] [Server thread/WARN]:    at net.minecraft.server.v1_10_R1.MinecraftServer.run(MinecraftServer.java:629)
[16:20:13] [Server thread/WARN]:    at java.lang.Thread.run(Thread.java:745)
[16:20:13] [Server thread/INFO]: Saved the world
@Puremin0rez
Copy link
Member

Have you tried deleting (but first backing up) your usercache.json file in the root of the server directory? This file can sometimes become corrupt for some people and cause errors similar to this.

@mibby
Copy link
Author

mibby commented Jun 22, 2016

The error stopped occurring today after the server restarted. So no need to delete the json file. Just thought I'd report the error anyways in case there was a way to prevent saving UUIDs that are blank.

@zedwick
Copy link

zedwick commented Jul 3, 2016

I am also getting this, but my usercache.json appears to have no errors in its structure. Had seen it just after updating to 1.10, but like above it seemed to go away after a reboot or maybe just when a certain player was not online. It returned today.

@zachbr zachbr closed this as completed in 29e16ba Jul 17, 2016
@Tych0n
Copy link

Tych0n commented Nov 16, 2016

@mibby & @zedwick people say this is old bug, check the workaround in the link if it is still actual for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants