Thanks Webster, unfortunately that didn't help. There are no firewalls to contend with in this scenario. Also, I'm fairly confident nothing is blocking communication because I can run the Get-XAApplicationReport cmdlet with browser name and it returns results relatively quick. I'm assuming the process is actually timing out because the command I'm running has to parse through all of the applications by browser name and filter for the ApplicationID. I'm thinking the latency between the remote data collector and the database is a contributing factor. Running the same command against a data collector in the same site as the database returns results in about 20 seconds.
I'm willing to deal with the script taking longer to execute if I could find out where to adjust the timeout settings. - Sean On Wed, Jul 15, 2015 at 4:50 PM, Webster <[email protected]> wrote: > Execute Set-XADefaultCOmputerName RemoteDataCollector > > > > Then try the command > > > > Make sure TCP Port 2513 is open in Firewalls (Windows and physical). > > > > Thanks > > > > > > Webster > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Sean Martin > *Sent:* Wednesday, July 15, 2015 5:09 PM > *To:* [email protected] > *Subject:* [powershell] XenApp 6.5 Scripting > > > > I'm working on some automation scripts for VMware Site Recovery Manager, > one of which is automating the publishing of XenApp published applications > to workergroups based on where the back-end application is operating. > > > I originally had the script working by passing the BrowserName parameter > to Get-XAApplicationReport, and then executing the changes based on that. > However, we'd like to pass the actual ApplicationID because the names of > applications can change and I'd rather not have to worry about updating our > SRM Recovery Plans. > > > > I'm running into a problem running the following command against a data > collector that is in a different data center from the XenApp database: > > > > Get-XAApplicationReport * -Computer <name> | where {$_.ApplicationID -eq > "xxxxx"} > > > > I'm assuming the latency between our sites (75-85ms) is attributing to the > following error: > > > > *Get-XAApplicationReport : This request operation sent to > net.tcp://<redacted>:2513/Citrix/XenAppCommandsRemoting did not receive a > reply within the configured timeout (00:01:00). The time allotted to this > operation may have been a portion of a longer timeout. This may be because > the service is still processing the operation or because the service was > unable to send a reply message. Please consider increasing the operation > timeout (by casting the channel/proxy to IContextChannel and setting the > OperationTimeout property) and ensure that the service is able to connect > to the client.* > > > > * At line:1 char:31 + $app = Get-XAApplicationReport <<<< * > -Computer REDACTED | where {$_.ApplicationID -eq $appid} + > CategoryInfo : NotSpecified: (:) [Get-XAApplicationReport], > TimeoutException + FullyQualifiedErrorId : > System.TimeoutException,Citrix.XenApp.Commands.GetAppReportCmdlet* > > > > I'm not having much luck identifying where I might be able to increase the > timeout referenced in the error. Any help would be much appreciated. > > > > - Sean > > > ================================================ > Did you know you can also post and find answers on PowerShell in the > forums? > http://www.myitforum.com/forums/default.asp?catApp=1 > > ================================================ > Did you know you can also post and find answers on PowerShell in the > forums? > http://www.myitforum.com/forums/default.asp?catApp=1 > ================================================ Did you know you can also post and find answers on PowerShell in the forums? http://www.myitforum.com/forums/default.asp?catApp=1
