Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

RunDll32 failing

Updated: 21 May 2010 | 4 comments
Gene Allen's picture
0 0 Votes
Login to vote

Hello all,



I’m confused. I have a field problem that I don’t know how it happened. I’m installing a device driver in the Execute Deferred section.



It’s an Execute Program from Destination task and my commend line is

[SystemFolder]rundll32.exe setupapi,InstallHinfSection DefaultInstall.NTx86 128 .\SoxAudit.inf

The working directory is the installation directory.



Since the driver doesn’t get installed, I’m assuming that this call is failing.



So my question is 2 fold:

1. Any ideas why it would fail? It’s worked countless times before.

2. How do I test for a return value from this and recover?....actually I don’t think I can recover so I’m going to have to abort the install altogether.



Thank you in advance.



Gene

Discussion Filed Under:

Comments

Bill MacEachern's picture
10
Mar
2009
0 Votes 0
Login to vote

Look in the System and Application event logs to see if there is anything related. Run the install again with verbose logging and see if that shows anything.

EdT's picture
11
Mar
2009
0 Votes 0
Login to vote

What operating system? What security settings in the antivirus? Some installs are blocked by security software, or your operating system may need a signed install in order to perform it silently.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Gene Allen's picture
11
Mar
2009
0 Votes 0
Login to vote

It's a 2003 machine and the driver and the msi are both signed. I didn't sign the inf though...think that could cause a problem?



Our central console deploys to the "workstation" and it appears to fail only on this one. (they all basically the same) so I'm trying to figure what could be different enough to make it fail.



EdT's picture
15
Mar
2009
0 Votes 0
Login to vote

Check that the workstation doesn't already have an instance of the file you are trying to install, present in one of the folders on the machine. There may also be existing registry entries applicable to the file if it is present.

Sometimes, this type of issue can be very difficult to track down, so if you are working with a corporate operating system image, then perhaps it would be sensible to rebuild the machine rather than waste too much time on this one.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.