January 12, 2023 at 9:09 am
Dear All,
I have set up a consistency check job on an SQL server which runs well but doesn't write the output. thank you in advance.
Best Regards....Arshad
January 12, 2023 at 1:15 pm
With zero details, I've no idea what the answer could be. Any chance of posting code or at least describing what this job does? Write the output to where? What output?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 13, 2023 at 5:06 am
Grant , its a DBCC CheckDB that I am calling from an agent job. It runs well but has error message at the end saying it cannot see the output file. Cannot be a rights issues with the Agent service account as I logged in with the same user and tested it. but same result. I even created an output file on the default location (Program Files\MSSQLServer...\Log) but no change .Attached below is a sample of the error log.
thank you.
January 13, 2023 at 5:06 am
Grant , its a DBCC CheckDB that I am calling from an agent job. It runs well but has error message at the end saying it cannot see the output file. Cannot be a rights issues with the Agent service account as I logged in with the same user and tested it. but same result. I even created an output file on the default location (Program Files\MSSQLServer...\Log) but no change .Attached below is a sample of the error log.
thank you.
January 13, 2023 at 7:49 am
Here is the full error from the error log
"
Date 13/01/2023 11:45:04 AM
Log SQL Server Agent (Current - 13/01/2023 11:37:00 AM)
Message
[136] Job CheckDBIntegrity reported: The process could not be created for step 1 of job 0x5C1E54654FB6DC4F9AC7255E53A53D1A (reason: The system cannot find the file specified)
"
January 13, 2023 at 10:05 am
From your post I believe you are mentioning about job output file. Do you have the output file in place? Create a file with the mentioned name in SQL job and try.
January 13, 2023 at 12:24 pm
Hi,
I think you created the job via maintenance plans?
I did this on my test environment, and I got the same error.
I changed the job owner to sa, and now the job was running fine.
Please check your account, wich owned the job.
Good luck,
Andreas
January 13, 2023 at 1:23 pm
Sure sounds like a security issue.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 14, 2023 at 8:17 am
You may be looking at either OS permission issue or SQL server permission. Have you checked the OS event viewer?
Please ensure you have the latest SQL server service pack and latest OS windows updates. You may repair the SQL server installation.
Please run a chkdsk on your drive. Use the sysadmin permission to see if it works with that.
Basic things make a difference.
DBASupport
January 18, 2023 at 1:51 pm
Hi All,
It was a permissions issue of the SQL server agent account on the directory . It couldn't write even being an administrator..I added specifically and it worked. However, though it writes inside the 'Log' directory of SQL binaries location , can anybody help know why it doesn't write to any other directory I ask it to.|Thank you.
January 18, 2023 at 2:11 pm
Does the SQL Server agent account have permissions on those other directories?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply