DDC and FTP errors

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #410
    rigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Does anyone know why I would be getting this type of error when the DDC is running …
    Error 10001 No valid FTP Information Set Line #:31 Cmd: SF “MS06-066_xpesp2cqfespmsg.dll” “C:qfespmsg.dll”

    This error shows in the Update ManagerScheduledpackages window in the first of several queued packages. All of the other packages behind this one show a Red Cross, with message “package stopped by previous related error package”

    Rapport v 4.4.1 XPe S90

    Thanks

    [/url]

    #9525
    rigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    So my Default Device Configuration sees that it needs to update a device, and it queues the required packages, but fails on installing the first one.

    I have manually installed this package on other devices, so its not that package.

    #9547
    rigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Anyone with any ideas on this ?

    #9548
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi Rigs,

    Sorry I am not sure on this one. Can you DDC any package? Try download on from this site and see if you can DDC it to a device.

    As an aside, I have tried to DDC packages to XPe and I find that the Lock User/End Lockout does not work and I had to make a RB (reboot) at the end of the script.

    -TT

    #9561
    rigs
    Member
    • Total Post: 12
    • Regular Joe
    • ★★

    Thanks for the reply TT,

    The packages Ive included in the DDC are wyse released MS patches, and as such all have a LU, EL, and RB in them.

    Cheers.

    #9664
    karaziel
    Member
    • Total Post: 74
    • Back Stage Pass
    • ★★★★

    Its little bit of a stretch but have you checked the ‘JOB’ table of the Database?

    The devices scheduled updates are stored in the ‘COMMAND’ table and the SWREP sync jobs are stored in the ‘JOB’ table. I’ve seen orphaned “jobs” stuck in the ‘JOB’ table and that could cause a problem like this as it would try to process a sync JOB that doesn’t actually exist.

    You could also try to download the debugviewer to see what’s actually happening in the background.

    -k

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