February 16, 2010 at 7:22 am
I have a script task that is calling an ashx "page" (.net 2.0 framework) inside a script task. The ashx file does some back end processing that I am not concerned with. Therefore I am calling it asynchronously. Here is the code. Note that I have 8 of these in there with different query string params.
obj = CreateObject("MSXML2.SERVERXMLHTTP")
obj.setTimeouts(5000, 60000, 30000, 27000)
obj.open("POST", <url>, True)
writeFile.WriteLine(String.Format("URL: {0}", <url>)) // used for logging
obj.send()
The problem is this. I run the job to kick of the SSIS while I am here at work, and all goes well. When I schedule it for 8 PM, It does not call the ashx files. My log file contains all the URLs so I know the task is completing. But I checked the IIS logs and there is nothing. Has anyone ever had this problem? Any help is appreciated. I realize there could be several reasons other than SSIS having problems here, but I wanted to poll the masses. I am running out of ideas here.
Thanks
February 17, 2010 at 2:05 pm
Not being terribly familiar with what you are working on, I'll just take a stab at it.
Could this have something to do with the permissions granted to whatever is running the package when you are away? That'd be the first thing I would check if I could run it manually and it worked and the automation was failing.
February 18, 2010 at 6:39 am
When we were testing before, we were just scheduling the job so it was a similar scenario. Sorry, I should have mentioned that.
Tried a different approach. Set the calls back to synchronous and split them out into 8 different script tasks. This seems to have worked. I would venture to guess that the asynchronous calls were giving me problems, but the solution I have now is working. I'm not going to look any further into it.
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply