Hi,
We have few DTS packages, which I moved from one SQL Server instance to
another SQL Server Instance. Below are the configurations of Old SQL server
OS – Windows 2003 Sp2 x 32 bit
SQL Server – SQL Server 2000 Developer Edition
Oracle client – Oracle 32 bit client
Below are the configurations of new SQL server Instance
OS – Windows 2003 SP2 X64 bit
SQL Server – SQL Server 2000 Enterprise Edition 32 bit (no x-64 bit client
available)
Oracle Client – Oracle 10g 32 bit client.
Note- It’s SQL Cluster
After movement DTS packages are running fine when I tried to run it through
DTS designer, but when I tried to scheduled the DTS packages it’s failing
with driver issue.
Could any one help to fix this issue?
Feel free to revert back if need more information.
Regards,
Nandan Pandey
Nandan - 15 Jul 2008 11:37 GMT
Hi,
I issue has been resolved, I have taken following steps to fix it
1- Copied C:\Program Files (x86)\Microsoft SQL Server\80\Tools and all
sub-directories to D:\Microsoft SQL Server\x86ClientTools.
2- Added D:\Microsoft SQL Server\x86ClientTools to the PATH environment
variable.
3- Restarted SQL Server Agent service.
This has to be done because SQL Server Agent Jobs which access DTS don't
like paths with a ( or ) in the path name.
You can choose any directory that you want, but I used D:\Microsoft SQL
Server\x86ClientTools.
Still I am wondering like such an issue, and it’s very difficult to
identify. I think Microsoft think about their testing guys, who did not
notice it.
Regards,
Nandan Pandey
> Hi,
>
[quoted text clipped - 23 lines]
> Regards,
> Nandan Pandey