Sometimes, when creating a new character, the toon will spawn in Mos Eisley with no clothes or hair. When that happens, the following also shows up on the server's console:
(where Player 13021818 is the one I just made)
Verify and lock name requested for stationId 652293343
WARNING: (f5966200): Player 13021818 has lost their datapad
(f5966200): Player 13021818 has lost their datapad
WARNING: (1940b2db): Player 13021818 has lost their mission bag
(1940b2db): Player 13021818 has lost their mission bag
WARNING: (db8185f6): Player 13021818 has lost their bank
(db8185f6): Player 13021818 has lost their bank
If I then immediately shut down the server and restart it and log in again, my clothes and hair appear, but now the following is in the console:
WARNING STRICT FATAL: (cce20ac4): Could not depersist item [13021844] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
(cce20ac4): Could not depersist item [13021844] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
WARNING STRICT FATAL: (cce20ac4): Could not depersist item [13021825] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
(cce20ac4): Could not depersist item [13021825] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
WARNING STRICT FATAL: (cce20ac4): Could not depersist item [13021822] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
(cce20ac4): Could not depersist item [13021822] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
WARNING STRICT FATAL: (cce20ac4): Could not depersist item [13021821] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
(cce20ac4): Could not depersist item [13021821] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
WARNING STRICT FATAL: (cce20ac4): Could not depersist item [13021820] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
(cce20ac4): Could not depersist item [13021820] into container [13021818] because there was no good arrangement, ContainerErrorCode=4. See previous warning. We then attempted to find a different arrangement to put the item into, because the item really belongs in this container, but could not because it was either already occupied or the arrangement of the item was changed so that it cannot be placed in this container anymore. This is typically bad, and may result in the item being in an invalid state or even moved to 0 0 0 in the world. This might happen because the arrangement file was changed for this object and existing objects could no longer be persisted into their containers.
These errors will appear every time I start the server and then log in.
In SQL Developer, I can see that those 5 objects got created twice. They are my datapad, bank, mission_bag, appearance_inventory, and default_weapon.
Also sometimes starting items like Jabba's Comlink are missing.