Jake Hunter said:

When rebuilding a roo, the sl assest server posted this as the roo disappeared.

[05:15] Meeroo #811272 Meeroo: The Second Life Asset server created a duplicate Meeroo #811272. This extra one is being released to the wild.
[05:15] Meeroo Home V1.0: A problem occurred updating meeroo ID #811272, going to skip its update this time,
but it will be retried soon. Don't Panic!

Easy for the SL to say Don't Panic, but now it doesen't even show in spreadsheet. Any suggestions would be well appreciated as the roo was to be mated (sierra & red)both in season fall(seasons is another issue I'm having, so a CSR tells me, supposedly a good glitch).

ANSWER: Hi Jake! The Asset server citing false duplications (i.e. recognizing itself as a duplicate even when it is not) has been a problem since beta and the bane of my existence, as well as our customer support team! Meeroos falsely vanishing as a result of the "Asset Server" make up about 40%-60% of our total tickets. I know for so many of our customers this is incredibly frustrating. I'm over Levio's shoulder about this exact issue and getting a lot of pushback, but I promise you I won't stop nagging until this issue is fixed once and for all.
Ultimately, it's not Second Life's Asset Server causing this problem. It's our code kill-trigger and Second Life's ability to relay information to our database in a timely fashion, so we are partly to blame for this. I have had this happen to me many times during testing. If you pick up a meeroo into your inventory and set it back down within a minute, our database thinks it is still present at it's old location. Therefore, rezzing it onto the ground makes the Meeroo believe incorrectly that it is a "duplicate" despite it not being at all. Second Life did not deliver the status change (That it had been picked up) before the player sets it down again. The database then thinks there are two and "releases it to the Wild."
The reason for the script was to save customers and ourselves the headaches that come along with clones. Levio integrated this script in order to ensure that each meeroo was individual and authentic. Without it, I'm told that there could be thousands of clones. I've insisted that we speak to a third party professional to find a work around so we can get rid of the kill script completely while still preserving the integrity of your meeroos.
You also had an error reaching the database, thats scary when it happens, I know! but wait a moment and try a rebuild. If it appears broken, don't worry. Our CSR's will ALWAYS return Meeroos that vanish as a result of false duplications or that have been broken as a result of a database glitch. Just send us your ticket and we'll get your content back for you!
Thanks!

catherine