You may run into a problem where either send or receive specific timeouts are too low for the environment especially with a large number of GPOs.
An error about the sendTimeout or receiveTimeout may appear which looks similar or the same as follows:
System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9843734. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.
The default timeout values could be to low for the environment.
Increase the "sendTimeout" and "receiveTimeout" on the client and server side.
Client Side
For the GPOADmin Client, edit the "C:\Program Files\Quest\GPOADmin\Connections\Default.Client.Connection.Config" file using notepad.
Locate the "binding name="NetTcpBinding_GPOADmin"" and "binding name="NetTcpBinding_GPOADminStream"".
Paste the following after "maxReceivedMessageSize" for both of the above bindings: sendTimeout="00:10:00" receiveTimeout="00:10:00".
The client bindings should look like so:
Locate the "binding name="NetTCPBindingConfiguration"" and "binding name="NetTCPStreamBindingConfiguration"".
Paste the following after "maxReceivedMessageSize" for both of the above bindings: sendTimeout="00:10:00" receiveTimeout="00:10:00".
The server bindings should look like so:
NOTE: The timeouts are specified as HH:MM:SS. In this example we are setting a timeout of 10 min for the client and server side. You may have to increase the timeouts.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center