[SIMS] CommandReporter Timeout

[PeterH]

I have a fairly big behaviour log report that always runs OK manually, but when run using CommandReporter it almost always times out. I assume CommandReporter is ignoring the CommandTimeOut in the Connect.Ini file. Is there any way to specify a CommandTimeout for use with CommandReporter?

[dapaulio]

Just thinking out loud

 

My first thought would have been timeout within the connect.ini on the sims server. If you have a redirect change it to include a longer timeout within the sims install location

 

Second thought is a timeout setting in sql database management

[Esteban_Child_of_the_Sun]

I logged a call about this in the middle of last year and never got a conclusive answer. The gist of what I got back was that commandreporter should use the commandtimeout value specified in the connect.ini stored in the location specified in the c:\Windows\sims.ini file for the SIMSDotNetDirectory. However, they couldn't answer if commandreporter can process redirects or unc paths in either .ini file and in addition there may be "Local conditions" that cause it not to be adhered to, but these were never specified.

In my case rather than keep chasing Capita for answers they don't have I divided my report into 2 smaller reports then used a PowerShell script to join the results together to generate the original report, thus removing the need to work out the details.

If you want to log your own call with Capita and would like the analyst who picks it up to see what was discovered previously, then point them to case 1708-3662390

[PeterH]

Thanks I'll have a look at the INI files and see if I can spot any problems there.