Software Deployment

I am assuming this is a snapshot and if that is the case it clearly means that you didnt re-pacakage it properly :)

Use procmon to find the problem, as im sure vbscab will say when he reads this post.

P

ORIGINAL: Inabus
Use procmon to find the problem, as im sure vbscab will say when he reads this post.For once, ProcMon isn't going to be much use here. You will be much better off going into the VBA Editor in XL (Alt+F11) and running the relevant macro step-by-step (F8). This will highlight which array has no elements (which is the cause of the problem) and you can work back from there.

I presume we're talking about the ESSBase XL add-in? As an extreme favour, I've posted a copy of the WSI we use for v9.30 here http://senduit.com/184627 The link expires in 24 hours. The WSI is set to use external files, the structure of which will be obvious if you examine the WiseSourcePath table. You'll need to alter some of the other properties to suit your environment. Lastly, if you're not using a Wise product, WSIs can be opened in Orca and written out as regular MSIs.

My post was based on the assumption that a re-package has occured, obviouslly I didnt take account of him using a vendor MSI.

P

ORIGINAL: Inabus
My post was based on the assumption that a re-package has occured, obviouslly I didnt take account of him using a vendor MSI. ? I'm not sure what you mean, Paul. Irrespective of whether it's a re-package or not (it is: Hyperion uses the Java-driven InstallShield installer), PM won't help much here, other than showing the add-in being opened by XL.

The 'Subscript out of range' error occurs in VB/VBA/VBScript when an attempt is made to access an array element which doesn't exist so running the code is the only way to begin a diagnosis. For example:

Dim intIndex
Dim arrTest(2) '//Define a 3-element array (arrays are zero-based)
arrTest(0) = "Tom"
arrTest(1)="Dick"
arrTest(2)="Harry"

WScript.Echo arrTest(1) '// This will display the string 'Dick'
WScript.Echo arrTest(3) '// This will produce the errorBTW, I posted the WSI for the OP because I'm reasonably sure that he has fallen foul of how to properly add add-ins to XL. I can almost guarantee that his capture assumes that the add-in is the only one in use and has overwritten the 'OPEN' registry key. The WSI includes a CA to add the add-in correctly.

Aye, the point I was trying to get at was if its a re-capture it may very well be a problem with the registry keys for the addon, or lack of keys due to a too vigorous clean up!

Of course he doesnt say its a re-package so all my points are mute until this bit of information is forth comming, like the version number etc. I was, however, of the assumption in that during the process of "loading" hyperion he got this error message, i.e. missing keys / files, this of course isn't neccasarily the case.

P

the java installer on Hyperion Essbase requires Excel to be installed prior to installing Hyperion.

If excel is not detected then it does not prompt nor install the excel addin's. effectively leaving the application useless. (kinda smart thinking on hyperion's account I think)

anyway there is two excel addins that need to be copied from a working machine and or reinstalled with excel on prior. You will also need to activate the two addin's as VBScab briefed over with the registry keys missing.

when i packaged this i installed excel first in order to capture it to an MSI state. (not ideal but it works)