ParkFinder App - Browser Issue

[BrianLord1]

I am new to Javascript and have been working on configuring the ParkFinder Template from the Local Government App Gallery (http://www.arcgis.com/home/item.html?id=734512384d3b4b849aba2db0e33a80f2).  So far I just swapped out all the ESRi layer/field names for mine.  I got the app to work on Chrome and FIrefox, but run into an issue when testing it in IE7.

The app loads and everything is fine until I try to search for parks.  The map says "Loading" and never actually loads anything.  As you can see in the attached image, the search Results portion is populated.  However the Park info and Directions boxes do not even show up.  I am guessing it is something with the routing functionality, but am not sure where to start.

Any help would be greatly appreciated.

Thanks,
Mark

Also, I just noticed that the infowindow does not work when I click on the park either.

[BrianLord1]

So after using fiddler to watch the request/responses from my app, I am pretty sure the issue is with the route.solve task that gets sent to ArcGIS online. 

When I use Firefox and Chrome I can see that this is sent as a GET request and returns in less than 1 second.  However, when using IE7 this never even shows up in Fiddler and the map gets stuck.  The previous request (a spatial query to find the parks within a 1 mile buffer) is sent via POST to my server but I can see the response so I believe it returned fine.

Any ideas on what could cause an issue with the route.solve task in just IE7?

[JeffPace]

since you are running on your own server, you need to add ESRI's servers to the proxy.

[BrianLord1]

I did double check to make sure I have ESRIs server listed on the proxy, and I do.

I was running my webmap using debugging in Visual Studio and I kept getting an error on the following line.

if (infoPopupFieldsCollection[key].DisplayText) {
            td1.innerHTML = infoPopupFieldsCollection[key].DisplayText + ':';
        }

I have attached a screenshot of the error I get.

Any ideas as to what may cause this and wether or not this might be the cause of the IE issues?