SQL Server job failed. The Job was invoked by Schedule 11 (NAV Backup 1). The last step to run was step 1 (Subplan_1)

Question

Date 07-01-2014 10:00:00 PM
Log Job History (NAV Backup 1.Subplan_1)
Step ID 1
Server NAVSRV
Job Name NAV Backup 1.Subplan_1
Step Name Subplan_1
Duration 00:02:26
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
1122

Answer 1

About your question on How and Who changed it, i told that nobody changed it. I found in this way.
1122
I also Saw the plan and the path of Database and database log was ok , i mean PHARMANEXT_LOG_95ABA2F6-DC67-4CFC etc...
was exactly like in the C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA
Maybe is something wrong with my backup script, but i dont think so because before 23 of december
everithing was ok. After this date it failed.
Anyway check this script of "Remove SQL log" , the one that you think is a culprit:
DECLARE @name VARCHAR(50)
DECLARE @fileName VARCHAR(256)
DECLARE db_cursor CURSOR FOR 
SELECT name 
FROM master.dbo.sysdatabases 
WHERE name NOT IN ('master','model','msdb','tempdb') 
OPEN db_cursor  
FETCH NEXT FROM db_cursor INTO @name  
WHILE @@FETCH_STATUS = 0  
BEGIN  
SET @filename = @name + '_log' 
Exec ('Use [master] alter database [' + @name + '] set recovery simple')
Exec ('Use [master] alter database [' + @name + '] set recovery FULL')
        Exec ('Use [' + @name + '] DBCC SHRINKFILE ("' + @filename + '",1)')
       FETCH NEXT FROM db_cursor INTO @name  
END  
CLOSE db_cursor  
DEALLOCATE db_cursor
go
Hello,
You have created a cursor which will take all user databases and change recovery model to Simple and then to full what this will cause it will break the log chain and you might loose your RPO and RTO.This operation truncates the log .Please stop this job
immediately.It is worst you can do to your Database recovery and availability.After this you are trying to shrink .
As pointed out it is seriously not advised to shrink data file.And if you have proper trn log backup it manages the growth of log file
Hope this helps
Keep looking for any such activity which might change anything in your database
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers