TCX failed to add device

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #6816
    Avatarkramman
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    Hello,

    I am trying to use a USB rfid reader on a R10l thin client. We are connecting to a windows 2003 box that we use for administration. TCX seems to work properly on the system. I have attached other USB devices that have been passed thru properly, but when I attach this reader TCX recognizes it and the warning dialog box comes up but it never passes it thru. I took a log of when connecting it and among other things it says Failed to Add Device. Is this an issue with the device or TCX? I have also tried to add a uniquie exception for the specific device with the same results. Here is the entire log




    ****************************************************************************
    TCX USB Virtualizer : 4, 1, 0, 19
    ****************************************************************************
    g_nDebugZone = 0xffff, "File logging" enabled
    +__AuthenticateWorkerThread(), TID = 0x0000100c
    Received Client HELLO_MESSAGE
    Protocol version - 1, Compatible with USB Virtualizer 2.X.X
    Connection from "32 bit WTOS" client machine
    Client Product version is (4.0.0)
    Sending Server HELLO_MESSAGE (protocol version 2)
    Server Product version is (4.0.0)
    Received AUTH_INIT_MESSAGE
    Sending AUTH_CHALLENGE_MESSAGE
    Received AUTH_RESPONSE_MESSAGE, Authentication PASSED
    Sending AUTH_RESULT_MESSAGE
    Received CREATE_WRITE_CHANNEL_MESSAGE
    Sending CREATE_WRITE_CHANNEL_MESSAGE, Device Id (Unique id) = 0x00008000, StatusCode = 0x00005000
    Adding CConnectionContextV1 to the map: hContext = 0x00008000
    +__AuthenticateWorkerThread(), TID = 0x000011f8
    Received Client HELLO_MESSAGE
    Protocol version - 1, Compatible with USB Virtualizer 2.X.X
    Connection from "32 bit WTOS" client machine
    Client Product version is (4.0.0)
    Sending Server HELLO_MESSAGE (protocol version 2)
    Server Product version is (4.0.0)
    Received AUTH_INIT_MESSAGE
    Sending AUTH_CHALLENGE_MESSAGE
    Received AUTH_RESPONSE_MESSAGE, Authentication PASSED
    Sending AUTH_RESULT_MESSAGE
    Received CREATE_READ_CHANNEL_MESSAGE, Device Id (Unique id) = 0x00008000, Session Id = 0x00000001
    -__AuthenticateWorkerThread(), TID = 0x0000100c
    Administrator has enabled security warning pop-ups
    The server is configured to allow this device, VID = 0x1071, PID = 0x0001
    processpath - C:Program FilesWyseTCXServerUSB Virtualizer\UIuserprompt.exe, arguments - 14,
    Attaching "New device" to the virtual USB bus.......
    m_lpFtBusApi->AddDevice() failed, GetLastError() = 0x57
    FAILED to AddDevice
    Sending CREATE_READ_CHANNEL_MESSAGE, Device Id (Unique id) = 0x00000000, StatusCode = 0x0000500c
    WSAGetLastError = 0x00000000, Protocol error (NET_ERROR_XXX) = 0x500c
    -__AuthenticateWorkerThread(), TID = 0x000011f8
    #20969
    ConfGenConfGen
    Keymaster
    • Total Post: 11241
    • Jedi Master
    • ★★★★★★★

    With “unique exception” you mean a ForceRedirect command in the wnos.ini?

    CG

    #20975
    Avatarkramman
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    no I added an entry into the TCX software, but upon searching the force redirection in the wnos.ini seems like it might work. The way my company has the terminals set up they dont currently use a wnos.ini file. Is there a tutorial on how to get the terminals to use the wnos.ini file? Would i use the WYSE device manager?

    #20983
    ConfGenConfGen
    Keymaster
    • Total Post: 11241
    • Jedi Master
    • ★★★★★★★

    Products – WTOS – Getting Started.

    CG

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