SQL Server Agent

  • If it is DNS Caching then you can just type in ipconfig /flushdns and a ipconfig /registerdns. This will flush all the cached DNS info and then re register the new DNS

    edited the spelling of registerdns

    -Roy

  • Yeah, I've actually already run the ipconfig commands already...didn't help the situation. Maybe I'll try dropping and re-adding the server after business hours tonight, because at this point I'm running out of things to try.

    Thanks for everyone's help. If anyone can think of anything else I can try, it would be greatly appreciated.

  • Just out of curiosity, have you run an ipconfig /displaydns to see what is there?

  • I ran it, but I'm not really sure what I need to be looking for.

  • Not really sure myself other than a entry with a NDS name that has the wrong IP address associated with it.

  • I just glanced back through the posts and I didn't see answer to my question regarding how/where you are creating your maintenance plans.

    I may just have missed it, though with these old eyes.

  • Whoops sorry, I must have gotten distracted...I'm creating the maintenance plans through SSMS.

  • From your desktop or the server? Did you run the ipconfig on your desktop or server?

  • SSMS - desktop

    IPCONFIG - both server and desktop

  • Okay, I'm at a loss now also. If I think of anything before you resolve the issue (and if you do, please post back), I'll post here again.

  • How exactly did you get those maintenance plans onto the new 2008 system? Did you restore the msdb database from the 2005 system to the 2008 system?

    If so, then you do have a problem with the maintenance plans and how they connect to the local connection. To verify, review the local connection information in the maintenance plan and identify what the connection information is.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • The connection is to the old server. I didn't do a full restore of the msdb database, but I did do a compare on it to make sure that all the user created objects were moved from the old instance to the new instance. Maybe I accidentally moved a table or something that i wasn't supposed to move, but then again the tool I use doesn't compare sys objects. Hmm...

    So is there a way to fix the local connection? Please say 'yes'!

  • Well, I am not sure about that - let me take a look around and see if I can find something.

    Generally, I have found the best method is to just recreate the plans. I can't imagine it taking a very long time.

    One option you can try, that is not guaranteed to work and could potentially cause problems is to use BIDS, import the maintenance plan - modify the connection string and copy back to the server. Don't change anything else using BIDS or you'll definitely cause problems.

    Once that is done, verify the maintenance plan and re-save it.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Jeffrey Williams (3/4/2009)


    How exactly did you get those maintenance plans onto the new 2008 system? Did you restore the msdb database from the 2005 system to the 2008 system?

    If so, then you do have a problem with the maintenance plans and how they connect to the local connection. To verify, review the local connection information in the maintenance plan and identify what the connection information is.

    Good catch. I hadn't even thought of that.

  • I have tried recreating the plans, but the local area connection still points to the old server. It is grayed out and I can not change it. I tried creating a new connection and using that within my plan, but that doesn't work either.

Viewing 15 posts - 16 through 30 (of 40 total)

You must be logged in to reply to this topic. Login to reply