Archive for January, 2009

[RESOLVED] Support Portal is Currently Inaccessible

Saturday, January 31st, 2009

[3:14pm PST] [RESOLVED] The support portal is accessible again.

Our support portal at secondlife.com/support is currently inaccessible. We’re investigating the issue and will have things up and running as soon as possible. Please check back for further updates.

[Resolved] Difficulties with Teleporting and logins.

Friday, January 30th, 2009

[Resolved 3:52pm PST] All issues seem to have been resolved: We are currently experiencing some issues in relation to teleportation and logins. We are tracking down the cause and will update the blog with more information as it becomes available.

[Resolved] Network Issues- Some regions offline

Friday, January 30th, 2009

[Resolved 2:03pm] The issues discussed here have now been resolved: We are currently experiencing network issues. Some regions may appear offline, and unreachable. We are working to resolve this as soon as possible and will update the blog with any further information.

[RESOLVED] Teleporting difficulties, Region crossing and Search options

Friday, January 30th, 2009

[RESOLVED - 12:32pm PST] All issues have been resolved. Should you experience any related issues, please contact us through normal support channels (http://secondlife.com/support/).

[UPDATED] Network issues

Friday, January 30th, 2009

[UPDATED 9:58am PST] - While we have not had confirmation from our network providers, the issue appears to be resolved at this point. We will update this blog when we receive confirmation that this has been resolved.

[07:13AM] We are still working on a resolution to the ongoing issues with our network, we will continue to update you on the situation which we hope to resolve as soon as possible.

[04:13AM] The problems in-world being experienced by residents are related to difficulties at our network provider. We are liaising with them to resolve these as quickly as possible.

[03:50AM] RE-OPENED - We are still getting reports that some residents are still unable to teleport. We will update you as soon as the issue has been resolved.

[02:52AM] [RESOLVED] All issues have now been resolved.

[1:15AM] This is still being looked into. For now, there is nothing new to report.

[11:35PM] You may be unable to view L$ balances, teleport, search, cross regions or connect to Second Life. If you’re inworld, please refrain from rezzing or derezzing no-copy objects.

[11:20PM Pacific] We are aware of an issue with our network that may affect inworld services. Please keep an eye on this post for additional information as it becomes available.

[Resolved] Temporary Login and TP issues.

Thursday, January 29th, 2009

[Resolved 10:08am] This issue has been resolved. You may now resume your activities.

[09:41 am PST]  We’re investigating a server issue which may cause some Residents to experience problems with some Inworld services.  Affected services include logins, teleporting and rezzing.  Please refrain from rezzing no-copy items and making transactions until the all-clear is given.  Our engineers are already working to resolve the issue.

[RESOLVED] Inventory Server Rotation

Thursday, January 29th, 2009

[RESOLVED 04:03 am PST] The maintenance was concluded successfully.

[03:14 am PST] As part of scheduled maintenance, we are rotating two clusters of agent databases.

For a small group of our Residents that will cause inability to log in, or if they are already inworld, they will be logged out.

This work is about to begin now, and we will let you know here as soon as it’s finished.

[UPDATED] Parcel Directory Fees Being Charged Twice

Wednesday, January 28th, 2009

[4:35pm Pacific] Residents who were charged twice for parcel directory listings or group liabilities will be reimbursed.  If you have been charged twice but do not see a refund after 24 hours, please contact support.

Residents who were paid double stipend this week will not receive a stipend next week. All affected residents will be emailed.

[03:29am Pacific] We have found the cause of the duplicate fees and we are now in the process of identifying the affected residents to resolve the issue.

[02:25AM Pacific] We’re receiving some reports of residents being charged parcel directory fees and potentially group liabilities twice.   We are also receiving reports that stipend’s are being paid twice.

We’re looking into it the issue and will update you as and when we have more information.

[RESOLVED] Database Issues Affecting Some Inworld Services

Wednesday, January 28th, 2009

[RESOLVED 13:30] The database issue has been corrected.  Affected inworld services have returned to normal functionality.

We are investigating a database issue affecting some inworld services.  Affected services include Searches, Mapping and Teleporting.  Please monitor this post for updates and further information.

New Test Viewer: 1.22 RC7 Now Available

Wednesday, January 28th, 2009

The seventh iteration of the 1.22 Viewer, Release Candidate 7, has been released. Please help us to identify any new bugs before it becomes an official Second Life Viewer download.

If you have been using the sixth Release Candidate (RC6), you will be required to update to RC7. Please keep in mind that participation in the viewer Release Candidate cycle is completely optional. This viewer may be installed along side the official 1.21 viewer.

RC7 includes a fix for a crash occurring on display of textures, which relates to LLTextureFetchWorker::decodeImage.  As always, release notes can be found at:

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release_Candidate/1.22

While we’ve made many improvements, we still need your help to find crash cases and final feedback as we prepare to release the official 1.22 viewer - very soon! Please download the Release Candidate here and start experimenting:

http://secondlife.com/support/downloads.php#download-Testviewers

You can participate in discussions about this new Release Candidate here in the SL Forums.

Don’t forget to report new issues at jira.secondlife.com, and be sure to set the “Affects Version/s” to “1.22 Release Candidate”. We are only able to investigate bugs that are reported in this way.