![]() Maintenance Plans are SQL Server Integration Services packages. Step 3: Confirm these suspicions by opening the job itself and viewing the content (you’ll have to Edit in order to see the internal configuration of the job, but don’t make any changes – and always cancel out when you’re done, never save *). The job name is a clue, also – the two-part name usually indicates that this job was created by a Maintenance Plan. The clues are in the error message Source (SQLISPackage) and Description that starts with “Package …”. Step 2: open up the job history for the job and see if there’s any additional information:Īs it turns out, there isn’t, not in the main entry for the job history description or in the subplan step. (The jobs with the tiny red downward-pointing arrows as part of the icon have been disabled.) Sure enough, there’s a scheduled job with the same name in the job list, and it’s an active job. Step 1: this error message is pointing to a job (Application/SQLISPackage) called Dynamics DB Integrity Check.Subplan, so it’s logical to start with the SQL Server Management Studio scheduled jobs. ![]() This was taken from the Windows Event Log/Application Log:ĭescription: Package “Dynamics DB Integrity Check” failed. Here’s a good example of a job that failed without a whole lot of information as to why it failed. Troubleshooting error messages can be a little tricky, especially if you’re new to the task.
0 Comments
Leave a Reply. |