User Tools

Site Tools


login_fail_without_cache_clear
Advertisement

Login Fail Without Cache Clear

This page covers login problems which fit the following description:

  • You are unable to log in properly without having to clear cache fully before doing so.
    It should never be necessary to clear cache before logging in, so if you have to do this, something is wrong. Some find that if they don't clear cache each time, they get logged out within seconds of logging in, or perhaps they are ruthed or a cloud every time, or even that they crash shortly after log in.
  • You are able to log in but find yourself under water (all you can see is a blue screen) at coordinates 10, 10, 10.
    If you log in to an all blue screen, check your location, see if you are near the SIM corner, at 10, 10, 10. If so, your issue can hopefully be solved by one of the suggestions given here.
  • If you have more than one account, only one is affected.

In some cases, you will see that there is an error in loading one or more gestures. If you do, make careful note of which ones, then find them and deactivate them - or better, delete them. If there is no such message, then please read on.

Delete Inventory Cache

One possibility is that your inventory cache has become corrupted. If this is the case, then deleting it should solve the problem once and for all - assuming it doesn't become corrupted again at some future date.

  • Locate your cache folder. You will probably need to do this manually, if you are unable to log in. Use a file manager (like Windows Explorer for Windows system, Dolphin, or some such) to locate the cache folder. In its default location, the cache folder is hidden on most OSs. To find it, you will need to show hidden folders. Default cache locations are:
    • Firestorm Viewer:
      • Windows XP: C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Firestorm\Cache
      • Windows Vista: C:\Users\[USERNAME]\AppData\Local\Firestorm\Cache
      • Windows 7: C:\Users\[USERNAME]\AppData\Local\Firestorm\Cache
      • Mac: ~/Library/Caches/Firestorm
      • linux: ~/.firestorm/cache
  • In this folder, locate the files named data.db2.x.* and index.db2.x.* (where * is a digit: 0, 1, 2, etc; you may have more than one of each type of file)
  • Delete all files that match these two names.
  • Log back into SL, to a quiet region (try the Phoenix Firestorm Support parcel or a Linden water region such as aich or hatton). Allow your inventory to repopulate fully.

If your issue was a case of a corrupt inventory cache, then subsequent log ins should work normally. If however, your next log in fails as before, then your will need to locate the problem item in your inventory and eliminate it. So try the solutions described below, one at a time, until (hopeffuly) one of them fixes the problem.

Too Many Items in Single Folders

This can be caused by an issue called having a “flat inventory.” If you have folders with a lot of items in them, the viewer can stall trying to create the “inventory view” (inventory folder structure in memory). The solution is simple, but tedious: you will have to create more folders (or subfolders) and sort your inventory such that no one folder has too many items in it. Ideally, aim for under 1000 items per folder.

Alternatively, because this is not a viewer-specific problem, Linden Lab can also help you deflatten your inventory if you file a support ticket with them. Just make sure to log in on the official Second Life viewer twice (once to fill the inventory cache and a second time to confirm that you're experiencing the issue on their viewer) before contacting Linden Lab.

Vintage Skin

If you use Vintage Skin (default when logging in using “Phoenix Mode”), the “too many items in single folders” problem may be more likely to occur than when using other viewer skins. This is thought to be because the inventory structure in this skin is slightly different from that of the other skins. Try changing your viewer skin to Latency, which shares Vintage's V1-style appearance but does not increase your likelihood of having this issue, or any of our other skin options. Do this in Preferences → Skins. Change to Latency or another option and relog.

Excess Calling Cards

There have been cases where people have ended up with a mass of duplicated calling cards in inventory, so many that they end up preventing successful log in. So try the following:

  • Start the viewer and try to log in.
  • If you are able to log in, open your inventory window, find the Calling Cards folder, and delete all of them, then empty trash.
  • Now log out, then restart the viewer, and log in.

Hopefully, this will solve the problem. If not, then read the next section.

Deactivate All Active Gestures

Should the above method not give a permanent fix, then you should try to deactivate all your active gestures. Yes, all of them. At the bottom of the Inventory window, click the gear icon, and select Show Filters. Click the None button, then check Gestures. Then type (Active) in the search field at the top of the Inventory window.

The above will list all your currently active gestures. Select them, then right click and select Deactivate. Double check that all gestures are deactivated by bringing up the gesture picker at the bottom of the screen; it should show none active.

Now relog and see if you still have issues logging in.

If this solves the problem, the next step is trying to find the bad gesture(s). The best way to do this is with a “divide and conquer” approach. It is not difficult, but it can be long and tedious, depending on how many active gestures you had. Using filters to show only gestures will make this somewhat easier.

  • The idea is to attack the collection of gestures by halves: activate half, deactivate the rest, then relog.
  • If you can log in ok, then the problem gesture(s) are in the deactivated half. If instead you have problems logging in, then the bad gesture(s) are in the ones currently active.
  • Having identified which half has the problem gestures, again, split this remaining group of gestures in half: activate half, deactivate half, then repeat as before.
  • Continue this way, dividing in half each time, until you have narrowed down to the one (or more) problem gestures - which you should at least leave inactive, but preferably simply delete outright.

Remove Landmarks

One final rare case is similar to the above but involves landmarks rather than gestures.

In this case, it is recommended that you box up all of your landmarks, then delete the originals from inventory, then empty trash (saving the boxed copies). See if this allows for a normal login.

If so, then you can use the “divide and conquer” method above to find the problem landmark(s).

login_fail_without_cache_clear.txt · Last modified: 2017/02/03 20:27 by lette