[BUG-9907] Login eror: "There was a problem saving the default permissions due to the following reason: STATUS_EXPIRED"

[sl-service-account]

Steps to Reproduce

Logging in to Second Life using Second Life Viewer or Firestorm

Actual Behavior

Receives the following error when logging in: "There was a problem saving the default permissions due to the following reason: STATUS_EXPIRED"

Expected Behavior

Normal login without errors

Other information

Key accounts does not get the same error when using admin login. Has performed clean reinstall, inventory fixes, and KA attempted to manually set default permissions with no change in behavior.

Links

Duplicates

• [ ] https://github.com/secondlife/jira-archive/issues/16610

Original Jira Fields

| Field | Value | | ------------- | ------------- | | Issue | BUG-9907 | | Summary | Login eror: "There was a problem saving the default permissions due to the following reason: STATUS_EXPIRED" | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | SeleneLily Galicia (selenelily.galicia) | | Created at | 2015-08-16T14:06:07Z | | Updated at | 2017-07-07T15:52:13Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2015-08-16T09:21:05.510-0500', "Is there anything you'd like to add?": 'Key accounts does not get the same error when using admin login. Has performed clean reinstall, inventory fixes, and KA attempted to manually set default permissions with no change in behavior.', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'Receives the following error when logging in: "There was a problem saving the default permissions due to the following reason: STATUS_EXPIRED"', 'What were you doing when it happened?': 'Logging in to Second Life using Second Life Viewer or Firestorm', 'What were you expecting to happen instead?': 'Normal login without errors', } ```

[sl-service-account]

Whirly Fizzle commented at 2015-08-16T14:21:06Z

Heya SeleneLily,

Please see BUG-9066 for this bug. There is a fix pending upstream fro this problem in Lion.

The warning message itself is harmless. Are you actually having problems apart from just seeing this warning message at login? If your login is being really slow for some reason then you will likely see this warning message with a STATUS_EXPIRED or NO_CONNECTION reason but that's just a side effect of whatever the problem is, not the cause.

If you are not having any problems apart from seeing this warning message then it's nothing to worry about. If you are having problems getting logged in, then please comment back.

Thanks :)

[sl-service-account]

SeleneLily Galicia commented at 2015-08-16T15:05:09Z

Yes I am having problems logging in. If you saw the photo that I had sent TJ at SL, if you look at the bottom, takes very long to log in... then the message shows up..then its still spinning.

When I finally do log in, I'm pretty much ok after that..but not always. Very odd I know.

Thank you for looking into this..what else should I be doing.

[sl-service-account]

Whirly Fizzle commented at 2015-08-16T15:19:47Z

Ahhh. No I didn't see the photo. I'm just a normal Resident.

Ok so, given you are seeing the warning message at login with the STATUS_EXPIRED message & you say logins are really slow, a pretty common cause of that these days is inventory views taking a long time to create during login. Your viewers logs will show the time it takes to create inventory views.

Are you having the same problem on both Firestorm (you gave Firestorm in your system info) and on the LL viewer? I'm guessing LL support already had you test on their viewer. If the problem is slow creation of inventory views then you will get the same problem on both viewers as long as the inventory is fully cached.

Do you have any alts and can your alts login without any problem? What size is your inventory on the affected account? If you clear cache in the viewer, are you always able to login at normal speed for that first session after clearing cache?

Let me know if you also have this problem on the LL viewer, because it's best to use that one for this JIRA issue.

[sl-service-account]

Grumpity Linden commented at 2015-08-17T16:58:28Z

We see that TJ is working with you and is planning to escalate. Will investigate and follow up through support channel. Thanks!

[sl-service-account]

SeleneIsabella commented at 2015-08-18T01:54:49Z

Well I just did a complete uninstall..clean reinstall my inventory is missing over 20K items, in firestorm im still getting the default message its still giving me not responding

ALL this on my Main Account ONLY Alts are all great.

Im so flustered at this point..HELP

[sl-service-account]

Whirly Fizzle commented at 2015-08-18T02:44:51Z

Selene, if LL support is escalating your case, then its probably best to just wait to see what happens.

From what you say though, it really does sound like an inventory issue on the affected account - it could be a large flat inventory structure causing your logins to time out or something else wrong with the inventory. LL support have special tools to fix those problems.

What you can try while waiting for LL support is to clear your cache and see if that lets you login & remain stable. If that does work then its likely just a large flat inventory structure. If it works, you will likely have to purge cache before every session. You seem to be using Firestorm as your main viewer, so - launch the viewer to the login screen. Go to Viewer -> Preferences -> Network & Files -> Directories -> Click the "Clear cache" button -> Apply -> Ok. Then quit the viewer. Launch the viewer again - the viewer will delete your cache and then login.

Are you able to login & remain stable the session after doing that?

[sl-service-account]

Kyle Linden commented at 2015-08-20T18:38:33Z

Hello Selene,

We believe your problem has been resolved. Will you please confirm whether you have been able to login?

Thank you!

[sl-service-account]

Saeros Linden commented at 2017-07-07T00:35:34Z

Our apologies, it appears this jira has been a victim of a spammer. We're cleaning up the offending comments, sorry for the mess!