DTS Package - "Provider generated code execution exception: "EXCEPTION_ACCESS_VIOLATION"
-
When running a step within my DTS package I'm receiving the following error - "Provider generated code execution exception: "EXCEPTION_ACCESS_VIOLATION".
I think it may be something to do with my global variable, but I'm not sure as I'm pretty certain I've set it all up correctly.
Below are screenprints showing my settings.
http://img153.imageshack.us/my.php?image=19tv1.jpg
http://img153.imageshack.us/my.php?image=25wz1.jpg
http://img153.imageshack.us/my.php?image=39pf.jpg
http://img164.imageshack.us/my.php?image=43nx.jpg
http://img164.imageshack.us/my.php?image=51ao.jpg
http://img164.imageshack.us/my.php?image=64lo.jpg
http://img164.imageshack.us/my.php?image=71yn.jpg
Any advice of fixing this would be greatly appreciated.
-
I was having a bit of a hard time reading your screen shots so I'm takign a few stabs in the dark. I noticed you have a bunch of connections. Are they all connecting to the same datasource/destination, and if so are there any limitations to the number of connections to that resource? I ran into the problem once, when I wasn't closing my connections before I opened another and found I was limited to connecting to one of my datasources only 5 times before it started giving the same error.
Also have you tried checking the execute on main package thread checkbox?
Also there is a way to turn on Logging for a DTS package on the options tab, if you turn that on, what do you see in the log file?
-
Thanks for the response Luke.
Yes, they're all connecting to the same datasource. The wizard created them.
Yes I tried checking execute on main package but it didn't seem to have any affect.
I'll have a look into logging - thanks
Btw, these are my specific settings if you helps:
http://www.files2net.com/files/46053431/1.JPG
-
From the transform data task properties, to top section where is states exceptionfile name. type the path to a log file on your machine. Then save and run your package and see what is generated in the log file. You may see error numbers that you can post that may be a bit mroe descriptive than just the access violation.
Also, on the workflow properties option page for each transaction, verify that close connection on completion is checked and execute on main package thread is checked as well.
-
Thanks for your response Luke, managed to solve it by changes the settings to the following:
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply