I got a dts package running ok manually. But it does not work when scheduled.
I read article 269074. But I wonder if trouble could come from ODBC FoxPro
driver :
My dts job includes accesses to FoxPro source, and SqlServer source (data
pumps). Accesses to SQLServer source work ok, which is not the case for
FoxPro source. However, I installed the VFPODBC.msi driver, downloaded from
Microsoft.
Error message includes warning about FoxPro source not found.
Anyone could help ? ? ?

It still could be what is covered in 269074. What is the
path to the FoxPro files? Is it on a network drive, are you
using a UNC path, does the service account have access to
this location? I'd start by looking at issues related to
that.

-Sue

On Tue, 16 May 2006 03:40:02 -0700, Jason
<Jason (AT) discussions (DOT) microsoft.com> wrote:

Hi Jason,

Thank you for using MSDN Managed Newsgroup Support. And thanks for Sue's
suggestion.

Since you could run the DTS package successfully, the most possible cause
of this issue is the SQL Agent Services Start account does not have proper
permission.

Would you please check the job history to see are there any errors there?

Also you may try to change the SQL Agent Services start account to the one
you could run DTS package successfully.

Setting up Windows Services Accounts
http://msdn.microsoft.com/library/de...us/instsql/in_
overview_6k1f.asp

Hope this will be helpful.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks to you two. You were right.

I could finally manage. The problem was this :

1. My scheduled DTS package had been running OK for one year.
2. It seems that trouble came from SqlServer SP4 implementation, which
strengthened security : the network drive I was using before, did not work
any longer after SP4. The problem was solved by using a UNC path instead.

Many thanks for help.

"Wei Lu" wrote:

Hi Jason,

Thank you for the update and glad to hear that you resolved by using a UNC
path instead of the network drive.

If you have any questions or concerns, please feel free to let me know.

Sincerely,

Wei Lu
Microsoft Online Community Support

==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.