• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 94 subscribers
  • Views 9154 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DGE No Suitable group found

Jaipal.Sivaiah
over 8 years ago

Hi All,

        I have configured Windows Managed host and added a folder under governance and published folder to IT Shop. System able to get resource activity etc.. As well as assigned Read and ReadWrite groups to published folder. Then executed a Request Access from D1IM web portal for published folder.

But VI_PersonWantsOrg_PrefillITShopOrgFinalForGroup script unable to get suitable groups and ended up with error while running funciton called VI_GetMostSuitableGroupDN.  Here are the details:

 

Error: A call to SSPI failed, see inner exception

Parameters for call were:  xxx - NTFS\Folder - RequestWriteAccess -xxxxx

No Suitable group found.

 

I'm using Windows Authentication to connect SQL, NOT SQL ACCOUNT.  So DGE Server Service running under Service Account NOT LOCAL Account

Agent is running same service account.

Environment Details:

Version: D1IM 7.1

DB: MS SQL Server 2012

Any idea what could be causing this issue?

 

Thanks,

Jaipal.

Parents
  • 0 over 8 years ago
    Is the identity manager job service (the one specified as the data governance connector) on the same machine as the DGE service? If so, try using a different job service, if possible. One that's not on the same machine.

    DGE agent isn't involved in this scenario.

    Last resort is to change the DGE SQL connection back to SQL authentication. Can either use the powershell commands for reinitializing the DGE service, first setting it to run as local system. Or just run through the DGE deployment wizard again.
Reply
  • 0 over 8 years ago
    Is the identity manager job service (the one specified as the data governance connector) on the same machine as the DGE service? If so, try using a different job service, if possible. One that's not on the same machine.

    DGE agent isn't involved in this scenario.

    Last resort is to change the DGE SQL connection back to SQL authentication. Can either use the powershell commands for reinitializing the DGE service, first setting it to run as local system. Or just run through the DGE deployment wizard again.
Children
No Data