Dean's Blog

One of my customers contacted me a couple of weeks ago with this issue, but had a different setup that ruled out all the other resolutions he’d come across online. First, the error:

Recently, a customer came to me with an interesting issue. While migrating SharePoint 2010 sites from one farm to another, he was seeing errors in the system event log on the target farm similar to the following:

I’ve seen questions around logging the real client IP in the IIS logs come up a handful of times in the past few weeks, so I figured I’d try and tackle that here. If you’re using load balancing with IIS (who isn’t these days?), then you’ve probably seen that by default, the load balancer’s IP address is generally what’s logged as the client IP in the c-ip field in your IIS logs. These days, most load balancers (and proxy servers) should have the ability to preserve the original client IP in an optional header: X-Forwarded-For. All well and good, but how exactly do we get IIS to log that XFF value to the c-ip field?

From time to time, I see some fairly common questions come across our internal discussion alias that we really don't do a good job of documenting externally, so I figured that as I see these frequently asked questions come up, I’d go ahead and post the answers here. I’ll start with one of the more common ones.

A few years ago, I was lucky enough to have a very small hand in the birth of DebugDiag. In version 1.0, I got to do some work on the analysis scripts, as well as work on one of the debugger extensions it uses for analysis. As a result of the time I spent working on it, it’s still one of my favorite troubleshooting tools.

In part 1 and part 2 of this series, I talked about working around situations where the WFF controller and/or farm servers needed to access a proxy server to be able to pull the RSS feed used by the platform provisioning piece.

In part 1, I focused on how to work around situations where your WFF controller has to pass through a proxy server in order to successfully retrieve the products feed. The configuration sample I provided didn’t address another possible scenario: What if that proxy server requires authentication?

While setting up a Web Farm Framework environment recently, I ran across an issue where the Platform Provisioning piece of the UI was failing to pull the products feed down. In my case, the error was: