up vote 0 down vote favorite
share [g+] share [fb]

I have a setup that includes a dedicated application server, 2 front-end webservers and a dedicated SQL server. One of the web servers also act as a load balancer for both.

As the application server is responsible for crawling sites for the search index, it needs to have access to all sites and such. The thing is, I experience errors when visiting certain parts of the site from the application server, while the same parts work fine if I view it from outside or from one of the WFEs.

The errors are either File not found or I get errors that certain assemblies could not be loaded ("Could not load assembly 'AssemblyName, Version=1.0.0.0, Culture=..., etc' or one of it's dependencies")

link|improve this question
2  
is your architecture setup so that the app server is also a wfe for search indexing? If so, are you going to the web site on the app server, or to the "public" web site when you see the errors? – MattB Dec 16 '10 at 14:54
@MattB is correct, if you have your app server set up as a WFE so that the search service doesn't hit your public WFEs, it may be an issue where there was something installed (custom code, 3rd party web parts, etc) installed on your public WFEs but not your application server's WFE. – SQL3D Dec 16 '10 at 21:33
It turns out to be what you both suggesed. We installed a 3rd party plugin they were using and it works. If you want credit, just copy the comment to an answer. – Christian P. Jan 10 '11 at 11:35
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.