The product level is insufficient for component "Data Conversion 1" (117)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Javilen
    New Member
    • Sep 2007
    • 20

    The product level is insufficient for component "Data Conversion 1" (117)

    Hello,

    edit: added some more info

    I am trying to set up a job to run a SSIS package in SQL 2005, the SQL 2005 is installed on a Windows server 2003 machine.

    start Edit
    I have the Management studio (I am working from) installed on windows XP (fully up today with the SPs). I have the installed on this machine the integrated Services, I do not know if they have been installed on the Windows 2003 machine that has the DB.
    end Edit

    The job is failing with the following error message:

    Code:
    Description: SSIS Error Code DTS_E_PRODUCTLEVELTOLOW.  The product level is insufficient for component "Data Conversion 1" (117).  ...  The package execution fa...  The step failed.

    Some background:

    The Package
    The Package it's self has the job to Pull all the data from a table between specified dates, in this case, last weeks data. it then exports the results to an Access Database.

    when I create the package, if I do the "run it now" option it works, it runs with out error and successfully exports the data.

    I then created the same package with all the same options except this time I saved it to the file system.

    The Job

    My next step is to set up the job, I set this up to pick the package and run it, once a week at a specified time.

    I save the new job and then manual ask it to run(for a test)

    when the job runs it errors with the above mentioned error message.

    for all of this I am using the System Admin user to create and deploy this job/package.

    any suggestions would be greatly appreciated as remote desktoping to work on the weekends to manually create and run the package is not how I want to spend my weekends.

    Thanks
  • Javilen
    New Member
    • Sep 2007
    • 20

    #2
    For the interested people.

    We installed the integrated Services onto the server and then remote desk topped into the machine and logged in as the DB owner.

    We created the package from scratch and the job under this login.

    When we ran the job it worked without error.

    Thanks

    Comment

    Working...