none
WIA WS Push Scan fails on Remote Desktop Connection (RDP) session RRS feed

  • Question

  • Hello Community,

    We are executing WS-Push Scan in to PC logged in remotely.

    When we log-in to Windows PC(Windows 10 20H1) remotely (using RDP) and executes WS-Push Scan, the Scan fails.

    Looking at the wiatrace log we found that, if "console” session is Active, WIA will start Scan by sending “CreateScanJobRequest”. If “console” session is not Active, WIA will NOT start Scan.

    Below is snippet from Wiatrace.log:

    WIA: 9104.1960 1000 0 0 [wiarpc.dll] WiaEventHandlerLookup::getHandlerRegisteredForEvent, We found key ScanButton, looking for default handler...
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] WiaEventHandlerLookup::getHandlerRegisteredForEvent, Found handler:
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo::Dump, EventHandlerInfo for (0000028617D05340):
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo::Dump, Name: @WFSR.DLL,-25105
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo::Dump, Description: @WFSR.DLL,-25106
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo::Dump, Icon: wfs.exe,-128
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo::Dump, Command line: wfs.exe
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo::Dump, CLSID: {EABBD70D-A25F-4E90-96A4-7105FD3B53B1}
    WIA: 9104.1960 1000 0 0 [wiarpc.dll] WiaEFireEvent, Command line registered event handler
    WIA: 9104.1960 1016 0 0 [wiarpc.dll] ERROR: GetUserTokenForSession, GetWinStationUserToken failed (0x000003F0), target session id: 5
    WIA: 9104.1960 1016 0 0 [wiarpc.dll] WARNING: WiaEFireEvent, The session currently attached to the console (5) does not appear to be an active user session

    WIA: 9104.1960 1016 0 0 [wiarpc.dll] WiaEFireEvent, Processing WIA event completed
    WIA: 9104.1960 1016 0 0 [wiarpc.dll] WiaEProcessNonPendingCall, Processing non pending async RPC call completed (pending call: 0, RPC status: 0x00000000)
    WIA: 9104.1960 1016 0 0 [wiarpc.dll] WiaERpcCallback, Async RPC callback complete, self-stop..
    WIA: 9104.14388 1016 0 0 [wiarpc.dll] WiaEventsTerminate, Event termination in progress..


    On further analysis, whenever, we logged-in to Windows 10 PC using Remote Desktop Connection (RDP), “rdp” session will be Active and the state of “Console” session will not be “Active” ( “Conn”).

    We understood that, the failure to start Scan from WIA is due to RDP login, as below,

    • When user logged-in to Windows PC, from its physical location, and executes WS-Push Scan, the Scan succeeded.
    • When user logged-in to Windows PC, remotely, (using RDP), and executes WS-Push Scan, the Scan failed.

    Whether this behavior of WIA is expected or an issue or limitation?

    Or is it OS limitation while using RDP?

    Is there any workaround given from Microsoft?

    Thanks and Regards,
    Divya

    Tuesday, June 30, 2020 2:38 PM

Answers

  • I believe this is policy.  There is some security risk in allowing a remote user to access a local camera.

    Tim Roberts | Driver MVP Emeritus | Providenza & Boekelheide, Inc.

    • Marked as answer by Divya Kr Thursday, July 2, 2020 3:52 AM
    Wednesday, July 1, 2020 3:13 AM

All replies

  • I believe this is policy.  There is some security risk in allowing a remote user to access a local camera.

    Tim Roberts | Driver MVP Emeritus | Providenza & Boekelheide, Inc.

    • Marked as answer by Divya Kr Thursday, July 2, 2020 3:52 AM
    Wednesday, July 1, 2020 3:13 AM
  • Thank you for reply, Tim Roberts.

    I understand, some security risk is involved in allowing remote access to a local camera.

    But is it defined or mentioned anywhere in MSDN?

    Regards,

    Divya

    Wednesday, July 1, 2020 4:47 AM