Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-6928

IIS - Unable to start pipes server on latest win 2008r2 image

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • IIS 4.4.0
    • iis, windows
    • Hide

      init.ps1 should have a call to Add-Type -Assemblyname System.Core added to the script right before the attempt to create the server object.

      The acceptance tests should now pass on all platforms.

      Show
      init.ps1 should have a call to Add-Type -Assemblyname System.Core added to the script right before the attempt to create the server object. The acceptance tests should now pass on all platforms.
    • Windows
    • Windows 2018-03-28
    • Automated Test
    • Needs Assessment

    Description

      Module Version: 4.3.1
      OS Name/Version: Windows 2008r2

      In the latest patched version of this Windows OS, the assemblies loaded by default into the app domain are not consistent with what has been loaded in the past. By default the System.Core assembly is not present. This causes problems for the init.ps1 script which starts the pipe server in the PowerShell process to fail to create the server object, which causes the entire module to fail since commands cannot be passed to PowerShell from Ruby.

      Desired Behavior: The init.ps1 script should automatically load the System.Core assembly into the app domain no matter what the current state of the loaded assemblies is. This will enable the script to correctly create the pipe server.

      Actual Behavior: Currently, if the System.Core assembly is not present, it is not automatically loaded when the script attempts to create the server object. This means there is no pipe server on the PowerShell process side waiting for commands.

      Attachments

        Issue Links

          Activity

            People

              william.hurt William Hurt
              william.hurt William Hurt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support