Error Message FAQ

This page lists common Sansar error messages and troubleshooting steps.

Related FAQs: General FAQ | Troubleshooting Import Errors

Visiting worlds

Could not visit world due to the error: unable to connect to regionserver

Solution: VPN and connection issues, try restarting the client or your router.

---

Could not visit this world because all instances are full.

Solution: Wait and try again later, or join a different instance if one is available.

---

Could not visit this world because the specified instance is full.

Solution: Retry without targeting that specific instance, or wait for space to open in that instance.

---

Could not visit this world because the specified instance was not found.

Solution: Open the world again from its listing and retry. The instance may have already closed or the instance link may no longer be valid.

---

Sorry, this world instance is full. Please try visiting again.

Solution: Wait and try visiting again later.

---

Visit world failed because the requested world is not in the current grid.

Solution: You may be on a outdated client, be sure to login to the most recent one.

---

Visit world failed because the requested world was not found.

Solution: Check that the world link is correct and that the world still exists. If it is your own world, make sure the intended scene is still linked to that world.

---

Visit event failed because the event was not found.

Solution: Open the event again from its event page and retry. The event may have ended or the link may no longer be valid.

---

Visit world failed because the specified URI could not be parsed.

Solution: Use a complete, valid Sansar world or event URL instead of a partial or malformed link.

---

Visit world failed because the world failed to load.

Solution: If this is your own world, make sure the scene is linked to the world and has been built before visiting. Then retry.

---

Visit world failed for an unknown reason.

Solution: VPN or connectivity issues, try without a VPN or connecting to a different location.

---

Visit world failed because Sansar was in the wrong state.

Solution: Try again,

Edit mode and scene editing

Edit server is already occupied

Solution: Usually after a crash, waiting some time 15 - 30 mins, will resolve on its own, if not support may need to intervene.

---

Unable to connect to local edit server

Solution: Only seen on test clients.

---

There was an error saving the file.

Solution: Make sure you have disc space.

---

Unable to save scene: Please close the material editor before saving your scene.

Solution: Close the Material Editor, then save the scene again.

---

Unable to build scene: Please close the material editor before building your scene.

Solution: Close the Material Editor, then build the scene again.

---

Unable to close scene: Please close the material editor before closing your scene.

Solution: Close the Material Editor first, then close the scene.

---

Unable to extract selection: Please close the material editor before extracting selection.

Solution: Close the Material Editor first, then try extracting the selection again.

---

You can't move an object into one of its children.

Solution: Choose a different parent, or move the child object back to the top level before regrouping.

Store and inventory

No store listing was found for that item number or URL.

Solution: Enter the listing's 36-character item number or use the store listing page URL or Edit Listing page URL for an existing listing.

---

You cannot change another user's store listing.

Solution: Only replace or update listings that you own. If you need to sell your version, create your own listing instead.

---

You can only update store listings for script items.

Solution: Make sure you are using the replace flow on a supported item type. Script listings are updated from the scene editor, while avatar-related items are updated from the avatar editor flow.

---

An error occurred. The item was not updated in the store.

Solution: Verify that the item type is supported for listing updates, the product ID or URL is correct, and avatar-related items include a thumbnail, then retry.

Avatar and looks

%s is already in use. Please choose a different name.

Solution: Enter a different name that is not already being used.

---

The avatar failed to load and may be corrupted. Would you like to delete this look?

Solution: Try duplicating the look.

---

To list an item in the store, the item must have an inventory thumbnail. Please reupload the item with a thumbnail.

Solution: Reupload the item with a thumbnail image before listing it. Avatar-related items need a thumbnail if you want to list or replace them in the store.

---

This look cannot be customized because the custom avatar has been deleted from your inventory.

Solution: Restore or reimport the custom avatar to your inventory, or switch that look to a different avatar.

---

Invalid product ID or URL.

Solution: Use the listing's 36-character item number, the store listing page URL, or the Edit Listing page URL.