Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-OPENED] Report Assist to Info Assist

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CASE-OPENED] Report Assist to Info Assist
 Login/Join
 
Gold member
posted
Good Afternoon,

My group is currently in the process of upgrading from WF7.7 to WF8.0.0.4. We have several older Report Assist Reports in Power Users folders, which we were told would automatically convert to Info Assist Reports in WF8.
Many of our report will automatically convert. We access the report right click, choose open with Info Assist and the report opens without error. However we also have a large chunk of reports that when trying to open in Info Assist, appear to open but return the following error: An unrecoverable error has occurred. We are sorry for the inconvenience. If we click the exit button on this error message the tool closes.

Report code has been examined between reports that will open in IA and those that get the error, no differences can be identified. we have also examined the WF7 HTML files for the reports and again no differences can be found that would cause this issue.

Has anyone else had this problem and how was the issue resolved at your site?

This message has been edited. Last edited by: <Kathryn Henning>,


WebFOCUS 7.7 and WebFOCUS 8
Windows, All Outputs
 
Posts: 36 | Registered: August 17, 2010Report This Post
<Emily Duensing>
posted
Lynsi,

It sounds like those procedures are corrupted somehow... either on the migrate to 8.0, or as they were loaded into the repository database... not sure if there is any real way to know. But that has been my experience with the error you are receiving. I would suggest you open a case with Information Builders Tech Support and see if they can help resolve the issue.
 
Report This Post
Gold member
posted Hide Post
Lynsi,

I would recommend opening a case with Technical Support so that they can review and assess the differences between working and non-working procedures.

You can call support at 1-800-736-6130.

Thanks,
Vicky Lozovsky
 
Posts: 52 | Registered: January 19, 2007Report This Post
Member
posted Hide Post
Lynsi,
Did you ever get a resolution on this? We are migrating from WF 7703 to WF 8.0.0.5 and have the same issues - 'coded' reports are fine, but we found that My Reports that a) are accessing older (circa 2003) Reporting objects and b) the RO's have more then one join and c) the report references at least one field on the secondary joined tables will not allow IA to open. We got a fix to add TAG to the join, and this fixed the RO so NEW reports would work, but didn't help the existing ones. We also tried to add the TAG line in the existing WF 7 joins in the RO's, then run the migration, but it didnt' work for the reports. Apparently somewhere between WF 4 and WF 7 the RO's changed, and now the IA tool (and migration tool) can't deal with it.


Webfocus 8.0.0.8
AIX 7.x and Windows 2012
EXL2K/07, PDF, HTML
 
Posts: 7 | Location: Altamonte Springs, FL | Registered: July 26, 2011Report This Post
Member
posted Hide Post
Lynsi,

Are you using InfoAssist Basic or the full version? We are being told by IBI that the fix may be upgrading from Basic to full. We have requested a temporary license to try it out, but was wondering which one you had.

Thanks

Bill


Webfocus 8.0.0.8
AIX 7.x and Windows 2012
EXL2K/07, PDF, HTML
 
Posts: 7 | Location: Altamonte Springs, FL | Registered: July 26, 2011Report This Post
Gold member
posted Hide Post
Are you referring to InfoMini when you mention Basic Info Assist?

We are using the full version of IA.


WebFOCUS 7.7 and WebFOCUS 8
Windows, All Outputs
 
Posts: 36 | Registered: August 17, 2010Report This Post
Member
posted Hide Post
No, apparently InfoAssist Basic is provided at not upgrade cost to replace Report Assist. It's a stripped down version of full IA (which I thought had InfoMini in it). The latest is that they are working on a migration fix for us - the licensing upgrade idea didn't appear to be a fix after all. We have between 1700-3800 reporting-object-based user reports, so manually fixing them is out of the question. I've been searching IBI, focal point, everything to see when the join started to enforce the 'tag' - looks like it came about with Developer Studio, which would then migrate to IA much cleaner. From the 7.1 release notes, I found this:

The Applet Join tool generates a 'redundant join' error message when you create a
second recursive JOIN in the MR Applet interface. This error message occurs because
the Applet Join tool does not have JOIN tag support and there is no way for users to
identify a tag name as they can in HTML Report Assistant and Developer Studio.

And we probably did most of our joins way back when with the join (applet) tool, or if we coded them manually, just didn't use the tag (was there a reason to?).

There was never a real push from IBI (at least locally) to go from Report Assist to Dev Studio - if we had know the potential issues, we definitely would have earlier on (before 8).


Webfocus 8.0.0.8
AIX 7.x and Windows 2012
EXL2K/07, PDF, HTML
 
Posts: 7 | Location: Altamonte Springs, FL | Registered: July 26, 2011Report This Post
Member
posted Hide Post
Lynsi,

Late Friday we received a fix from IBI, and after about 2 hours of testing, it appears to be working. We will continue to exercise it. This is now allowing us to open (in InfoAssist Basic) reports generated with Report Assist that used reporting objects, regardless of the number of joins in the old RO.

We still have to check to see if the RO itself will open in the join tool - with > 1 join, it wasn't working before. This is a less critical item for us.


Webfocus 8.0.0.8
AIX 7.x and Windows 2012
EXL2K/07, PDF, HTML
 
Posts: 7 | Location: Altamonte Springs, FL | Registered: July 26, 2011Report This Post
Gold member
posted Hide Post
Thank you for the heads up Bill. I am going to check with IBI since we were not issued a copy of this fix.


WebFOCUS 7.7 and WebFOCUS 8
Windows, All Outputs
 
Posts: 36 | Registered: August 17, 2010Report This Post
Member
posted Hide Post
No problem. My understanding is that it's not a migration fix, but rather a fix to the actual WF 'engine'. One caution - the join tool doesn't always show the correct joined fields (relationships), but they still seem to work. Our RO's are pretty status after 12+ years.

Our contact who faciliated the fix delivery was:
Renee Teatro
WebFOCUS Support Manager
Customer Support Services
Information Builders


Webfocus 8.0.0.8
AIX 7.x and Windows 2012
EXL2K/07, PDF, HTML
 
Posts: 7 | Location: Altamonte Springs, FL | Registered: July 26, 2011Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CASE-OPENED] Report Assist to Info Assist

Copyright © 1996-2020 Information Builders