Steven Van de Craen's Blog

hi steven, I'm getting this exact problem, "Server was unable to process request. ---> Attempted to perform an unauthorized operation." Even though I trying to invoke the UserProfileService Web Service, from a console application executed by my own account, which is defined as site collection admin, and IIS anonymous access is disabled. any additional pointers?

Try to specify some credentials after instantiation your Web Service:

Service serv = new Service();

serv.Credentials = System.Net.CredentialCache.DefaultNetworkCredentials;

Hi... I'm getting this error but there's a bit more to it. I only get the error when calling QueryEx() method. The Query() method for me works fine! Unfortunately though I would really like my full results returned as a DataSet so I want to use QueryEx(). I'm getting the same results whether running the test tool on the server or remotely. So.. Why would QueryEx() fail with "Attempted to perform an unauthorized operation" when Query() successfully returns results, given the same query XML???? I am so confused. Also, I looked at one of the QueryService classes with Reflector... I couldn't see what in there could possibly cause this behaviour? Thanks -Adrian

Adrian, can you get a detailed stack trace of the error ? Which version of MOSS do you have; RTM, SP1, Infrastructure Update ?

I have MOSS SP1 installed on my primary dev server. Unfortunately I wasn't able to get a full stack trace of the error since it was happening inside the sharepoint web service... Probably could have configured things to get a full output. But anyway I solved my problem, it was in fact to do with anonymous access. I created another sharepoint site with anonymous disabled, and QueryEx works on that. My colleague suggested disabling anonymous access only for the search.asmx file. I did this on my anonymous-enabled site and had success. Unfortunately though the application performing the query must be running under a user account that has the required permissions to access the web service. This meant I had to move my search app to a new app pool and change it's user account to one that was common to both servers. I hope this can help someone.

as suggested by one of the comments, overriding the anonymous setting in IIS for search.asmx does the trick

hola yo tambien tenia ese problema que no podia ejecutar mi consulta con queryex nada mas lo podia hacer con query. pero ya pude resolver el problema y el cual era que no estaba creando bien mi xml de la consulta aqui les paso como es que debe de ser el xml. en donde dice hola ahi va la cadena concatenada que biene siendo el filtro. Espero esto les resuelva su problema. hola scope:"FileShare" SharepointSearch 1 200 true Suggest true true true true