Scheduled job fails with Dynamic properties task

  • We used Dynamic properties task to set UDL file paths from Environment Variables in DTS Package . Package executes succesfully from Enterprise Manager manually, but fails when scheduled giving an error - "Environmental variables not found". The same package without dynamic properties task runs successfully when scheduled. Help needed in this context.

    Thanks

  • Remember that environment variables are specific to a login, and that a scheduled task is not run with the same login as when you run it from the Console.

    Question: Does the package run successfully from the Enterprise Manager if you are at the Server console?

    Question: How are the environment variables set up?

    quote:


    We used Dynamic properties task to set UDL file paths from Environment Variables in DTS Package . Package executes succesfully from Enterprise Manager manually, but fails when scheduled giving an error - "Environmental variables not found". The same package without dynamic properties task runs successfully when scheduled. Help needed in this context.

    Thanks


  • Hi!

    Thanks for ur reply. From the Enterprise Manager it was successfull. Logins used for both scheduled job and EM are same . I couldn't able to understand "How are the environment variable set up?". Please explain more.

    We have created the environment variables in WIN 2000 environment, using them with Dynamic properties task. When logged on to Enterprise Manager, there is no prblem with this. But when scheduled (Dynamic Properties Task) not finding environment variables.

  • Check the Registry value on the server in this hive:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

    This is where environment variables related to this sequence are located. Are the values you need in this key?

  • Also, you should look at this MS article on Security relating to running DTS packages:

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;269074

    There are a number of things to check that can cause this type of error.

  • Got the solution to the problem. My SQL Server agent was running with system account. Modified the login info..logged on as .\administrator. That solved my problem. Your reply helped us in thinking in that direction.

    Thanks for your reply.

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

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