1489180 - Instances\ServerName.RAS registry key remains after deleting RAS in the CCM

• Deleting a Report Application Server using the Central Configuration Manager
• The corresponding server entry in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Report Application Server\Instances remains.

• Crystal Reports Server Embedded 2008

0. Open the Central Configuration Manager by going to Start -> Programs -> BusinessObjects Enterprise XI 3.1 -> Central Configuration Manager.
0. Click the Add Report Application Server button.
0. Add the new RAS.
0. Start the RAS.
0. Open the registry editor by going to Start -> Run. Type regedit. Click OK.
0. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Report Application Server\Instances
0. Note the additional server listed under Instances.
0. Go back to the Central Configuration Manager.
0. Stop the recently added RAS, then delete it.
0. Go back to the registry and refresh it.
0. Note the server key entry remains.

• The registry key is created by the crystalras.exe process when it starts for the first time.
• The CCM doesn't delete the registry keys.
• The entries there won't interfere with the other RAS services.
• Be careful when adding new RAS' to the system. There is a chance the new RAS will use the pervious RAS settings.
  • This is only an issue if the default settings have been modified.
• The orphaned RAS instance entry can be safely deleted if it is no longer required.

KBA , BI-DEV , Business Intelligence Software Development Kits (SDKs) , Problem