Mailing List Archive

Hi Patrick,

On Wed, Jan 4, 2017 at 8:00 AM, <patrick.schoenenberg@web.de> wrote:
>
> Hello,
>
> after an RT-Upgrade I am not able to add Watchers to on Queue.

What version were you running?

What version did you upgrade to?

> Error Message: In german "Rollen Gruppe 'AdminCc' nicht gefunden"
> In English something like "Role Group 'AdminCc' not found"

What actions did you take to generate this error? Please be specific.

Thanks!

-m

Hello, > What version were you running? 4.0.18 > What version did you upgrade to?
4.2.18
>> Error Message: In german "Rollen Gruppe &#39;AdminCc&#39; nicht gefunden"
>> In English something like "Role Group &#39;AdminCc&#39; not found"

> What actions did you take to generate this error? Please be specific. I logged into RT as an admin:
-> Admin -> Queues -> Select Queue -> Watchers
Then: - New Watcher -> Find NAME -> Choose Option "AdminCc" --> Save Changes
ERROR: Role group &#39;AdminCc&#39; not found The Debug-Log says:

"[7814] [Wed Jan 4 14:28:00 2017] [warning]: Use of uninitialized value in join or string at /usr/share/perl5/DBIx/SearchBuilder.pm line 1087, <DATA> line 1662. (/usr/share/perl5/DBIx/SearchBuilder.pm:1087)
[7814] [Wed Jan 4 14:28:00 2017] [warning]: DBD::Pg::st execute failed: FEHLER: Syntaxfehler bei &Acirc;&raquo;)&Acirc;&laquo;
LINE 1: ...nt(main.id) FROM GroupMembers main WHERE (main.GroupId = )
^ at /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 586, <DATA> line 1662. (/usr/share/perl5/DBIx/SearchBuilder/Handle.pm:586)

Greetings,
Patrick

On Wed, Jan 4, 2017 at 8:30 AM, <patrick.schoenenberg@web.de> wrote:

> I logged into RT as an admin:
> -> Admin -> Queues -> Select Queue -> Watchers
>
> Then:
> - New Watcher -> Find NAME -> Choose Option "AdminCc" --> Save Changes
> ERROR: Role group 'AdminCc' not found

I just ran a quick test and it works for me with 4.2.11.

> The Debug-Log says:
>
> "[7814] [Wed Jan 4 14:28:00 2017] [warning]: Use of uninitialized value in
> join or string at /usr/share/perl5/DBIx/SearchBuilder.pm line 1087, <DATA>
> line 1662. (/usr/share/perl5/DBIx/SearchBuilder.pm:1087)
> [7814] [Wed Jan 4 14:28:00 2017] [warning]: DBD::Pg::st execute failed:
> FEHLER: Syntaxfehler bei »)«
> LINE 1: ...nt(main.id) FROM GroupMembers main WHERE (main.GroupId = )
> ^ at
> /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 586, <DATA> line 1662.
> (/usr/share/perl5/DBIx/SearchBuilder/Handle.pm:586)

Looking at the above SQL error it looks lie there is no main.GroupId
in the query. The formatting of the email causes the caret (^)
indicator to not point at the right error.

What would cause the GroupId to be scrubbed?

Do you have some custom JS or any Overlays or Callbacks that would interfere?

-m

Hi,

I finally found the problem.
Some Upgrade-Script deleted the "AdminCc, Cc, Owner, Requestor"-entries in the column 'name' in the
table group. Column updated (the correct entries are also in the column type) and it works.

Greetings
Patrick
 
 

Gesendet: Mittwoch, 04. Januar 2017 um 15:41 Uhr
Von: "Matt Zagrabelny" <mzagrabe@d.umn.edu>
An: patrick.schoenenberg@web.de
Cc: rt-users <rt-users@lists.bestpractical.com>
Betreff: Re: [rt-users] How to create a new RoleGroup?
On Wed, Jan 4, 2017 at 8:30 AM, <patrick.schoenenberg@web.de> wrote:

> I logged into RT as an admin:
> -> Admin -> Queues -> Select Queue -> Watchers
>
> Then:
> - New Watcher -> Find NAME -> Choose Option "AdminCc" --> Save Changes
> ERROR: Role group 'AdminCc' not found

I just ran a quick test and it works for me with 4.2.11.

> The Debug-Log says:
>
> "[7814] [Wed Jan 4 14:28:00 2017] [warning]: Use of uninitialized value in
> join or string at /usr/share/perl5/DBIx/SearchBuilder.pm line 1087, <DATA>
> line 1662. (/usr/share/perl5/DBIx/SearchBuilder.pm:1087)
> [7814] [Wed Jan 4 14:28:00 2017] [warning]: DBD::Pg::st execute failed:
> FEHLER: Syntaxfehler bei »)«
> LINE 1: ...nt(main.id) FROM GroupMembers main WHERE (main.GroupId = )
> ^ at
> /usr/share/perl5/DBIx/SearchBuilder/Handle.pm line 586, <DATA> line 1662.
> (/usr/share/perl5/DBIx/SearchBuilder/Handle.pm:586)

Looking at the above SQL error it looks lie there is no main.GroupId
in the query. The formatting of the email causes the caret (^)
indicator to not point at the right error.

What would cause the GroupId to be scrubbed?

Do you have some custom JS or any Overlays or Callbacks that would interfere?

-m