MF:186 or similar error in Web Access or other Panorama view component in Dashboard

MF errors can be caused by several factors therefore it needs to be identified prior applying correct resolution. To resolve the error, you will need to take into consideration the desribed properties such as: error consistency, appearance place and trigger. There's no solid solution for this kind of errors because of the variety of triggers that might be causing them. The error resolution might take time and patient investigation.

For beginning, try the most simple solution that works in many cases, Clean Java cache and cookies (Instructions)

The other common scenarios for this type of errors are:

1. Incorrect driver version that enables connectivity to OLAP from Panorama server. Follow the steps in #1 under "Solution" section below on this page.
2. The cube structure : dimension, hierarchy, level was changed - members that included in : Formulas, Selections, Set, KPI, Reorder, Filter, Advanced Exceptions was removed or renamed. Follow the steps in #2 under "Solution" section below on this page.
3. Illegal character in view/book/level/dimension/member name.Follow the steps in #2 under "Solution" section below on this page.
4. MDX error in the view. This may be result of: wrong formula created, formula that enters "endless loop", formula that relies on missing members and so on. To resolve MDX errors, MDX knowledge required. Follow the steps in #3 and #5 under "Solution" section below on this page.
5. Whether you are using cache mechanism, and dimension structure changes, the view initially trying to load the previous dimension structure. Follow the steps in #6 under "Solution" section below on this page.

Error consistency

Whether the error appears consistently, this can indicate a problem with the calculations in the view. Inconsistency of the error can be caused by variety of reasons:

1. Incorrect OLAP driver version.
2. Cache contents of the view could not be retreived and the view not updated. Follow the steps in #4 under "Solution" section below on this page.
3. The view contains restricted characters or named with one os special ASCII characters such as , . ? / " !%& ect.

Error appearance trigger

Identify whether the error related to client or server side. If it appears on all views or all client machines, it is probably related to server. Whether the error inconsistently appears on some of the clients, this is client-side issue.

Open the view with error in Desktop client on the server and perform the same operation that caused the error to appear on Web application. Whether MDX or other error appears, this is the cause to the MF error on client side. Whether the view opens correctly, proceed on.

Define the error trigger: does it appear when the view opens of after performing some operation, such as preview dimention members. Provide all gathered information to support team prior

 

 

MF error on view open

1. To compare the drivers on Panorama server and OLAP server, follow this link. In some cases, re-install of connectivity driver resolves the issue, especially if the errors consistently appear.
2. Recreate the same view via Desktop client under name "test" in book named "testbook". If the error doesn't appear, re-check the names of your views/books. Review the next link to learn which characters should avoid:
   http://blogs.msdn.com/lduff/archive/2006/06/30/652913.aspx
3. Simplify the view, when there's no sorting, filtering, exceptions, selections, complicated formulas and hidden members applied. Select only one member on row and column.
4. In that case you will have to rebuild the view. In some cases the recommendations in this link might help.
5. Another option to try is validate the view (which is XML file that is not updated) against cube structure.Instructions:
   
   1. Open the Desktop and go to Tools>Options>Advanced
   2. Refresh the book (right click on the book>refresh)
   3. Change the following setting, whne you logged on as Administrator:
      
   4. Clean cache and cookies in the browser
   5. Create "tree" file as instructed here and run the MDX on SQL Management studio. You will be able to find the error using this tool and fix this on OLAP side.
6. Clean Panorama database cache. (Instructions)

Whether the problem persists, take the steps in this link to extract the detailed Java console and compare to the list of error meanings below. Send the relevant information to Support team, including detailed Java log, MF error and the XML of the view.

 

MF errors meaning

The MF error is constructed from error ID and sub error ID. The sub error ID can be previewed with Java console only (recommended to use the extended mode with ctrl+alt+double click on title). For detailed instructions, follow this link
The log will contain a text in the end, similar to this:
-> Alert Info -> MainFrame:186:608
By sub error, you can find a definition of the problem.

• MF:186:601 - Missing grid properties - no string can be received(all data received from server as a string that turns to a number).
• MF:186:602 - Missing grid properties. String received but it is not a number.
• MF:186:603 - O members : no string.
• MF:186:604 - the string couldn't be parsed to number.
• MF:186:605 - error when parsing X axis
• MF:186:606 - Parsing ok in X axis but no members received.
• MF:186:607 - error when parsing Y axis
• MF: 186:608 - This error means that the grid structure the client gets from the server is wrong: axis Y doesn't contain members
• MF:186:609 - Get chunk error - no grid attached
• MF:186:610 - Error parsing grid data
• MF:186:611 - Error parsing grid data using "more" buttonNext 2 errors related to grid vs axis structure. The grid and axis sent separately from server to Java client and connected finally.
• MF:186:612 - Relate to X axis: structure of the grid doesn't fit X axis
• MF:186:613 - Relate to Y axis: structure of the grid doesn't fit X axisNext errors related to name of briefing books/legend
• MF:875: Data from private briefing book was not parsed.
• MF:867: Data from public briefing book was not parsed.
• MF:854 : Data from legend was not parsed.
• MF:916 - Error in server information (boxa section).
• MF:186:163 - The reason of the problem is wrong grid axis Y data structure. The height of some leaf members in this axis is bigger than one row.
• MF:1012: Critical important server information is missing (application tree/table/slicers/legend). The most common: Table or slicers. It means that the server returns result that doesn't contain expected information parts (grid, application tree, legend, etc.)
• MF:1041 - Can be any type of problem on server: Analysis services down, no connectivity, ect.
• TBI:3717 - Unexpected exception when parsing server data for advanced search dialog
• #ERROR#WSAWaitForMultipleEvents() error: 0 This error means that the service didn't return result in the expected time. There must be an error in application log. This error related to timeout.
• Get Tree error: return the tree of dimension members. To debug, can compare the results using CallShowTree() function. Java console should point out the dimension in that case.

• All versions