Palisade Knowledge Base

Knowledge Books

• Knowledge Books
• Standalone Licenses
• Network Guide
• More on Networks
• End User Setup
• Techniques and Tips
• Troubleshooting
• Licencias individuales
• Guía para Administradores de Red
• Licencias de red
• Configuración de usuario final
• Técnicas y Consejos
• Soluciones
• Licenças Standalone
• Licenças de Rede
• Configuração do usuário final
• Técnicas e Dicas
• Soluções
• Obsolete Articles

• Main Support Page

Home → Troubleshooting → All Products: Startup → @RISK Initializes, But No Tab Appears in Ribbon

2.16. @RISK Initializes, But No Tab Appears in Ribbon

Tambien disponible en Español: @RISK se inicializa, pero no aparece ninguna pestaña en la cinta de opciones

Applies to: All products, running under Excel 2007 or newer
(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

If one of these more accurately describes your situation, please refer to that article instead of this one:

• @RISK Creates Add-Ins Tab in Ribbon, with Tiny Icons
• @RISK Creates Empty Add-Ins Tab in Ribbon
• If you have BigPicture also, please launch it. If you get the error "Initialization Error: Shapes Initialization", the two problems have a common cause. Please refer to that article.

When I launch @RISK, I see the initialization window, and the status messages at the bottom of the Excel window. There's no error message, but the @RISK tab doesn't appear, and there's no Add-Ins tab.

There are several possible causes and cures for this problem. In no particular order:

1. You may simply need to tell Excel to trust our software.
   1. To test this, launch Excel only.
   2. Click File » Open, and navigate to C:\Program Files (x86)\Palisade (if it exists) or C:\Program Files\Palisade.
   3. Under that folder, open the folder for your software, such as RISK7 or StatTools6. If you have the DecisionTools Suite, it doesn't matter which product folder you select.
   4. Then double-click the appropriate add-in, which will be Risk.xla, Evolver.xla, NeuralTools.xla, Ptree.xla, StatTools.xla, TopRank.xla, or BigPicture.xlam.
   5. If you get a security popup, look in the dialog for a check box labeled Trust all from this publisher, and tick it. If the software then opens normally, you have solved the problem and you won't get the security prompt in the future.
   6. Use this Microsoft article to uninstall Office completely. We recommend the easy Fix It in Option 2.
2. Your COM Type Library may have outdated entries, or may not be functioning correctly. To check for outdated entries, see Removing Outdated References to Office from the System Registry. If your COM system is not functioning correctly, a repair of Microsoft Office may or may not fix it, but it's definitely worth a try.
3. Another possibility is a setting in Group Policy or Office Customization Tool, "Disable UI extending from documents and templates" which prevents our software from adding its tab to the Excel ribbon.
   
   • If you have software release 6.3.1 or newer, and this Group Policy setting exists, the software will display the message "@RISK cannot be started because of the following Office security setting ... noextensibilitycustomizationfromdocument=1". Please see that article for the solution.
   • If you have software releases 6.3.0 or older, it will not display a message, even if the condition exists. Therefore, please follow the numbered steps near the bottom of that article to learn whether that Group Policy setting is the problem, and to fix it if it is.

   See also: Group Policy and Office Customization Tool Settings: Technical Reference.

4. Did your antivirus software block a Palisade component based on a false positive? Check your antivirus logs, and unblock the software component. Please report the exact name of the blocked file, and the full name of your antivirus program, to Palisade Technical Support, so that we can contact them to get the false positive corrected.
5. One of the above solutions works for almost everyone with this problem, but for a small minority, they all fail. Two users found that after they uninstall 64-bit Office and install 32-bit Office, @RISK works normally. We don't know why.
   

    If you don't actually need 64-bit Office, and everything else has failed, you might wish to try this option also. Most people need only 32-bit Office; Should I Install 64-bit Excel? can help you decide whether you are one of them.

   We can't guarantee that this "nuclear option" will work for you, but we're not aware of anyone who has tried the other suggestions without success, then switched to 32-bit Office, and not had it solve the problem. If you decide to go this route, then before you uninstall 64-bit Office make sure you have your product key and that it will cover 32-bit Office also. (Most product keys cover both, but we can't help with issues installing or licensing Microsoft software, so check this yourself.)

Last edited: 2019-11-05