Yesterday we fell for a nasty trap setup by the network security team. We were adding a Bing maps service to our ArcGIS Server 10 web application using the ArcGIS manager. Sounds easy just follow the help file and your done, NAAH!
There began our excruciating journey in the Google's search valley. Searching for every possible reasons we could imagine right to the spells for getting rid of the Gremlins. As usual not much is available for ESRI. But then we stumbled upon a nifty spell called ArcGIS KB 35445, bless the soul who created it.
We cast the spell on the ProxyServer.config located in deep crevices of the install folder "C:\Program Files\ArcGIS\Server10.0\DotNet" ( for 64bit in Program File (x86)).
We followed the spell line by line and voila our problems were resolved!
Tip: Use capital case for DOMAIN\USERNAME.
There began our excruciating journey in the Google's search valley. Searching for every possible reasons we could imagine right to the spells for getting rid of the Gremlins. As usual not much is available for ESRI. But then we stumbled upon a nifty spell called ArcGIS KB 35445, bless the soul who created it.
We cast the spell on the ProxyServer.config located in deep crevices of the install folder "C:\Program Files\ArcGIS\Server10.0\DotNet" ( for 64bit in Program File (x86)).
We followed the spell line by line and voila our problems were resolved!
Tip: Use capital case for DOMAIN\USERNAME.
