Bug ID 476528: Sandbox file cannot be linked to access profile on non-common partitions

Last Modified: Mar 12, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
12.0.0

Opened: Aug 22, 2014
Severity: 3-Major

Symptoms

The GUI keeps waiting if an attempt is made to link a sandbox file to access profile in any non-Common partition.

Impact

GUI keeps spinning. An error message is seen on the webui logs: ERROR common.AjaxUtils:handleSQLException - java.sql.SQLException: General error: 01070734:3: Configuration error: Invalid mcpd context, folder not found (/null) in statement [SELECT ref_count,profile_name,sandbox_name,partition_id,object_id FROM sandbox_profile_access]

Conditions

Linking sandbox file to profile access in a non-Common partition.

Workaround

Can add sandbox files to access profile in non-Common partitions from TMSH

Fix Information

Sandbox files can be linked to access profiles on non-Common partitions

Behavior Change