Target Computer in F110

Hi,
Can anyone please advice what is the use of Target Computer in APP F110 during Schedule Payment proposal and Schedule Payment Run.Can it be possible that I can download the report or the payment list from this Target Computer.
Right now I am getting my server as an option after F4 Help.What should i do to add some other option or any drive or location so that I can download the Payment list over there.
Please advice
Thanks
Rahul

Hi
Target computer specifies which computer is used to schedule the back ground job.
Ideally, we leave it empty which means that the system considers itself and does the background run for payments.
Hope you are clear...
Good Luck!
Lucid-Mind...

Similar Messages

A problem in provisioning target computer

Guys, I am engaged on keyboard driver developement. In host computer, the tool sets include visual studio 2013 and WDK 8.1 and in target computer, I installed WDK driver test service and run it as automatic service. The host OS is win7 ultimate version 64bits
and the target OS is win7 Embedded Standard 64bits. When I provision the target computer in visual studion 2013, at the step of Provision Computer and choose debugger settings->windows debugger(kernel mode), I selected serial as connection between host
and target, and then a series of steps are performed in configuration proccess. At last the proccess failed at the step, 'creating system restore point', the followings are logs, I just copied from log file,
Progress event: Current: 0, Max: -1, Message: "Connecting to computer "vsapp-enc""
Initialize: Computer: vsapp-enc
InstallComputer: Host Computer: AVU-CLIENT
InstallComputer: Host Architecture: x86
InstallComputer: Host 64bit Operating System: True
InstallComputer: Host Operating System Version: 6.1.7601.65536
InstallComputer: Process Administrator Privilege: True
Progress event: Current: 1, Max: 17, Message: "Connecting to driver test automation service"
Progress event: Current: 2, Max: 17, Message: "Getting computer system information"
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Progress event: Current: 3, Max: 17, Message: "Copying driver test automation files"
Progress event: Current: 3, Max: 17, Message: "Copying driver test automation files succeeded"
Progress event: Current: 4, Max: 17, Message: "Configuring WDK Remote User Account"
Progress event: Current: 4, Max: 17, Message: "WDK Remote User Account successfully created"
Initialize: Computer:
Initialize: Computer: vsapp-enc
Start result group:
Name: Install Driver Test Components
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestGroups\Install Driver Test Components.xml
Computer: vsapp-enc
Initialize: Computer: vsapp-enc
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Progress event: Current: 5, Max: 17, Message: "Installing .NET Framework (possible reboot)"
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\dotNetFx40_Full_x86_x64.exe" /select:"@Name='Installing .NET Framework (possible reboot)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_.NET_Framework_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:05:259]: [Installing .NET Framework (possible reboot)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\dotNetFx40_Full_x86_x64.exe" /select:"@Name='Installing .NET Framework (possible reboot)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_.NET_Framework_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing .NET Framework (possible reboot) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing .NET Framework (possible reboot) 00008.log
Computer: vsapp-enc
Test Binary: %SystemDrive%\DriverTest\Setup\dotNetFx40_Full_x86_x64.exe
Test Name: Installing .NET Framework (possible reboot)
Test Display Name: Installing .NET Framework (possible reboot)
Initialize: Computer:
Initialize: Computer:
RemoteExecute: Binary: %SystemDrive%\DriverTest\Setup\dotNetFx40_Full_x86_x64.exe
RemoteExecution: Arguments: /q /norestart /log %SystemDrive%\DriverTest\Logs\DotNetInstall.log
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Initialize: Computer:
Progress event: Current: 6, Max: 17, Message: "Installing test automation (x86)"
Initialize: Computer:
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:23:724]: [Installing test automation (x86)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x86) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x86) 00008.log
Computer: vsapp-enc
Test Binary: msiexec.exe
Test Name: Installing test automation (x86)
Test Display Name: Installing test automation (x86)
Initialize: Computer:
Initialize: Computer:
RemoteExecute: Binary: msiexec.exe
RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Test Authoring and Execution Framework x86-x86_en-us.msi" /qb- KITSROOT="%ProgramFiles%\Windows Kits\8.1" KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Test Authoring
and Execution Framework x86-x86_en-us.msi_install.log"
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Progress event: Current: 7, Max: 17, Message: "Installing test automation (x64)"
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:24:720]: [Installing test automation (x64)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing test automation (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_test_automation_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x64) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing test automation (x64) 00008.log
Computer: vsapp-enc
Test Binary: msiexec.exe
Test Name: Installing test automation (x64)
Test Display Name: Installing test automation (x64)
Initialize: Computer:
Initialize: Computer:
RemoteExecute: Binary: msiexec.exe
RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Test Authoring and Execution Framework x64-x64_en-us.msi" /qb- KITSROOT="%ProgramFiles(x86)%\Windows Kits\8.1" KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Test Authoring
and Execution Framework x64-x64_en-us.msi_install.log"
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Progress event: Current: 8, Max: 17, Message: "Installing debuggers (x86)"
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
Initialize: Computer:
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:25:582]: [Installing debuggers (x86)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x86)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x86)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x86) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x86) 00008.log
Computer: vsapp-enc
Test Binary: msiexec.exe
Test Name: Installing debuggers (x86)
Test Display Name: Installing debuggers (x86)
Initialize: Computer:
RemoteExecute: Binary: msiexec.exe
RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\X86 Debuggers And Tools-x86_en-us.msi" /qb- /l*v "%SystemDrive%\DriverTest\Logs\X86 Debuggers And Tools-x86_en-us.msi_install.log"
Initialize: Computer:
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Initialize: Computer:
Progress event: Current: 9, Max: 17, Message: "Installing debuggers (x64)"
Initialize: Computer:
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:26:641]: [Installing debuggers (x64)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing debuggers (x64)'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_debuggers_(x64)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x64) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing debuggers (x64) 00008.log
Computer: vsapp-enc
Test Binary: msiexec.exe
Test Name: Installing debuggers (x64)
Test Display Name: Installing debuggers (x64)
Initialize: Computer:
RemoteExecute: Binary: msiexec.exe
RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\x64 Debuggers And Tools-x64_en-us.msi" /qb- /l*v "%SystemDrive%\DriverTest\Logs\x64 Debuggers And Tools-x64_en-us.msi_install.log"
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Progress event: Current: 10, Max: 17, Message: "Installing driver test framework"
Initialize: Computer:
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
Initialize: Computer:
Initialize: Computer:
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing driver test framework'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_driver_test_framework_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:27:707]: [Installing driver test framework] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\msiexec.exe" /select:"@Name='Installing driver test framework'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Installing_driver_test_framework_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing driver test framework 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Installing driver test framework 00008.log
Computer: vsapp-enc
Test Binary: msiexec.exe
Test Name: Installing driver test framework
Test Display Name: Installing driver test framework
Initialize: Computer:
RemoteExecute: Binary: msiexec.exe
RemoteExecution: Arguments: /i "%SystemDrive%\DriverTest\Setup\Windows Driver Testing Framework (WDTF) Runtime Libraries-x64_en-us.msi" /qb- KITTARGET=1 /l*v "%SystemDrive%\DriverTest\Logs\Windows Driver Testing Framework (WDTF) Runtime Libraries-x64_en-us.msi_install.log"
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Initialize: Computer:
Progress event: Current: 11, Max: 17, Message: "Registering logging components"
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\regsvr32.exe" /select:"@Name='Registering logging components'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Registering_logging_components_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:28:743]: [Registering logging components] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\regsvr32.exe" /select:"@Name='Registering logging components'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Registering_logging_components_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Registering logging components 00008.xml
Log Path:
Computer: vsapp-enc
Test Binary: regsvr32.exe
Test Name: Registering logging components
Test Display Name: Registering logging components
Initialize: Computer:
RemoteExecute: Binary: regsvr32.exe
RemoteExecution: Arguments: /s %SystemDrive%\DriverTest\WTTLogcm.dll
Initialize: Computer:
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Progress event: Current: 12, Max: 17, Message: "Configure debugger settings (x64) (possible reboot)"
Initialize: Computer:
Initialize: Computer:
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
Initialize: Computer:
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
[11:23:29:020]: Removing any existing files from test execution folder
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureKernelDebugger'" /p:"DebugTransport=SERIAL" /p:"SerialPortNumber=1" /p:"BaudRate=115200"
/p:"StartPolicy=Active" /p:"IgnoreUserModeExceptions=0" /p:"SuppressReboot=1" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:29:373]: [Configure debugger settings (x64) (possible reboot)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureKernelDebugger'" /p:"DebugTransport=SERIAL" /p:"SerialPortNumber=1" /p:"BaudRate=115200" /p:"StartPolicy=Active"
/p:"IgnoreUserModeExceptions=0" /p:"SuppressReboot=1" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure debugger settings (x64) (possible reboot) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl
Computer: vsapp-enc
Test Binary: C:\Program Files (x86)\Windows Kits\8.1\Testing\Tests\Utilities\X64\DriverTestTasks.dll
Test Name: DriverTestTasks::_ConfigureKernelDebugger
Test Display Name: Configure debugger settings (x64) (possible reboot)
Initialize: Computer:
RemoteExecute: Binary: $KitRoot$\Testing\Runtimes\TAEF\te.exe
RemoteExecution: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureKernelDebugger'" /p:"DebugTransport=SERIAL" /p:"SerialPortNumber=1" /p:"BaudRate=115200"
/p:"StartPolicy=Active" /p:"IgnoreUserModeExceptions=0" /p:"SuppressReboot=1" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Initialize: Computer: vsapp-enc
Initialize: Computer: vsapp-enc
[11:23:30:613]: Result Summary: Total=1, Passed=1, Failed=0, Blocked=0, Warned=0, Skipped=0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Progress event: Current: 13, Max: 17, Message: "Configure computer settings (x64) (possible reboot)"
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
[11:23:31:204]: Removing any existing files from test execution folder
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureCommonSettings'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:31:596]: [Configure computer settings (x64) (possible reboot)] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureCommonSettings'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure computer settings (x64) (possible reboot) 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl
Computer: vsapp-enc
Test Binary: C:\Program Files (x86)\Windows Kits\8.1\Testing\Tests\Utilities\X64\DriverTestTasks.dll
Test Name: DriverTestTasks::_ConfigureCommonSettings
Test Display Name: Configure computer settings (x64) (possible reboot)
RemoteExecute: Binary: $KitRoot$\Testing\Runtimes\TAEF\te.exe
RemoteExecution: Arguments: "%SystemDrive%\DriverTest\Run\DriverTestTasks.dll" /select:"@Name='DriverTestTasks::_ConfigureCommonSettings'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_computer_settings_(x64)_(possible_reboot)_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Initialize: Computer:
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0
Initialize: Computer: vsapp-enc
Initialize: Computer: vsapp-enc
Initialize: Computer: vsapp-enc
[11:23:33:864]: Result Summary: Total=1, Passed=1, Failed=0, Blocked=0, Warned=0, Skipped=0
Result completed
Test process exit code: 0
Result status updated: Pass
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Progress event: Current: 14, Max: 17, Message: "Creating system restore point"
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
Initialize: Computer: vsapp-enc
InternalRunTest: Host Computer: AVU-CLIENT
InternalRunTest: Host Architecture: x86
InternalRunTest: Host 64bit Operating System: True
InternalRunTest: Host Operating System Version: 6.1.7601.65536
InternalRunTest: Process Administrator Privilege: True
Initialize: Computer: vsapp-enc
GetMachinePropertiesFromService: Computer Name: vsapp-enc
GetMachinePropertiesFromService: Architecture: AMD64
GetMachinePropertiesFromService: Operating System Version: 6.1.7601.0
GetMachinePropertiesFromService: Operating System Product Type: 1
GetMachinePropertiesFromService: Domain Joined: True
ExecuteProcess: Arguments: "%SystemDrive%\DriverTest\Run\cscript.exe" /select:"@Name='Creating system restore point'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Creating_system_restore_point_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
[11:23:34:288]: [Creating system restore point] Command Line:
te.exe "%SystemDrive%\DriverTest\Run\cscript.exe" /select:"@Name='Creating system restore point'" /rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml /enableWttLogging /wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Creating_system_restore_point_00008.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated
Created new result:
Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Creating system restore point 00008.xml
Log Path: C:\Users\Administrator\AppData\Roaming\Microsoft\DriverTest\TestRepository\Results\Creating system restore point 00008.log
Computer: vsapp-enc
Test Binary: cscript.exe
Test Name: Creating system restore point
Test Display Name: Creating system restore point
Initialize: Computer:
RemoteExecute: Binary: cscript.exe
RemoteExecution: Arguments: %SystemDrive%\DriverTest\Setup\CreateRestore.js
Initialize: Computer:
RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: -2147217406
Result completed
Test process exit code: -2147217406
Result status updated: Fail
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Initialize: Computer:
Progress event: Current: 14, Max: 17, Message: "Creating system restore point failed. Please ensure connectivity with the remote machine, and then restart the provisioning process."
Initialize: Computer:
Initialize: Computer:
[11:23:35:413]: Install Driver Test Components summary:
[11:23:35:413]:   Installing .NET Framework (possible reboot): Pass
[11:23:35:413]:   Installing test automation (x86): Pass
[11:23:35:413]:   Installing test automation (x64): Pass
[11:23:35:413]:   Installing debuggers (x86): Pass
[11:23:35:413]:   Installing debuggers (x64): Pass
[11:23:35:413]:   Installing driver test framework: Pass
[11:23:35:413]:   Registering logging components: Pass
[11:23:35:413]:   Configure debugger settings (x64) (possible reboot): Pass
[11:23:35:413]:   Configure computer settings (x64) (possible reboot): Pass
[11:23:35:413]:   Creating system restore point: Fail
Result Group Completed: Fail
Progress event: Current: 17, Max: 17, Message: ""
Progress event: Current: 17, Max: 17, Message: "Computer configuration log
My question is why I got such an error? And does this step depend on any service of target computer? I surf the net a little, it seems there is Volume Shadow Copy Service relevant. But it is missing in the target computer's service list, I found. Is this
the root cause?
Appreciate any help.

Hi Suma,
Did you check that VIRSANH/VIRSAHR BAPI are correctly installed on relevant back-ends ? Moreover, if using CUA to provision users, BAPI should be installed not only on the system hosting the CUA, but on every client system (eg. ECC, SRM, BI, ...).
You also may verify in SPAM transaction that you installed correct BAPI depending on your basis install (640, 700, ...) and on your GRC AC version (5.1, 5.2, ...). For example, if you are installing AC 5.2 on a BASIS700 system, corresponding package should be VIRSANH520_700 and/or VIRSAHR520_700. You may find more detailed information in "GRC Access Control ABAP install guide".
Best regards,
JC

Imac host doesn't see target computer

Hello,
I'm having difficulty copying files from the host computer to the target computer. The target computer is an Imac 700Mhz G3 and the host is a 400Mhz (DV?) G3. Both are running OS 10.3.9. The problem is that the target computer does not show up on the host desktop. I've tried rebooting the host but to no avail. Is this a firewire firmware issue? How can I check the firewire firmware version? Any info would be greatly appreciated.
Thanks,
Al

Hey Al,
Have you read through:
http://docs.info.apple.com/article.html?artnum=58583
The only thing there is requirements for the target:
"iMac (Slot Loading) with Firmware version 2.4 or later"
but you've got to have 4.1.9 since you're running 10.3.9.
But to check it go to "about this Mac > more info > Hardware overview
It should say:
"Boot ROM Version 4.1.9 f1"
Try another FireWire cord.
Try different FireWire spigots
Try switching host and target wouldn't make any difference for dragging files around.
Could have a blown FireWire ( A client blew hers out with a bad cord, I mean it was smoked! Scorch marks on the board and everything. Those are easy to diagnose "Uhhh I think it's this place where it's totally burned")
Richard

Licensing my application on a target computer

I built an application and intend to sell it for use in a target computer. How can I incorporate a parallel key for use with my application? Or are there other ways I can license my product? Help is greatly appraciated. Thanks.

Hi Kian,
we use Wibu Key for our own software product. Unfortunatly we do not have a LV interface because the app was written in C++.
The other method is a software method. The most popular is the one NI uses. The method is developed by Macrovision.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Host computer won't recognize the target computer.......

So here is a rundown of what happened....
I just bought Leopard and tried to install it on my computer. It said I did not have enough free space ( I need 11 GB, I have 1.4 available) and that it would have to delete everything on my computer to get it to install. Well, I didn't want that since not everything was backed up. Now, when I start up my computer the apple logo comes up with the spinning "sunshine rays" and then just shuts off. There is no way to get my computer to restart. I have tried using the "restart from" and selecting my hard drive and then the computer restarts, sunshine thingy spins, and then my computer turns off.
I have tried to run the disk repair only to have an error message come up half way through saying "the underlying task reported failure on exit". No idea what this means. There has to be some way for me start my computer back up or save all my files. I have bought the 1TB time capsule so that should fee up enough room for Leopard to run smoothly once I get it installed
I tried repairing it and I got the same message as I did trying to verify it. So here is another weird little tid-bit. When I try to re-install Tiger it doesn't locate my hard drive as an option to install it on. But when I use the install disk from Leopard it does locate and give me the option to install it on my hard drive. If I install Leopard and erase and format (journaled?) my hard drive in order to do so, will I be able to use any programs to recover my lost files?
So now I am trying to use my iMac as a host computer and the G4 that won't start as the target computer. I have tried everything I can think of but the host computer will not recognize the target hard drive. Everything is hooked up correctly I think and the hard drive from my bad computer should be on the desktop of my iMac but it isn't. Any ideas????

Hi-
The error report "the underlying task reported failure on exit" is a hard drive error that Disk Utility couldn't repair. However, if the Disk Utility was from the Leopard install disc, then the version is wrong. If the error came from the Tiger disc, you may need DiskWarrior to correct the error.
First, though, try repairing the hard drive with fsck.
Boot to Single user mode by holding Command+S while booting. In the resulting screen, at the command line, type /sbin/fsck -fy and press Return.
fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
The volume (nameofvolume) appears to be OK
If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
FILE SYSTEM WAS MODIFIED
Important: If this message appears, repeat the fsck command you typed until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do). Two, three or four tries may be necessary.
When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
Your computer should start up normally and allow you to log in.
If the fsck returns that the drive is OK in the first pass, and typing "reboot" doesn't get a proper startup, try resetting the PRAM on the G4. Hold CommandOption+PR while booting, hold until the second startup chime, and release. The machine, hopefully will boot.
Let us know how you fare with this.....

