ServiceDesk

Hi All,

Has anyone seen this error before, even some pointers in a direction that may help me would be great. I get quite a few of these in the Service Desk Log Viewer per hour.

Application Name : Ensemble2006
Process ID : 2936
Date :26/05/2011 8:06:27 AM
Log Level :Error
Log Category :ReportLogProcessPermission
Machine Name : XXX-XXX-XX
Message :
[global] Error saving process permission.
[global] -- error.ToString() --
[global] System.Exception: Permission for 'Support I' already exists.
[global]    at LogicBase.Ensemble.Reports.ServiceCore.ReportLogProcessPermission.AddNew(String sessionID, ReportLogProcessPermission[] permissions, Boolean performMapping) 

I get this error all the time. I always thought that I caused it by renaming the Support I group something else through the servicedesk application settings and then creating another group with the same permission set as Support I and with the same name as the one that I named Support I. Confusing, I know.

Example:

I created a group called Helpdesk in Admin - Users - Groups and gave it the same permissions as Support I

I then open the ServiceDesk settings and renamed Support I to Helpdesk 

I then added another group into ProcessManager (Admin - Data - Application Properties, lightning bolt, edit, next, add a new user group) and then rename that Helpdesk as well.  So basically I have more than one group existing in ProcessManager with the same name. 

I see this error fairly often.  Anyone have any ideas what the resolution is?

I've had to ignore it. I think the issue is that the name for the support group has changed in the Application Properties of servicedesk from Support I to something else and then the permissions are applied more than once. I really don't know for sure but haven't bothered to pursue it either.

In various places ServiceDesk tries to update permissions on the incident, often just with Add Permissions component without checking if there already is a permission for the group. As Support I permissions are most likely already there, this error shows up. It is harmless.