Aborted - Package integration [13] The data is invalid

Ceyarrecks

Member
Excuse me Please:
I am attempting to hone a win7u sp1 64bit install on an Alienware system using the OEM disk as source.
I am using NTLv1.6.3.6440 64bit and Clanger's W7-Lite-v4 preset.

I have received the error while integrating .msu patches for an off-line store.

Aborted - Package integration [13]
The data is invalid.


(having difficulty remembering where find the .log file, please remind me for inclusion, if need be)

is this error enough to render understanding as to what I have done incorrectly?
 
Prolly the oem disc causing this problem, i dunno i never used them as a source, go to my interesting things page, iso downloads, get a full w7 iso from ms and retry. Lite v4 shouldnt give you any problems on its own, even if you modify it for language and location needs, enjoy. :)

Log file will usually be saved in the source folder and inside the temp folder, see Settings for its location.
 
is the detail that NTLite STOPPED after the integration important? all 300-someodd .msu files? it did not process anything further.
 
ok,.. what is the usual naming convention NTL uses for its logs? I will search for it,... (nothing jumped out as being obvious in the system's current %\Temp\ directories)
 
NTLite.log. NTLite may have cleaned its files out of the local/temp folder. Im not sure of exactly what the tool does these days.
 
found it!
seems near the end of the file is where the error is displayed:

2/27/2019 2:36 AM Deleting temporary files - C:\Users\test\AppData\Local\Temp\NLTmpScratch\NLTmpS01
2/27/2019 2:36 AM Deleting temporary files
2/27/2019 2:36 AM
2/27/2019 2:36 AM
2/27/2019 2:36 AM - DCS 1
2/27/2019 2:36 AM - UR ld0
2/27/2019 2:36 AM - DCS
2/27/2019 2:36 AM - DS
2/27/2019 2:36 AM #
2/27/2019 2:36 AM - UR ld0
2/27/2019 2:36 AM Error: Aborted - Package integration [13] The data is invalid.

2/27/2019 9:04 AM - UR<-- this is when i came back to system to see above error.}
2/27/2019 9:04 AM - UR ld0
2/27/2019 9:04 AM - UR ld0
2/27/2019 9:04 AM Deleting temporary files - C:\Users\test\AppData\Local\Temp\NLTmpScratch

I am beginning to think the pre-integration of system-specific drivers are a possible cause; so will try again with no driver integration.
Will report back with results.
Thank you for the assistance in finding the .log file :)
 
Ahh, .net exe packages cant be integrated, they have to be run post setup(correct me please nuhi). I have an old topic on installing net472 on windows 7 somewhere, i mention it in this topic too.
He will have to advise on the driver Wrong Architectrure warnings.
 
Last edited:
aye, the .exe vs. .msu, right, the program advises that they can not be used, and are not included in the integration list, just the KB#'d ones are.
so far, at 98% of patch integration,... but even last time all 312 the KBs were listed as being done,... then the vague error,...
 
Sit tight and wait for nuhi. :) Damn .nets are an abomination and more hassle than they are worth. :mad:
 
Worst of all is that some program installers demand a certain .net and fail install if they cant download them. swear word swear word swear word.
Combine with the windows 10 fiasco and it proves ms is full of script kiddies and social media junkies.
 
Did I not recall some setting that stated force only latestest use of .net or something? Was not entirely sure. But the setting makes sense. Expecting 4.0 has what 3.5 has and each latest edition ought have everything unique that was included since 1.0....
/insight
the kiddies reference now makes even more sense, as those who programmed 1.0 have a prideful inferiority complex, expecting to standalone and be indispensable, disregarding those in the 1.5 camp, and the 2.0 camp, and ad nauseum....o_O {we need a vomit smiley ;) }
 
ok, so I removed all the drivers, I removed from the patch store directory all of the .exe files, and each time I am still receiving the frustratingly vague error: Error: Aborted - Package integration [13] The data is invalid.
which data?
 
Hi,

any reason why use build 6440 instead of the latest 1.7.3.6760?

If it's simple for you, can you please retest with a clean ISO + your preset?
If you still have the issue, or no time to retry, I will.

Thanks.
 
no real reason beyond 6440 is what worked flawlessly in the recent past.
(do I need to purchase another or renew my current license ?)
will create ISO of the install CD and work with that. (was initially just copying the contents of the disk to hard drive directory)
when you state "preset" meaning the auto-save that contains all the other changes I made beyond what are included with Clanger's v4?
Thank you for the assistance in this situation.
will report back results, this may take a little while to complete,...
 
It's always best to use the latest version, due to fixes.
License never expires, whatever worked before, works better later.
Only the added features after your expired date, including new Windows support, is timed, but that just didn't exist or work properly on the older version so you are again ok with the newer one.
If you see anything that is not better with the newer one, or locked more, do let me know.

Install CD, or an ISO content, copied to a new folder on the disk is all you need.
I was just saying to copy it fresh, not previously edited, to avoid compounded complications.

Preset, yes, your actual preset used, it gets copied as autosaved session to the resulting ISO/folder, unless that option was explicitly disabled on the Apply screen.
 
well, installed newest version, and was presented with the "The program unexpectedly crashed" error. apparently, NTLite.dmp is not an allowed extension.... opened with and saved as .txt
 
Thanks, can you please reupload the DMP file, it seems to have been changed by the forum since it was a TXT transfer.
I have added the DMP file to the allowed ones, you can also ZIP it.

Btw your log shows serious problems with the image, tons of "post-cleanup may be needed", which means internal structure of components is broken.
Can you start from a fresh ISO, or this was it, not some custom/pre-edited ISO?
But make sure to unmount, copy fresh, then reload the image.

I'm interested in that preset if this happens on a clean image.

Thanks again.
 
Thank you again for the continued assistance.
That I may understand fully, the statement "problems with image" means the files that were copied from the OEM DVD itself?
while I have a .iso of the disk created by Imgburn, I have not found a means to directly use it within NTLite.
So all I have done thus far is copy the Alienware OEM disk contents to a directory on the HDD.
(it's install comes up automatically "activated" where-as Dell OEM disks do not, go figure)
This is on a system that is as barebones as possible--started with blank HD, straight from DVD OS install to NTLite; no drivers beyond the Ethernet card are installed (had to do online activation of NTLite).
(additionally, I can move the NTLite process to a different system if it is deemed useful or preferred)

I have since the generation of the attached .dmp file, re-copied the DVD to directory, and emptied the mount folders, and had NTLite Unmount/Forget, also, not using previous autosave, only Clanger's v4 preset, let me finish its configuration and have it to attempt to slipstream the patches.

p.s.
not sure if this is an important detail, but the current version of NTLite seems to move much more slowly on the patch integration process using the same patches then the previous version,.. is this expected?
 
Back
Top