I am having an issue with sharepoint web services

%3CLINGO-SUB%20id%3D%22lingo-sub-2623831%22%20slang%3D%22en-US%22%3EI%20am%20having%20an%20issue%20with%20sharepoint%20web%20services%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2623831%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20we%20are%20running%20a%20sharepoint%202016%20on%20premise%20server.%20When%20opening%20files%20through%20a%20client%20application%20(called%20Bluebeam%2C%20an%20alternative%20PDF%20editor%20to%20adobe)%20it%20is%20calling%20the%20following%20web%20services%20for%20every%20content%20type%20in%20the%20library%20(i'm%20getting%20this%20from%20fiddler)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPOST%20%2Flrc%2FLandUse%2F_vti_bin%2FLists.asmx%20HTTP%2F1.1%3C%2FP%3E%3CP%3ESOAPAction%3A%20%22%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fsharepoint%2Fsoap%2FGetListContentType%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fsharepoint%2Fsoap%2FGetListContentType%3C%2FA%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ein%20my%20farm%20when%20it%20tries%20to%20open%20a%20file%20it%20has%20to%20make%20this%20call%20for%20every%20content%20type%20in%20the%20library.%26nbsp%3B%20the%20first%20time%20i%20open%20the%20file%20it%20takes%20about%2015-20%20seconds%20for%20each%20of%20these%20calls%20to%20complete%20and%20there%20about%20about%2010%20content%20types%20in%20the%20library%20so%20it%20takes%20a%20Long%20time%20to%20open%20the%20document.%26nbsp%3B%20Weirdly%20this%20doesn't%20happen%20in%20all%20my%20libraries%2C%20only%20in%20some%2C%20i%20think%20its%20happening%20in%20some%20libraries%20that%20were%20created%20from%20templates%20originally.%20Note%20that%20when%20it%20does%20happen%20it%20only%20happens%20the%20first%20time%20a%20document%20is%20loaded%20from%20the%20library%2C%20on%20subsequent%20times%20it%20is%20ok.%26nbsp%3B%20Has%20anyone%20seen%20this%20and%20might%20know%20what%20is%20causing%20this%20weird%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2623831%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2700138%22%20slang%3D%22en-US%22%3ERe%3A%20I%20am%20having%20an%20issue%20with%20sharepoint%20web%20services%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2700138%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F883211%22%20target%3D%22_blank%22%3E%40krdube%3C%2FA%3E%26nbsp%3B2%20issues%20here-%3C%2FP%3E%0A%3CP%3E1)%20The%20calls%20taking%2015-20%20seconds%20might%20point%20to%20performance%20issues%20with%20the%20server%3C%2FP%3E%0A%3CP%3E2)%20BlueBeam%20could%20use%20other%20calls%20that%20are%20not%20relying%20on%20legacy%20APIs%20(ASMX%20web%20services)%20to%20get%20that%20data%2C%20possibly%20in%20one%20call.%20They%20could%20also%20use%20async%20calls%20to%20that%20you%20don't%20end%20up%20multiplying%20the%20amount%20of%20time%20taken%20by%20the%20calls%20since%20they%20can%20all%20be%20executed%20in%20approximately%20the%20same%20time%20frame.%20I%20believe%20they%20could%20get%20the%20info%20with%20the%20REST%20endpoint.%20Make%20sure%20you%20are%20using%20a%20version%20of%20their%20product%20that%20is%20compatible%20with%20SP%202016%20on-prem.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi we are running a sharepoint 2016 on premise server. When opening files through a client application (called Bluebeam, an alternative PDF editor to adobe) it is calling the following web services for every content type in the library (i'm getting this from fiddler)

 

POST /lrc/LandUse/_vti_bin/Lists.asmx HTTP/1.1

SOAPAction: "http://schemas.microsoft.com/sharepoint/soap/GetListContentType"

 

in my farm when it tries to open a file it has to make this call for every content type in the library.  the first time i open the file it takes about 15-20 seconds for each of these calls to complete and there about about 10 content types in the library so it takes a Long time to open the document.  Weirdly this doesn't happen in all my libraries, only in some, i think its happening in some libraries that were created from templates originally. Note that when it does happen it only happens the first time a document is loaded from the library, on subsequent times it is ok.  Has anyone seen this and might know what is causing this weird issue?

4 Replies

@krdube 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...

It 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...