Actually I'm pretty familiar with troubleshooting(in this case the error didn't reproduce.) But I don't want to be troubleshooting this layer of the system. And it's not that I mind helping every once in a while, but from my experience, once you start with tasks outside you're usual responsibility area, they always end up becoming your responsibility going forward, and now you're doing many jobs, and everything that's broken becomes your problem.

And the new duties are unofficial, so there's not hope of additional pay, and if you just stop doing the unofficial job, you might as well be finding another job at another organization. This is how, as a DBA at another organization, I was a regular suspect for people to assign Microsoft Office and desktop support tasks to, because at one point someone asked for my help, and after trying to help, it became one of my responsibilities... Of course this was the same organization that wanted me to train another employee so they could take over the DBA duties, and this would free me up so I could deal with the troublesome Business Objects platform that I had been helping with (this was my reward for helping after being asked to help temporarily) and now someone had to support. I pointed out that they could just get the other employee trained on BO as they had as much experience as I had (and they had no experience on Sql Server,) and then I could go back to just being a DBA.

The spluttering, frothing fits that prompted on the part of the management should have been recorded on video for further viewing later. I quietly found another job and quit within 30 days, and was glad to be gone.