header1   header
header
header Register : : Login header
header
connector   connector
menuleft menuright
submenu   submenu
left
Fragment Blob Error
Last Post 27 Mar 2008 07:11 AM by Marco Shaw (MVP). 3 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
RabbitzUser is Offline
New Member
New Member
Posts:2
Avatar

--
21 Feb 2008 06:16 PM

    Using the 2.0 CTP

    Command:

    Invoke-Expression -ComputerName MyMachine -Command Get-Service

    Returns:

    Invoke-Expression : Fragment blob length is out of range: 1814058546

    At line:1 Char:10

    + Invoke-Expression <<<< -ComputerName MyMachine -Command Get-Service

     

    I have tried this with a remote machine name and also the local machine name.

    I have also tried with various commands.

    All with the same result.

     

    If I omit the -ComputerName then it returns correctly. 

    What have I missed?

     

    Colin W

    Marco Shaw (MVP)User is Offline
    Veteran Member
    Veteran Member
    Posts:1647
    Avatar

    --
    03 Mar 2008 04:36 AM
    What OS? Using invoke-expression, especially on a a remote machine will try to open a temporary runspace on the remote machine. There's some kind of problem though.

    The PSH v2 install should have required winrm 1.1, so you should be good there, but I'd want to verify the winrm and winrs commands are running. From PSH or DOS: winrm -? or winrs -?.

    Try a few remote commands to make sure the remoting layer is working OK.
    Marco

    *Microsoft MVP - Windows PowerShell
    https://mvp.support.microsoft.com/profile/Marco.Shaw
    *Co-Author - Sams Windows PowerShell Unleashed 2nd Edition
    *Blog - http://marcoshaw.blogspot.com
    RabbitzUser is Offline
    New Member
    New Member
    Posts:2
    Avatar

    --
    25 Mar 2008 03:54 PM

    Sorry in the delay getting back to this.

     

    OS's are XPSP2, 2k3.  winrm appears to be running, but regardless no joy.

     

    There were some DCOM errors being generated.  Apparently due to permissions.  However if it is using DCOM I am not interested (once bitten...)

    I will put this on hold until the full release.

     

    Colin W

    Marco Shaw (MVP)User is Offline
    Veteran Member
    Veteran Member
    Posts:1647
    Avatar

    --
    27 Mar 2008 07:11 AM
    invoke-expression (**even locally**) depends on the remoting layer, so winrm must be working properly. The winrm client is written in VBScript and uses COM to interface with winHTTP.dll.
    Marco

    *Microsoft MVP - Windows PowerShell
    https://mvp.support.microsoft.com/profile/Marco.Shaw
    *Co-Author - Sams Windows PowerShell Unleashed 2nd Edition
    *Blog - http://marcoshaw.blogspot.com
    You are not authorized to post a reply.


    Active Forums 4.3
    right
    footer   footer
    footer Sponsored by Quest Software • SAPIEN Technologies • Compellent • Microsoft Windows Server 2008 R2 footer
    footer   footer