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     [CLOSED] Worp-out! Dashboard Viewbuilder messed up!

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] Worp-out! Dashboard Viewbuilder messed up!
 Login/Join
 
Francis Mariani
Expert
posted
One of my colleagues was reassigning user views to group views by performing the following activity:


  • log in to ViewBuilder
  • reassign user views to group views
  • log out of ViewBuilder
  • log in to Dashboard as the user to verify the view change
  • log out of Dashboard

At some point during this process, after logging in to ViewBuilder, clicking on "Group Views" gives us a "There are no Group Views" message and clicking on "Manage Users" gives us the dreaded HTTP 500 message.

We've opened a case with Tech Support but I'm hoping to solve the problem myself - I'm not sure where to begin.

I'm looking for how ViewBuilder determines the list of Group Views, it can't be just by looking in the folder Drive:\ibi\WebFOCUS53\worp\worp_custom.

Any ideas?

This message has been edited. Last edited by: Kerry,


Francis


Give me code, or give me retirement. In FOCUS since 1991

Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
 
Posts: 10577 | Location: Toronto, Ontario, Canada | Registered: April 27, 2005Report This Post
Trav
Platinum Member
posted Hide Post
Francis, are you looking for the c:\ibi\WebFOCUS71\worp\conf\mpv.xml file?

That has the list of groups and the list of users and their default views.


Production: 7.6.6 WF Server  <=>  7.6.6 WF Client  <=>  7.6.6 Dev Studio
Testing: <none>
Using MRE & BID.  Connected to MS SQL Server 2005
Output Types: HTML, Excel, PDF
 
Posts: 230 | Location: Wichita, KS | Registered: May 27, 2005Report This Post
mcav
Member
posted Hide Post
Please let me know what comes of this as I have encountered the same issue in the past.

Thank you,

Mike


WebFOCUS Dev Studio 7.7.03
Windows 2003 64bit
HTML/Excel2K/PDF Output Formats
 
Posts: 11 | Location: Overland Park, KS | Registered: December 06, 2007Report This Post
Joey Sandoval
Gold member
posted Hide Post
Does anyone have a resolution to this? Our mpv.xml got cleared out when one of our guys reassigned a user view. We replaced the corrupted mpv.xml with a copy from our nightly backup, but we are still experiencing the HTTP 500 message when we click on the available views.



Prod/Dev: WebFOCUS 8.0.08 on Windows Server 2008/Tomcat , WebFOCUS DevStudio 8.0.08 on Windows 7 Pro

 
Posts: 94 | Location: Austin, TX | Registered: August 08, 2012Report This Post
mikegalu
Member
posted Hide Post
Did you recycle the web-application and clear the cache through the admin console?
 
Posts: 1 | Registered: February 24, 2004Report This Post
dhagen
Virtuoso
posted Hide Post
This isn't a solution, but one of the first things I do on a dev or testing install is edit the web.xml and comment out the following: 
  <error-page>
      <error-code>500</error-code>
      <location>/applicationErrorPage.jsp</location>
  </error-page>


This is a catch all for error messages, and prevents you from seeing the actual exception. This may not help, but this has helped me a lot in the past for isolating errors.


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report 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     [CLOSED] Worp-out! Dashboard Viewbuilder messed up!

Copyright © 1996-2020 Information Builders