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,

Similar Messages

DVD Burn problem. "Device error - the target device isn't suitable for use"

Hello everyone,
I initially had a lot of problems with PE8. However the nVidia driver update solved most of them.
Just thought it was important to report success as well as failure!
However one problem remains. I get the following error at the 96% mark while burning. "Device error - the target device isn't suitable for use". It is always at the 96% mark and the program is "compiling [something]" when this happens.
Having searched this site I notice that user rgferg posted a similar problem 13 days ago but was redirected to repost in a different place, but never did.
I have tried to burn a 1hr clip 4 times and every time I have selected the slower burn speed (8MB/s) as has been suggested. It seems that inferior media is a culprit, so I have bought some [quality] Verbatim DVD-R media to try in my Phillips SATA optical drive. I am sceptical this will work, but open minded nonetheless. I will give it a whirl when my computer has stopped capturing the VHS I am working on.
Each time the burn failed the disk was automatically ejected and the burn process had actually started and progressed perhaps ~40% or so.
This indicates to me that it is a drive sharing issue, rather than a media issue. Somewhere on this forum it suggests that I go through a 20+ step process and delete/disable every piece of software that can compete with Premiere among other things. IF I do this what do I burn with outside of Adobe? Do I have to get imgburn or whatever it was called? What if I like Nero? Nero 6 has worked great for me for 3 years.
So given I am willing to uninstall my old optical drive burning software, who out there can recommened commercial software that for them creates a painless Adobe burning experience with no errors or conflicts? Perhaps there is another solution that I did not see on this forum?
I am running Windows XP SP3. I have the latest nVidia drivers for my SLI GeForce 7600 GS cards. I have 3 monitors. RAID 0 SATA, 2GB RAM, Athlon X2 5400.
Justin.

OK been working through the list of 20 things Adobe recommends to fix DVD burn error. No luck yet:
system meets minimum requirements
Project size does not exceed disk capacity
successfully burned project to DVD folder -thus skip to step 8.
8. Using new blank media for burning
9. Try different media and DVD burners. Bought Verbatim DVD-R. Don't have another DVD burner. Adobe's supported burner list is VERY short, so of course mine is not on it.
10. Uninstalled Nero 6. Did NOT uninstall Acronis True Image workstation or Lightscribe. These do not access the drive unless I say so!
11. Have not yet disabled startup items and services. This will take a lot of work and will leave to last. Deactivated Spybot thus far.....
12. Disabled IMAPI CD burning COM
13. DMA if available already set. Haven't set this in BIOS yet. I already think it is, but will check next boot.
14. Updated DVD firmware
15. Already updated nVidia drivers
16. Don't have any other DVD drives to disconnect.
17. MPEG workaround. Will resort to if required.
18. Disable Autoplay? XP only has "prompt me each time to choose an action". I have set this for ALL file types.
19. Have NOT refreshed the DVD drivers in the registry. This step involves uninstalling PE8. Will leave this as last resort.
20. Visit forums to see if other have the same problem. Hi guys
So still working through some of the items above.
Can anyone direct me to advice on how to write the encoded files sent to the hard drive, or the VOB files that PE8 failed to burn to a disk? Will the former work with DVD menus?
What a process.
Stay tuned.
Justin.

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

Device Error-The Target Device Isn't Suitable For Use

I read this in another forum after I experience this problem. Hope it helps some of you. I encountered the problem when I was exporting my finished movie. I had added a few effects like transitions and menu makers as well as stop markers to my timeline. When I went to Share, Create Disc and was exporting to a folder on my drive so I can preview the movie before I actually burn it to a Disc. During encoding well after 50% it stopped and said "DEVICE ERROR-THE TARGET DEVICE ISN'T SUITABLE FOR USE". I tried a few things that were normal when trying to export.
1. Restarting.
2. Created a new folder.
3. A different drive.
4. A DVD-RW.
Nothing was working, so I turned to Adobe forums and others like it. I found that Stop Markers can cause problems as well as some menu markers. It advised to delete the markers and try exporting again. Sure enough it worked, it exported with no problem. But I didn't like that after watching to video and reaching the end it would go to the next chapter without going back to the menu like most DVD videos do after playing. So I restarted Premiere and added all my Stop Markers to the timeline and began to export the movie and it worked just fine. I'm guessing that it just needed to be deleted and added again later after doing a restart so the computer has a fresh cache. Restarting computer works well after 1 hour of editing.

