Guys
A follow up question on this.
We deploy our PAfE versions via a software package which comes down the pipe to the users' laptop
Our steps have been to launch the Uninstall on the user laptop, and then, as a "belt and braces" remove the following folders, before forcing a restart of the laptop itself :
- C:\Program Files (x86)\ibm
- C:\Program Files\ibm
- C:\Users\<USER.ACCOUNT>\AppData\Roaming\Applix
- C:\Users\<USER.ACCOUNT>\AppData\Local\Cognos
The installation of the new version then takes place and the connection strings are added back in.
We are on v64, and we are aware that from v65 onwards there is no longer an issetup.exe but we have the xlls.
How are these added to the user machine ? Is there an install to follow or do we need to push these out and change our package to lift the xll in the Excel add-ins, after we have placed it somewhere appropriate ?
Cheers
Ajay
------------------------------
AJAY CHANDHOK
------------------------------
Original Message:
Sent: Sat August 21, 2021 02:51 AM
From: George Tonkin
Subject: IBM Framework for Office and PAfE 2.0.66 installs
HI Adam,
Thanks for all the assistance - much appreciated.
There was nothing remaining in my Add or Remove Programs but tracked down the Uninstall for the IBM for MS Office framework and removed it.
After doing that, all is working as expected now.
------------------------------
George Tonkin
Original Message:
Sent: Fri August 20, 2021 04:22 PM
From: Adam Havas
Subject: IBM Framework for Office and PAfE 2.0.66 installs
George,
The PAFE API has not changed. We cut over from 2.0.57 to 2.0.66 and all VBA functionality remains working.
When you say "referencing the older framework", are you seeing a VBA error w/
Set m_oCOAutomation = Application.COMAddIns("CognosOffice12.Connect").Object.AutomationServer
We have only seen this issue in one case, and only in testing, never in production. If you have BOTH classic PAFE and XLL-based PAFE enabled simultaneously, the XLL-based PAFE is blocked from creating a COM Addin named "CognosOffice12.Connect" and will instead name the COM Addin "CognosOffice12.ConnectPAfEAddin".
Workaround would be:
Set m_oCOAutomation = Application.COMAddIns("CognosOffice12.ConnectPAfEAddin").Object.AutomationServer
HOWEVER, you should not need the workaround. Instead you should make sure the classic PAFE is fully uninstalled.
Let me know if this is what you're seeing or it's something else.
------------------------------
Adam
Original Message:
Sent: Fri August 20, 2021 04:07 PM
From: George Tonkin
Subject: IBM Framework for Office and PAfE 2.0.66 installs
Hi Adam,
Thanks for the feedback.
I agree that 2.0.65 onwards should be standalone but not seeing the automation components needed for my templates with macros to run.
The API code is referencing the older framework and I have not seen anything on a new framework or changes required for API code when upgrading to 2.0.65 or higher.
I am definitely missing something, just not sure what.
------------------------------
George Tonkin
Original Message:
Sent: Fri August 20, 2021 03:52 PM
From: Adam Havas
Subject: IBM Framework for Office and PAfE 2.0.66 installs
Hi George,
Assuming there's no Cognos Analytics in the mix, from my experience with PAFEv65+, there is only a single XLL file to manage.
Sequence:
- Users should uninstall the "Classic" IBM PAFE add-in using the Uninstaller that's on their Start Menu.
- Then, the user should add the single XLL to Excel Add-Ins and enable it.
- Upon enabling the Excel Add-in two additional COM Add-ins automatically appear: IBM Planning Analytics for Excel Addin + IBM Planning Analytics for Excel Addin (Custom Task Pane Helper). No further action is required.
IBM Framework for Office is part of the "Classic" IBM PAFE that should be uninstalled in step 1.
This is how we're using it on my end.
Thanks!
------------------------------
Adam
Original Message:
Sent: Fri August 20, 2021 02:44 AM
From: George Tonkin
Subject: IBM Framework for Office and PAfE 2.0.66 installs
HI,
Does anyone know what the installation method and sequence should be for new users who will be using templates that leverage the PAX API?
Essentially, if the user has the IBM_PAfE_x64_2.0.66.9.xll added to their Excel does this somehow add the IBM Framework for Office?
I cannot see this on my installation as my CognosOfficeShim12.dll is still dated 2021/02/12.
Is there a separate install for IBM Framework for Office? Only seeing Cognos for Microsoft Office on Fix Central.
I may have missed it in the documentation somewhere but would appreciate if someone can guide or clarify on the above.
Thank you.
Edit: Enabling the IBM Framework for Office gives me 2 PA Menus in Excel - one for 2.0.62 and another for 2.0.66. Previous versions of PAfE were removed before switching to 2.0.66. Without enabling the IBM Framework for Office, all macro code with API calls fail.
------------------------------
George Tonkin
------------------------------
#PlanningAnalyticswithWatson