VB.NET service stops running after 10 minutes

  • Thread starter Thread starter Sam Straub
  • Start date Start date
S

Sam Straub

Hello,

I've written a windows service that runs on a server, every 24 hrs it
generated a ton of files, sometimes in the neighborhood of 3-5,000. When
there are that many files to generate, the script seems to stop running
after 10 minutes, I see the dates on the files generated range by 10 minutes
almost exactly. That tells me there's a 10 minute time limit on the windows
service. How do I change this? Or is there a better way to do it?

Thanks,

Sam
 
In my service, I have a reference to an asp.net dll, with which I use a
procedure to generate the files. I'm assuming that since the service sends
the request to the asp.net dll, and the dll takes longer than 10 minutes to
work, the service times out. To test this theory, I put the procedure in
the service code and removed the reference to the asp.net dll. It took 13
minutes for it to finish, but it did. Can someone give me an idea of what's
going on? Is there a way to keep the procedure in the asp.net dll, use the
reference, but call the procedure in such a way that the service doesn't
time out waiting for a response?
 
Hi Sam,

It sounds very complex, but also as something for multithreading.

Did you had a look for it what that can do for you?

Cor
 
Back
Top