Pam,
A reinstall of Incident is a pretty big hammer to use on this problem.
If you really want to do it, you can probably fool the install into
proceeding by deleting (back them up first) the Incident Management
related records from the SHARE:Application_Properties form. I do NOT
actually recommend this though. I would guess that you will get a boat
load of dup data errors and will very likely end up with duplicate
configuration data. You are likely to have bigger problems than the
permissions issue. In general, unless you can go back to a db backup of
what the system looked like just prior to install of the app (losing all
modifications made after install), then a reinstall of the app is not a
good idea. I'm not speaking from direct experience with IM 7.0... just
Remedy apps installs in general.
The second reason not to do that is that if there is some role/group
corruption that got created during your config process, it will likely
still be there (unless you start with a pre-IM db backup.) The new
install will not delete groups/roles that are already there.
The incident app is made up of a collection of deployable applications.
If you've defined a new role, it might help things to add that role to
the list of groups/roles permissions for those applications... ??? This
is just a wild guess on my part - but something to try.
Colleen Eilbert
Consultant
Effective Technologies
Pam Hollis wrote:
The reason it stopped working is I was trying to get a Role setup and
was having problems and believe they got corrupted. - but not 100% sure.
You don't get an error message - unless the forms doesn't have any other
permissions and then you get the message stating that the User isn't
Licensed for that Form. But, otherwise if it has Public permissions or
another permission the user is a member of - it comes up fine. The
problem is that the forms/applications do not display on the Home Page
or the navigation links either - unless they have Public permissions.
It is very weird. We are trying to reinstall Incident but get a fatel
error message that my version is different.
Pam Hollis
Senior Programmer - Remedy
Tractor Supply Company
(615 )366-4617 (telephone)
(615) 277-4617 (fax)
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Colleen M. Eilbert
Sent: Tuesday, October 17, 2006 9:23 AM
To: [email protected]
Subject: Re: Incident Management Permissions 7.0 patch 2
Pam,
What is the error message you receive if any? Is it coming from the
server or from workflow? Or are they just unable to login?
Here are a couple things to validate - does the data in the Person entry
match the data in the User entry? particularly regarding group
permissions, login and license type? Are there entries in
CTM:PeoplePermissionGroups for people and their permissions. Should be
1 per person per group for ITSM type groups (not for Administrator or
other non-ITSM groups.)
It's strange that it worked at first and stopped. That would make me
suspect a licensing issue. If you have permissions to be everything
under the sun (AR Goddess), but your license suddenly becomes a read
license, you look like an AR Nobody to the system.
Hope that helps.
Colleen Eilbert
Effective Technologies
Pam Hollis wrote:
I am building our Test Box with the New ARSystem 7.0.1 and ITSM Suite
7.0
Patch 2 - everything was working fine - but now the permissions on the
Incident Managment are not working - (Incident User, Viewer, Master,
Admin
etc) - they are there but when assign to People it is like those users
do
not have permissions.
I have tried reinstalling Incident Managment but receive fatel errors
due
to the version.
Any ideas.
Oracle 10g
Linux Red Hat System
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
