Forum Discussion
I am having an issue with sharepoint web services
Microsoftkrdube 2 issues here-
1) The calls taking 15-20 seconds might point to performance issues with the server
2) BlueBeam could use other calls that are not relying on legacy APIs (ASMX web services) to get that data, possibly in one call. They could also use async calls to that you don't end up multiplying the amount of time taken by the calls since they can all be executed in approximately the same time frame. I believe they could get the info with the REST endpoint. Make sure you are using a version of their product that is compatible with SP 2016 on-prem.
WestleyH thanks for the suggestions... i'm chasing this down with premier support. just to update as to where I am with this now... it appears that the web service calls are actually fast, its just that the application takes a long time between calls, i'm thinking its loading all the managed metadata termsets into memory or ??.
The weird part about this issue is that as soon as i make one of my content types the default content type for a library, this is when the application (bluebeam) starts loading all the content types (regardless of what content type the document is). This isn't happening in all of my site collections, only some of them. I'm not sure what is making it load the content types in the affected site collections. I can confirm its using the Lists.asmx web service calling "GetListContentType". After it does this call it takes 23 seconds until it calls it again for the next content type. At first i thought the call took that long but with support they pointed out the call is less than a second, its the application thats taking 23 seconds. But why its calling it is a mystery.. it does it in some site collections but not others...
- WestleyHIt seems like it may just be an issue with the logic in the 3rd party application. We would need to debug that to see why it is taking so long, and how they decide to pull content types etc.
ya, the strange part is that this is confined to document libraries created in a a particular spweb. If i go to subsites under this web they are ok, its only happening in one particular web. Or if i go to other site collections its ok. Really strange... The web that its happening is a root web under the site collection...