Test Data Manager

Expand all | Collapse all

TDoD GT Installer: Is there an Error Code Listing Showing Error 4108

Jump to Best Answer
  • 1.  TDoD GT Installer: Is there an Error Code Listing Showing Error 4108

    Posted 09-22-2017 02:53 PM

    Is there a location that lists TDoD installer errors? I have not located anything in docops.

    The GT Installer is erring out. The error code is preventing the installer from completing.

     

    The error code I see in the logs is:

     Error 4180. There was an error during the Windows features configuration process.

    Your original configuration will be restored.

    MSI (s) (38!38) [08:39:52:637]: Product: GT - Test Data On Demand -- Error 4180. There was an error during the Windows features configuration process.

    Your original configuration will be restored.

     

    CustomAction AI_WinOptFeaturesConfig returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Action ended 8:39:52: InstallExecute. Return value 3.MSI (s) (38:58) [08:40:41:979]: RESTART MANAGER: Session closed.



  • 2.  Re: TDoD GT Installer: Is there an Error Code Listing Showing Error 4108
    Best Answer

    Posted 09-25-2017 12:26 PM

    Joel,

     

    I believe the error is caused when the installer fails to enable Windows features like configuring .NET. Can you check the windows logs to see if there any additional details?

     

    Thanks,

    Anil



  • 3.  Re: TDoD GT Installer: Is there an Error Code Listing Showing Error 4108

    Posted 09-26-2017 11:46 AM

    Thanks, Anil_Kumar_Appukuttan. Good suggestion.

    In the CBS log, I see what appears to be an add/update against WAS Parameters in Registry. However, I do not see / have this key when I use Regedit to review it.

     

    The installer executes under a login account that has admin privileges.

    If I try running the GT installer .exe using Run As Administrator, even stranger things happen and the installer does not shut down properly.  

     

    Following is the error (edited for readability) I see in the CBS logs at the time the installer is running.

    2017-09-25 16:36:37, Info CSI 00000015 Creating NT transaction (seq 2), objectname [6]"(null)"
    2017-09-25 16:36:37, Info CSI 00000016 Created NT transaction (seq 2) result 0x00000000, handle @0x1164
    2017-09-25 16:36:40, Error CSI 00000017 (F) STATUS_ACCESS_DENIED #3052904# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysSetValueKey(key = 36c ("\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\WAS\Parameters"), vn = [l:22{11}]"InstallPath", ti = 0, t = 0, data = {l:52 b:2500770069006e0064006900720025005c00730079007300740065006d00330032005c0069006e00650074007300720076000000})[gle=0xd0000022]
    2017-09-25 16:36:40, Error CSI 00000018@2017/9/25:21:36:40.929 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(4228): Error STATUS_ACCESS_DENIED originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysSetValueKey expression: Status
    [gle=0x80004005]
    2017-09-25 16:36:41, Error CSI 00000019 (F) STATUS_ACCESS_DENIED #3052903# from Windows::Rtl::SystemImplementation::CKey::SetValue(f = 0, vn = [l:22{11}]"InstallPath", t = 2, data = {l:52 b:2500770069006e0064006900720025005c00730079007300740065006d00330032005c0069006e00650074007300720076000000}, disp = (null))[gle=0xd0000022]
    2017-09-25 16:36:41, Info CSI 0000001a Error STATUS_ACCESS_DENIED while executing operation SetKeyValue on [l:310{155}]"\Registry\MACHINE\SYSTEM\CurrentControlSet\Services\WAS\Parameters, InstallPath, , JQB3AGkAbgBkAGkAcgAlAFwAcwB5AHMAdABlAG0AMwAyAFwAaQBuAGUAdABzAHIAdgAAAA=="

    2017-09-25 16:36:41, Info CSI 0000001b Creating NT transaction (seq 3), objectname [6]"(null)"
    2017-09-25 16:36:41, Info CSI 0000001c Created NT transaction (seq 3) result 0x00000000, handle @0x1164

    Any other ideas?



  • 4.  Re: TDoD GT Installer: Is there an Error Code Listing Showing Error 4108

    Posted 09-26-2017 05:34 PM

    Joel,

     

    Not sure if there is some corruption in your windows files. You may want to run the below command from an elevated command prompt and see if it finds anything.

     

    sfc /scannow

     

    Thanks,

    Anil