Group not found

When trying to add a watcher to a ticket, we are getting the following
error:

[Thu Mar 15 13:16:25 2007] [warning]: RT::Handle=HASH(0x9af33f8) couldn’t
execute the query 'SELECT main.* FROM GroupMembers main WHERE
((main.GroupId = )) ’ at
/usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 518

DBIx::SearchBuilder::Handle::SimpleQuery(‘RT::Handle=HASH(0x9af33f8)’,
‘SELECT main.* FROM GroupMembers main WHERE ((main.GroupId =…’) called
at /usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder.pm line 231

We are using rt 3.0.8 at the moment - to be upgraded shortly.

Has anyone else seen this/know how to fix it ?

Thanks,

Alison

Alison Downie, Computing Officer
School of Informatics, University of Edinburgh
Room B21, 5 Forrest Hill, EDINBURGH, EH1 2QL

Tel: 650 3095

A bit more information:

The ticket currently doesn’t appear to have a Requestor at all. I think
this might have happened by someone trying to change the original
Requestor to someone else but by accident entering the details of a
non-existing account ?

AlisonOn Wed, 28 Mar 2007, Alison Downie wrote:

When trying to add a watcher to a ticket, we are getting the following error:

[Thu Mar 15 13:16:25 2007] [warning]: RT::Handle=HASH(0x9af33f8) couldn’t
execute the query 'SELECT main.* FROM GroupMembers main WHERE
((main.GroupId = )) ’ at
/usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 518

DBIx::SearchBuilder::Handle::SimpleQuery(‘RT::Handle=HASH(0x9af33f8)’,
‘SELECT main.* FROM GroupMembers main WHERE ((main.GroupId =…’) called at
/usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder.pm line 231

We are using rt 3.0.8 at the moment - to be upgraded shortly.

Has anyone else seen this/know how to fix it ?

Thanks,

Alison

Alison Downie, Computing Officer
School of Informatics, University of Edinburgh
Room B21, 5 Forrest Hill, EDINBURGH, EH1 2QL

Tel: 650 3095

Alison:

That could be the case, though what looks like is happening is whatever
watcher you’re assigning doesn’t seem like they have a groupID at all
though that could just be a fluke given the ticket doesn’t have a
requestor which is odd because RT shouldn’t allow that to happen in the
first place as far as I know.

Regards,

Alan Brault
UNIX & Web Applications Developer
Hardware and Tools CorpOn Thu, 2007-03-29 at 17:34 +0100, Alison Downie wrote:

A bit more information:

The ticket currently doesn’t appear to have a Requestor at all. I think
this might have happened by someone trying to change the original
Requestor to someone else but by accident entering the details of a
non-existing account ?

Alison

On Wed, 28 Mar 2007, Alison Downie wrote:

When trying to add a watcher to a ticket, we are getting the following error:

[Thu Mar 15 13:16:25 2007] [warning]: RT::Handle=HASH(0x9af33f8) couldn’t
execute the query 'SELECT main.* FROM GroupMembers main WHERE
((main.GroupId = )) ’ at
/usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 518

DBIx::SearchBuilder::Handle::SimpleQuery(‘RT::Handle=HASH(0x9af33f8)’,
‘SELECT main.* FROM GroupMembers main WHERE ((main.GroupId =…’) called at
/usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder.pm line 231

We are using rt 3.0.8 at the moment - to be upgraded shortly.

Has anyone else seen this/know how to fix it ?

Thanks,

Alison

I must admit it does seem strange that the ticket is able to be
’requestor-less’! I wish I could make sense of the intricacies of RT a bit
better but I can only assume that at the point of changing the Requestor
name, it removed the old one successfully then didn’t complain too much
that it didn’t recognise the new requestor (that probably had a typo). Now
that we have spotted the mistake and are trying to correct it, it’s
complaining bitterly!
Anyway, I can change the Requestor on another ticket to the Requestor that
we are trying to allocate to the rogue ticket in question so the Requestor
that we are trying assign would appear to have a valid groupID :slight_smile:

Thanks for your comments, though - at least my train of thought isn’t too
far off the mark!!

AlisonOn Thu, 29 Mar 2007, Alan Brault wrote:

Alison:

That could be the case, though what looks like is happening is whatever
watcher you’re assigning doesn’t seem like they have a groupID at all
though that could just be a fluke given the ticket doesn’t have a
requestor which is odd because RT shouldn’t allow that to happen in the
first place as far as I know.

Alan,

I have run into the "Requestorless" tickets before and found that it 

only happens when I use the “Quick Ticket” function at the bottom of the
home page. I mentioned this to Jesse over a year ago and my
understanding was that it was addressed in 3.6.3. As to the no GroupID
stuff, are the tickets in the same Queue? Perhaps the group has
privileges in one Queue and not the other? Just a thought.

Kenn
LBNL

Alison Downie wrote: