Hi there,

working on a conversion from an installshield-exe to an .msi with WPS i run into the same errors on every and every try:
.
.
.
RegisterTypeLibraries: LibID: {000204EF-0000-0000-C000-000000000046}
RegisterTypeLibraries: LibID: {00025E01-0000-0000-C000-000000000046}
Action 16:00:54: RegisterUser. Registering user...
RegisterUser: {2A4D23B5-D941-4862-9BAA-B102A9B31A46}
Action 16:00:54: RegisterProduct. Registering product...
RegisterProduct: {2A4D23B5-D941-4862-9BAA-B102A9B31A46}
Action 16:00:54: WiseConvertPaths.
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
Internal Error 2835. ErrorIcon, ErrorDialog
Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
MSI (s) (0C:D4) [16:01:00:562]: Product: XYZ -- Error 1719. The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
Action ended 16:01:00: InstallFinalize. Return value 3.
Action 16:01:00: Rollback. Rolling back action:
Rollback: WiseConvertPaths
Rollback: Registering product...
Rollback: Registering user...
Rollback: Registering type libraries...
.
.
.
Yes, i am a rookie in building MSIs, but the ones i worked on are ok and running after some hours and just this is drivin me crazy!
What means the E1719 while an installation?
Anyone with an idea out there?

kind Regards,
Yag
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
Are you sure that the EXE doesn't extract and execute an MSI? Check your %TEMP% folder (having cleared it out first) for an MSI when the EXE presents its first display (normally a 'Welcome' dialog). Remember, though, that some vendors are now extracting to a folder beneath %AppData% so check there, too, if there's nothing in %TEMP%.
Answered 07/27/2010 by: VBScab
Red Belt

Please log in to comment
0
There's a bit more information about that particular error here:

http://itninja.com/question/help-with-msi-1719

I'd go with Ian's advice there may well be an msi in that exe. Which means you'd be capturing an msi installation.
Answered 07/27/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
You both are right!

There is an MSI inside. My problem: the MSI only installs some core components like DLLs, little helpful EXEs and data base stuff, writing "some" regkeys (and so on) as well and also comes with a lot of custom action. But the bigger (in MB) part of the installation is outside the MSI in the setup.exe.

So what to do???

Setting up a clean VM --> installing the embedded MSI --> snapshot --> running setup.exe --> comparison --> building my MSI from the difference? That is my last idea. Came in a lucid dream this night [&:]
Answered 07/28/2010 by: Yagharek
Senior Yellow Belt

Please log in to comment
0
probably a good place to start, But are you sure the msi doesn't function on it's own?

you can always add the differences to the msi via a transform rather than creating a whole new msi
Answered 07/28/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
That's about the size of it. Good strategy.
Answered 07/28/2010 by: VBScab
Red Belt

Please log in to comment
0
Is there a trick to sort out or prevent the changes during setup.exe (starting the embedded MSI)? Not that everything is in my transformfile as a change only cause the files, regkeys, ... are written a second time?

EDIT: @timmsie: the main program files come somewhere in the setup.exe, not in the MSI. If the setup would only be a container for a fully functional MSI - you would find a very happy Yag here with a tiny lil´ transform file and no problems at all [:)]
Answered 07/28/2010 by: Yagharek
Senior Yellow Belt

Please log in to comment
0
I'm not sure I understand the question but what I *think* you're asking is, will there be a problem with capturing the MSI when it runs the second time, i.e. when it's executed by the EXE.

Short answer, no. However, you will have to rename the relevant 'Uninstall' key in the registry, to prevent the EXE from seeing that it's already installed and thus running the MSI in maintenance mode. Also, if it's not in your exclusion list, remember to remove that same key from your capture. Since all the MSI's components will already be installed, you shouldn't capture any of its activity.
Answered 07/28/2010 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

I'm not sure I understand the question but what I *think* you're asking is, will there be a problem with capturing the MSI when it runs the second time, i.e. when it's executed by the EXE.

That is exactly what i wanted to ask, sorry for my poor english!
I will try your hint and post my results,

regards Yag
Answered 07/28/2010 by: Yagharek
Senior Yellow Belt

Please log in to comment
0
The good strategy did not work!
Running the littleMSI alone I get following Errors:

InstallFiles: File: DAO2535.TLB, Directory: C:\Program Files\Common Files\Microsoft Shared\DAO\, Size: 73184
DEBUG: Error 2356: Couldn't locate cabinet in stream: MsiData1.cab.
DEBUG: Error 2835: The control ErrorIcon was not found on dialog SetupError
Internal Error 2835. ErrorIcon, SetupError
Internal Error 2356. MsiData1.cab
MSI (s) (D0:A0) [14:40:10:454]: Product: littleMSI -- Internal Error 2356. MsiData1.cab
Action ended 14:40:10: InstallFinalize. Return value 3.
Action 14:40:10: Rollback. Rolling back action:

So I think, the setup.exe provides anything to the littleMSI that is not in it.
While running setup.exe on a very slow VM I noticed a Window saying "install Visual Studio something" (to short to screenshot), I don´t want to know what else is running unbeknown to me.

Now the circle is closed: how to do what a good packager normally don´t do: repack the whole EXE, ignoring the guidelines not to repack vendor MSIs and however get rid of the E2835 / E1719?
Answered 08/04/2010 by: Yagharek
Senior Yellow Belt

Please log in to comment
0
Check whether the EXE extracts that CAB also, alongside the MSI. Sorry, I thought that that would be obvious...
Answered 08/04/2010 by: VBScab
Red Belt

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