As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
The only difference between it and other objects in MRE is that it was not previously on the prod server and was copied, not moved via MRE change control.
I found that the permission list looks different for that file. It is missing an Administrator permission that says "not inhertited".
I tried repeating the migration via MRE. Now it works for me but still fails for everyone else ????
I then tried deleting the HTM file to remove all settings and repeated the migration, same results.
I have read about "soft" versus "hard" deletes and wonder if a "soft" delete is preventing removal of the file so that it can start "clean".
This is our production rollout and we are frantic.
Okay... Our problem is now resolved and it was actually two issues:
Issue 1) MRE could not see the HTM
Resolved by using MRE Change management Tool to migate that file. Previously we simply copied the file from server to server. Obviously the MRE tool does more than that.
Issue 2) The link was found but client received error 19402 "Your session has expired or been invalidated". After logging again a second time, the page was displayed.
This was due to a certificate error. Redirected link to authenticated web site.
Apparently the different permissions had nothing to do with issue.