I'm trying to install Directx 9 using SCCM, I have downloaded the latest version from Microsoft and created a package. But when the command runs from SCCM I get the following error.

22/05/2009 3:00:56 PM Script for Package:PC100016, Program: Install failed with exit code 4294967287

I have run the same dxsetup.exe /silent command from the SCCM server on the same machine manually and get no errors in the Directx.log and all the files are installed.

Has anyone come across this issue?



Execmgr.log

22/05/2009 2:59:36 PM Execution Request for package PC100016 program Install state change from WaitingContent to NotifyExecution
22/05/2009 2:59:36 PM Checking content location C:\WINDOWS\system32\CCM\Cache\PC100016.9.System for use
22/05/2009 2:59:36 PM Successfully selected content location C:\WINDOWS\system32\CCM\Cache\PC100016.9.System
22/05/2009 2:59:36 PM Executing program as a script
22/05/2009 2:59:36 PM Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\PC100016.9.System\dxsetup.exe" /silent
22/05/2009 2:59:36 PM Command line = "C:\WINDOWS\system32\CCM\Cache\PC100016.9.System\dxsetup.exe" /silent, Working Directory = C:\WINDOWS\system32\CCM\Cache\PC100016.9.System\
22/05/2009 2:59:36 PM Created Process for the passed command line
22/05/2009 2:59:36 PM Raising event:
[SMS_CodePage(850), SMS_LocaleID(3081)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = "PC1201F4";
ClientID = "GUID:9FE85124-5751-4318-A9D0-43B675934117";
CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\PC100016.9.System\\dxsetup.exe\" /silent";
DateTime = "20090522045936.822000+000";
MachineName = "W14140";
PackageName = "PC100016";
ProcessID = 436;
ProgramName = "Install";
SiteCode = "PC1";
ThreadID = 3592;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\PC100016.9.System\\";
};

22/05/2009 2:59:36 PM Raised Program Started Event for Ad:PC1201F4, Package:PC100016, Program: Install
22/05/2009 3:00:33 PM Mandatory execution requested for program Software Updates Program and advertisement {3A2B5547-1F5E-4755-82C4-B56C97960181}
22/05/2009 3:00:33 PM Creating mandatory request for advert {3A2B5547-1F5E-4755-82C4-B56C97960181}, program Software Updates Program, package {3A2B5547-1F5E-4755-82C4-B56C97960181}
22/05/2009 3:00:33 PM Execution Request for package {3A2B5547-1F5E-4755-82C4-B56C97960181} program Software Updates Program state change from NotExist to Ready
22/05/2009 3:00:56 PM Program exit code -9
22/05/2009 3:00:56 PM Looking for MIF file to get program status
22/05/2009 3:00:56 PM Script for Package:PC100016, Program: Install failed with exit code 4294967287

22/05/2009 3:00:57 PM Raising event:
[SMS_CodePage(850), SMS_LocaleID(3081)]
instance of SoftDistProgramErrorEvent

DirectX.log

