The error in log file is
01/06/15 04:51:25.986 ERROR bldeploy - [TestScript] Command returned non-zero exit code: 255 The extended attributes are inconsistent.
Most probably the issue is with the scriptlet code
Can you take that snippet and run from command line on the target? Do you get the same error?
You can also refer to Getting Error The extended attributes are inconsistent.
Thanks Pankaj, I have already checked this post, in my case however this works perfectly fine from command prompt, hence not really understanding why is BL Package comaplaining, even tried checking if \t (tab) characters are required anywhere in the script for correct intrepretation, but in vain...
1 of 1 people found this helpful
The difference in run script (set of commands) using BLPackage - External command & command prompt is -
1) BLPackage - External command open new shell for each command
2) Script run using command prompt will use single shell for all commands
Thanks & Regards,
Going by this suggestion I have changed the for loop command to all in one line (to generate DM.txt with the value), but it still is complaining of the same error
for /f "tokens=2 delims=: " %i in ('systeminfo ^| findstr /C:"Domain:" ^| findstr [a-z][a-z][a-z][a-z][0-9].[a-z][a-z][a-z][a-z][a-z][a-z][0-9].[a-z][a-z][a-z]') do echo %i>DM.txt
Thanks Rajan, this helped me to understand the syntax. Below is the correct syntax:
for /f "tokens=2 delims=: " %%i in ('systeminfo ^| findstr /C:"Domain:" ^| findstr [a-z][a-z][a-z][a-z][0-9].[a-z][a-z][a-z][a-z][a-z][a-z][0-9].[a-z][a-z][a-z]') do echo %%i>DM.txt
set /p MachineDomain=<DM.txt
While working I lost and changed %%i to %i, because of some other syntax error messages