Hyperion Essbase
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
Answers (11)
Please log in to answer
Posted by:
MSIMaker
20 years ago
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.
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.
Posted by:
CBuford
18 years ago
I am attempting to package the Essbase plugin and I get the exact same error. Does anyone have any additional ideas?
Posted by:
tlopez
17 years ago
I have packaged version 7.1.6 using rsp file it works for intalling but having issues uninstalling anybody have any ideal
Posted by:
jmcfadyen
17 years ago
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.
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.
Posted by:
Inabus
17 years ago
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
Paul
Posted by:
anonymous_9363
17 years ago
I concur with the last 2 posts: you need both files to be present.
Posted by:
Tone
17 years ago
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..
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..
Posted by:
anonymous_9363
17 years ago
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])
Posted by:
Tone
17 years ago
My script takes care of the version and launches excel, will take a look a OBJxl.AddIns.Add tho' [:D]
Posted by:
anonymous_9363
17 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.