Target file is Version 9.15.779.0
Source file is Version 9.15.779.0
05/22/09 15:00:52: dxupdate: Installed file C:\WINDOWS\system32\x3daudio1_1.dll
05/22/09 15:00:52: dxupdate: DirectXUpdateInstallPlugIn(): Registering: XACT2_6_x86.inf - [DllRegisterServer]
05/22/09 15:00:52: dxupdate: RegisterDLL(): C:\WINDOWS\system32\xactengine2_6.dll is registered successfully.
05/22/09 15:00:52: dxupdate: -----
05/22/09 15:00:52: dxupdate: DirectXUpdateInstallPlugIn(): 64bit Plug-In [Feb2007_XACT_x64.cab] is skipped on this platform.
05/22/09 15:00:52: dxupdate: -----
05/22/09 15:00:52: dxupdate: DirectXUpdateInstallPlugIn(): Installing Apr2007_d3dx9_33_x86.cab...
05/22/09 15:00:52: dxupdate: DXCheckTrust(): C:\WINDOWS\system32\CCM\Cache\PC1000~1.SYS\Apr2007_d3dx9_33_x86.cab is trusted.
05/22/09 15:00:52: dxupdate: Extracted file C:\WINDOWS\system32\DirectX\DX168.tmp\apr2007_d3dx9_33_x86.inf from cab
05/22/09 15:00:52: dxupdate: DirectXUpdateGetSetupInformation(): DirectX Version: 4.09.00.0904.0
05/22/09 15:00:52: dxupdate: CheckDependency(): no dependency.
05/22/09 15:00:52: dxupdate: DirectXUpdateGetSetupInformation(): Section [4.09.00.0904.0-4.09.00.0904.0_WinXP] is being installed.
05/22/09 15:00:52: dxupdate: Extracted file C:\WINDOWS\system32\DirectX\DX168.tmp\d3dx9_33_x86.cat from cab
05/22/09 15:00:52: dxupdate: Extracted file C:\WINDOWS\system32\DirectX\DX168.tmp\d3dx9_33.dll from cab
05/22/09 15:00:52: dxupdate: Extracted file C:\WINDOWS\system32\DirectX\DX168.tmp\d3dx9_33_x86.inf from cab
05/22/09 15:00:52: dxupdate: Extracted file C:\WINDOWS\system32\DirectX\DX168.tmp\d3dx9_33_x86_xp.inf from cab
05/22/09 15:00:52: dxupdate: Files: 5
05/22/09 15:00:52: dxupdate: Size: 2230272
05/22/09 15:00:52: dxupdate: DirectXUpdateInstallPlugIn(): Installing: d3dx9_33_x86_xp.inf - [x86_Install]
05/22/09 15:00:55: dxupdate: ExecuteInf(): SetupInstallFromInfSection() failed, error = 1168.
05/22/09 15:00:55: dxupdate: ExecuteInf(): Unable to install C:\WINDOWS\system32\DirectX\DX168.tmp\d3dx9_33_x86_xp.inf:[x86_Install]. The file may be damaged.
05/22/09 15:00:55: dxupdate: DirectXUpdateInstallPlugIn(): ExecuteInf() failed.
05/22/09 15:00:55: dsetup32: CSetup::InstallPlugIn(): DirectXUpdateInstallPlugIn() failed.
05/22/09 15:00:55: dsetup32: CSetup::SetupForDirectX(): InstallPlugIn() failed.
05/22/09 15:00:55: dsetup32: start finalizing: phase: 131 - 131, total: 0 - 82
05/22/09 15:00:56: dsetup32: Installation ended with value -9 = Internal or unsupported error
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
This may be related to the account permissions that you are installing the software with. I assume that as you are installing it via SCCM, that you installing the software using the local system account ?

What happens if you install as the user account? What happens if you manually install the software using the local system account?
Answered 05/25/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
What happens if you manually install the software using the local system account?

Hi Michael,

I would like to know how to install using local account. I tried looking on google but could not find a method.

TIA
Answered 05/25/2009 by: dvdzonenz
Purple Belt

Please log in to comment
0
Whether or not the installing program runs in user or System context is controlled by an SCCM. it'll be in 'Software Distribution\Packages\[SCCM_Package_Name]\Programs'. Select the program's properties and click the 'Environment' tab. Obviously, the context option will only be available if you select the option 'Program can run:' with the option 'Only when user is logged in'.

Having said that, I don't believe the issue is to do with account permissions: Clearly, the setup stub thinks one of the files is corrupt. Have you tried a locally-run installation? If you can't easily get to the physical machine, does it install on one with an identical build? If THAT isn't an option, can you RDP to the box to run the install locally? Or via PSExec?

Lots of options open to you to debug what's going on...
Answered 05/26/2009 by: VBScab
Red Belt

Please log in to comment
0
VBScab Thanks for getting back to me.

Yes I have run the same installation on the same machine from the command line using the silent option and it works fine. What I haven't tried is using the local System account as Michaelnowell mentioned.

I will give that a go now.

Jo
Answered 05/27/2009 by: JMWebster
Orange Belt

Please log in to comment
0
In SCCM when you right click on your package "Program" what option do you have checked for this package Under the "Environment" tab.

Is it Run "with user's rights" or run "with Administrative rights" ? under Run Mode..

Just wondering..
Answered 05/27/2009 by: LB3
Senior Yellow Belt

Please log in to comment
0
To run something manually as the local system account, follow the following instructions.........

On your test machine ensure that all apps are closed. Open a command prompt and type in the following command.....

at xx:xx /interactive cmd.exe