Error 21 on target computer

I am trying to run a labview executable on a target machine that only has the runtime version of labview installed. After installing all of the drivers that I could think of the program is still missing vis. However, after searching the source computer, I couldn't find the vis on that machine either.
The vis that it is missing include for example: DIO Port Config.vi, DIO Port Write.vi, AO Group Config.vi, AO *.vi, AI Control.vi, Counter Group Config. vi.
When the program stops complaining about missing all of these vis it tries to open with GUI but it only has the skeleton (none of the buttons, etc that are normally part of the GUI).
Again, I can't find any of these vis on the computer that has a full version of labview (and where the program works). So I don't know how to find them or what package they are apart of.
Any help/suggestions would be much appreciated.
I am not the developer of this program. I just have the executable which has worked on the two systems which have the same version of labview installed. I have Labview runtime 7.1 installed on the target computer.

Hello megresearch,
All of the VI's you mentioned are part of the Traditional NI-DAQ driver. The most recent version of this driver is 7.4.1, but you can download any version you might need from the following page on our website:
Drivers and Updates: Multifunction DAQ
Try installing this driver on your deployment PC and see if your executable works then. Let us know if you are still having any trouble.
Best regards,

WDK 8.1 Provisioning of target computer failure

I need help solving a test computer provisioning failure. I am trying to provision a Windows 8.1 (x64) target computer for WDK 8.1 driver testing using a Windows 7 (x64) host computer. Everything passes until the "Configure computer
settings (x64) (possible reboot)" step. The section of log file attached below shows an "Unknown error occurred:" after "Configure kernel debugging..." and "Configure test signing..." .
?xml version="1.0" encoding="UTF-16" ?
WTT-Logger
RTI ID="2294575628" Machine="MABRY0" ProcessName="C:\DriverTest\Run\te.exe" ProcessID="1900" ThreadID="3640" BaseTime="2015:1:29 19:12:54:964" Frequency="1998203" /
CTX ID="384048256" Current="WTTLOG" Parent="ROOT" /
Machine
Build="9600.00"
Platform="AMD64"
OS="Windows 8.1 Pro"
ServicePack=""
Version="6.3"
BuildLab="winblue_r3"
BuildDate="140827-1500"
Language="English (US) (REDMOND)"
Config="n/a" CA="2422874" LA="2423010"
rti id="2294575628" /
ctx id="384048256" /
/Machine
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="Taef:Title"
AttributeValue="Test Authoring and Execution Framework v3.7k for x64" CA="2456257" LA="2456391"
rti id="2294575628" /
ctx id="384048256" /
/MetadataRef
RTI ID="4144358067" Machine="MABRY0" ProcessName="C:\DriverTest\Run\te.exe" ProcessID="1900" ThreadID="4936" BaseTime="2015:1:29 19:12:55:964" Frequency="1998203" /
CTX ID="2681058065" Current="DriverTestTasks::_ConfigureCommonSettings" Parent="WTTLOG" /
StartTest
Title="DriverTestTasks::_ConfigureCommonSettings"
TUID="" CA="2549161" LA="2549324"
Data
WexTraceInfo ThreadId="4936" ProcessId="1900" TimeStamp="93985572759"/
/Data rti id="4144358067" /
ctx id="2681058065" /
/StartTest
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="Architecture"
AttributeValue="x64" CA="2575028" LA="2575125"
rti id="4144358067" /
ctx id="2681058065" /
/MetadataRef
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="OriginalName"
AttributeValue="C:\DriverTest\Run\DriverTestTasks.dll" CA="2599587" LA="2599684"
rti id="4144358067" /
ctx id="2681058065" /
/MetadataRef
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="TaefTestType"
AttributeValue="Native" CA="2626121" LA="2626221"
rti id="4144358067" /
ctx id="2681058065" /
/MetadataRef
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="OriginalName"
AttributeValue="DriverTestTasks" CA="2652519" LA="2652646"
rti id="4144358067" /
ctx id="2681058065" /
/MetadataRef
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="OriginalName"
AttributeValue="DriverTestTasks::_ConfigureCommonSettings" CA="2684909" LA="2685047"
rti id="4144358067" /
ctx id="2681058065" /
/MetadataRef
MetadataRef
Id="WexLogger"
Inherit="False"
AttributeName="RebootPossible"
AttributeValue="true" CA="2710373" LA="2710474"
rti id="4144358067" /
ctx id="2681058065" /
/MetadataRef
RTI ID="1911229277" Machine="MABRY0" ProcessName="C:\DriverTest\Run\te.exe" ProcessID="1900" ThreadID="3836" BaseTime="2015:1:29 19:12:56:214" Frequency="1998203" /
Msg
UserText="Configure kernel debugging..." CA="3035933" LA="3036090"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986073209"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Unknown error occurred: -1069350910" CA="3342998" LA="3343122"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986442763"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Failed to enable kernel debugging. Error: 32768." CA="3437768" LA="3437902"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986537544"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="" CA="3481908" LA="3482191"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986539132"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Configure test signing..." CA="3506742" LA="3506928"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986583604"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Unknown error occurred: -1069350910" CA="3787285" LA="3787417"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986887010"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Failed to enable test signing. Error: 32768." CA="3877649" LA="3877797"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986977439"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="" CA="3902410" LA="3902578"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93986978998"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Configure registry settings..." CA="3933167" LA="3933345"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93987004144"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Key: SYSTEM\CurrentControlSet\Control\CrashControl" CA="3965886" LA="3966065"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93987034959"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
Msg
UserText="Failed to configure the driver test computer" CA="5700051" LA="5700201"
Data
WexTraceInfo ThreadId="3652" ProcessId="4300" TimeStamp="93988791146"/
/Data rti id="1911229277" /
ctx id="2681058065" /
/Msg
EndTest
Title="DriverTestTasks::_ConfigureCommonSettings"
TUID=""
Result="Fail"
Repro="" CA="5731542" LA="5731698"
Data
WexTraceInfo ThreadId="4936" ProcessId="1900" TimeStamp="93988802236"/
/Data rti id="4144358067" /
ctx id="2681058065" /
/EndTest
PFRollup
Total="1"
Passed="0"
Failed="1"
Blocked="0"
Warned="0"
Skipped="0" CA="5773445" LA="5773613"
rti id="2294575628" /
ctx id="384048256" /
/PFRollup
/WTT-Logger

