June 27, 2017 at 5:51 pm #17827[email protected]Participant
after finally upgrading from OpenIDM 3.1 to 4.5 and OpenICF Connectorserver from 188.8.131.52 to 184.108.40.206 and MsPowerShell.Connector.dll from 220.127.116.11 to 18.104.22.168, I discovered a problem. It disappeard after moving back to Connectorserver 22.214.171.124 and MsPowerShell.Connector.dll 126.96.36.199.
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.
Patrick.June 27, 2017 at 6:04 pm #17828Tom WoodParticipant
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:
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.June 30, 2017 at 3:59 pm #17881[email protected]Participant
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 188.8.131.52, didn’t try 184.108.40.206 yet.
You must be logged in to reply to this topic.