Scheduled jobs suddenly failing

I have MS SQL Server 2000 sp? on Windows 2000.
I have various jobs set up to run with the SQL Server Agent. I have a
job that imports data from an Access database located on the same
server. Then later, a job runs that updates some rows.

The import job fails with an error saying the source data is opened
exclusively by someone else, or I don't have permission. I have
verifed through various tests that no one else is using the source
Access database. I have even tried this import from excel files and
csv text files.

The job which updates a few rows will run with no problem.

This is a newly created job (actually a DTS package that was saved and
scheduled to run as a job)

Recently though, the server was renamed, and I feel this is the cause.
I have checked the msdb.sysjobs table and some of the jobs with the
new server name work, and some of them don't. The DTS jobs don't seem
to work.

I have maintenace jobs that used to run successfully, but now fail.

I have also tried to run the job with various users as well as SA.

Any ideas would greatly be appreciated.<OakRogbak_erPine@.yahoo.com> wrote in message
news:13fdc9b4.0408100537.1b66cbec@.posting.google.c om...
> I have MS SQL Server 2000 sp? on Windows 2000.
> I have various jobs set up to run with the SQL Server Agent. I have a
> job that imports data from an Access database located on the same
> server. Then later, a job runs that updates some rows.
> The import job fails with an error saying the source data is opened
> exclusively by someone else, or I don't have permission. I have
> verifed through various tests that no one else is using the source
> Access database. I have even tried this import from excel files and
> csv text files.
> The job which updates a few rows will run with no problem.
> This is a newly created job (actually a DTS package that was saved and
> scheduled to run as a job)
> Recently though, the server was renamed, and I feel this is the cause.
> I have checked the msdb.sysjobs table and some of the jobs with the
> new server name work, and some of them don't. The DTS jobs don't seem
> to work.
> I have maintenace jobs that used to run successfully, but now fail.
> I have also tried to run the job with various users as well as SA.
> Any ideas would greatly be appreciated.

You might want to investigate if the server name was changed correctly - did
you follow the steps in Books Online exactly?

http://support.microsoft.com/defaul...4&Product=sql2k

You might also want to check if sp_helpserver and select @.@.servername return
the correct output. If you have data sources in DTS packages which reference
the old name, then they will need to be updated in each package also (unless
you set the name dynamically at runtime of course).

If this doesn't help, please post the precise error messages, as well as the
version of MSSQL/Excel.

Simon