Ethan, please run through this provisioning scenario with tracing enabled and send me the resulting .etl log file:
Close VS 2013
Start WDK tracing by running the following commands from an elevated command prompt:
IF NOT exist %temp%\WDK md %temp%\WDK
::Create text file containing WDK providers (all flags, all levels)
set TempWdkEtwProv=%Temp%\WDK\WdkEtwProviders.txt
echo {cc266499-ae72-483f-92eb-68fe819ad751} 0xff 0xff > %TempWdkEtwProv%
echo {dabf2b2d-0b18-4391-a6e6-c6030445b5de} 0xff 0xff >> %TempWdkEtwProv%
echo {be23ac82-fb9b-4dab-b532-bd02a1164ff2} 0xff 0xff >> %TempWdkEtwProv%
echo {061c5f03-df1c-45de-ac2a-c9c0f4dbbcc3} 0xff 0xff >> %TempWdkEtwProv%
::Create and start new trace session with the above WDK providers
logman create trace WdkConfigCompSession -o "%temp%\WDK\ConfigureComputerTrace.etl" -pf "%TempWdkEtwProv%"
logman start WdkConfigCompSession
Start VS 2013 and try to provision your target computer as before. This will take a little longer with detailed tracing enabled. Please let me know if it's unbearably slow and we can ratchet down the logging level and redo.
Once it gets to the point where it appears to hang, wait for a minute or two and then cancel out of the dialog
Close VS 2013
Stop WDK tracing by running the following commands from an elevated command prompt:
logman stop WdkConfigCompSession
logman delete WdkConfigCompSession
start %temp%\WDK
This should pop up File Explorer at the %temp%\WDK folder. Copy the ConfigureComputerTrace_######.etl file from there and upload it to my OneDrive Pro (send me your MS account info to
[email protected] and I'll send you a folder you can upload this to)
Thanks,
Steve
This posting is provided AS IS with no warranties, and confers no rights.

