I'm using call web service to call UserProfileService with getUserProfileByName web part and I am getting the following error <soap:Fault xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>soap:Server</faultcode><faultstring>The User Profile Manager object could not be loaded. ---> UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.GetRawPartitionID has null proxy</faultstring><detail /></soap:Fault> any idea how to fix it? using Nintex 2013
Could be a permissions issue. I would first make sure that there is a User Profile Service and it is associated with the webapplication. Then make sure the app pool account has permissions to read from the application service. Then verify the credentials you are using in the Nintex Call to Web Service action, and make sure there are appropriate credentials used.
I'd start with those basics to try and rule out a permissions issue before going further.
can you post your workflow screenshot?
thanks we purchased the Nintex Enterprise and I'm using QueryUserProfileLookup function without an issue
Hi, I have the same error message but I am using Nintex Enterprise, workflow version 3.0.8. I put a Query User Profile workflow action on my workflow, but when I double-click it to configure, I get an error saying UserProfileApplicationNotAvailableException_Logging :: UserProfileApplicationProxy.GetRawPartitionID has null proxy. Can anybody help with this?
I also tried using a Calculated Value control and using runtime function userProfileLookup(Current User, "FirstName") but this did not return a value.
Does the user who initiated the workflow have permissions to query the user profile service? Or did you provide a login within the action? If you are unable to configure the action, then there could be a permission issue even as a designer. you can update permissions to the service itself in Central Admin -> Manage Service Applications, select the service and Manage Permissions
The error "UserProfileApplicationProxy.GetRawPartitionID has null proxy." is often related to the configuration of the service application and/or your UPS proxy not being configured correctly. The following Microsoft article outlines a similar issue and the resolution that may be of help.
Let me know if either of these articles are helpful!