Skip to main content

Excel and the Mysterious Hang

Sometimes, it’s hard just to figure out which needle you’re looking for in haystack. Once you got it figured out though, that needle will look like a big stick.

Question Mark 2My wife came home tonight asking me to look at her laptop. In the last week, her Excel program would hang trying to open Hyperion but would eventually find its way back home. She might have mentioned that Outlook was also opening slowly but having mistook the rest of her sentence as something related to finance, I promptly ignored it – my eyes fixed on the real prize: a chance to tinker.

When you don’t know where the problem is, sometimes it’s best to get all the information and start sifting it for signals. When I started off, I was SURE it was some kind of timeout problem so I immediately started with a packet trace.1 #NOPE There was nothing evident of a long or delayed response.

Well, I knew Excel was problematic (you know, since I forgot about Outlook) and decided to hone in on the processes involved with it. I fired up the handy little Sysinternals Process Monitor and had my wife run through her steps again. I captured the specimen and moved it into the laboratory for closer examination.

wikipedia.com

What I was looking for now was a gap. I knew there was some kind of delay or timeout and was hoping something in the procmon trace would show me. If you don’t use any filters to limit the information, no amount of hope is going to make it show up. I had to keep excluding things which was only marginally helpful. I gave up and went all in. I excluded anything that wasn’t Excel and hid all SUCCESS results.

By slowly dragging the net across the screen, I finally managed to see the little tear I was looking for. The time values jumped. That’s significant. It went from 6:42:48 to 6:43:27. It was nearly 40 seconds. That was when I knew what needle I was looking for and when that needle became a big stick.

2016-04-04_22-09-13

The events immediately before and after showed reg key calls related to wpad. Hmm. Wpad. That’s familiar. In fact, it probably stands for Windows Proxy Auto Detect. #NOPE #2  According to Wikipedia, it actually stands for Web Proxy Autodiscovery Protocol.

The Web Proxy Auto-Discovery Protocol (WPAD) is a method used by clients to locate the URL of a configuration file using DHCP and/or DNS discovery methods. Once detection and download of the configuration file is complete, it can be executed to determine the proxy for a specified URL.

If that’s really the problem coming out of Excel, I was willing to bet that Excel was using the proxy settings of Internet Explorer. I fired up IE. It hung. HELLZ YEAH. Looking at the LAN settings1 revealed all. While my wife was onsite at a different company, the local IT staff reconfigured her browser to use their proxy.

welovecatsandkittens.com

I unchecked the Use automatic configuration script setting. IE worked. Excel worked… and uhhh, yeah. So did Outlook. ;-)

Hope that helps you out! Happy hunting.

 

1 Did you know you can capture packets from a cmd prompt without Netmon, Message Analyzer, or Wireshark installed? Oh, yes, you can. http://marcusoh.blogspot.com/2014/10/using-netsh-to-capture-packets.html

2 You can view the LAN settings by navigating to the following path: Internet Explorer / Internet Options / Connections tab / LAN settings.

Comments

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m