Page 1 of 1

batch file stall for no apparent reason

Posted: Thu Oct 12, 2017 4:11 pm
by ggodw000
i maintain some dos batch files to automate stuff however in recent ed. of Windows (10, 2016 etc) it stall for no apparent reason. Literally execution of script halts and nothing happens. If I "nudge" but pressing an enter key at the command prompt then it continues. It is highly sporadic and intermittent event. Not sure how it is explained.

Re: batch file stall for no apparent reason

Posted: Fri Oct 13, 2017 12:36 am
by iansjack
Well, thanks for telling us but do you expect sensible comment from people who haven't seen your batch files?

Re: batch file stall for no apparent reason

Posted: Fri Oct 13, 2017 3:48 am
by AJ
ggodw000 wrote:Not sure how it is explained.

Code: Select all

pause
?

As iansjack says, we need more information. Is the batch file in question a reasonable size to post in code tags?

Adam

Re: batch file stall for no apparent reason

Posted: Fri Oct 13, 2017 12:51 pm
by ggodw000
there is no pause or anything like that. just normal simple batch commands. No loops or convoluted code just series of commands.

Re: batch file stall for no apparent reason

Posted: Sat Oct 14, 2017 2:58 am
by AJ
Hi,

Let me check my crystal ball...

This really still doesn't help. Please post the exact bacth file you are running (not an edited or re-typed one for the forum) in code tags if you want any assistance.

Adam

Re: batch file stall for no apparent reason

Posted: Wed Nov 15, 2017 11:22 am
by Thomas
Hi ggodw88,

I suspect some of the programs you call batch file is causing the issue. There is no information, if you are on a deadline and do not have enough time to diagnose it, then write simple program that attaches to the Batch file window ( using C#, use the {Process class to get process details, gets the content , see if its stuck or not and then sends it an enter using SendKeys.SendWait or something .. ). This an absolute last resort if you have nothing else available and not at all recommended, sometimes when I was a test developer I had to resort means like this when some of the utilities inherently have lot of bugs. Ugly for sure!

--Thomas