Post reply

"Cancelled by user" error

  • September 11, 2003 at 10:47 am

    #106944

    Has anyone come across the "cancelled by user" error when running a DTS package with an Execute Package task in it? The error always shows up when the package is run in DTS designer- it does not seem to happen when the same package is run with DTSRun. It seems to happen when the inner package hits a data pump task.

    I have seen the references to this problem on usenet but none of the suggestions there seem to work, including rearranging tasks within the inner packages. The error also never seems to be in the package from the start. It often appears after the package has run many times without error. Maybe someone cancels the execution and then the cancelled state get saved to the package? I don't know.

    I also get another error on the same task: Server Busy- This action cannot be completed because the other program is busy. Choose 'switch to' to activate the busy program and correct the problem." The funny thing about this is that the package does continue executing until it hits the "cancelled by user" error.

    Neither of these errors show up with the same package using DTSRun.

    Thanks for any ideas on this problem.

    -Mike

  • September 15, 2003 at 8:00 am

    This was removed by the editor as SPAM

  • March 23, 2005 at 3:30 pm

    #548622

    Yes, this happens to me too...  I'm desperately looking for an answer, so I'll find one if you haven't yet (years later)

  • March 23, 2005 at 4:00 pm

    #548627

    This seems to be one of those irritating intermittent bugs that has no definite reproducible steps. I have a couple of Packages that suddenly started coming up with this error . Nothing I did with those packages fixed the problem. Creating a new package and pasting in the steps from the old package fixed some of them but not all.

    The best solution I've come up with is to Replace the ExecutePackage task with either an ActiveXScript task, or an ExecuteProcess task. The ActiveXScript task uses the LoadFromSQLServer method to load and then execute the package and the ExecuteProcess task executes DTSRUN. Personally I'm leaning to the ExecuteProcess task. It just seems a bit clearer.

     

    --------------------
    Colt 45 - the original point and click interface

  • March 23, 2005 at 4:11 pm

    #548630

    I have also run across this and gave up on fixing it. There are articles out there that explain what causes it - can't recall, but it can happen if the sub-package ends in a certain type of step and only happens when the dish runs away with the spoon or some other obscure triggering event.

    There is a 3rd alternative - you can run the sub-package via an ExecuteSQL task, using system procedure sp_OACreate to instantiate the COM objects needed to run a package.

    Do a Google search on keywords "sp_OACreate dts" and you'll find several examples.

     

     

  • March 23, 2005 at 4:21 pm

    #548631

    The sp_OA... procs are kinda handy, but it gets a bit hairy when you're passing in more than a couple of global variables for your package.

    That's one of the reasons I like the ExecuteProcess task. I store the value for the ExecuteProcess task in a table along with my other Global Variables. Then there is one property set via a DynamicProperties task.

     

    --------------------
    Colt 45 - the original point and click interface

  • March 28, 2005 at 8:11 am

    #549128

    I've tried the ActiveX Script to run a package in the package, but I got the following error:

    Login failed for user '(null)'.  Reason: Not associated with a trusted SQL Server connection

    For authentication, I'm using the SQL server and windows.........So, I don't know why I still get this error.  Any clue?

    Now, I'm trying to use the other option: Execute Process task that's mentioned above....But I'm not sure how to do this.  Can someone kindly walk me throught on how to do this?

    Thanks in advance

  • March 28, 2005 at 4:42 pm

    #549219

    For the ActiveXScript task you'll need to supply the correct parameters for the Load method.

    object.LoadFromSQLServer ServerName, [ServerUserName], [ServerPassword], _

        [Flags], [PackagePassword], [PackageGuid], [PackageVersionGuid], _

        [PackageName], [pVarPersistStgOfHost]

    The "Flags" parameter takes one of two values, specify zero for SQL Authentication and then provide a username and password, or specify 256 for Windows Authentication and make sure your Windows login is authenticated to SQL.

    For the Execute Process task. Set the Win32 process by browsing to the location of DTSRUN.exe (usually 'C:\Program Files\Microsoft SQL Server\80\Tools\Binn'). Then enter the parameters for DTSRUN in the parameters field. Best way to get the parameters is to generate a command line using DTSRUNUI.

     

     

     

    --------------------
    Colt 45 - the original point and click interface

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply