1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Powershell call fails with "Scripting Integrator 2016 (PowerShell)" license error

Discussion in 'Support' started by felixkasza, May 20, 2017.

  1. felixkasza

    Joined:
    May 20, 2017
    Messages:
    10
    Likes Received:
    0
    I seem to have a little trouble getting powershell to work from within TCC 21. Powershell itself works:

    D:\bin\btm> powershell get-help get-help

    NAME
    Get-Help

    SYNOPSIS
    Displays information about Windows PowerShell commands and concepts.

    [… remainder of output elided …]

    D:\bin\btm> ver /r

    TCC 21.00.27 x64 Windows 10 [Version 10.0.15063]
    TCC Build 27 Windows 10 Build 15063
    Registered to FKL

    Regrettably, the owners of IPworks somehow have their fingers in this pie, too:

    D:\bin\btm> echo %@pshell[get-help get-help]
    [Error message is displayed, see attached screen shot]

    D:\bin\btm> pshell /s get-help get-help
    [Error message is displayed, see attached screen shot; then:]
    PSHELL: Could not find a valid license for Scripting Integrator 2016 (PowerShell) in this system. For more information, please visit www.nsoftware.com.

    This happens after a number of attempts that just report the error "PSHELL: The library file is missing or specified functions can't be found."

    Soon after the license error pops up, TCC becomes unstable and crashes.

    Any help is appreciated.

    Thanks,
    Felix.
     

    Attached Files:

  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,869
    Likes Received:
    83
    This is a bug in the updated version of the third-party library. I'm rolling it back to the previous version pending a fix from the developers and will post a new TCMD build today.
     
  3. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,970
    Likes Received:
    30
    I get this message.
    Code:
    v:\> echo %@pshell[get-help get-help]
    PSHELL: The library file is missing or specified functions can't be found.杮
     
  4. felixkasza

    Joined:
    May 20, 2017
    Messages:
    10
    Likes Received:
    0
    Thank you for the speedy response and, of course, for the 23 years that I've been using 4DOS, 4NT and now TCC/TCMD!

    Cheers,
    Felix.
     
  5. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,869
    Likes Received:
    83
    I got a fix from the Nsoftware developers today and will have 21.0.28 posted in the next day or two. (Currently jpsoft.com is being attacked from a number of sites in China, so I'm trying to make sure that is resolved first.)
     
  6. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,869
    Likes Received:
    83
    Fixed in build 21.0.28 (already uploaded).
     
  7. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,970
    Likes Received:
    30
    With build 28, I now get this (which seems odd).
    Code:
    v:\> echo %@pshell[get-help get-help]
    TCC: (Sys) The process cannot access the file because it is being used by another process.
     "V:\]"
     
  8. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,970
    Likes Received:
    30
    I don't know exactly what is happening, but the command in my previous post causes a file named "]" to be created in the CWD.
    Code:
    v:\> d ]*
    
    v:\> echo %@pshell[get-help get-help]
    TCC: (Sys) The process cannot access the file because it is being used by another process.
     "V:\]"
    
    v:\> d ]*
    2017-05-24  01:00               0  ]
     
  9. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,869
    Likes Received:
    83
    WAD; there's nothing wrong with @PSHELL.

    The problem is your ECHO - which is expanding all of the embedded < and > characters in the "get-help" output.
     
  10. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,970
    Likes Received:
    30
    Roger! Got it. I just copied the command from the original post in this thread.
     

Share This Page