Got the message about tbaddin64 add-in.

Arif Lalji-Oracle

User_Y7EUY - As the root cause is coming from Windows/Office Build update and not Template Builder itself, we will need to wait for Microsoft to address this issue.

johndavid78 - Thank you for pointing this out to me! I will go ahead and correct it - also note for next time, for any KM articles you think needs amendments, you can add a comment to it and the owner of the article will be notified.

OlivierD

Alright, it seems clear now that the issue is coming from Microsoft and the procedure in the Oracle Ticket didn't work for us somehow but the solution suggested by @User_5BASX on August 20th in this thread did fix the issue for us.

However, for security puposes we can only consider this as a temporary solution. If the issue is coming from Microsoft, is there any MS issue ticket number yet ?

With it we could at least know when we will be able to reactivate the MS Updates.

Arif Lalji-Oracle

OlivierD We do not have any direct support contract with Microsoft since we are using the same general MSDN though UNO user however should you wish, you are more then welcome to contact them directly in regards to this

Gino.Corti

I've tried to follow the steps shown by @User_5BASX unsuccessfully. Although the issue is comming from Microsoft, I think that Oracle must provide a solution because BI Publisher is a tool to develop on Fusion envoriments.

Arif Lalji-Oracle

Gino.Corti - agree on the part of the BI Publisher Add-in however this is a supplement to the Microsoft code which we have no control or access to. Also some of the workarounds including refreshing to get the current update has worked for other customers which leads us to confirm the changes need to be made on their end.

And as much as we would want to give you a resolution, all parties including us are at a standstill until it officially gets resolved on Microsoft end.

Arif

User_K1VM3

According to the Knowledge Article
E-BIP/OAP/OAS: Template Builder - Addin using Office 365 Aug 1 Version 2407 (Build 17830.20138) (Doc ID 3041646.1)

The solution heading is:

"The BI Publisher development team has reviewed the issue in detail and determined that the issue is as a result of a Microsoft Office/Windows Update which Oracle has no authority over in making any changes and are hoping that future updates from Microsoft corrects this specific issue."

I am concerned with the use of "hoping that future updates from Microsoft corrects this specific issue"

Has there been a case opened with Microsoft, since this is impacting many of your customers. Have you notified them that a change they made is impacting production solutions for your customers? If Oracle has not logged a case directly with Microsoft. What information would you recommend your customers share with Microsoft so that they may provide comprehensive details of the issue?

OlivierD

@User_K1VM3, I already asked the same question and @Arif -Oracle already answered to this on august 29th.

User_M4S36

Is this issue resolved? do we have any work around for it so we can work with BI Publisher plug-in and can start working on reports.

User_UQ4TV

Is there a third party program that allows the creation and modification of these reports or is this add in only way to do it?

david.stmartin

As a workaround, downgrading Office as mentioned by EJ on aug. 17th worked for me :

1. Open office.
2. File, Office Account, Update Options and click on Disable Updates.
3. Start typing cmd on the Start screen in the task bar search field to find the Command Prompt then click Run as Administrator
4. "C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.17726.20160
5. Start an Office application

Just want to add that you might need to go re-enable the Publisher plugin if Word disabled it earlier by going to Options - Add ins - Manage disabled items.

Update : I've attempted to re-update to the latest 2408 version (skipping over 2407 from 2406 using the method above directly to 2408). So far, my Publisher plugin has been stable using this version. I wonder if the specific issue was brought in by 2407, but carries forward unless you revert, and skip the July update in favor of the latest directly.