May 21, 2018 at 7:44 am
Hi All,
2008 R2 instance. We frequently copy databases for new DBs as it's a lot less work to get clients situated.... So, I was tasked with copying a database for a new client. I did this via the object explorer/copy DB wizard. Didn't seem like anything out of the ordinary. I name the Package, and it appears in the SQL Agent job list once I finish with the wizard. I have since deleted the job, and I don't see it in the object explorer nor in sysjobs, and yet it is sending out notifications when it 'fails'. Any suggestions?
I have looked at the temp files and found nothing (based on this post: https://www.experts-exchange.com/articles/1602/Jobs-deleted-are-still-running-in-MS-SQL-Server.html) Please advise.
May 21, 2018 at 8:38 am
scarr030 - Monday, May 21, 2018 7:44 AMHi All,2008 R2 instance. We frequently copy databases for new DBs as it's a lot less work to get clients situated.... So, I was tasked with copying a database for a new client. I did this via the object explorer/copy DB wizard. Didn't seem like anything out of the ordinary. I name the Package, and it appears in the SQL Agent job list once I finish with the wizard. I have since deleted the job, and I don't see it in the object explorer nor in sysjobs, and yet it is sending out notifications when it 'fails'. Any suggestions?
I have looked at the temp files and found nothing (based on this post: https://www.experts-exchange.com/articles/1602/Jobs-deleted-are-still-running-in-MS-SQL-Server.html) Please advise.
It may not be that particular job that you deleted. The notification could be from a job on another server or a different job on the current server.
Sue
May 21, 2018 at 8:41 am
Okay, it would have to be the latter as this is all on one server. Do you have any suggestions to figure out what job it may be? I don't see any failures in the history...
May 21, 2018 at 9:02 am
Did you check both the source and desintation servers? Maybe the job is on the other one?
May 21, 2018 at 9:19 am
There is only one server involved.
May 21, 2018 at 10:32 am
scarr030 - Monday, May 21, 2018 9:19 AMThere is only one server involved.
You could check what jobs were running around the time you get the notification.
Sue
May 24, 2018 at 6:34 am
Okay, I've given it a couple of days and have more information.
We have an app manager that is used to show metrics and warnings based on certain criteria. This seems to be some sort of RackSpace product, or is at least tied to our rackspace servers (where this instance is housed). This app manager is where this notification is coming from. At 0419 this morning, it alerted us to the failed job mentioned in my original post. Taking a look at the SQL Agent history: there were some failed steps in a completely separate job. These occurred at 0104; 3 hours before the alert. Most of these are due to Error 22050 'Error formatting query, probably invalid parameters.' There were no other failures around that time. Again, the task that is being explicitly named has been deleted for quite some time and does not show in any of the sysjobs tables (that I can find). Suggestions?
Thanks again for your time.
May 24, 2018 at 7:11 am
You mention there's an app manager involved. Does this manager also manage job in the Windows Scheduler? Are there any errors in the Windows Event logs (system and application) around the time of the notification?
May 24, 2018 at 9:11 am
Interesting. I wonder if the notification is crossed in the App Manager? Saying the error is from x, but it's coming from y.
May 24, 2018 at 9:20 am
Checking the event logs now.
Steve, I had the same thought, so I spent some time going through those errors I mentioned on the unrelated job. We'll see if that has any effect, though I'm skeptical because of the time difference.
May 25, 2018 at 11:49 am
Another update: almost certainly not another job causing the issue. Cleared the error but it came back 3 minutes later.... job definitely did not run during that time.
I mentioned before that this was a 'package', and really I didn't/don't have a complete understanding of the implications of that. I happened to find a couple of tables, sysssispackages and sysssispackagefolders, in the msdb database. What do you know, I see the name of this 'package' there. So, I go to the directory where this is supposed to be stored and it's empty. Thinking that this record was causing the issue, I dropped it from the table. However, the error came back again just a few minutes after being cleared. Any suggestions given this new information?
Thanks
May 25, 2018 at 12:02 pm
That is really odd. Do you have the source of the notification you're getting? I assume an email, but can you trace the header to a sender?
May 29, 2018 at 8:05 am
It's not an email, but an alert internal to this App Manager. This job/package does in fact seem to be running in the background somewhere as it also seems to trigger a buffer hit ratio warning. Are there any other places to look for something like this besides the SQL Agent in the object explorer and msdb.dbo.sysssispackages and msdb.dbo.sysssispackagefolders?
May 29, 2018 at 10:22 am
Had a similar issue years ago, it transpired that it was a remotely stored ssis package that was run using osql command's in a batch file as a scheduled task! I found the offender using sp_readerrorlog which identified the ip address, after that it was a not so simple process of finding the files! Not sure that helps, hope it does.
...
May 30, 2018 at 5:15 am
Packages created by the "copy DB wizard" are stored in the [msdb]. You can manage them using the following steps:
1. Open a connection from SSMS to Integration Services of the server by specifying "Integration Services" as server type
2. Open up the Stored Packages>MSDB
3. Locate the package
To get more insight, could you post the full notification message? Perhaps someone here recognizes the message and can tell more about the origin of it or make assumption out of the content of the message.
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply