I am using SetupAPI DiInstallDriver to install a driver.
It works fine when there is no driver installed.
But, it failed with error code 0x103 (259) when a same driver is already installed, even with DIIRFLAG_FORCE_INF flag is set.
There is no explanation on this error code in the page of DiInstallDriver/DiInstallDriverA/DiInstallDriverW.
In System Error Codes, it only refers to ERROR_No_MORE_ITEMS, no more data is availale.
When 0x103(259) is returned during a same driver force installation, it is said ‘Device does not need an update. No better matching drivers found for device’ in setupapi.dev.log.
Question:
1. Does 0x103(259) only indicate the scenario where there is already a better driver installed?
2. If answer is No for #1, what are the other scenarios which can be indicated by 0x103(259) for DiInstallDriver?
3. How can I determine by return code of DiInstallDriver that there is already a better driver installed and the new driver is not installed?
Thanks.
SCENARIO
You are deploying a package and you get an error 0x103(259). This error means that the installer you are calling exits withing 20 seconds with a code 259 and SCCM interprets it as a failure. In my case I was getting this error because I misspelled the name of a .bin file in my command line. But it may have something to do with your application as well.
You can run a script to deploy the package that monitors the status of the installation and exit properly: https://social.technet.microsoft.com/Forums/windows/en-US/fbccc114-3605-4363-b983-b2f7b02fe266/program-exit-code-259-in-sccm-cllient?forum=configmgrgeneral
DETAILS
I am including some of the details from the execmgr.log (client log) in case you want to look at what the log says when you run into the problem I had.
Checking content location C:\WINDOWS\ccmcache\2c for use execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Successfully selected content location C:\WINDOWS\ccmcache\2c execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Executing program as a script execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Successfully prepared command line «C:\WINDOWS\ccmcache\2c\HPBIOSUPDREC64.exe» -s -p pswd.bin -f N78_0115.bin -b execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Command line = «C:\WINDOWS\ccmcache\2c\HPBIOSUPDREC64.exe» -s -p pswd.bin -f N78_0115.bin -b, Working Directory = C:\WINDOWS\ccmcache\2c\ execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Running «C:\WINDOWS\ccmcache\2c\HPBIOSUPDREC64.exe» -s -p pswd.bin -f N78_0115.bin -b with 32bitLauncher execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Created Process for the passed command line execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = «XXXXXXX»;
ClientID = «GUID:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx»;
CommandLine = «\»C:\\WINDOWS\\ccmcache\\2c\\HPBIOSUPDREC64.exe\» -s -p pswd.bin -f N78_0115.bin -b»; <<<That is not the correct .bin name!
DateTime = «20180308173644.802000+000»;
MachineName = «XXXXXXXX»;
PackageName = «XXXXXXX»;
ProcessID = 2068;
ProgramName = «BIOS Update — HP Elitebook 840 G4»;
SiteCode = «COB»;
ThreadID = 2232;
UserContext = «NT AUTHORITY\\SYSTEM»;
WorkingDirectory = «C:\\WINDOWS\\ccmcache\\2c\\»;
};
execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Raised Program Started Event for Ad:COB2009E, Package:COB00177, Program: BIOS Update — HP Elitebook 840 G4 execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»COB00177″,ProgramID=»BIOS Update — HP Elitebook 840 G4″, actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»COB00177″,ProgramID=»BIOS Update — HP Elitebook 840 G4″, actionType 1l, value ClientUX, user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
EvaluateRequestForExecution — Updated current running request execmgr 3/8/2018 10:36:44 AM 2232 (0x08B8)
MTC task with id {8C58E77B-0330-4F2C-9598-DB8D8D92B028}, changed state from 4 to 5 execmgr 3/8/2018 10:36:44 AM 11136 (0x2B80)
Program exit code 259 execmgr 3/8/2018 10:36:49 AM 5668 (0x1624)
Looking for MIF file to get program status execmgr 3/8/2018 10:36:49 AM 5668 (0x1624)
Program ran past its maximum runtime. It will be orphaned execmgr 3/8/2018 10:36:49 AM 5668 (0x1624)
I am using SetupAPI DiInstallDriver to install a driver.
It works fine when there is no driver installed.
But, it failed with error code 0x103 (259) when a same driver is already installed, even with DIIRFLAG_FORCE_INF flag is set.
There is no explanation on this error code in the page of DiInstallDriver/DiInstallDriverA/DiInstallDriverW.
In System Error Codes, it only refers to ERROR_No_MORE_ITEMS, no more data is availale.
When 0x103(259) is returned during a same driver force installation, it is said ‘Device does not need an update. No better matching drivers found for device’ in setupapi.dev.log.
Question:
1. Does 0x103(259) only indicate the scenario where there is already a better driver installed?
2. If answer is No for #1, what are the other scenarios which can be indicated by 0x103(259) for DiInstallDriver?
3. How can I determine by return code of DiInstallDriver that there is already a better driver installed and the new driver is not installed?
Thanks.
metarushej
Contributor
07-02-2019
12:44 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We are virtualising a Win 2011 SP1 server using VMware vCenter Converter Standalone — running locally on the server.
We encounter @ 3% complete.
The error code is FAILED: Unable to create a VSS snapshot of the source volume(s). Error code:
259 (0x00000103).
Can anyone advise on what might be causing the error\how to resolve?
Thank you
John
Reply
0
Kudos
-
All forum topics -
Previous Topic -
Next Topic
1 Solution
Accepted Solutions
POCEH
VMware Employee
08-15-2019
01:22 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More clear explanation that «snapshot creations take too long time ( > 5min)» is not possible.
View solution in original post
Reply
0
Kudos
10 Replies
daphnissov
Immortal
07-02-2019
05:35 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The last version of Converter to support Windows 2000 was version 4.0, and even then it required SP4 be installed. Regardless, I think you’re going to need SP4 anyhow.
——————
How to Ask for Help on Tech Forums
https://neonmirrors.net
Reply
0
Kudos
metarushej
Contributor
07-02-2019
05:59 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, the source server is a Windows SBS Server 2011 SP1.
Regards
Reply
0
Kudos
POCEH
VMware Employee
07-02-2019
06:24 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems that snapshot creations take too long time ( > 5min)
Try again, after worker service restart, or to limit number of active snapshots via vssadmin command, or to exclude some disk(s) from conversion.
HTH
Reply
0
Kudos
RajeevVCP4
Expert
07-02-2019
07:53 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Refer this KB
VMware Knowledge Base
VMware Knowledge Base
Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
Reply
0
Kudos
metarushej
Contributor
08-13-2019
08:16 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Apologies for the delay in replying here.
I have done some further analysis here and can see that the event log contains the following error.
Exchange VSS Writer (instance b**********************************) failed with error code -2147221233 when preparing for Snapshot.
Any insight that can be provided into the above would be appreciated.
Thank you
Reply
0
Kudos
daphnissov
Immortal
08-13-2019
08:20 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a Windows/Exchange issue and not one that is VMware related.
——————
How to Ask for Help on Tech Forums
https://neonmirrors.net
Reply
0
Kudos
metarushej
Contributor
08-14-2019
10:34 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Sorry, I saw an Exchange-related error VSS error in the evet log and assumed that this was related to the problem. I see that the Converter job continued past that point so I guess that the the xchange-related error VSS error is not the root cause.
Does anyone know what Error code: 259 (0x00000103) is \what its cause is?
Thank you.
Reply
0
Kudos
Alex_Romeo
Leadership
08-14-2019
10:54 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
It’s a bit old and the version isn’t the same thing, but I think it might be useful.
[SOLVED] VMWare converter failed — Spiceworks
[SOLVED] VSS causes image push to fail — VMware Forum — Spiceworks — Page 2
Alessandro Romeo
Blog: https://www.aleadmin.it/
Reply
0
Kudos
POCEH
VMware Employee
08-15-2019
01:22 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More clear explanation that «snapshot creations take too long time ( > 5min)» is not possible.
Reply
0
Kudos
metarushej
Contributor
08-18-2019
05:15 AM
Jump to solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Based on your feedback (snapshot take too long), I shut down a number of database services on the server to free up resources.
I found that the migration then ran successfully.
Thank you!
Reply
1
Kudo
I am setting up my first software deployment from SCCM. I started off simple and went with an easy install, google chrome. I packaged the installation and pushed it out to my test pc. I can see the installation begin within software center. Then it
fails. I looked at the Execmgr.log (see below) and see that it failed with error code 259. I restarted the install and it once again failed. So, I copied the file from c:\windows\ccmcache to my desktop and kicked off msiexec /I. It ran with no issue. I did
the same using the /qn command so it is now running the exact command used by SCCM deploy. It installs with no issue. So why am I getting this 259 error when SCCM attempts to install it? All it is doing is downloading the file and executing the command….
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»C0100046″,ProgramID=»Google Chrome», actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time=»14:09:20.151+300″
date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»4796″ file=»event.cpp:405″>
<![LOG[Validating chain of dependent programs for package C0100046 optional program Google Chrome]LOG]!><time=»15:31:26.351+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″
file=»execreqmgr.cpp:2348″>
<![LOG[Validating package C0100046 program Google Chrome in the chain. The content request ID is {00000000-0000-0000-0000-000000000000}]LOG]!><time=»15:31:26.351+300″ date=»04-18-2016″ component=»execmgr» context=»»
type=»1″ thread=»2952″ file=»execreqmgr.cpp:2091″>
<![LOG[Creating an optional execution request for package C0100046 program Google Chrome ]LOG]!><time=»15:31:26.375+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″
file=»execreqmgr.cpp:2428″>
<![LOG[Requesting content from CAS for package C0100046 version 1]LOG]!><time=»15:31:26.397+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″ file=»contentaccesshelper.cpp:246″>
<![LOG[Successfully created a content request handle {9210EA74-1B56-44A7-9182-A788E959E654} for the package C0100046 version 1]LOG]!><time=»15:31:26.403+300″ date=»04-18-2016″ component=»execmgr» context=»»
type=»1″ thread=»2952″ file=»contentaccesshelper.cpp:331″>
<![LOG[An existing MTC token was not supplied, using ExecutionRequest’s Id as MTC token and this execution request is the owner of resultant MTC task.]LOG]!><time=»15:31:26.403+300″ date=»04-18-2016″ component=»execmgr»
context=»» type=»1″ thread=»2952″ file=»executionrequest.cpp:8960″>
<![LOG[Request a MTC task for execution request of package C0100046, program Google Chrome with request id: {27E920BC-3B49-4AD5-A92D-E90DCE3F0F44}]LOG]!><time=»15:31:26.403+300″ date=»04-18-2016″ component=»execmgr»
context=»» type=»1″ thread=»2952″ file=»executionrequest.cpp:8984″>
<![LOG[Execution Request for advert package C0100046 program Google Chrome state change from NotExist to Ready]LOG]!><time=»15:31:26.462+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″
thread=»2952″ file=»executionrequest.cpp:513″>
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»C0100046″,ProgramID=»Google Chrome», actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time=»15:31:26.463+300″
date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″ file=»event.cpp:405″>
<![LOG[MTC task with id {27E920BC-3B49-4AD5-A92D-E90DCE3F0F44}, changed state from 0 to 4]LOG]!><time=»15:31:26.467+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″
file=»execreqmgr.cpp:6288″>
<![LOG[MTC signaled SWD execution request with program id: Google Chrome, package id: C0100046 for execution.]LOG]!><time=»15:31:26.503+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″
thread=»3716″ file=»execreqmgr.cpp:6406″>
<![LOG[Sending ack to MTC for task with id: {27E920BC-3B49-4AD5-A92D-E90DCE3F0F44}]LOG]!><time=»15:31:26.506+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″
file=»executionrequest.cpp:9023″>
<![LOG[Executing program msiexec.exe /i googlechromestandaloneenterprise.msi/qn in Admin context]LOG]!><time=»15:31:26.512+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″
file=»executionrequest.cpp:3251″>
<![LOG[Execution Request for advert package C0100046 program Google Chrome state change from Ready to NotifyExecution]LOG]!><time=»15:31:26.512+300″ date=»04-18-2016″ component=»execmgr» context=»»
type=»1″ thread=»3716″ file=»executionrequest.cpp:513″>
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»C0100046″,ProgramID=»Google Chrome», actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time=»15:31:26.513+300″
date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»event.cpp:405″>
<![LOG[Checking content location C:\WINDOWS\ccmcache\1 for use]LOG]!><time=»15:31:26.540+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»executioncontext.cpp:1663″>
<![LOG[Successfully selected content location C:\WINDOWS\ccmcache\1]LOG]!><time=»15:31:26.540+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»executioncontext.cpp:1719″>
<![LOG[Executing program as a script]LOG]!><time=»15:31:26.542+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»executionengine.cpp:82″>
<![LOG[Found executable file msiexec.exe with complete path C:\WINDOWS\system32\msiexec.exe]LOG]!><time=»15:31:26.542+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″
file=»execengnutility.cpp:296″>
<![LOG[Successfully prepared command line «C:\WINDOWS\system32\msiexec.exe» /i googlechromestandaloneenterprise.msi/qn]LOG]!><time=»15:31:26.542+300″ date=»04-18-2016″ component=»execmgr» context=»»
type=»1″ thread=»3716″ file=»scriptexecution.cpp:650″>
<![LOG[Command line = «C:\WINDOWS\system32\msiexec.exe» /i googlechromestandaloneenterprise.msi/qn, Working Directory = C:\WINDOWS\ccmcache\1\]LOG]!><time=»15:31:26.543+300″ date=»04-18-2016″ component=»execmgr»
context=»» type=»1″ thread=»3716″ file=»scriptexecution.cpp:352″>
<![LOG[Running «C:\WINDOWS\system32\msiexec.exe» /i googlechromestandaloneenterprise.msi/qn with 32bitLauncher]LOG]!><time=»15:31:26.543+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″
thread=»3716″ file=»scriptexecution.cpp:370″>
<![LOG[Created Process for the passed command line]LOG]!><time=»15:31:26.580+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»scriptexecution.cpp:513″>
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramStartedEvent
{
AdvertisementId = «C012003B»;
ClientID = «GUID:50C2BFB5-BFF2-4786-B765-1671A6D32980»;
CommandLine = «\»C:\\WINDOWS\\system32\\msiexec.exe\» /i googlechromestandaloneenterprise.msi/qn»;
DateTime = «20160418203126.584000+000»;
MachineName = «PL-SUN05»;
PackageName = «C0100046»;
ProcessID = 3204;
ProgramName = «Google Chrome»;
SiteCode = «P01»;
ThreadID = 3716;
UserContext = «NT AUTHORITY\\SYSTEM»;
WorkingDirectory = «C:\\WINDOWS\\ccmcache\\1\\»;
};
]LOG]!><time=»15:31:26.586+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»event.cpp:715″>
<![LOG[Raised Program Started Event for Ad:C012003B, Package:C0100046, Program: Google Chrome]LOG]!><time=»15:31:26.587+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″
file=»executioncontext.cpp:459″>
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»C0100046″,ProgramID=»Google Chrome», actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time=»15:31:26.589+300″
date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»event.cpp:405″>
<![LOG[Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»C0100046″,ProgramID=»Google Chrome», actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l]LOG]!><time=»15:31:26.596+300″
date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″ file=»event.cpp:405″>
<![LOG[MTC task with id {27E920BC-3B49-4AD5-A92D-E90DCE3F0F44}, changed state from 4 to 5]LOG]!><time=»15:31:26.606+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»3716″
file=»execreqmgr.cpp:6288″>
<![LOG[Program exit code 259]LOG]!><time=»15:51:26.661+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″ file=»scriptexecution.cpp:676″>
<![LOG[Looking for MIF file to get program status]LOG]!><time=»15:51:26.662+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″ file=»executionstatus.cpp:282″>
<![LOG[Program ran past its maximum runtime. It will be orphaned]LOG]!><time=»15:51:26.668+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″ file=»executionstatus.cpp:232″>
<![LOG[Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistProgramExceededTime
{
AdvertisementId = «C012003B»;
ClientID = «GUID:50C2BFB5-BFF2-4786-B765-1671A6D32980»;
DateTime = «20160418205126.673000+000»;
MachineName = «PL-SUN05»;
MaximumTime = «20»;
PackageName = «C0100046»;
ProcessID = 3204;
ProgramName = «Google Chrome»;
SiteCode = «P01»;
ThreadID = 2952;
};
]LOG]!><time=»15:51:26.684+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″ file=»event.cpp:715″>
<![LOG[Raised Program Exceeded Time Event for Ad:C012003B, Package:C0100046, Program: Google Chrome]LOG]!><time=»15:51:26.686+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″ thread=»2952″
file=»executioncontext.cpp:857″>
<![LOG[Execution is complete for program Google Chrome. The exit code is 259, the execution status is Unknown Status]LOG]!><time=»15:51:26.687+300″ date=»04-18-2016″ component=»execmgr» context=»» type=»1″
thread=»6008″ file=»execreqmgr.cpp:4165″>