**
In my environment (6.3) the Group form uses 20 for
tables. Use the number of your original Group tables. I am not sure
if the number itself is that relevant, except perhaps that the ARS system
"knows" which number it is expecting for Group.
Stephen From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LAU, DARREN (ASI) Sent: Monday, October 16, 2006 8:22 AM To: arslist@ARSLIST.ORG Subject: Re: Notify Action To Group Not Working Thanks for the
suggestion. Our original table number for the Group form was 80.
Wouldn’t we want to use that instead of 20? Also I installed a fresh, out
of the box installation of AR 7.0 on a test machine and the table number for
Group was 21. FYI. Darren
Lau AT&T Advanced
Solutions Inc. 925-479-6025 [EMAIL PROTECTED] From: Action
Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen Darren, Here is something that
*may* work - I haven't tried it. 1. Create a full SQL
database backup, just in case. 2. Delete the new Group
form within the Administrator Tool. 3. Write down the value
of schemaId in the 'control' table. 4. Change the schemaId
value in the 'control' table to 19 (1 less than the Group form's table
number). 5. Re-import the Group
form. Hopefully this will force ARS to create the tables using number
20. 6. Change the schemaId
value in the 'control' table back to the previous
value. 7. Restart the Remedy
service(s). HTH. Stephen From: Action
Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen ** Darren, Can you restore the
original tables that comprise the group from from the most recent SQL database
backup? This should preserve the table
numbers. Stephen From: Action
Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LAU, DARREN (ASI) ** Listers, Need some help quick! We just
upgraded to AR 7.0 in a server group, load balanced environment. We have
run into several problems with the migration, one of them being that all the
filter or escalation notify actions that have a Remedy User Group in the “User
Name:” field does not get resolved when emails are being sent out. If a
Remedy Group(s) is specified, then individual emails to each and every member in
that group is supposed to generated. Instead all we get is one email being
generated and the “To:” line has the name of the Remedy Group in it.
Obviously it fails each and every time. Has anyone ever run into this
problem before or have any clue on how to fix this? As a side note one of our other
problems that could be related was that our Group form was corrupted in the
upgrade process. So I had to delete the form manually and import it back
and import all the records. In the process the table changed from T80 to
T825. I’m wondering if this could have broken Remedy’s ability to resolve
Groups into individual users for the notify action. Any help at this point would be
greatly appreciated. I’m currently waiting to get my account back with
Remedy Support so I can open up a ticket with them.
Thanks. Darren
Lau __20060125_______________________This posting was
submitted with HTML in it___ __20060125_______________________This posting was
submitted with HTML in
it___ |
- Re: Notify Action To Group Not Workin... Heider, Stephen
- Re: Notify Action To Group Not W... David Sanders
- Re: Notify Action To Group Not W... Julie Rockwood
- Re: Notify Action To Group N... LAU, DARREN (ASI)
- Re: Notify Action To Gro... Julie Rockwood
- Re: Notify Action To Group Not W... McKenzie, James J C-E LCMC HQISEC/L3
- RESOLVED: Notify Action To G... LAU, DARREN (ASI)