- 0
Can't sign-in for 12 hours. An old alt sign-in works immediately. Password ok. What is going on?
You are about to reply to a thread that has been inactive for 4419 days.
Please take a moment to consider if this thread is worth bumping.
Question
Shabana Paneer
PLEASE NOTE:
By mistake I clicked "resolved" for this question; unfortunately my issue is not yet solved. The original question thread (started 8/22/12) is here:
http://community.secondlife.com/t5/Account/Can-t-sign-in-for-12-hours-An-old-alt-sign-in-works-immediately/qaq-p/1643913/comment-id/12718#M12718
Problem:
--I can't sign in my usual account but an old alt works perfectly every time.
--I DID get in once for about 30 seconds and in that time went to Preferences to clear cache and I noted some invisible prims on the feet were messed up (invisible ankles and feet) and was attempting to look into that when I got the usual message which was: "You have been logged out... The region may be experiencing trouble...." with a 'View IM...' and 'Quit' buttons
--I used to have a non-standard symbol in my username but took that off and its all vanilla script now
--I dont use a router, modem only and I restarted with no effect.
--changed password, reinstalled Firestorm to latest build
--have changed sign in location to various others with no effect
I have taken Echo's suggestion and:
--put the Advanced / Develop menu up on my alt in SL, exited and
--brought up my regular alt and got the usual "You have been logged out" message, but this time got the whole raft of console information. Unfortunately you can't cut & paste this and I don't see any upload jpeg file function in this forum, so I copied much of what seemed the most important information for you here. It is not exact or complete--the log of course goes on extensively.
Here it is:
WARNING:/Message /avatarnamecache.(ccp291) : AvatarNameCache : : HandleAgentError get legacy for agent [long 20-character code]
XML_STATUS_ERROR parsing:
Info: newview inventory model background fetch.cpp(555)
InventoryModelFetchDescendentsResponder: : Error 499: STATUS_EXPIRED
Link to comment
Share on other sites
8 answers to this question
Recommended Posts
Please take a moment to consider if this thread is worth bumping.
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now