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.
We were having trouble importing a CM package with a single portal in it from one 8104 environment to another, and somehow the package took, but we can't run the portal, or rename it, or even delete it because of the following error:
Obviously, that's not a very helpful error, and I don't know if this is a configuration error that is causing this, or what to do to troubleshoot this.This message has been edited. Last edited by: <Kathryn Henning>,
WE usually have to delete the offending item whether it is a fex or portal on the site you are importing to.
What we have found is if you rename a fex or portal, not the description, but the fex or bip name, this error happens. Seems the import looks for the internal key, and a name and a missmatch happens.
So I work with J Hines. We are migrating to a new server. I had gone in before to edit a portal and it disappeared upon save. When trying to import a new version of the portal from an existing server it gave me a sql insert error. There wasn't anything to delete so I created a new portal with the same name so that I could import the cm package.
From there it brought back the original plus the one I created. Now we can't delete either of them. Is there a way to correct this?
8.1.0.4 Windows 7 Excel, AHTML, HTML,PDF
Posts: 41 | Location: North Carolina | Registered: September 14, 2012
Our admin apparently solved this by basically deleting everything in repository database. I'm not sure if it could have been solved with something less drastic, because it took a while to migrate user, rules, etc back over from the other environment, but we eventually got this sorted out.