Last week I was in a bit of a panic when Excel Services and SQL Reporting Services (MOSS Integrated) broke on nearly all of my “demo” Hyper-V images.

I could publish to Excel Services, but attempting to render caused this exception to get thrown:

ProcessWebException: A Web exception during ExecuteWebMethod has occurred for server: http://atlasone:56737/SharedServices1/ExcelCalculationServer/ExcelService.asmx, method: OpenWorkbook, ex: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

All of these machines had worked flawlessly before, so I was flummoxed.

In addition, when I tried to render any SSRS MOSS Integrated reports…no joy:

Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host

Interestingly enough, if I manually browsed to http://server/reportserver, I could run reports with no problems…just no luck via MOSS

I also noticed that all of the RSS feeds on my MOSS site had stopped working.

After doing a bit of back-tracking, I saw that all of these boxes had one thing in common: Windows Update had attempted to install security hotfix KB967723, and for reasons unknown, the process had failed. If there was no initial attempt to install KB967723, I had no problems…if WU tried to install it, my image was hosed.

Happy endings: By manually downloading and installing the hotfix and then bouncing the machine, all the broken stuff started functioning correctly. (The hotfix just happens to be network-related in nature, go figure)

Posting this in the hopes I can give someone back an afternoon of their lives!

Most people have discovered by now that in order to use Windows 2008 as a “client” in BI demonstrations that you need to install the “Desktop Experience” feature of the OS. Without it, you’ll have problems getting into SharePoint from Office.

During a recent POC,  I was working with an “all 2008 image” (SQL 2008/Windows 2008/MOSS SP1/PPS SP1/Office 2007), and had a bear of a time getting Excel to browse MOSS libraries. Desktop Experience was installed, but when I attempted to browse to a MOSS library in Excel, the Web Query dialog would pop instead:

If I just plugged the URL of a report or document library into the Open: dialog, Excel was actually importing the page as HTML!

Office 2007 leverages WebDav in order to open MOSS libraries as folders, so I figured that was the problem – I found I was unable to Map a Network Drive to any of the MOSS libraries so I knew I was on the right track.

After several un-install / re-installs of the Desktop Experience component with no change in behavior,  I went ahead and  installed the IIS 7.0 WebDav Extension: It adds some additional configuration UI to InetMgr, and I thought having access to those extra knobs and dials might solve my problem. No joy.

Long story short, I took off my geek hat, put on my consumer hat and got the help of Rakki from PSS. After noticing that I had the IIS 7.0 WebDav Extension installed, he mentioned that MOSS uses its own implementation of WebDav and we didn’t need the extension. He suggested we remove it. I frankly didn’t think it would make a difference since I had the problem before I had installed it and putting the component on the box was an attempt to solve the issue to begin with, but whatever.

So, we un-installed it, and lo and behold, I was able to map drives to my MOSS libraries and Excel / Office was able to browse them. Why? We’re not sure – perhaps the un-install of IIS WebDav did something to nudge the “broken” MOSS WebDav implementation back to life. Complete speculation on my part.

But, if you run into the same issue, maybe this will save you some time (or maybe not, who knows).