Handling failed webservice calls?

[jholl016]

I know very little about hosting/deploying web services, so please take that into account if you respond :)

I have been using this web service productively in my SCCM environment for some time now to perform just a few infrequent operations. On a couple of occasions, I've tried to use the webservice as part of a larger deployment operation that targeted a number of existing clients at the same time. It didn't go well, as many of the calls to the web service will timeout if too many calls are made around the same time by different clients. At this time, I really don't have a feel for what that threshold is, though.

In general, what is a realistic expectation for the level of workload that this web service is designed to handle if installed/configured using the default settings on a "typical" Windows Server? In general, does the service simply construct an internal queue of incoming requests and evaluate them one-at-a-time in the order received? And is there anything that can be done on the IIS side or in the configuration of the service to allow the service to handle a greater number of requests in a short period of time?

Again, I know very little about IIS, so any feedback (whether specific solutions or links to general IIS concepts) is appreciated!

[jbudd0649]

I am experiencing the same issue as jholl016. If I run a task sequence on 1 PC it works just fine. If I try to run an entire lab the task sequence will fail on several machines. When I check the logs I see error 454.

[Stuart42]

I'd start by watching Performance Monitor on your IIS server when you run your task sequences. We run several hundred task sequences a day and haven't had this reported yet,

[jbudd0649]

Sorry I read that wrong. IT isn't error 454. IT is error at line 454.
ApplyDriverPackage.log

[jholl016]

A thought just occurred to me... it's probably a bad idea to be hosting this on my SCCM primary site server, isn't it? The site server uses IIS for a bunch of stuff. Is it a best practice to host this web service on a dedicated server?

[jbudd0649]

Mine is also hosted on the Primary site server.

[jbudd0649]

jholl016 I am curious what your log files look like. Are you seeing anything similar to mine?

[jholl016]

Not sure where to find the logs. Can you point me in the right direction?

[jbudd0649]

The ApplyDriverPackage.log is stored in the same location as the smsts.log. So it can be in a few different places depending on when the TS fails. I have a step in my TS that copies the logs to a network share if the TS fails.

Here is a good post on where to look https://www.ronnipedersen.com/2014/08/12/sccm-2012-r2-smsts-log-located/

[jholl016]

Oh, you're looking at SCCM logs. I thought you were asking for ConfigMgrWebService logs. I've looked through smsts.log and didn't find anything helpful.

[jbudd0649]

Do you have a ApplyDriverPackage.log?

[jholl016]

I'm not using this web service as part of any driver package installation solution, such as "Modern Driver Management". So, the ApplyDriverPackage.log isn't relevant in my case. I'm simply calling the webservice from a powershell script to perform AD operations.

[jbudd0649]

Ah. I see.