We had this bug. It turned out to be a user ID missing a record in the
RemoteObjectID table. The reassign has to populate a drop down box of all
users in the system. If one of the user IDs is corrupt for some reason
(we never really figured out how it got corrupted), then the pull down box
cannot populate. You should be able to see which user ID is bad in the
MethodServer logs.
The fix was to find the bad user ID in the logs, then in the
RemoteObjectID table restore the record where ida2a2=43701 using
information from a database back up made prior to the error. You may also
have to look into the RemoteObjectInfo table, since there may or may not
be a missing record there, as well. If there is a missing record, then
restore that record for the bad user from a database back up made prior to
the error.
Since you ran into this, it must be a PTC bug of some kind. But I don't
think it is reproduceable on demand, so it will be hard for them to fix
it.
Al Anderson
Solar Turbines Incorporated.
"Ely, Nick" <nicholas.ely@otis.com>
08/09/2011 09:01 AM
Please respond to
"Ely, Nick" <nicholas.ely@otis.com>
To
"Lockwood,Mike,IRVINE,R&D" <mike.lockwood@alconlabs.com>,
-
cc
Subject
[solutions] - RE: Reassign task error
