Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Stand Alone service limit on Windows Server 2012r2?
#26
Did some more digging, a new theory below:

>>This error message "A call to "HttpCreateRequestQueue"
>>failed: Cannot create a file when that file already exists"
>>is pretty clear about the problem: There is a conflicting
>>name reservation on that same machine...

It looks like a 'conflicting name reservation on that same machine' comes from HttpAddUrlToUrlGroup, not HttpCreateRequestQueue.  For HttpCreateRequestQueue ERROR_ALREADY_EXISTS is 'The pName parameter conflicts with an existing request queue that contains an identical name'.  Based on the output of 'netsh http show servicestate' (thanks JNP for that) pName parameter may be an IW created value like 'IW_Q_215281600' which is colliding and creating the failure.

netsh http show servicestate output:

Server session ID: EE00000220000052
    Version: 2.0
    State: Active
    Properties:
        Max bandwidth: 4294967295
        Timeouts:
            Entity body timeout (secs): 120
            Drain entity body timeout (secs): 120
            Request queue timeout (secs): 120
            Idle connection timeout (secs): 120
            Header wait timeout (secs): 120
            Minimum send rate (bytes/sec): 150
    URL groups:
    URL group ID: F40000024000004D
        State: Active
        Request queue name: IW_Q_215281600
        Properties:
            Max bandwidth: inherited
            Max connections: inherited
            Timeouts:
                Timeout values inherited
            Number of registered URLs: 2
            Registered URLs:
                HTTPS://MS8.ABC.COM:443/TILES/
                HTTP://MS8.ABC.COM:80/TILES/
Reply


Messages In This Thread
RE: Stand Alone service limit on Windows Server 2012r2? - by MJS@mjs.us - 09-11-2021, 06:51 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)