Unsolved
This post is more than 5 years old
8 Posts
0
108396
CCTK/SCE - Option not available or cannot be configured
The SCE package will work once or twice, and then log a message that the options I'm using are not available or cannot be configured. When I try to run the CCTK.exe with my option directly, the tool stops responding, and crashes.
I know these options are available because I they will get configured sometimes. I haven't been able to pinpoint what's different when it does work.
I've tried this on a Optiplex GX520 as well as a Latitude E6430, and both behave the same.
Here is the full log file:
[03/30/15 15:29:42] Self Contained Executable(SCE) Execution Start
[03/30/15 15:29:42] Original command line: "C:\Downloads\Bios_Kiosk_SCE.exe"
[03/30/15 15:29:42] SCE EXE Version: 3.0.0.0
[03/30/15 15:29:42] SCE Release: R309560
[03/30/15 15:29:42] User Command: unattended
[03/30/15 15:29:42] SCE Capabilities Value: 471859199 (0x1C1FFFFF)
[03/30/15 15:29:42] SCE Vendor Software Version: 3.0.0
[03/30/15 15:29:42] Local System/Model Compatible with this Package? Yes
[03/30/15 15:29:42] Local System OS Version: 6.1.1.0
[03/30/15 15:29:42] OS Compatible with this Package? Yes
[03/30/15 15:29:42] Local System OS Language: EN
[03/30/15 15:29:42] Language Compatible with this Package? Yes
[03/30/15 15:29:47] Identified Behavior : unattended
[03/30/15 15:29:47] Temporary payload log file name: C:\ProgramData\dell\drivers\Bios_Kiosk_SCE\SCE31AA.tmp
[03/30/15 15:29:47] Translated Command Line : applyconfig.bat -l="C:\ProgramData\dell\drivers\Bios_Kiosk_SCE\SCE31AA.tmp"
[03/30/15 15:29:47] Path : C:\ProgramData\dell\drivers\Bios_Kiosk_SCE
[03/30/15 15:29:47] Identified Behavior : unattended
[03/30/15 15:30:26] Append Vendor Software Log: C:\ProgramData\dell\drivers\Bios_Kiosk_SCE\SCE31AA.tmp
[03/30/15 15:30:26]
--- Start of Vendor Software Log ---
[03/30/15 15:30:26] ASCII payload log file detected.
[03/30/15 15:30:26] 2015/03/30 15:30:22 cctk -
Option : acpower
2015/03/30 15:30:22 cctk - The option 'acpower' is not available or cannot be configured
through this tool.
2015/03/30 15:30:22 cctk -
Option : autoon
2015/03/30 15:30:22 cctk - The option 'autoon' is not available or cannot be configured
through this tool.
2015/03/30 15:30:22 cctk - autoonhr=6
2015/03/30 15:30:22 cctk - autoonmn=0
CCTK STATUS CODE : SUCCESS
[03/30/15 15:30:26]
--- End of Vendor Software Log ---
[03/30/15 15:30:26] Get name of the Folder file: C:\Downloads
[03/30/15 15:30:26] Vendor Software Return Code: 0
[03/30/15 15:30:26] Name of Exit Code: SUCCESS
[03/30/15 15:30:26] Name of Exit Code: SUCCESS
[03/30/15 15:30:26] Exit Code set to: 0 (0x0)
[03/30/15 15:30:26] Result: SUCCESS
[03/30/15 15:30:26] Name of Exit Code: SUCCESS
[03/30/15 15:30:26] Execution terminated at date-time 03/30/15 15:30:26
[03/30/15 15:30:26] ######
Shrinidhi Katte
77 Posts
0
March 30th, 2015 23:00
Hi therealjoshuad,
Thanks for getting in touch.
From the log provided, it looks like BIOS is not supporting the mentioned feature or the system may need a restart. Are you using the latest BIOS on these systems?
We shall check on this on the optiplex and Latitude platforms and get back.
therealjoshuad
8 Posts
0
March 31st, 2015 07:00
Hi Shrinidhi,
I checked, and the GX520 is at the latest (A11) BIOS. I know these features are supported, because the tool will run, but not consistently. I can't narrow down what conditions cause the tool to think that those options are not available.
Shrinidhi Katte
77 Posts
0
March 31st, 2015 08:00
Hi therealjoshuad,
Thanks for the update.
The features supported by DCC rely on BIOS support. If at anypoint, BIOS indicates that feature is not supported, it simply conveys the same.
Can you please indicate the steps that you tried on the GX520 and E6430 systems, so that we can try out.
therealjoshuad
8 Posts
0
March 31st, 2015 10:00
Shrinidhi,
I created the SCU package using the Dell Command tool, and tried running it on the computers by double clicking the executable. I also tried right-clicking and administrator. The account that I was logged in as is an administrator on the computer.
karthikchandran89
49 Posts
0
March 31st, 2015 23:00
Hi therealjoshuad,
Can you please help us with the values that you choose while creating SCE.
eg-
under Create Multiplatform Package
acpower - value to set "last"
autoon - value to set "weekdays"
autoonhr - value to set "6"
autoonmn - value to set "0"
Regards,
Karthik.C
therealjoshuad
8 Posts
0
April 1st, 2015 07:00
acpower = on
autoon=everyday
autoonhr=6
autoonmn=0
are the values that I'm trying to set.
loosus
17 Posts
1
April 6th, 2015 23:00
I know it is not very helpful to this discussion, but I have had unexplained behavior with this tool, as well. It sometimes just doesn't set all the settings that it's supposed to; sometimes, I can run it a second time, and -- poof -- all the settings will be correctly set that second time.
Over 50% of the time, it will get it the first time. Sometimes, I have to run it twice. Rarely, I have to run it three times.
For us, the settings that don't seem to take as well are the wake-on-LAN and PXE-on-wake settings.
karthikchandran89
49 Posts
0
April 7th, 2015 06:00
Hi THEREALJOSHUAD,
we tried the same steps in our environment and was not able to reproduce the issue on E6430 . If you are not trying with the Latest DCC 3.0.0.1 Windows download , can you please try the latest DCC and let us know the more information ( Bios Version, OS details, etc ) of the system where you see failures.
Is the CCTK.exe crashes consistently on this machine ? .
Regards,
Karthik.C
karthikchandran89
49 Posts
0
April 7th, 2015 06:00
Hi LOOSUS,
We are sorry for the inconvenience caused . Please help us with the more information on the systems which failed.
Is the options which are failing are available with a + symbol with them when you give command "cctk -h --wakeonlan" in failing machines ?
Regards,
Karthik.C
therealjoshuad
8 Posts
0
April 8th, 2015 07:00
Hi Karthik,
I am using the latest version, and it does not consistently crash. It will crash, but sometimes a reboot will fix it, but not always.
karthikchandran89
49 Posts
0
April 14th, 2015 13:00
Hi THEREALJOSHUAD,
Sorry for the inconvenience. There could be any infra changes that is causing this crash. When you notice this issue next time, please share us the information about the DotNet version installed, OS Version and any other information from the event logs about the crash. this will help us to recreate the issue here for more analysis.
Thanks,
Karthik.C