Super Search (V13.0) Upgrade Troubleshooting

Note: This instructions apply specifically to issues after upgrading to  Version 13.0, and are not meant for previous versions.

Restarting Railo

In many of the instructions below, you may be asked to restart Railo. You can do this by:

  1. Click Start
  2. Type "railo"
  3. Find the application "Railo-Tomcat Service Control"
  4. Right click the application, and choose Run as Administrator.
  5. Click Stop and then Start to restart Railo.

Performance, Large File Uploads, and Request Timeouts

The upgrade installer will attempt to configure both Railo and IIS to allow for better performance, large file uploads, and long requests (such as active directory synchronization). However, if these settings already exist, the upgrade installer will not modify existing values. Please see Super Search (V13.0) Railo and IIS Settings to check if your Railo / IIS settings match our standards.

 

Blue Screen Prompting for Railo Password and Serial Number

trouble1.png

If after upgrading, you keep getting redirected to a screen that looks like this, it indicates that the intranet is having trouble connecting to the database. The solution is not to fill out the fields, but instead to fix the database connection.

  1. Edit the \Intranet\Admin\cfregdn.cfm file and note the data source name <cfset sSQLDSN = "SQLFunctions">.
    If this file does not exist, your data source name is "SQLFunctions".
  2. Open the Railo Web Administrator: http://<your_server name>/railo-context/admin/web.cfm
  3.  Unless changed, the default password is "connections"
  4. In the left menu, under Services, click on Datasource
  5. Look for the entry which matches your data source name and click the pencil icon to edit.
  6. Verify the database settings are correct.
  7. If the settings look correct, but verifying the data source fails, ensure your SQL Server is configured to allow this connection.
  8. SQL Server must have: SQL Server authentication enabled, TCP/IP enabled, server login "intranetconnections" mapped to database user "intranetconnections" with db_owner role membership.

 If you needed to change the data source settings, you will need to restart the intranet as these settings are cached.

500 - Internal server error on Grey / Blue Screen

trouble2.png

If after upgrading you get a screen which generally matches this formatting: grey background, box with blue title bars, this indicates that the ColdFusion Handler mappings were not removed prior to running the upgrade. Please see the "Remove ColdFusion Handler Mapping" section in the Upgrade Instructions to remove these mappings.

  1. Remove ColdFusion handler mappings.
  2. Stop all ColdFusion services not to start automatically.
  3. Restart IIS and Railo (or alternatively reboot the server).
  4. Once the intranet is up, restart the search indexing process (Admin, Setup tab, Site Search, and click "Re-index my site data")

Default Welcome to the Railo Word! Page Displayed

trouble3.png

If you have changed your site's physical path to point to the Intranet folder (to remove "/Intranet" from the URL), and you are now seeing the Default, Welcome to the Railo World when trying to browse your site by server name or localhost, you can fix this by editing the Railo server.xml file:

  1. Edit this file: C:\railo\tomcat\conf\server.xml

  2. Remove this entire section (near the bottom) and save. 
    <Host name="localhost" appBase="webapps">
    <Context path="" docBase="C:\inetpub\wwwroot\" />
    </Host>

  3. Restart IIS and Railo (or alternatively reboot the server).

  4. Once the intranet is up, restart the search indexing process (Admin, Setup tab, Site Search, and click "Re-index my site data")

HTTP Error 404.0 - Not Found

If you are attempting to access a .cfm page (view.cfm or site_login.cfm) and you get this error message, it can indicate that the handler mappings for .cfc or .cfm files are missing in IIS. If you are upgrading from a ColdFusion 8 or 9 site, you can fix this issue with the following steps:

  1. Open IIS Manager  (Internet Information Services Manager)
  2. Select the site which hosts the intranet (by default, "Default Web Site").
  3. Double click on  "Handler Mappings" icon.
  4. Verify that there are no handler mappings for .cfc or .cfm files.
  5. Proceed to the next step only if there are no handler mappings for .cfc or .cfm files.
  6. In the right menu, under Actions, click "Revert to Parent" and choose "Yes".
  7. After clicking "yes" BonCode handler mappings should appear in Handler Mappings.
  8. The intranet site should now work.

 

Generic Communication Error or HTTP Error 500.21 - Internal Server Error: Handler

HTTP Error 500.21 - Internal Server Error: Handler "Boncode-Tomcat-CFM-Handler" has a bad module "ManagedPipelineHandler" in its module list

See the Railo 4 IIS-Boncode Connectivity Issue article to resolve these errors.

 Railo 3.3.4.003 Error (expression)

This indicates that Railo 3.3 handler mappings were not removed successfully. To fix this issue, you must manually remove the Railo 3.3 handler mappings for the webiste using IIS.

  1. Start IIS, choose the intranet site, and click "Handler Mappings".
  2. Click "Handler" column name to sort by Handler.
  3. Remove all mappings related to Handler HeliconZoo_x64 and HeliconZoo_x86.

 Verify Railo Handler Mappings (CF to Railo)

This step can be entirely skipped for Railo environments.

Now that the upgrade installer has completed, you should now have 3 Boncode mappings within IIS. Please confirm this by opening up IIS (Intranet Information Server) and select your website from the list of sites > open Handler Mappings and look for the 3 BonCode connectors outlined below:

boncode.jpg

If these are missing, it is likely due to previous IIS configuration created by ColdFusion.  You can click "Revert to Parent/Inherited" to pull in the new handlers if necessary:

revert.jpg

 If the handler mappings still do not appear, you can re-run the BonCode Connector application to create the mappings.  Please run the program as administrator.  Use default settings, except for the screens below:boncode1.png

boncode2.png

There was an error logging in to Microsoft SQL Server

If the installation stalls at the database connection with the error as in the screenshot below, it may be because the SQL server is not configured to allow SQL Server Authentication logins.

1. In this case, in SQL Server Management Studio (SSMS), right-click the instance of the server you want to connect to and click Properties > Security.

2. Choose the server authentication mode "SQL Server and Windows Authentication mode". Click OK.

3. Test the login and password you intend to use in the upgrade process.

Referenced by:

Have more questions? Submit a request

0 Comments

Article is closed for comments.