Solved! Go to Solution.
Solved by ajay.choudhary. Go to Solution.
Please follow the instructins to solve this issue at http://crackingthevault.typepad.com/crackingthevault/
I ended up finding that post late yesterday. It seems to have fixed the problem for now.
Any ideas what caused the problem? Can I expect this to happen again?
This will fix your Assembly Load problem.
The problem is caused by wrong OS account loading the assembly and then in subsequent calls other OS accounts were unable to access it.
OK, I'm still not getting it. The operating system account?
A few months ago, we had a major server crash that resulted in a domain name change. So all the Windows accounts were new from that point. Is that relevant?
No domain name change is not relevant in this case.
ADMS uses one particular account to impersonate and all assemblies [dll] are loaded using its credentials - in this particular error differnt user accounts were used to load assembly, resulting in subsequent access denied error.
Hope this helps.
So, this wasn't something that a user did? Is there anything that can be done to prevent it from happening again, or is it a bug in the software?
We rebuilt the search index Thursday afternoon. This morning, we started to getting errors when searching.
What is the error message?
Please post vlog file along with your response.
Have you applied the steps I referred to earlier?
Please make sure that is not reverted.
If you are sure that the recommenmded IIS settings are present then please contact product support.
We went though the procedure again (verified everything yesterday). The search is not working again this morning.
I opened a support request.
Can't find what you're looking for? Ask the community or share your knowledge.