Erwin - thank you for the tip. I have had the same problem and tried several builds as you have taking aroound 2.5
hours per build. Removing the Stop marker has enabled me to write to a directory, Still have an error with regard to the menu not automatically shoiwng. However, as I write, burning direct to a DVD to remove any copying problems..
Again, many thanks for your help.
Tony

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.....

What to do about Backup failed with error: The target volume is read-only

This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again. Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.

Pondini wrote:
odysseus wrote:
This is a weird story. My wife has a PowerBook G4/1.33 GHz that she uses in clamshell mode with a 20" Cinema Display. One day under OS X 10.5.6, her Time Machine backups (to a networked 500 GB Time Capsule) failed with the error: Backup failed with error: The target volume is read-only. So I upgraded her to 10.5.7 and erased the sparseimage file, starting a new Time Machine backup. And it just happened again.
Try repairing the sparse bundle, per #A5 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
I've tried this before, but it can't be repaired, because it can't be mounted.
Any idea how this sort of problem arises? My wife was doing something at her computer when the Time Machine error occurred.
One possibility is, the HD in the Time Capsule is beginning to fail (all HDs fail, sooner or later).
I'm backing up to my own sparseimage bundle just fine.
Please don't advise us to upgrade to 10.5.8, because her PowerBook freezes not infrequently with any OS later than 10.5.6, and I was just about to downgrade her from 10.5.7 to 10.5.6.
Those two things may be related. Whatever's going wrong may very well be what's corrupting the backups.
I'd recommend finding out what's wrong with the Powerbook. It's impossible to tell, of course, but that may be the root of the problem.
There's a problem with PowerBooks and Cinema Displays. I've posted a lot about this. Even after a motherboard replacement, my PowerBook G4/1.67 GHz had freezes, and eventually Apple gave me a MacBook Pro, but I think there's a failure involving hardware/software design.
If you haven't yet, I'd start by dong a +*Verify Disk+* on it's internal HD (also per #A5);
That checks out fine.
if there are no errors, or they're fixed and the problem continues, run the +Apple Hardware Test+ from the disc that came with the Mac. (One of the discs should have that, and instructions for running it, printed in tiny type on the label).
If still no help, I'd be inclined to do an +Archive & Install, preserving users & settings,+ of Leopard, then download & install the appropriate "combo" update. That's a combination (thus the clever name) of all the updates to Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate (change the last "8" to the desired number). Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

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.

Partition failed with the error: The target Core Storage volume is locked

partition failed with the error: The target Core Storage volume is locked
Hello everybody!
Please help me.
I'm using MacBook Pro (Retina, 13-inch, Mid 2014), Processer:2.6 GHz Intel Core i5, Memory: 8 GB 1600 MHz DDR3.
my computer i have divided in 3 drives: 1-Machintosh HD (Mac OS) 2-Bootcamp (Window OS) & 3-Data (drive for data storage).
I don't want to use Window OS on my computer anymore so I decided to delete drive Data (the third drive) & Window OS (the second drive).
I want my hard drive become a single drive back but when I was formatting, there were some problem display:
then i clicked ok and it displayed like this:
then i try to format or create new partition, it's nothing happen when press button apply.
my computer has storage space 256GB but now when it is happened like this my storage space is only 127GB only.
so please help me.. what so I do with this problem.
Thank you.!

arajs wrote:
I used Boot Camp Assistant (for instaling Windows XP) and there was Partition error:
+*The disc cannot be partioned because some files cannot be moved.*+
+Back up the disk and use Disk Utility to format it as a single Mac OS Extended (journaled) volume. Restore your information to the disk and try using Boot Camp Assistand again.+
so I tried Yasu, verified permission, verified disk, and everything was ok, but in Disk Utility I was trying to split or change size of my disk but there is one error again:
+*Partition failed.*+
+Partition failed with the error: No space left on device+
but I have 64GB free space!
how must I "+Restore your information to the disk+" or what else can I do?
thanks!
This is a standard error message.
If you would have checked into the bootcamp forum you would have instantly found the solution.
http://discussions.apple.com/forum.jspa?forumID=1244&start=0
All that error message means is that you do not have enough conguous disk space available. No big deal at all for an older system. You have bits of files strewn over the "free space."
The solution as you would find in the bootcamp forum is to clone your HD, using a file-file clone, then test the clone to be sure it is working and then to erase your HD and clone back.
Works every time.
Message was edited by: Theodore

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?

Error message: this computer is not supported by the system recovery media.

