Post reply

Problems with Import Wizard??

  • December 3, 2004 at 5:39 am

    #165594

    I am having a problem when I use the import wizard.  I am trying to pull information from a TopSpeed Database (maitnenance work orders and History).  When I go through the wizard I have it drop a table then recreate the table, and then I save the DTS package for later execution.  When I execute the package it starts to run and suddenly Enterprise manager will shut down I can re-run the package and it will work fine one time and the next it will shutdown again.  Has anyone had a problem like this before.  I do not get any error messages.  Thanks in advance!

    Kurt Kracaw

  • December 3, 2004 at 8:53 am

    #532482

    corrupt file on the sql install, possibly?

    version/sp? os? etc.

  • December 3, 2004 at 9:50 am

    #532507

    Or something in the package that causes a fatal error. Do you know when it fails? Add in logging in the package maybe to see when it fails?

  • December 6, 2004 at 8:25 am

    #532676

    Good Morning,

    I have tried a few different things this morning and the error does not occur at the same time everytime.  Sometimes when I execute the package it dies right away sometimes it is when the table is being filled, and then this morning it died when I hit the preview button while generating the new package.  We have several packages that run hourly and none of them have a problem it is only the one I am working on.  I am still fairly new to DTS and SQL in general, how do I add logging to the package.  Maybe I do not have a setting completed right?  I tried creating a new database on a differernt server (presently) everything is on a development server.  When I recreated the database and made a new package Enterprise manger died again.  Different computer and a different server.  Is it possible that the ODBC or one of its settings we purchased is causing the error? 

    Kurt Kracaw

  • December 22, 2004 at 8:01 am

    #534761

    Follow-up:  I recently moved the DTS package from the development server to the LIVE server.  Now that the package is moved it only failed the first time and had run succesfully the remainder of the time.  I am thinking that over the holidays we will re install SQL and test it on the development server again to see if it makes a difference

    Kurt Kracaw

Viewing 5 posts - 1 through 4 (of 4 total)

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