Runtime error -1004 and 429
Hi All,
I am a packaging engineer and the application I am repackaging right now is Cognos TM1 9.5.2 Contributor. It has three folders
1. First is a Base part,
2. Second one is the workflow part
3. Third upgrades the first one.
Each folder contains an EXE and an MSI. The application installs fine when I install it using the EXEs'. There is one MS-EXCEL (named "Perspectives of Excel") shortcut for this application. The shortcut launches fine and I can find an extra tab "TM1" in the EXCEL sheet as mentioned in the instructions provided by the application owner.
But when I install the app using the MSIs which are basically called by the EXE during installation and launch the shortcut (EXCEL) I get a runtime Error -1004 as shown in the screenshot. So is the EXE doing something more than just calling the MSI. Why am I encountering this error??
I went ahead with repackaging this application and when installing the packages I am still getting the same error. How do I resolve this issue in my package. But when I install using the MSI's which basically are called by the EXE during installation But when I install using the MSI's which basically are called by the EXE during installation But when I install using the MSI's which basically are called by the EXE during installationt when I install using the MSI's which basically are called by the EXE during installationBut when I install using the MSI's which basically are called by the EXE during installation But when I install using the MSI's which basically are ca
Another issue is, when I install my first package(Base part) silently using /qb switch and immediately after installing this first part when I launch the shortcut I get another runtime error as shown in the screenshot below. This error doesnt appear when I install the package without /qb switch. The package was created by creating a Transform for the MSI. So all the necessary changes are there in the transform but still I get the error when installing silently and launching the shortcut.
Kindly, help me out with this. how should I go about this. What changes should I make.
Any inputs would be appreciated
Thank you,
Hitesh
Comments
Oops
I think this is a repost of a thread you already have open elsewhere in this forum. You also have a cut and paste problem with the same sentence repeated several times.
The 1004 error looks like it could be caused by a VBscript which calls the Excel automation object to load an add-in. For this to work three things are required:
1. Excel should not be running.
2. Excel must have been started at least once by the user for whom the installation is taking place.
3. The code needs to run under the user account for which it is being installed, as Excel add-ins are installed to the user's profile.
If you are deploying with a different account to that which will use the Excel add-in, you need to run the script via self healing so that the add-in gets included automatically. Or you need the user to manually add the add-in to Excel.
I suspect that if you install the MSI silently or with a reduced UI, it may interfere with the correct operation of the installer. Does running the EXE allow a silent install? If it does, then my suspicion is not an issue.
Runtime Error 429 may be caused by your Browser permissions or if you are using a browser other than IE, as ActiveX is only supported by IE.
IE Browser policies may also disable the running of ActiveX controls unless their source is included in the security list as a safe location.
No doubt actually googling on the errors will provide you with a list of other possibilities.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Sorry for the repeated sentences
Hi Edt,
This post relates to the old one as it is based on same application. Initially I had problem with the Raw media and now the error I am getting is when I package the application.
Now the baseline of the post is, I am gettin this RUNTIME ERROR - 1004. Everything on Google is related to VB code. This is not helping me out as I need to work around with the MSIs alone and no other option.
The first MSI (Base part) is installing fine as I launched the shortcut and there was an extra TAB (TM1) in EXCEL.It didn throw any error. but after installing the second one (Workflow), when I launched the shortcut I got this Runtime Error -1004.
What i assume is the second MSI is altering something/replacing some files. How do I troubleshoot this issue. I have no clue.
Thank you
Hitesh
Would it be fair to assume
Would it be fair to assume that you are new to packaging?
When you say you are "repackaging" these apps, are you capturing MSI installs?
If you are using capture, you will find that the capture process only records the changes that an installer makes, but does not record the method by which those changes are made - and the method can be as important as the changes.
For the moment however,. you suspect that the second MSI is altering something or replacing some files but you cannot see how to diagnose this. One way is to open a copy of this MSI in your editor and look at what files are being installed to what locations, and what registry keys are being installed. This can then be compared with a test machine that has the first version installed and you will be able to compare existing files and registry keys with the new ones that the second MSI installs.
The other technique is to enable verbose logging of the MSI install, and then review the changes that are recorded in the logfile.
Finally, there is the option of using a capture tool to record the changes made during the installation of the second MSI, as there may be custom actions involved which do more than just replacing files and registry keys, so any changes recorded in the capture which are not in the file or registry tables of the second MSI are likely to be due to custom actions (or normal operating system changes).
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Error 429...
...is almost always due to a call being made to an object which has not been created. That, in turn, is due to the file containing the object not being registered. I suspect that the EXE is registering the DLLs and/or OCXs which the MSI installs. Classic, incompetent packaging...
- Ensure your Wise tool is set up to use the advertising tables instead of the registry for COM objects
- Use WiseComCapture to create .REG files for all the OCXs and registerable DLLs in the package
- Add a transform to your package and import the .REGs created above. Remember to answer 'Yes' when prompted about using the advertising tables.
As EdT says, you need to set up the package to run the add-in script in the context of the logged-in user. Check out the 'sticky' which deals with Excel add-ins on the 'Package Development' forum at AppDeploy.com
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Thank you VBScab
The ActiveX runtime error 429 has been solved. When I specifically pass INSTALLDIR argument and mention the installation directory it works and also a few DLLs were registered. This issue is resolved.
But I am still not able to resolve runtime 1004. Kindly, help me out with it.
Please indicate what steps
Please indicate what steps you have taken so far to try and diagnose runtime 1004. Some suggestions were made earlier in this thread so until you tell us whether any of the suggestions have been tried, it is difficult to take this any further.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.