I have packaged Hyperion Essbase which is an Excel addin but when I go to launch Excel it comes up with errror "This file is not in a recognizable format" Any ideas please?
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
Sounds like a corrupt file maybe?

Perhaps it requires some particular registry key that you have missed in the package.

Install your msi and then start a capture.
Install the vendor setup and capture the differences.

Thats where I would start.
Answered 08/01/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
I have repacked version 6.5 - no problems.....
Answered 08/26/2004 by: fetgor
Senior Purple Belt

Please log in to comment
0
I am attempting to package the Essbase plugin and I get the exact same error. Does anyone have any additional ideas?
Answered 12/19/2005 by: CBuford
Senior Yellow Belt

Please log in to comment
0
I have packaged version 7.1.6 using rsp file it works for intalling but having issues uninstalling anybody have any ideal
Answered 09/07/2007 by: tlopez
Yellow Belt

Please log in to comment
0
I had similiar issues and found that there were actually two addins that needed to be registered.

I am no longer onsite where I had the package done from memory there was one xll and one xla file. Both needed to be present in the same folder. You need to have office installed prior to capturing essbase as it does not drop all files when excel is not installed.
Answered 09/09/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
I had the same problem and found that as previously stated there was 2 excel files and double clicking on the file manually worked successfully. As i dont work at the company anymore I cant be more help than that but it was due to the excel files themselves.

Paul
Answered 09/10/2007 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I concur with the last 2 posts: you need both files to be present.
Answered 09/10/2007 by: VBScab
Red Belt

Please log in to comment
0
The version I am looking at writes the plugin that needs running to HKCU\Software\Microsoft\Office\11.0\Excel\Options\Open.

If Office 2003 hasnt been launched by the user before the Essbase installation the registry settings used by Essbase are wiped, could be something similar..
Answered 09/13/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
0
Never, never, NEVER use that reg entry to add add-ins: it's not version-agnostic (as you can see with the '11.0' key being present). Use Excel automation instead - OBJxl.AddIns.Add([path_to_and_name_of_add-in])
Answered 09/13/2007 by: VBScab
Red Belt

Please log in to comment
0
My script takes care of the version and launches excel, will take a look a OBJxl.AddIns.Add tho' [:D]
Answered 09/13/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
0
Sure. My point was that using the .AddIn method means your script can be used for pretty much any flavour of XL. I trust you keep copies of your useful scripts...? I do, mainly because I lose track of which package I used them in so I like to keep them in one place.
Answered 09/13/2007 by: VBScab
Red Belt

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