where xx:xx represents a time on your machine (in 24 hr format). You're best bet is to set it one or two minutes in the future.

Close the command prompt, open Task Manager, end the process explorer.exe and then close Task Manager. Your screen should now just be sitting with just the background and nothing else.

A command prompt will appear at the time that you specified and this will be running as the local system account. You can load explorer from here and run anything that you want.

Hopefully, you'll be able to see something on the screen or via logging to help you out with your installation.

Good luck.
Answered 05/28/2009 by: michaelnowell
Second Degree Blue Belt

Please log in to comment
0
Hi JMWebster,

Did you end up getting this resolved?

I have the same issue. SCCM etc.

I was going to take this approach but late in the day. Thought I would check in here first and see how you resolved if at all.

Was maybe thinking this direction.

1.) Create a new MSI project in WISE
2.) Put the file(s) in a directory in the files page (MUST be the DX executable)
3.) Go to the MSI Script tab and choose Execute Deferred
4.) Click on InstallFinalize
5.) Double click Execute Program from Installed Files
6.) Select the executable you wish to run
7.) Fill in the command line with any arguments
8.) Go to the properties tab and set In-Script Options to "Deferred execution - System Context"
9.) Set Processing to "Synchronous, ignore exit code"
10.) Click OK, Compile, and choose a file name for the MSI
Answered 02/01/2010 by: Killragtshirts
Orange Belt

Please log in to comment
0
Killragtshirts

From what I remember I had to change the SCCM Program to allow the user to interact with it. I still ran it silently with the command line above, but just changed that setting.

Hope that help

Jo
Answered 02/01/2010 by: JMWebster
Orange Belt

Please log in to comment
0
I would recommend that you NEVER set any CA to 'Ignore exit code', since I can't see the point in running a CA if you're not bothered about whether or not it succeeded.

Also, why not let Windows Update/WSUS take care of DirectX?
Answered 02/02/2010 by: VBScab
Red Belt

Please log in to comment
0
Just had a thought -

Windows 7 comes with DirectX 11
Windows Vista comes with DirectX 10
Windows XP SP2 included DirectX 9.0c

You must be running Windows 2000 to not already have it on your machines....

Dunnpy
Answered 02/02/2010 by: dunnpy
Red Belt

Please log in to comment
0
Hi Guys, Thanks for all your inputs

JMWebster im running in a OSD task sequence. Bombed out in the task sequence when I changed the user interaction settings.

Dunnpy. I need at least the Aug2009 version. Its a prereq for another piece of software.

VBscab. Need this app to run in a task sequence for OSD deployment. I need them built and shipped off ASAP.

The problem is I cant seem to find out what the exit code of -9 or 4294967287 means.
Answered 02/02/2010 by: Killragtshirts
Orange Belt

Please log in to comment
0
VBscab. Need this app to run in a task sequence for OSD deploymentSoooooooooo........have your server team add it to WSUS, if it's not already present. What's the problem?
Answered 02/03/2010 by: VBScab
Red Belt

Please log in to comment
0
OK...So I ran off on MSI tangent for a couple of hours and then took a break and chilled...Then your words echoed again VBscab....We use SCCM for updates so ill change direction. Thanks for the heads up....
Answered 02/03/2010 by: Killragtshirts
Orange Belt

Please log in to comment
0
Doesn't seem to be available via WSUS/SCCM Updates [:(]. Only the security updates for directx...No latest Redist package...Can you confirm that it is actually is available via WSUS/SCCM downloads?

Thanks
Answered 02/03/2010 by: Killragtshirts
Orange Belt

Please log in to comment
0
Google for 'WSUS directx'. See the first hit.

This Google thing will probably catch on pretty soon.
Answered 02/03/2010 by: VBScab
Red Belt

Please log in to comment
0
Yeah thanks to Google i found this site [;)]

Created a wrapper in WPS and its all working now without the errors in the Direct X logs. WSUS doesn't have the version that I need.

Thanks for your help.
Answered 02/04/2010 by: Killragtshirts
Orange Belt

Please log in to comment
0
JM remembered correctly. The only thing I needed to change in SCCM was the "Allow users to interact with this program" checkbox under the package Environment tab. I created a simple SCCM package using the /silent switch just like JM, changed that one setting, and got 100% success.
Answered 09/19/2011 by: mgranto
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity