*If you are still having difficulties after trying these remedies please call the Help Desk at 754-321-0411.*

New Problems    

1. School Reports:
   We would appreciate suggestions on what you would like to see on this Reports Menu.  Please send an email to DWH Mail with your suggestions.
   

2. Web Query Users:
   Please do not update your browser past Internet Explorer 5.5 or Netscape 4.72 because the Web Queries application will not function properly.
   

 

3. Macintosh FileMaker Pro Users:
   There is a conflict with the FileMaker ODBC drivers and MacMidrange. When you installed FileMaker Pro 5 or a higher version on the MAC, it installed the FileMaker ODBC drivers.  These drivers interfere with the MacMidrange drivers for BRIO.  BRIO will not work and you will get a "Type 1" error message when you logon to BRIO. There should be no reason you will ever need these drivers. If you have already installed the ODBC drivers for FileMaker, you must remove ALL references to ODBC.

   • Select Apple/Sherlock or Sherlock2 (Shortcut is Apple [Command] and [F])
   • Enter ODBC and click on the magnifying glass
   • Drag all the files found to the TRASH. Be careful you are only discarding ODBC files!
   • Empty TRASH
   • Repeat these above steps until there are 0 ODBC files found
   • Now click here and print these instructions to reinstall MacMidrange
   • You do NOT need to reinstall FileMaker or BRIO

   On a PC, uninstall Filemaker and then resetup your ODBC.  To reinstall FileMaker, the "Custom Install" must be used.  The "Easy Install" must NOT be used.  All items under the "Custom Install" can then be checked except: "FileMaker Pro Web Support" and "ODBC".  This MUST be left blank.

 

LOGIN PROBLEMS

1. If you have a problem logging in to the School Reports Menu:
   The signin and password is case sensitive.  Most are in lower case. If lower case does not work, try upper case for the signin.  Please check your case before seeking help. Please contact the ETS Help Desk.
   

2. Cannot Login after initial Installation
   CHANGING USER ID / SERIAL NUMBER

    When a customer completes network login with id used during installation, Hyperion opens successfully. When a customer completes network login with id other than id used during installation, Hyperion requests serial number. This is a new security measure for Hyperion 8.

    

   There are two workarounds for it :

   1. Log in as first user,

   2. start regedit,

   3. manually export the registry keys for Brio Software to a textfile,

   4. logout,

   5. login as second user,

   6. start regedit,

   7. import that text file.

   OR

   1. Have local admin rights granted to install product, then remove admin rights
      

3. If you are on a Mac, and your screen freezes when you try to login:
   The MacMidrange software needs to be upgraded to handle the faster processing time of our new equipment.  Upgrade to MacMidrange 2.0d2

   **If you are still having difficulties after trying this, please call the help desk, so that they will be aware that you are having a problem.

4. Can't log onto BRIO (Mac):
   If you can't log onto BRIO, you can usually pinpoint the problem by going to the Control Panels and checking the settings.
   * MacMidrange Configuration: In order to access the Data Warehouse AS400 you must have the correct information entered in this Control panel. The Control Panel should look like this (but with your own Default User ID number):
   

• ODBC SETUP PPC control panel has several "tabs" or sections that need to be configured. The General Tab is where most of the errors occur. It should look like this
  

• The main item is the AS400 connection. It must read AS9625C in order to access the Data Warehouse server.

3. User can not log in:
   Try to Ping the server. The Ping utility is located on the BRIO Installs folder. They want to Ping 10.252.0.135. If the Ping is successful at least you know their IP configuration, etc is OK.

4. BRIO asks for Serial Number every time you log in:
   Go to your System/Preferences folder and drag all the BRIO preferences to the trash. Empty the trash and restart BRIO. You will be prompted to enter the BRIO serial number (318208409-300730377) and the problem will go away.

INSTALLATION PROBLEMS   Back to Top   

1. IP address for school AS400:
   Installing MacMidrange for BRIO means replacing existing InterAxcess settings. This also means it loses connection information to the school AS400. You can goto you DPC or TLC for the school AS400 IP address or you can get it from typing SYSINFO on the command line of TERMS if you have access.

2. Different ODBC SETUP PPC Control Panel:
   The install notes refer to a Control Panel that is created when a user does a COMPLETE install of the Value Pack found on the Office 98 CD. In order to fix this problem, Office 98 must be completely removed - the remover is in the BRIO Installs folder. Once it is removed, install BRIO and then reinstall Office. When reinstalling the Value Pack install everything except the item called DATA ACCESS.

3. Install OK but never allows user to log into BRIO:
   If the user says that they have finished the install but the system just displays the timer watch when they attempt to log in they need to make sure Ethernet is turned on and they see their Zone. Many users have their system set to Modem/Printer Port in the Apple Talk Control Panel. They must go in and change this to Ethernet in order to log into BRIO. They can do a complete install of BRIO via Apple Talk but BRIO needs the Ethernet configured in order to log in.
   

4. BRIO Insight does not install:
   If you are trying to run web queries and get a prompt to download ods.ods, you must install BRIO Insight.
   PC Users: 
        Click on the following link to force BRIO Insight to be installed to your computer http://dwh01/odshtml/zeroadmin/wizcab1.insight.html
   
   Mac Users: 
       Refer to the download instructions for installing BRIO Insight on the web.

ERROR MESSAGES    Back to Top   

1. "HTTP Status 404 - /Hyperion:8080/browse/Main
      description: The requested resource (/Hyperion:8080/browse/Main) is not available.
   This is caused by the proxy setup on the machine not being set up to allow access to the Hyperion portal.  The settings for the proxy server should be as below:
   
   
   

2. "RW Tools.sh++.slib:"
   This occurs when you are running OS 8.5. The install procedure for MacMidrange does not completely install all files under 8.5. There are 4 files that need to be manually copied to the System\Extensions folder. They are in the BRIO Install folder in a subfolder called OS 8.5 Fix. Just copy these files and then continue with the install. No need to reboot.

2. "Duplicate licenses for InterAxcess:"
   As part of the installation you are asked to trash your old InterAxcess aliases, preferences, etc. since MacMidrange will install the newest version. If you don't do that, the system thinks there are two copies running and gives the error message.

3. Communication Link failure upon login:
   If your message is:
   



Either you have entered the password or ID incorrectly or your userid has been disabled from more than 3 invalid sign-on attempts. Try it again. If it still doesn't work, Data Warehouse staff may have to check the ID.
OR you have entered the wrong IP address for the MacMidrange Config of AS9625C. Make sure the IP address is 10.252.0.135

4. "Type 1" error message:
   There is a conflict with the FileMaker ODBC drivers and MacMidrange. When you installed FileMaker Pro 5 or a higher version on the MAC, it installed the FileMaker ODBC drivers.  These drivers interfere with the MacMidrange drivers for BRIO.  BRIO will not work and you will get a "Type 1" error message when you logon to BRIO. There should be no reason you will ever need these drivers. If you have already installed the ODBC drivers for FileMaker, you must remove ALL references to ODBC.

   • Select Apple/Sherlock or Sherlock2 (Shortcut is Apple [Command] and [F])
   • Enter ODBC and click on the magnifying glass
   • Drag all the files found to the TRASH. Be careful you are only discarding ODBC files!
   • Empty TRASH
   • Repeat these above steps until there are 0 ODBC files found
   • Now click here and print these instructions to reinstall MacMidrange
   • You do NOT need to reinstall FileMaker or BRIO
   
   

   On a PC, uninstall Filemaker and then resetup your ODBC.  To re install FileMaker, the "Custom Install" must be used.  The "Easy Install" must NOT be used.  All items under the "Custom Install" can then be checked except: "FileMaker Pro Web Support" and "ODBC".  This MUST be left blank.

   .

5. "Type 11" error message:
   This is usually caused by using an older version of Open Transport. You must have version 1.1.1 or higher. The latest version of Open Transport can be found in the BRIO Installs folder. When running the  Open Transport installer it will replace or update all necessary files.

6. "Type 12" error message:
   This is usually caused by Mac Midrange. You must Remove and then Reinstall Mac Midrange.

7. "Not authorized to object . . . . :"
   If your message is:
   
   You are logged on as one type of user, but trying to access the repository as a different type of user.  For example, you have a district signon ("U......"), and you are trying to access School Administrator queries.   You are only able to access the queries as designated by you User Id.  If you have questions about your User Id, see FAQ #4 under 'Access to the System'.

1. No Results when processing a query:
   Verify that you have typed in the LIMIT correctly.  If you have typed in a space before or after the entry, BRIO interprets this as a character and will not find the correct results.

2. No items in the Open Catalog:
   The Open Catalog folder is where the user goes to choose their user type (ADMIN, INSTRUCT, DISTRICT) when logging in. If this folder is empty, you need to go to the BRIO Installs folder and copy the Open Catalog folder to your desktop. Then copy the contents into the BRIO Explorer Open Catalog folder on your hard drive.

3. Your Computer is Freezing:
   Check your memory settings. Highlight the BRIO icon on the hard drive.  Go to File, Get Info.  Set minimum memory to 25,000 and preferred memory to 50,000.    Also, check the version of Open Transport you are running.  Go to Control Panel, TCP/IP and click on Info.  It should be at least version 1.1.1, but preferably 1.2.

4. "Garbage": in blank fields:
   If you run a query and see garbage (boxes, symbols, etc.) in any of the fields it indicates that you have a corrupted Preference file. Go to your System/Preferences folder and drag all the BRIO preferences to the trash. Empty the trash and restart BRIO. You will be prompted to enter the BRIO serial number (318208409-300730377) and the garbage will go away.

5. Numbers saved in BRIO do not export to Excel:
   The problem is because the number is a decimal point. The field must be changed to a data type of REAL in order to allow export to another file format.  These are the steps:
        a.  Click on the Query section.
        b.  Go to the Request line and double-click on the decimal field that is not exporting.
        c.  Click on the Options button.
        d.  Go to the Datatype field and choose REAL.
        e.   Save the query and process.

6. Numbers saved in BRIO do not export to Filemaker:
   The problem is because the number is a decimal point. The field must be changed to a data type of STRING in order to allow export to Filemaker file format.  These are the steps:
        a.  Click on the Query section.
        b.  Go to the Request line and double-click on the decimal field that is not exporting.
        c.  Click on the Options button.
        d.  Go to the Datatype field and choose STRING.
        e.   Save the query and process.

7. Pages on the website do not print all the lines:
   Because all computers are not set to the same font, and all printers do not print the same, some lines may be left out when printing from the web. A new printable version (PDF format) of all pages will be available soon that will solve this problem.

8. The COUNT feature in the Pivot Report shows only 1s:
   The problem is because Surface Values feature has been turned on.  In the Pivot section:
        a.  Click on the Pivot on the menu
        b.  Click on Use Surface Values to turn the feature off

HOME