Unable to create object!

I've just taken an object from a simulator recently updated to v1.23 (it was updated today). The item is heavily scripted, and I have previous instances of it which I can rez just fine, however if I try to rez this one (only one taken from a v1.23 simulator) then nothing happens. If I take it to a v1.22 simulator and try to rez it then I get two error messages:

"Unable to create requested object"
"Unable to create item that has caused problems on this region"

The object was working fine when it was rezzed in world before I took, while it contains a lot of scripts few of these are demanding and only when the user performs a command.

Is anyone else having this same issue? The only simulator I can work on this item has been updated to v1.23, my other plot of land in a v1.22 simulator is reporting an incorrect prim count preventing me from even rezzing the item =/

Naturally this is something I'm trying to finish for TOMORROW and I can't even attach it to my HUD which is where it's supposed to be since it's well...a HUD item!

Just managed to get it to rez in a sandbox region running v1.22 and I still can't get it work! What the heck! What does "Unable to create requested object" even mean? WHY can't it be created?

I'd guess that one of the scripts went "Missing from database" which would keep the entire thing from being able to be rezzed.

Hope I'm wrong though . Do keep trying to rez it again at regular intervals and definitely report it as a ticket in case it's a 1.23 bug.

Hrm, I don't think it's even made it to the asset server, I was filing a support ticket when I noticed the asset's UUID is "00000000-0000-0000-0000-000000000000" which is definitely not right!

All the scripts seem to have text associated with them, and are running normally, like I say, the object rezzed in world is fine, I just can't take the damned thing to wear it or test it anywhere else =(

You probably did already, but if the script code is still there and present on the v1.23 sim, make sure you have an offline copy in case it goes missing entirely.

Thanks for the suggestion, I do have previous versions and the scripts are available elsewhere as the item is "generated" in sim before I then link it together and wear it.

On which note, I've discovered I _can_ wear it, but if I detach it the inventory entry is still UUID of NULL_KEY and won't rez at all.

I've tried generating the object in a v1.22 simulator and am having the exact same problem with that copy as well, it won't rez. I'm going to try re-building the script that generates the object in a v1.22 simulator to try and eliminate it as the problem. I've not changed anything in the scripts I've edited that should be causing problems like this though, only minor logic edits!

This is something LL implemented a couple server versions ago, and they changed again with this latest server version. But so far they have steadfastly refused to answer any questions as to what it does, what it's intended function is, how it is supposed to work, or what triggers it. It seems to be some big secret.

Bugger, this is extremely annoying, as the message is (in true Linden style) utterly useless and meaningless in any way

Argh, if I wear the item direct from simulator then TP somewhere then all the scripts are missing from database. So the object itself is making it into inventory, but none of the scripts are, I'm assuming due to the large quantity of them, but most of them are deactivated until needed and I haven't added any more scripts since I last edited it (yesterday when it worked fine). This would imply 1.23 was the problem, but it happens when taking the object from 1.22 simulators as well =(

If the object is generated, there must be a seed prim (or prims) inside a scripted rezzing object... could that seed prim itself have been somehow marked as Teh Evol and whenever it's rezzed is refused to the asset server? Would it be worth a test, temporarily replacing that seed prim with a new plywood box, suitably named?

(Caveat: I'm not understanding what seems to be happening. If I follow the description correctly, then I've never seen anything like this before.)

http://blog.secondlife.com/2008/07/10/rolling-restart-tuewedthu-july-8-10-please-test-sever-version-123-on-the-preview-grid-now/#more-2189

This is all they say about the change this time around:

"Toxic message alert (’Unable to create item that has caused problems on this region) is now a script error and throttled"

Before it wouldnt' even let you rez and wear the item. I have a friend who has this issue with her Omicron HUD. It's odd because I have an Omicron HUD I wear, and i have never had this issue. So it seems to be something specific to certain people on certain sims.

LL really needs to provide more information on what in god's name they are trying to do here.

Yes, and you don't see a single Linden posting there to tell us what this is all about. I'd like to know what they are hiding.

Hmm, it seems in my case this is an issue with the number of scripts. For some reason I can no longer take the item into my inventory without all of the scripts becoming corrupted and "missing from database". The item has a LOT of scripts in it (almost 1000) however the majority are not running until needed to get around LSL limitations, leaving 140 or so scripts that are idle until asked to do something.

I've carved this down to around 700 at a significant cost in the speed of the device and can now take it into inventory just fine.

I can understand wanting to reduce the size of assets or something, but a completely undocumented change which generates no useful or informative error message is not the way to go about it! A significant amount of time has been spent on the item to make it as efficient, and low-lag as possible. When idle it has little measurable impact on a simulator, and when running it doesn't generate much lag either as it switches its scripts on briefly, does a burst of work then shuts them all off again. Now because I've reduced the number of scripts it actually has MORE of a measurable impact because it takes longer to complete it's task

However, looking at the JIRAs on this, this error message is like a catch-all, it tells you nothing of the actual problem. It's very likely that it is due to missing scripts as Kitty suggests, which explains older items causing the error, and my item now causing it due to some undocumented change causing its scripts to go missing when taken =(

the UUID issue is a red herring. You can't get the UUID of an object from inventory. ALL OBJECTS come up as NULL_KEY.