HT4413 I completed the migration, however I get a message when I try to open the files on my target computer that I do not have "access."?

I recently completed a migration from an old laptop to a new one. It all well well, however I get a message when I try to open the files on my target computer that I do not have "access"?
Any suggestions?

Drag the migrated home folder to the desktop and provide your administrator password.
(88475)

Can't control mouse on target computer

Hi all:
I have ARD 3.0 and can connect to my laptop from my desktop via Apple Airport Extreme. The desktop of the target computer comes on screen. When I click the arrow to take control of the computer, the mouse moves and then jumps back to the position the mouse is in on the target computer. Also if I click on anything, it has no action, just jumps back to the mouse position. Any ideas why or how to fix it?
Thanks,
Phil

I have exactly the same problem.
I can not control the mouse on my remote Mini from my G5. Controlling the mouse on my remote iMac G5 works fine.
Suggestions?
G5 2x2.5 Mac OS X (10.4.8)

HT4889 Source computer getting stuck on "looking for other computers", but target computer finds source computer.

I'm hoping someone can help me get my source computer to find my target computer when running Migration Assistant. The source computer (late '08 macbook pro running OS X 10.7.5) gets stuck on "looking for other computers". But target computer (late '09 imac running OS X 10.7.5) finds source computer. Both show they are connected to same wifi network in System Preferences-network. Note: I have tried with both internet sharing on and off. Note: Source computer also can't find its external hard drive when plugged in. Related? Any ideas for either issue?

Ok, more updates.
In my old Mac (Pro) I have several hard drives installed. I was able to create a Time Machine back-up to a non-system HD. I plan on removing this volume and putting it in an external enclosure as soon as I can find the right cables for that enclosure. Meanwhile....
I saw on one support doc an instruction to open Sharing on the source Mac (my old one, in this case) and make sure the machine had a name specified. I already had done that, but noticed that a specific name based on that was mentioned for other computers to contact it. For example, if my source machine is named "myOldMac", other computers could address is at "myOldMac.local".
I connected the two computers directly via an Ethernet cable and I ran Migration Assistant again. When I got to the "Looking for source" screen, I clicked the button for "Other Server" and entered "afp://myOldMac.local". This actually found my old Mac. I was prompted to enter the password for the account "root". I changed the name to my account's short name -- "raboyle" not "Robert Boyle" -- and entered the correct password and I actually got a list of volumes to access. In the list were: the hard drives (by volume name), the home folders of the user accounts, and the Public Folders for each user account.
I tried accessing both my boot volume and the home folder for my primary account, and proceeded to a screen with the following text: "Choose which backup to transfer information from:". The list provided, however, was empty. On the chance that it was looking specifically for a Time Machine backup, I then specifically chose the HD volume with the backup I had just created. Again, the list to choose where to grab my data from was empty.
So, at least I'm advancing a little bit beyond the "Looking for source" screen ... but then again, since I hit yet another roadblock I can't say whether I've taken one step forward or two steps back.

How do I view the DESKTOP (not the hard drive) of my TARGET computer?

I've successfully linked two MACS using a Firewire cable and TARGET mode. When I click on the Target computer's icon, I am linked to its Hard Drive. But what I really want is to see the DESKTOP of the Target computer, and be able to drag files/folders from the Target computer to the linked computer. Is this possible? If not, how do I locate the files/folders on the Target computer desktop? Thanks

In FW Target Disk Mode only the hard disk drive and its folders/contents are seen
by the host computer viewing the TDM-enabled second machine.
If the status of the Target Disk mode computer were such that you could gain access
to a User account's Desktop folder in that user's folder (sans permissions issues)
the contents on a User's desktop folder may be retrieved. But not likely in TDM.
When the computers are both near equal in health, a way to gain access to a
remotely attached computer's hard disk drive, desktop/Finder, etc would be
through a Remote Desktop application; one could remote Administer that one.
There may be another way to do what you want, but viewing the FW TDM
enabled computer from the healthy one used to gain access to it, as though
it were a healthy computer and see its desktop file (finder) is unlikely.
The status of this questionable computer being an unknown, other ideas
would have to be based on more information to determine other options.
{and I see by the time I typed all this & had minor distraction, here, you
did get at least two replies that direct you to the user desktop folder.}
Good luck & happy computing!
{edited}

Is ExceptionDeployer run from the target computer or just pointed to the target?

Is ExceptionDeployer run from the target computer or just pointed to the target? I created a package with CCP. No problem pushing the .pkg in the Build folder to the target using Apple Remote Desktop. Then I copied the Exceptions folder to /Applications/Adobe/ on the the target machine and ran:
sudo /Applications/Adobe/Exceptions/ExceptionDeployer --workflow=install --mode=post
The output says
Starting the ExceptionDeployer...
Starting installation of payload (AdobeHelp)
But then it just hangs.
What could I be doing wrong? Is this the correct documentation?: http://helpx.adobe.com/creative-cloud/packager/using-exceptions-deployer.html

Thanks I still got all the notes in my iphone... but at the moment I cannot sync or manage my iphone in itunes as itunes says that I should restore my iphone or set up a new iphone...
If I do... I think I may lose all the notes which at the moment in my iphone perfectly... Itunes just does not pick up my iphone.. I tried to uninstall itunes and installed it again... but the same problem appears...
Anyone has some ideas?!Thankssssssssssssssss!

Installing Orchestrator Run Program Service requires administrative privileges on the target computer.

We have a simple runbook that runs an .exe program local on a remote server.
When I run the runbook within the Runbook Designer and the Runbook Tester it runs succesfully.
When I run the runbook within the Orchestration Console (http://server4:82) I get the error message "Access is denied. Installing Orchestrator Run Program Service requires administrative privileges on the target computer."
Orchestrator hierarchy:
server1 Management Server
server2 Runbook Designer
server3 Runbook Server
server4 Web Server

Already solved it!
Even after making the Service Account a Domain Admin it didn't work after restarting the two services on server1. But I forgot the service on server3! Apparently when you use the Web Server it runs the runbook through the Runbook Server and when you
use Runbook Designer it runs locally within the Runbook Tester?

Payment file duplication in target system in F110 Transaction

Hi All
Payment file duplication in target system. Wherein since the Print Job was scheduled twice by user, the duplication of payment had taken place.The payment medium program u201CRFFOAVIS_FPAYMu201D is use to control the generation of duplicate payment file at automatic payment run program(F110).User needs an warning message if print job is schedule twice on same date and same identification number.Has Any one implemented such a scenario.
Thanks!

Hi Vikram,
Please set up the validation with the help of your abaper in T.Code OB28 with message type E along with message variables co.code and header level tables.
Regards,
Srinivas Muthyala

Payment file duplication in target system at F110 transaction

Hi All
Payment file duplication in target system. Wherein since the Print Job was scheduled twice by user, the duplication of payment had taken place.The payment medium program u201CRFFOAVIS_FPAYMu201D is use to control the generation of duplicate payment file at automatic payment run program(F110).User needs an warning message if print job is schedule twice on same date and same identification number.Has Any one implemented such a scenario.
Thanks!

Hi
System usually gives warning message F0417 aaginst the duplicatate print schedule , no need to do anything to get this message..
Please check print log in additional filed tab in F110 , you will find this warning message in the log.
Further you can chcek this warning message property if you can change this from warning to warning plus email or any other option, which will prevent /alert duplicate file processeing.
Cheers
Mukta

Target Computer in F110

Similar Messages

Maybe you are looking for