Aye

I'm running SQL 2000, no Service pack on a W2k server SP4.0. I have a number of jobs that run fine when execued from the DTS package, but when these packages are scheduled as a SQl Job, they fail when executed with the following error

"runtime error R6025 - pure virtual function call"

Any assistance would be greatly appreciated.

Thanks

Sounds like your SQL Agent service account does not have privilege to do tasks in the DTS. What does the DTS do?.

If package accesses data from remote data source, should start sql agent service with domain account that has proper permission on remote data source.

The DTS package is copying two tables from an AS400. These are the steps I take. I select my database and choose import data. I follow all the steps necessary to import the data, at the end, I schedule, save and run the package from the import wizard. All of this is completed without error.. however the scheduled job will fail with the above error when executed, but the DTS wil run fine.

I have similar packages that compy from the AS400 that work fine. The only difference with these failing jobs seems to be that they attempt to import more than 1 table at the same time.

Possible to schedule them to run at different time?

That would be a possible workaround. . . but I really want to know what's causing this problem.

Then you need trace that on DB2/400.

I installed service pack 3a for SQL server 2000 and the error changed to the include the following "process exit code 1073741819" with the jobs still failing. I then installed Sp4 and now the jobs just say executing, but do not run. When I check the activity logs and locks, nothing pertaining to the job is being displayed, so it seems like athough the job is displayed as executing nothing is actually happening. This is very strange. Any more ideas.

How does sql talk to db2/400? Did you install client express on sql server? Which version?

SQL connects to the AS/400 using a driver called StarSql, this comes bundled with SNA server. So I have installed the Starsql driver on the server in question, by installing SNA 3.0 Client and only installing the StarSql odbc driver.

Not sure for that, I use as/400 client access express and have no problem.