I don't see the FS Pro 2013 menu

Background

FS Pro 2013 is a Word add-in. When Word or FS Pro crashes, Word may disable the active add-ins (or ask if you want to disable them) and remove the FS Pro 2013 tab from the Word Ribbon.

Please do not uninstall/reinstall FS Pro for this issue, doing so may invalidate your existing license key (causing the "license file was tampered with" error) and may require you to get a new license key and to re-activate FS Pro with the new key.

Use these solutions one at a time. Exit and re-start Word after each one until the menu tab is back. When it is back, you do not need to use any further solutions.

Solution 1: Enable the FS Pro 2013 add-in in Word

When you don't see the FS Pro 2013 tab in Word, try this solution first:

Step

Action

1

In Word, select File and then Options.

2

From the Options screen click Add-Ins in the left menu.

3

If FS Pro 2013 (and/or FS Pro 2013 Assistant) is in the list of Disabled Application Add-ins (near the bottom), then

  • Select Disabled Items from the Manage dropdown list and click Go...
  • Highlight the "...Information Mapping..." entry in the Disabled Items dialog, and
  • Click Enable, then click Close.

4

No matter where FS Pro 2013 is in the list, now do this:

  • Select COM Add-ins from the Manage dropdown list and click Go...

5

If FS Pro 2013 (and/or FS Pro 2013 Assistant) is present in the COM Add-ins dialog, select it (by "checking" the checkbox) and click OK.

 

Result: The FS Pro 2013 menu should be in the Word ribbon.

Solution 2: Register FS Pro again

The FS Pro 2013 tab may not be visible because it may need to be re-registered as follows:

Step

Action

1

Exit Word / FS Pro.

2

Navigate to C:\Program Files (x86)\Information Mapping\FS Pro 5.0

3

Double-click the file Register FS Pro Addin.bat to execute it. 

 

Result: A Command Prompt window will appear.

4

Press any key to close the Command Prompt window. 

5

Restart FS Pro.

Solution 3: Re-enable the add-in in the Registry

If the previous solutions have not worked, you may need to re-enable the FS Pro add-in in the Registry, as follows:

Step

Action

1

Exit Word / FS Pro.

2

Click the Windows Start button, type regedit.exe in the search field, and click Enter.

Result: the Registry Editor appears.

3

Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\Word\Addins\ InformationMapping.FSPro.Word\

4

Double-click LoadBehavior.

5

Change the value in the Value Data field to 3.

6

Click OK and close the Registry Editor.

7

Restart FS Pro.

Result: The FS Pro 2013 menu should be in the Word ribbon.

Solution 4: Delete the Word Options folder in the Registry

If the previous solutions have not worked, Word may have blacklisted the add-in due to an unhandled exception. In this case, you should delete the Word Options folder in the Registry Editor.

Warning: This will clear your Word options, including your Most Recently Used files list (it only clears the list, it does not remove the files).

Step

Action

1

Exit Word / FS Pro.

2

Click the Windows Start button, type regedit.exe in the search field, and click Enter.

Result: the Registry Editor appears.

3

Navigate to

  • HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word (for Word 2007), or
  • HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word (for Word 2010), or
  • HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Word (for Word 2013), or
  • HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word (for Word 2016)

4

Right-click the Word folder and select Delete.

Result: a confirmation message appears: "Are you sure you want to permanently delete this key and all of its subkeys?"

5

Click Yes.

6

Close the Registry Editor.

7

Because Word may have changed the LoadBehavior value again in the Registry, follow the procedure in Solution 3 above to re-enable the add-in.

 

Have more questions? Submit a request

Comments

  • Avatar
    Shubha Srivastav

    Very crisp and concise solutions (I used the third solution). I am happy as it saved me a lot of time that I would have otherwise spent interacting with the support team to get this issue sorted out.
    Thank you.

Powered by Zendesk