WISard-FAILURE-ENCODING

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • October 23, 2008 at 9:24 am #1541
    Bleeuwen
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    We have currently a new V90LE machine and are trying to pull an Image from it with WDM 4.5.1

    The terminal boots and is getting started, but then fails and reboots to XPe. The failure i’m getting in WDM is the following: Try 1:WISard-FAILURE-ENCODING

    Somebody an idea how to solve this issue? Is this an problem of WDM 4.5.1 and V90LE? All our existing devices (9150SE) are working properly.

    October 24, 2008 at 9:15 am #14205
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Have you installed any hotfixes on your WDM server? you should install the WDM 4.5.1 HF04051027707 Hotfix Rollup Beta!
    If you already have that, then manually copy the toolssa folder from the hotfix to your ftprootrapport folder.

    CG

    October 24, 2008 at 9:23 am #14206
    Bleeuwen
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    Hi ConfGen,

    Thanks for the reply i will download and install the rollup hotfix. When the test are done, i will let it now

    October 24, 2008 at 9:32 am #14207
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    If you see during the install of the hotfix that the copy process of the imaging files is very slow (overall install time of HF more than 5 minutes) it is very likely that the old files would still be there. In this case you should copy the tools folder manually afterwards.

    CG

    October 27, 2008 at 11:03 am #14223
    Bleeuwen
    Member
    • Total Post: 29
    • Frequent Flyer
    • ★★★

    The old tools were still there (it sure took a long time to update) so i’ve copied the new tools over them.

    When i try to pull an image i’m still getting the same error: Try 1:WISard-FAILURE-ENCODING.

    Should i look for network problems (non so far are found)?

    October 27, 2008 at 11:45 am #14224
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Two things to do:
    – open the pull.i2c file in the toolssa9v92folder
    – alter =YES to =NO

    Test again
    If it fails alter
    =NO to =YES
    in the same file and try again. This will not fix it at all but should write a more detailed log file in your fptrootrapportimagefolder

    CG

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.