Jump to content
  • 0

(darn. you have been logged out of second life?


ahmed Starkford
 Share

You are about to reply to a thread that has been inactive for 3204 days.

Please take a moment to consider if this thread is worth bumping.

Question

13 answers to this question

Recommended Posts

  • 0

You could try running the test at http://www.pingtest.net/ a few times, if for no other reason than to verify that your internet connection is ok. If you get a low grad, you may want to talk to your ISP about it. But first, try unplugging your modem and router for a minute or so, plug them back in again and try logging in.

Looking around, I see there are quite a few connection issues being reported. Maybe there is something on LL's end, and it will clear up by itself...

- Luc -

Link to comment
Share on other sites

  • 0

If logging in to another region doesn't fix it, try deleting the Second Life folder in AppData > Roaming and then relogging. Second Life will create a new default folder. I've seen this work for some people faced with a similar issue.

Windows XP - C:\Documents and Settings\<username>\Application Data\SecondLife
Windows Vista - C:\Users\<username>\AppData\Roaming\SecondLife
Windows Vista Home Premium - C:\Users\<username>\AppData\Roaming\SecondLife
Windows 7 - C:\Users\<username>\AppData\Roaming\SecondLife
Windows 7 - C:\Users\<username>\AppData\Local\SecondLife\ (Viewer version 1.23.5 (136262)

Was going to suggest resetting your modem/router but I see Luc already did that (waves to Luc!).

Have you by any chance a Netgear router? Some models are known to cause login problems.

Link to comment
Share on other sites

  • 0

/me waves back to Nyll! :)
Netgear router, you say? From what I learned from Peewee earlier today :), that sounds like it could be a possible cause. 

If what has been suggested, and you are on a wireless connection, try to connect wired and see if that does make a difference. 

- Luc -

Link to comment
Share on other sites

  • 0

This was the fix for me. It was the folder mentioned by Nyll Bergbahn that has helped me. I have had this problem several times and didnt realize that removing that one folder was helping me. I was uninstalling the whole program and reinstaling, which was unnessesary as it was just the one folder that needed deleting. Tried deleteling the folder and boom I was back in.

Link to comment
Share on other sites

  • 0

Lol no Luc...it's true. Linden Lab changed the message a month or so ago, their idea of humour I guess. I saw it a lot as I kept crashing recently due to an incompatible router that was eventually replaced after a month of arguing with my ISP. I mentioned this in a thread recently and even posted a pic of it but can't find the thread now.

Link to comment
Share on other sites

  • 0

LOL. Strangest thing I have seen for a while. If that's someones humor, it's even weirder than mine :|. But are you sure it is LL who changed it? Because I've had the being-logged-out-because-of-a-bad-connection lots of times, even after that thread was started, and I haven't seen THAT message yet. Perhaps it is a message from a different cause I got, because I don't think I have even seen the 'Darn' one.

 

Funny still, though. :D

 

- Luc -

Link to comment
Share on other sites

  • 0

There is a very easy solution to this. It's probably just the open notifications that are making your viewer crash. Just do this:

1. When you get the "Darn. You have been... etc." message, don't click on "Quit". Click on "view IMs" instead.

2. On the upper right corner, you'll see the "Notifications" button: it's a little rectangle resembling an envelope with the number 994 (that's the number of open notifications when the viewer stops counting). Right click on it and click "Close All". You'll need to wait a few seconds until your computer deletes the open notifications. (If your viewer crashes while doing this, try it again in some protected region like Smith. If you still crash, try closing manually a few notifications. But probably you won't need to do any of this.)

3. Quit and relog.

This should fix it. After that you only need to remember closing the open notifications from time to time! :)

 

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 3204 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...