MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Errors in running MSDT (a.k.a Microsoft Support Diagonostics Tool) on a Windows 2008 R2.

Folks,

Found this after so much of search and so I thought I’ll pen it down for anyone who might be looking for something related to this.

Recently, I opened a case with Microsoft and they requested me to run the Support Diagonostics tool on my Exchange 2010 running Windows 2008 R2 Enterprise. The online tool wouldn’t run on Win2k8 R2 and so, I had to use a in-built MSDT tool on these servers (instructions will be there on the mail that the MS Support Engineer sends).

Basically, the Microsoft Support Engineer would provide you with a passcode, which is pre-defined with a set of information to gather on the server having issues. When I run it, I got an error (please scroll down a bit below) and I wasn’t able to upload the logs to the MS. Clicking on the small link gives more details on the error.

After a bit of digging on the internet, I came accross the Microsoft KB article that answers the FAQs about this tool and has the error codes and the common troubleshooting steps.

The one that I feel is more often bound to happen would be 0x80072EF3. This is due to the fact that you have a proxy servers that provides internet access for your users (and servers wouldn’t have direct internet connection). You can use the netsh winhttp import proxy source=ie to import the Proxy settings from IE (if the Proxy settings is not forced by GPO, then you might have to configure your Proxy settings IE before running this command – few admins wouldn’t like to have GPO applied on them). You might want to run netsh winhttp reset proxy to revert to default settings after running this tool! 😉 There are few other codes in the KB article too, that might interest you!

Hope this helps someone wandering in the wild for an answer! :)Guys,

Found this after so much of search and so I thought I’ll pen it down for anyone who might be looking for something related to this.

Recently, I opened a case with Microsoft and they requested me to run the Support Diagnostics tool on my Exchange 2010 running Windows 2008 R2 Enterprise. The online tool wouldn’t run on Win2k8 R2 and so, I had to use a in-built MSDT tool on these servers (instructions will be there on the mail that the MS Support Engineer sends).

Basically, the Microsoft Support Engineer would provide you with a pass code, which is pre defined with a set of information to gather on the server having issues. When I run it, I got an error (below) and I wasn’t able to upload the logs to the MS. Clicking on the small link gives more details on the error.

Error on running MSDT

Error on running MSDT

After a bit of digging on the internet, I came across the Microsoft KB article that answers the FAQs about this tool and has the error codes and the common troubleshooting steps.

The one that I feel is more often bound to happen would be 0x80072EF3. This is due to the fact that you have a proxy servers that provides internet access for your users (and servers wouldn’t have direct internet

Error on running MSDT

Error on running MSDT

connection). You can use the netsh winhttp import proxy source=ie to import the Proxy settings from IE (if the Proxy settings is not forced by GPO, then you might have to configure your Proxy settings IE before running this command – few admins wouldn’t like to have GPO applied on them). Just make sure that https://support.microsoft.com and https://dcupload.microsoft.com is not blocked on your proxy. You might want to run netsh winhttp reset proxy to revert to default settings after running this tool! 😉 There are few other codes in the KB article too, that might interest you!

Command to enable/disable the Proxy settings

Command to enable/disable the Proxy settings

Hope this helps someone wandering in the wild for an answer! 🙂

 

Muthu

Team@MSExchangeGuru.com

3 Responses to “Errors in running MSDT (a.k.a Microsoft Support Diagonostics Tool) on a Windows 2008 R2.”

  1. Patil Says:

    what exactly you ar trying to achive here? with this steps we can see the IE setting using command rather than GUI.

    Straight foward answer.

  2. Muthukumar P Says:

    Patil,

    I think you haven’t read the article properly. The command is NOT to see your IE settings using commands, but to IMPORT your IE settings so that your OS can make use of it. 🙂

    Muthu

  3. http://andcarinsurancequotes.com Says:

    Great work! That is the type of info that are supposed to be shared across the net. Disgrace on Google for now not positioning this publish upper! Come on over and seek advice from my site . Thanks =)

Leave a Reply

migrate exchange to office 365

Categories

Archives