How do I fix Import and Export MSSQL Server Agent Jobs that have started failing?
Posted on 2008-06-13
On 6/9/2208 all of the stored import and export SQL Server Agent jobs started failing. Two of the imports had be working as of 6/4/2008. The third job was being tested to make sure that we had our fixed file format correct before scheduling it to run. I have started getting the following error message:
Date 6/13/2008 1:33:07 PM
Log - Job History (ApplicationDB-Std. Prospect Short Form 8.0.b-fc2d778c-a0fd-417b-b9b7-2c01f6c1b1f6)
Step ID:1 Server: Server Job Name:ApplicationDB-Std. Prospect Short Form 8.0.b-fc2d778c-a0fd-417b-b9b7-2c01f6c1b1f6. Step Name: Report Start Duration: 00:00:00 Sql Severity: 11
Sql Message ID: 50000
Executed as user: NT AUTHORITY\SYSTEM. The Client Base Folders are not available on the SQL Server's network. [SQLSTATE 42000] (Error 50000). The step failed.
This is the code that the step that fails is running:
DECLARE @r int
EXECUTE @r = [Server].[master].[dbo].xp_cmdshell 'dir "\\Server\SQL Client Base Folder\ApplicationDB\"', no_output
IF @r <> 0
RAISERROR ('The Client Base Folders are not available on the SQL Server''s network.', 11, 1) WITH SETERROR
DECLARE @d datetime
SELECT @d = getdate()
EXECUTE [Server].[ApplicationDB].[dbo].pcUpd_PJOB_Status @JobGUID = 'fc2d778c-a0fd-417b-b9b7-2c01f6c1b1f6' , @Status = 'Running' , @EndDate = @d
I've checked permissions on the folder. I've checked permissions on the job owner. I've checked the permissions of the owner of the SQL Server Agent service. I've done a dbcc checkdb on the application database that the imports and exports are running to. Any thoughts on what else I can do to fix this?