November 17, 2020 at 4:06 am
We have job which is configured to recycle the sql error log on daily basis and its failing with the error
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528) SQLServerAgent Error: 32. [SQLSTATE 42000] (Error 22022). The step failed.
we renamed the sql error log out file in agent properties , still getting this issue . with out restarting the agent serivces how can we solve the error .
November 17, 2020 at 3:43 pm
You tried to clean the logs manually? if so, did it worked?
November 17, 2020 at 5:07 pm
We have job which is configured to recycle the sql error log on daily basis
Are you using the standard sp_cycle_agent_errorlog proc or did you try something home grown? I've never had a real error with the standard proc, only a very occasional msg in effect that "it can't be done now".
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
November 17, 2020 at 9:45 pm
Just to confirm - you are NOT reindexing anything during that job step, right?
I just found this post:
https://www.sqlservercentral.com/forums/topic/sql-job-fails-giving-message-2528
which says that message 2528:
"The message 2528 is what DBCC Reindex always outputs"
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
November 18, 2020 at 5:09 am
i am using the standard Proc to recycle the error log'sp_cycle_agent_errorlog ', even i tried to run in different schedule.
November 18, 2020 at 10:06 pm
> we renamed the sql error log out file in agent properties <<
I think that would require a recycle of SQL Server. You don't need to do that. You should be able to copy the existing log files (other than the current log file) somewhere else and then delete them from the original location.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply