adpowershell issue, frequent loading of

This topic has 2 replies, 2 voices, and was last updated 3 years, 1 month ago by [email protected].

  • Author
    Posts
  • #17827

    Hi all,

    after finally upgrading from OpenIDM 3.1 to 4.5 and OpenICF Connectorserver from 1.4.1.0 to 1.5.2.0 and MsPowerShell.Connector.dll from 1.4.1.0 to 1.4.3.0, I discovered a problem. It disappeard after moving back to Connectorserver 1.4.1.0 and MsPowerShell.Connector.dll 1.4.1.0.

    The error is caused by powershell, “A connection to the directory on which to process the request was unavailable. This is likely a transient condition.”.

    There is little information, but according to http://webcache.googleusercontent.com/search?q=cache:vA5x9lg7N14J:wigposh.blogspot.com/2013/+&cd=8&hl=de&ct=clnk&gl=de the issue can be caused by frequently reloading the ActiveDirectory powershell-module, which I definitly need. Has anyone seen it? Is there a solution?

    I might be missing some configuration detail (did try modifying pooling). Haven’t found anything in the ticket-system and I’m not sure if it might be a bug in OpenIDM or in OpenICF?

    Any help would be greatly appreciated.
    Yours,
    Patrick.

    #17828
     Tom Wood
    Participant

    Hi Patrick,

    As noted, this is an issue with resourcing within the Active Directory Web Services module and occurs when you’ve exceeded the total available number of configured resources.

    As a workaround, you can modify the ADWS configuration here:

    C:\Windows\ADWS\Microsoft.ActiveDirectory.WebServices.exe.config

    And modify the following values to increase available resources:

        <add key="MaxPoolConnections" value="10" />
        <add key="MaxPercentageReservedConnections" value="50" />    
        <add key="MaxConnectionsPerUser" value="5" />

    Please note, increasing these values may have a performance impact on your AD implementation and should be thoroughly tested.

    #17881

    Hi Tom,

    whatever I did, nothing solved my issue, not even modifying the ADWS configuration. Like “not at all”.

    But I remembered http://openidm-users.989380.n3.nabble.com/OpenIDM-Conurrency-OpenICF-net-and-powershell-td4028290.html where I was told to explicitly set “UseInterpretersPool” to false, due to pool-issues and concurrency.

    Now I changed “UseInterpretersPool” back to true and all my troubles seem to be gone.

    At least with OpenICF 1.4.1.0, didn’t try 1.5.2.0 yet.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

©2020 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?