Marcus Tornberg Super Contributor.
Super Contributor.
721 views

Group - Insert conflicted with foreign key

Hi.

Running Identity Governance client version 3.0.1 revision 25950 and Identity Governance server version 3.0.1 from revision 25952.

Using eDirectory Identity with changes Collector - Template Version 3.0.1.

Getting this error on collecting Groups using Collect Group with the following mapping:
Group ID from Source - OBJ_ID
Object GUID - GUID
Group Members (Users and Groups) - member
Name - cn
Short Description - description

Error:
Collecting entity 'GROUP' - com.netiq.persist.PersistenceException: The INSERT statement conflicted with the FOREIGN KEY constraint "fke0e3062eb6adc31c". The conflict occurred in database "igops", table "dbo.SGROUP", column 'ID'.

I get this error message on pretty much all my groups. I have inherited the solution, so I do not know if this as ever worked.

Please help! 🙂

Best Regards
Marcus
0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Re: Group - Insert conflicted with foreign key

On 12/6/18 10:44 AM, marcus jonsson wrote:
>
> Hi.
>
> Running Identity Governance client version 3.0.1 revision 25950 and
> Identity Governance server version 3.0.1 from revision 25952.
>
> Using eDirectory Identity with changes Collector - Template Version
> 3.0.1.
>
> Getting this error on collecting Groups using Collect Group with the
> following mapping:
> Group ID from Source - OBJ_ID
> Object GUID - GUID
> Group Members (Users and Groups) - member
> Name - cn
> Short Description - description
>
> Error:
> Collecting entity 'GROUP' - com.netiq.persist.PersistenceException: The
> INSERT statement conflicted with the FOREIGN KEY constraint
> "fke0e3062eb6adc31c". The conflict occurred in database "igops", table
> "dbo.SGROUP", column 'ID'.
>
> I get this error message on pretty much all my groups. I have inherited
> the solution, so I do not know if this as ever worked.
>
> Please help! 🙂
>
> Best Regards
> Marcus
>
>

Greetings,

1) What is the exact version of MS SQL that is being used?

2) If you are using the eDirectory Identity with changes, are you
pointing to an eDirectory server that does not have IDM installed?
Also, have completed the rest of the requirements to use this Collector?

3) How many rows of data are already in the sgroup table?

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Marcus Tornberg Super Contributor.
Super Contributor.

Re: Group - Insert conflicted with foreign key

Hi Steven!

Thanks for your reply.

1) Microsoft SQL Server 2016 (SP2-CU3) (KB4458871) - 13.0.5216.0 (X64)
Sep 13 2018 22:16:01
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
In the documentation, it states MS SQL 2016 SP1 is supported. Does this mean that SP2 is NOT supported?

2) Yes, this is running the collector eDirectory Identity with changes and it is pointing to a eDirectory server with Identity Manager. However "Enable change event processing" for the collector is not checked (DISABLED). Identity sources are configured as unmerged identity source.

3) There are 95790 rows in the sgroup table. According to the Group collector filter, there are 2284 groups that should be collected from eDirectory.

I have somehow resolved my issue, but I cannot figure out what solved it. I removed Group Member mapping from the Group collector, and performed collect/publish with no errors. Then I re-added the Group Member mapping, and it all worked fine. Not all group members are part of the Identity Collector scope, not sure if this could be part of my issue?

Best Regards
Marcus
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Group - Insert conflicted with foreign key

On 12/10/18 6:34 AM, marcus jonsson wrote:
>
> Hi Steven!
>
> Thanks for your reply.
>
> 1) Microsoft SQL Server 2016 (SP2-CU3) (KB4458871) - 13.0.5216.0 (X64)
> Sep 13 2018 22:16:01
> Copyright (c) Microsoft Corporation
> Enterprise Edition: Core-based Licensing (64-bit) on Windows Server
> 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
> In the documentation, it states MS SQL 2016 SP1 is supported. Does this
> mean that SP2 is NOT supported?
>
> 2) Yes, this is running the collector eDirectory Identity with changes
> and it is pointing to a eDirectory server with Identity Manager. However
> "Enable change event processing" for the collector is not checked
> (DISABLED). Identity sources are configured as unmerged identity source.
>
>
> 3) There are 95790 rows in the sgroup table. According to the Group
> collector filter, there are 2284 groups that should be collected from
> eDirectory.
>
> I have somehow resolved my issue, but I cannot figure out what solved
> it. I removed Group Member mapping from the Group collector, and
> performed collect/publish with no errors. Then I re-added the Group
> Member mapping, and it all worked fine. Not all group members are part
> of the Identity Collector scope, not sure if this could be part of my
> issue?
>
> Best Regards
> Marcus
>
>

Greetings,

Please be aware that using this collector with an IDM set-up is not how
it was intended to be used and could cause problems in the future. I
understand that the "with changes" option is disabled currently. One
should be using either the "Identity Manager Identity" or the "IDM
Identity with changes" collector


Also, please be aware that if you are collecting permissions from IDM
and want to utilize "Automatic Fulfillment" with IDM you can experience
errors/problems when an eDirectory Identity Collector is utilized
instead of one of the IDM Identity Collectors.



--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Marcus Tornberg Super Contributor.
Super Contributor.

Re: Group - Insert conflicted with foreign key

stevewdj;2492255 wrote:
On 12/10/18 6:34 AM, marcus jonsson wrote:
>
> Hi Steven!
>
> Thanks for your reply.
>
> 1) Microsoft SQL Server 2016 (SP2-CU3) (KB4458871) - 13.0.5216.0 (X64)
> Sep 13 2018 22:16:01
> Copyright (c) Microsoft Corporation
> Enterprise Edition: Core-based Licensing (64-bit) on Windows Server
> 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
> In the documentation, it states MS SQL 2016 SP1 is supported. Does this
> mean that SP2 is NOT supported?
>
> 2) Yes, this is running the collector eDirectory Identity with changes
> and it is pointing to a eDirectory server with Identity Manager. However
> "Enable change event processing" for the collector is not checked
> (DISABLED). Identity sources are configured as unmerged identity source.
>
>
> 3) There are 95790 rows in the sgroup table. According to the Group
> collector filter, there are 2284 groups that should be collected from
> eDirectory.
>
> I have somehow resolved my issue, but I cannot figure out what solved
> it. I removed Group Member mapping from the Group collector, and
> performed collect/publish with no errors. Then I re-added the Group
> Member mapping, and it all worked fine. Not all group members are part
> of the Identity Collector scope, not sure if this could be part of my
> issue?
>
> Best Regards
> Marcus
>
>

Greetings,

Please be aware that using this collector with an IDM set-up is not how
it was intended to be used and could cause problems in the future. I
understand that the "with changes" option is disabled currently. One
should be using either the "Identity Manager Identity" or the "IDM
Identity with changes" collector


Also, please be aware that if you are collecting permissions from IDM
and want to utilize "Automatic Fulfillment" with IDM you can experience
errors/problems when an eDirectory Identity Collector is utilized
instead of one of the IDM Identity Collectors.



--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus


Hi Steven.

Thanks for your reply, and sorry for my late reply.

I have now reconfigured this client to using the Identity Manager Identity collector instead.

Best regards
Marcus
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.