#6 error when changing Component owner

[Jason E. Sweat]

update gives an error (Error! There is no user #, where
# does exist). Droping the component and creating new
with the owner I wanted worked fine. Okay for a work
around in the case of a new component but would not
work if bugs had already been assigned.

[Jason Lee]

Logged In: YES
user_id=665638

I think this is an issue with the installation procedure
(initialization of sequences, etc). I'm pretty sure another
user and I have covered this from a different angle in
private email, but I'll double check.