I'm running SQL 2005 sp2 on a Windows 2003 active/passive cluster.

We have some legacy DTS packages that are being called directly from a
scheduled SQL job. They have been running fine for a few weeks, until this
morning the jobs started failing, and I can't seem to figure out why.

If I run the DTS package manually, it runs without error, even when I'm
logged into the server using the account that both SQL and the SQL Agent are
running under.

Does anyone have any ideas on where I might start to debug this?

Here is the error I'm getting:
DTSStep_DTSActiveScriptTask_1 DTSRun OnFinish:
DTSStep_DTSActiveScriptTask_1 DTSRun OnStart:
DTSStep_DTSActiveScriptTask_3 DTSRun OnError:
DTSStep_DTSActiveScriptTask_3, Error = -2147220482 (800403FE) Error
string: Error Code: 0 Error Source= Microsoft VBScript runtime error
Error Description: File not found



This error is a little misleading. The file it is looking for (File Not
found error), is a log file that is created earlier in the VBscript. The
file is being created by running a .bat file, which as best as I can tell is
not being executed, and is not logging any errors.

Does anyone have any ideas on what to check? It seems funning that the
package would run fine manually, but then fails when run from a job.

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Jason,
I understand that your SQL job failed accidently with the error "File not
found" while it had been working fine for a few days.
If I have misunderstood, please let me know.

For further research, I recommend that you mail me
(changliw_at_microsoft_dot_com) the following information:
1. SQL error logs which are located in the folder %ProgramFiles%\Microsoft
SQL Server\MSSQL(.x)\MSSQL\LOG by default.
2. Trace file from Process Monitor.
You can use Process Monitor to monitor SQLAGENT90.EXE and DTEXEC.EXE.

You can download Process Monitor at this link:
Process Monitor v1.33
http://technet.microsoft.com/en-us/s...PHPSESSID=d926
bdd849b5aab10f7263dd7f5904f2

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi,
Just a kind reminder, I have not received your response. Please feel free
to post back at your convenience if you need further assistance.

Have a great day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======