R
Roshni Aithal
Guest
Hi,
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.
When checked network packets from wireshark, from DPWS side, the “ScanAvailableEvent” is sent to PC but PC has not sent the “CreateScanJobRequest” to MFP.
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 part of 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:ump, EventHandlerInfo for (0000028617D05340):
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Name: @WFSR.DLL,-25105
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Description: @WFSR.DLL,-25106
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Icon: wfs.exe,-128
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Command line: wfs.exe
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, 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..
When PC is logged-in using Remote Desktop Connection (RDP), “rdp” session will be "Active" and the state of “Console” session will be “Conn” (not as “Active”). If we perform WS-Push Scan on the PC which is connected remotely, the Scan will be failed, because of the above mentioned error.
When PC is logged-in at its physical location,"console" session is "Active" and if we execute the WS-Push Scan, the Scan is successful.
Is this the limitation of OS / WIA?
Can WIA driver control the same ?
Continue reading...
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.
When checked network packets from wireshark, from DPWS side, the “ScanAvailableEvent” is sent to PC but PC has not sent the “CreateScanJobRequest” to MFP.
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 part of 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:ump, EventHandlerInfo for (0000028617D05340):
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Name: @WFSR.DLL,-25105
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Description: @WFSR.DLL,-25106
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Icon: wfs.exe,-128
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, Command line: wfs.exe
WIA: 9104.1960 1000 0 0 [wiarpc.dll] EventHandlerInfo:ump, 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..
When PC is logged-in using Remote Desktop Connection (RDP), “rdp” session will be "Active" and the state of “Console” session will be “Conn” (not as “Active”). If we perform WS-Push Scan on the PC which is connected remotely, the Scan will be failed, because of the above mentioned error.
When PC is logged-in at its physical location,"console" session is "Active" and if we execute the WS-Push Scan, the Scan is successful.
Is this the limitation of OS / WIA?
Can WIA driver control the same ?
Continue reading...