I replaced a bad samasung hard drive in my Pavilion dv6z 3200 with a Seagate Momentus XT 750 GB 7200RPM SATA 6Gb/s 32 MB Cache 2.5 Inch Solid State Hybrid Drive ST750LX003 and when trying to restore Windows 7 64 bit OS get the error message "this computer is not supported by the system recovery media"

Is the new hdd at least as large a capacity as the original? Can be larger capacity, but sometimes smaller will cause error.
Enter BIOS by tapping F10 key. Is all system info intact/complete?
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

Error while burning dvd in pre 8.0 "device error-the target device isn't suitable for use."

I am trying to burn a dvd in premiere elements 8.0 but after 96% iam getting this error :
"device error-the target device isn't suitable for use."
I have tried all of these steps according to this link :http://kb2.adobe.com/cps/515/cpsid_51553.html.
System configration :
win vista 32 bit .
Processor :Amd athlon 64 dual core 2.60 ghz .
Ram :3 gb
Graphic card :nvidia geforce 6150 se .
Camcoder model number :JVC gz-hm320.
Format :.mts
Frame size :1920/1080
Frame rate :29.97.
Please look into this problem .
Regards
Manoj Khati

This is a user to user forum, not Adobe support... YOU look into things, based on advice other users are able to give
Things and Software to AVOID when authoring/burning a DVD
Read all links/sub-links to create a "best" burned disc
Start --> http://forums.adobe.com/thread/608660?tstart=0
#2 has WHY Explained http://forums.adobe.com/thread/607390
Plus a Microsoft note http://support.microsoft.com/kb/314060
And another note http://support.microsoft.com/kb/982116

Error Code: "This computer is no longer authorized for purchased items that are on this iPad."

I'm getting Error Code: “This computer is no longer authorized for purchased items that are on this iPad.”
I have tried re-authorizing and the error persists.
I have also tried de-authorizing ALL my devices, then re-authorizing and that did not help either.
My husband and I share this iPad and we have set up family sharing.
We have also each purchased apps using our separate iTunes accounts before I set up the family sharing.
How can we fix this error message so that I can back the iPad up to my Mac again?
Husband thinks that at some point we each synced the iPad to our respective Macs.
Could that be it?
Thx!!

I'm not using family sharing, but if you want to sync or backup the iPad with ITunes, I believe that you have to be signed into the same ID on the iPad that you are signed into on the computer and you also have to be authorized for all Apple ID's on that computer that you want to sync or backup with.
DO you have multiple iTunes libraries on the one computer?
http://www.imore.com/how-use-multiple-apple-ids-one-computer-and-itunes

HT1414 i am on iTunes 11.4.04. My iphone iOs is 6.1.3 and has 14 GB. I am trying to backup on my iMac iOs 10.6.8 and it has 113.GB free, But I am getting error messgae that computer doesnt have enough free space

i am on iTunes 11.4.04. My iphone iOs is 6.1.3 and has 14 GB. I am trying to backup on my iMac iOs 10.6.8 and it has 113 GB free, But I am getting error messgae that computer doesnt have enough free space

Settings > General > Reset > Reset Network Settings.
Basic troubleshooting is reset, restart, restore (first from backup then as new). Try each of these in order until the issue is resolved.
If the issue continues, contact the carrier to troubleshoot the network connectivity issues.

Error in target system !!!

Hello,
I have the same error in Dev, Quality and production (wich are in different machines) with XI 2.0 To R/3 4.7, we send tRFC to IDOC and all messages are " error in target system" in sm58
in sxmb_moni, for a message, the first flag is OK, the second flag (A. Status) is red.
When we check the RFC Connection in sm59, it's sometimes good, sometimes not, we think it's a network problem (maybe with firewall...)
have someone any idea please ?
Cedric Rousseau

Hi Manish,
If so, can you control the number of idocs sending to XI box. This is workaround
Is this may be because of number of work process . I am not sure here. So you can increase the work process.
But you can seek help from SAP to audit on this provided if you are able to reproduce the error..
This is just my views~
Regards,
moorthy

Error in target system : iDOC -XI-iDOC

We are getting this error in smq2 when we are processing bulk idocs thru XI "Error in target system " . The setting on receiving system is trigger by background program .
Manish

Hi Manish,
If so, can you control the number of idocs sending to XI box. This is workaround
Is this may be because of number of work process . I am not sure here. So you can increase the work process.
But you can seek help from SAP to audit on this provided if you are able to reproduce the error..
This is just my views~
Regards,
moorthy

Error 21 on target computer

Similar Messages

Maybe you are looking for