BFGWI0001 - BFGWI9999

BFGWI0001E: URI is incomplete (<insert_0>): incorrect resource type.
Severity: 20 : Error
Explanation: The resource type for the request has not been correctly specified in the URI.
Response: Specify a valid URI and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0002E: URI is incomplete: missing destination agent name.
Severity: 20 : Error
Explanation: The transfer cannot be started because the destination agent name parameter is missing, or specifies a blank agent name.
Response: Specify a valid destination agent name and resubmit the request. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0003E: URI is incomplete: missing destination directory/filename.
Severity: 20 : Error
Explanation: The transfer cannot be started because no destination file or directory name has been specified.
Response: Specify a correct destination file or directory name and resubmit the transfer.

BFGWI0004E: URI is incomplete: missing resource ID or query string.
Severity: 20 : Error
Explanation: The specified URI does not contain all the required resource identifiers.
Response: Update the URI to specify all the required resources for the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0005E: URI is incomplete: missing destination agent queue manager.
Severity: 20 : Error
Explanation: The transfer cannot be started because the destination agent queue manager parameter is missing, or specifies a blank agent queue manager.
Response: Specify a valid destination agent and destination queue mananger and resubmit the request. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0006E: File transfer request is incomplete: no files specified.
Severity: 20 : Error
Explanation: No files were specified for the file transfer request.
Response: Specify at least one filename and its contents for the transfer request. Then resubmit the request.

BFGWI0007E: File transfer request is incomplete: one or more filenames is missing.
Severity: 20 : Error
Explanation: Each file specified in the transfer request must have a filename specified as part of its Content-Disposition. One or more of the files requested for transfer is missing a filename specification or the specified filename is blank.
Response: Specify a non-blank filename for each file in the transfer request. If necessary consult the IBM MQ Managed File Transfer documentation. Then resubmit the request.

BFGWI0008E: Request body could not be parsed.
Severity: 20 : Error
Explanation: The body of the HTTP request could not be parsed for some reason.
Response: Correct the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0009E: The <insert_0> header or query parameter is invalid for resource <insert_1>
Severity: 20 : Error
Explanation: The resource was specified with an unsupported header or query parameter.
Response: Correct the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0010E: The <insert_0> header or query parameter is invalid for HTTP method <insert_1>.
Severity: 20 : Error
Explanation: The HTTP method was specified with an invalid header or query parameter.
Response: Correct the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0011E: The <insert_0> header or query parameter value of <insert_1> is invalid.
Severity: 20 : Error
Explanation: The header or query parameter was specified with an invalid value.
Response: Correct the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0012E: The <insert_0> header or query parameter value of <insert_1> is too long.
Severity: 20 : Error
Explanation: The header or query parameter was specified with an invalid value that is too long.
Response: Correct the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0013E: The <insert_0> header or query parameter has been specified multiple times.
Severity: 20 : Error
Explanation: The header or query parameter was specified in the request multiple times, but the protocol requires the header to be specified only once.
Response: Correct the request and resubmit.

BFGWI0014E: User not authorized to perform the request.
Severity: 20 : Error
Explanation: The request for a resource was made by an unauthorized user.
Response: If authorization is required contact the web application server administrator to grant access.

BFGWI0015E: The requested resource could not be found.
Severity: 20 : Error
Explanation: The requested resource, such as a transfer via its identifier, could not be found.
Response: Update the request to specify a valid resource and retry.

BFGWI0016E: A <insert_0> HTTP method is not allowed for the <insert_1> resource request.
Severity: 20 : Error
Explanation: A recognized resource request has been made, but it does not support the specified method.
Response: Update the request to specify a different resource or specify a HTTP method that is supported for the request.

BFGWI0017E: A request has been received with a media type which cannot be handled by IBM MQ Managed File Transfer.
Severity: 20 : Error
Explanation: The request specified a media type not supported by IBM MQ Managed File Transfer. The only supported media types are: multipart/form-data, multipart/mixed and application/xml.
Response: Update the request to specify a supported media type and retry.

BFGWI0018E: The request could not be completed due to an internal web application server error.
Severity: 20 : Error
Explanation: Whilst handling the request the web application server has encountered a problem.
Response: Contact the web application server administrator to investigate the problem.

BFGWI0019E: The request could not be completed for reasons due to a problem with the web application server.
Severity: 20 : Error
Explanation: The request could not be completed for reasons that are beyond the control of the HTTP client of the IBM MQ Managed File Transfer web application. For example there is an internal configuration issue with the web application server.
Response: Contact the web application server administrator to investigate the problem.

BFGWI0020E: The destination is temporarily unavailable.
Severity: 20 : Error
Explanation: The request cannot be processed because the web application server was unable to communicate with a required system. For example there is an internal MQ or database connectivity problem
Response: Either retry the request again or contact the web application server administrator to investigate the problem.

BFGWI0021E: An attempt to complete some part of the request has timed out, either because of time limits imposed by IBM MQ Managed File Transfer or time limits imposed by the HTTP client.
Severity: 20 : Error
Explanation: The request was accepted by system but part of the processing has taken longer than imposed time limits.
Response: Either retry the request again or contact the web application server administrator to investigate the problem.

BFGWI0022E: The supplied transfer ID did not have a length of 48 characters. This is not a valid transfer ID.
Severity: 20 : Error
Explanation: The transfer ID is an incorrect length.
Response: Check that you specified the correct transfer ID and resubmit the request.

BFGWI0023E: The supplied transfer ID contains characters that are not hexadecimal.
Severity: 20 : Error
Explanation: The transfer ID is specified incorrectly.
Response: Check that you specified the correct transfer ID and resubmit the request.

BFGWI0024E: The transfer ID in the request is null.
Severity: 20 : Error
Explanation: The transfer ID has not been supplied in the request.
Response: Check that you specified the transfer ID and resubmit the request.

BFGWI0025E: There is no transfer information for the specified transfer ID.
Severity: 20 : Error
Explanation: The transfer ID specified in the request cannot be found in the database.
Response: Check that you specified the correct transfer ID and resubmit the request.

BFGWI0026E: The request contains a file that is too large to be handled by the server.
Severity: 20 : Error
Explanation: The server was unable to process the request because the file being passed to it is too large.
Response: Specify a smaller file and resubmit the request.

BFGWI0027E: URI is incomplete (<insert_0>): missing destination type.
Severity: 20 : Error
Explanation: The transfer cannot be started because the destination type is missing or invalid.
Response: Specify a valid destination type and resubmit the request. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0028E: A queue manager name was expected in the URI, but was not provided.
Severity: 20 : Error
Explanation: The request cannot be processed because the agent's queue manager name was not provided. If the @ symbol is specified in the URI, this must be followed by a queue manager name.
Response: Specify the agent queue manager name after the @ symbol and resubmit the request. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0029E: URI is incomplete: missing file space name.
Severity: 20 : Error
Explanation: The request cannot be processed because no file space name has been specified, or the specified file space name is blank.
Response: Specify a file space name and resubmit the request.

BFGWI0030E: URI is incomplete: missing file path for download of a file from a file space.
Severity: 20 : Error
Explanation: The request cannot be processed because no file path has been specified, or the specified file path is blank.
Response: Specify a file path of a known file within the specified file space and resubmit the request.

BFGWI0031E: The requested resource is no longer available.
Severity: 20 : Error
Explanation: The requested resource, such as a file on disk, referred to in a file transfer, could not be found. This might be due to the resource having been deleted.
Response: If the resource is still available, contact the web application server administrator to investigate the problem.

BFGWI0032E: The parameter ''<insert_0>'' is not valid.
Severity: 20 : Error
Explanation: The parameter supplied by the user in the request is not valid. See the IBM MQ Managed File Transfer product documentation for valid parameters.
Response: Remove the invalid parameters and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0033E: Invalid value ''<insert_0>'' supplied for Start parameter.
Severity: 20 : Error
Explanation: The value supplied by the user for the Start parameter in the request is not valid. See the IBM MQ Managed File Transfer product documentation for valid values.
Response: Edit the URI Start parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0034E: Invalid value ''<insert_0>'' supplied for Count parameter.
Severity: 20 : Error
Explanation: The value supplied by the user for the Count parameter in the request is not valid. See the IBM MQ Managed File Transfer product documentation for valid values.
Response: Edit the URI Count parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0035E: Invalid value ''<insert_0>'' supplied for Sort parameter.
Severity: 20 : Error
Explanation: The value supplied by the user for the Sort parameter in the request is not valid. See the IBM MQ Managed File Transfer product documentation for valid values.
Response: Edit the URI Sort parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0036E: Invalid value ''<insert_0>'' supplied for SortBy parameter.
Severity: 20 : Error
Explanation: The value supplied by the user for the SortBy parameter in the request is not valid. See the IBM MQ Managed File Transfer product documentation for valid values.
Response: Edit the URI SortBy parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0037E: The URI specified contained a parameter multiple times.
Severity: 20 : Error
Explanation: The URI specified contained a parameter multiple times. URI parameters can only be specified once.
Response: Remove the superfluous parameter from the URI and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0038E: The dates specified do not define a valid range.
Severity: 20 : Error
Explanation: The dates specified do not define a valid range. Valid combinations are as follows: EndAfter must be a date before EndBefore, and StartAfter must be a date before StartBefore.
Response: Edit the URI date parameters and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0039E: The given value ''<insert_0>'' is not valid for the Accept parameter.
Severity: 20 : Error
Explanation: Either 'xml' or 'json' is expected for the Accept parameter.
Response: Edit the URI accept parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0040E: You cannot specify the parameter agent, and in the same URI specify a srcagent or destagent parameter.
Severity: 20 : Error
Explanation: The parameter agent cannot be specified with srcagent or destagent parameters in the URI.
Response: Edit the URI to remove the invalid parameters and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0041E: The given value ''<insert_0>'' is not a valid status value.
Severity: 20 : Error
Explanation: The given value is not a valid status value. Valid values are 'Complete', 'Started', 'Submitted' and 'Cancelled'.
Response: Edit the URI status parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0042E: The given status value has not been specified correctly.
Severity: 20 : Error
Explanation: The given status value has not been specified correctly.
Response: Edit the URI status parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0043E: The given agent name is not valid.
Severity: 20 : Error
Explanation: An agent name must not be longer then 28 characters, or contains characters that are not allowed.
Response: Edit the URI agent, srcagent or destagent parameter and resubmit the request. See the IBM MQ Managed File Transfer documentation for valid values.

BFGWI0044E: You cannot specify query parameters if you specify a transfer ID.
Severity: 20 : Error
Explanation: A transfer ID must be specified without query parameters.
Response: Edit the URI to remove the query parameters and resubmit the request. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0045E: File space ''<insert_0>'' is not accessible to user ''<insert_1>'' or could not be found.
Severity: 20 : Error
Explanation: The requested file space is either not accessible to the current user or does not exist.
Response: Specify an available file space that does exist and is accessible. If the file space needs to be created or made accessible then contact the web application server administrator to create the file space or grant access.

BFGWI0046E: URI contains unexpected additional data: <insert_0>
Severity: 20 : Error
Explanation: The request cannot be processed because it contains additional data that was not expected.
Response: Remove the additional data and resubmit the request.

BFGWI0047E: File space ''<insert_0>'' already exists.
Severity: 20 : Error
Explanation: The requested file space cannot be created because it already exists.
Response: Specify a different file space name and submit the request again.

BFGWI0048E: The HTTP entity body of the request, with a content type of ''<insert_0>'', could not be parsed due to: ''<insert_1>''.
Severity: 20 : Error
Explanation: The HTTP entity body contained data that could not be parsed.
Response: Check the content of the entity body that you sent in the request, correct any errors and resubmit the request. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0049E: A JMS queue connection factory called ''<insert_0>'' has not been defined.
Severity: 20 : Error
Explanation: A JMS queue connection factory is required to connect to the queue manager of the MQMFT web agent.
Response: Check a JMS queue connection factory called ''{0}'' has been defined in your application server, and that is has been defined in the correct scope for the MQMFT Web Gateway application. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0050I: No Web Gateway connection factory defined.
Severity: 0 : Information
Explanation: A JMS queue connection factory has not been defined. Some operations of the Web Gateway may be restricted.
Response: If file transfer operations of the Web Gateway are required you must define a JMS queue connection factory called ''{0}'' on your application server. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0051E: Transfer log information disabled, as no coordination queue manager has been defined.
Severity: 20 : Error
Explanation: The coordinationQMgr property for the MQMFT Web Gateway has not been defined. Transfer log messages will not be produced by the MQMFT Web Gateway.
Response: Define the coordinationQMgr property for the MQMFT Web Gateway, if transfer log messages are required. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0052E: The request is missing the required body content.
Severity: 20 : Error
Explanation: The body of the HTTP request was not specified and is required.
Response: Provide content in the body of your HTTP request and resubmit the request. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0053I: FTELOG: <insert_0> - <insert_1>. Requested by <insert_2> at <insert_3>. Information: <insert_4>
Severity: 0 : Information
Explanation: File space administration information log message.
Response: None.

BFGWI0054E: Bad file space definition. The 'action' attribute has not been specified.
Severity: 20 : Error
Explanation: When modifying an existing file space definition, the 'action' attribute must be specified on all 'authorized' and 'unauthorized' elements.
Response: Check the content of the entity body that you sent in the request, and ensure that the 'action' attribute has been specified with a valid value on all 'authorized' and 'unauthorized' elements. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0055I: FTELOG: <insert_0>. Requested by <insert_1> at <insert_2>. Information: <insert_3>
Severity: 0 : Information
Explanation: User administration information log message.
Response: None.

BFGWI0056E: User <insert_0> is not permitted to access the system due to an MQMD user identifier not being available.
Severity: 20 : Error
Explanation: All requests that require access to the MQMFT agent for the MQMFT Web Gateway require an MQMD user identifier to be defined. The Web Gateway maps the requesting user identifier to an MQMD user identifier by first attempting to look up a value set by the Web Gateway's system administrator. If no value is defined for the user then the Web Gateway's default value is used. If a default is not defined for the Web Gateway then this error will be reported.
Response: Contact your MQMFT Web Gateway system administrator to request an MQMD user identifier to be defined for your user identifier.

BFGWI0057E: File upload temporary directory invalid.
Severity: 20 : Error
Explanation: File upload temporary directory {0} cannot be used by the MQMFT Web Gateway.
Response: Check that the file upload temporary directory exists and the application server has authority to read and write to the directory. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0058I: File upload temporary directory has not been cleaned.
Severity: 0 : Information
Explanation: The file upload temporary directory used by the MQMFT Web Gateway to store temporary files during file upload has not been cleaned because it cannot be found.
Response: None.

BFGWI0059E: Maximum upload user quota ''<insert_0>'' is invalid.
Severity: 20 : Error
Explanation: The value set for the MQMFT Web Gateway configuration parameter 'maxTempFileUploadSpace' is invalid.
Response: Check the value set for the MQMFT Web Gateway configuration parameter 'maxTempFileUploadSpace'. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0060E: The file space ''<insert_0>'' is currently in use, and cannot be deleted.
Severity: 20 : Error
Explanation: A transfer is currently in progress for the file space and therefore cannot be deleted.
Response: Ensure that no transfers are currently using the file space and resubmit the request.

BFGWI0061E: You must specify exactly one 'filespace' element in a POST request.
Severity: 20 : Error
Explanation: A request containing more than one 'filespace' element in the body has been received and cannot be processed.
Response: Edit the body of the request to contain a single 'filespace' element and resubmit your request. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0062E: The Web Gateway name property 'webGatewayName' has not been defined for the Web Gateway Application.
Severity: 20 : Error
Explanation: The 'webGatewayName' property was not assigned a value when the Web Gateway Application was deployed. This property must be supplied for the Web Gateway to operate correctly.
Response: Update or re-deploy the Web Gateway Application and specify a value for the 'webGatewayName' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0063E: Invalid value for the ''webGatewayName'' property: <insert_0>
Severity: 20 : Error
Explanation: The specified value for the 'webGatewayName' property of the Web Gateway application is not valid. Valid values for this property name must be between 1 and 28 characters in length and be alphanumeric or use the period (.) or underscore (_) characters. The Web Gateway application will not operate correctly unless a valid value is specified for this property.
Response: Update or redeploy the Web Gateway application and specify a valid value for the 'webGatewayName' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0064E: The ''<insert_0>'' header is not valid in this context.
Severity: 20 : Error
Explanation: The specified header is only valid in a request if the 'type' value of the 'x-fte-postdest' header is set to 'executable'.
Response: Remove the specified header from the request or set the 'type' value in the 'x-fte-postdest' header to 'executable'. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0065E: The value of the 'x-fte-postdest' header is invalid.
Severity: 20 : Error
Explanation: The 'command' attribute has not been set on the 'x-fte-postdest' header.
Response: Set the 'command' attribute on the 'x-fte-postdest' header. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0066E: The ''<insert_0>'' header is not valid in this context.
Severity: 20 : Error
Explanation: The specified header is only valid in a request if the 'x-fte-postdest' header has also been set.
Response: Remove the specified header from the request or set the 'x-fte-postdest' header. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0067E: The ''<insert_0>'' header is not valid in this context.
Severity: 20 : Error
Explanation: The specified header is only valid in a request if the 'type' value of the 'x-fte-postdest' header is set to 'antscript'.
Response: Remove the specified header from the request or set the 'type' value in the 'x-fte-postdest' header to 'antscript'. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0068E: The Web Gateway coordination queue manager property 'coordinationQMgr' has not been defined for the Web Gateway application.
Severity: 20 : Error
Explanation: The 'coordinationQMgr' property was not assigned a value when the Web Gateway application was deployed. This property must be supplied for the Web Gateway to operate correctly.
Response: Update or redeploy the Web Gateway Application and specify a value for the 'coordinationQMgr' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0069E: Invalid value for the ''coordinationQMgr'' property: <insert_0>
Severity: 20 : Error
Explanation: The specified value for the 'coordinationQMgr' property of the Web Gateway application is not valid. Valid values for this property name are between 1 and 48 characters in length and contain alphanumeric characters or the period (.), underscore (_), percent (%) or forward slash (/) characters. The Web Gateway application will not operate correctly unless a valid value is specified for this property.
Response: Update or redeploy the Web Gateway application and specify a valid value for the 'coordinationQMgr' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0070E: The Web Gateway agent name property 'agentName' has not been defined for the Web Gateway application.
Severity: 20 : Error
Explanation: The 'agentName' property was not assigned a value when the Web Gateway application was deployed. This property must be supplied for the Web Gateway to operate correctly.
Response: Update or redeploy the Web Gateway application and specify a value for the 'agentName' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0071E: Invalid value for the ''agentName'' property: <insert_0>
Severity: 20 : Error
Explanation: The specified value for the 'agentName' property of the Web Gateway application is not valid. Valid values for this property name are between 1 and 28 characters in length and contain alphanumeric characters or the period (.), underscore (_) or percent (%) characters. The Web Gateway application will not operate correctly unless a valid value is specified for this property.
Response: Update or redeploy the Web Gateway application and specify a valid value for the 'agentName' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0072E: Multiple values found for form field: <insert_0>
Severity: 20 : Error
Explanation: The specified form field has multiple values defined in the request. Only the 'metadata' form field can be defined more than once in a request.
Response: Modify the HTML form used to submit the request so that only the field name given in the error message is defined only once.

BFGWI0073E: The ''<insert_0>'' form field is not valid in this context.
Severity: 20 : Error
Explanation: The specified form field is only valid in a request if the 'type' value of the 'postdest' form field is set to 'executable'.
Response: Remove the specified form field from the request or set the 'type' value in the 'postdest' form field to 'executable'. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0074E: The value of the 'postdest' form field is invalid.
Severity: 20 : Error
Explanation: The 'command' attribute has not been set on the 'postdest' form field.
Response: Set the 'command' attribute on the 'postdest' form field. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0075E: The ''<insert_0>'' form field is not valid in this context.
Severity: 20 : Error
Explanation: The specified form field is only valid in a request if the 'postdest' form field has also been set.
Response: Remove the specified form field from the request or set the 'postdest' form field. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0076E: The ''<insert_0>'' form field is not valid in this context.
Severity: 20 : Error
Explanation: The specified form field is only valid in a request if the 'type' value of the 'postdest' form field is set to 'antscript'.
Response: Remove the specified form field from the request or set the 'type' value in the 'postdest' form field to 'antscript'. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0077E: The <insert_0> form field value of <insert_1> is invalid.
Severity: 20 : Error
Explanation: The form field was specified with an invalid value.
Response: Correct the request and resubmit. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0078E: The directory path <insert_0> does not exist.
Severity: 20 : Error
Explanation: The specified directory path for storage of files does not exist.
Response: Create the directory and ensure the Web Gateway application has permission to create and remove files, then repeat this test.

BFGWI0079E: The Web Gateway application does not have read permission for directory path <insert_0>.
Severity: 20 : Error
Explanation: The Web Gateway application is not able to read the contents of the named directory. The application needs to be able to read this directory to perform transfer operations.
Response: Review the permissions on the directory and ensure that the Web Gateway application has read access before retesting.

BFGWI0080E: The Web Gateway application does not have write permission for directory path <insert_0>.
Severity: 20 : Error
Explanation: The Web Gateway application is not able to write to the named directory. The application needs to be able to write files in this directory to perform transfer operations.
Response: Review the permissions on the directory and ensure that the Web Gateway application has write access before retesting.

BFGWI0081E: The Web Gateway application is unable to create a unique file in directory <insert_0>.
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it attempts to find a file name which does not already exist. The application was unable to find a suitable file name.
Response: Investigate why there appear to be no available file names before retesting.

BFGWI0082E: The Web Gateway application was not able to create the sample test file <insert_0> because of the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it attempts to create a new file with a unique name. The application could not create the file for the given reason.
Response: Review the given reason and make any necessary changes before retesting.

BFGWI0083E: The Web Gateway application was not able to write to the sample test file <insert_0> because of the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it attempts to write to a sample test file. The application could not write to the file for the given reason.
Response: Review the given reason and make any necessary changes before retesting.

BFGWI0084E: The Web Gateway application was not able to complete writing to a sample test file <insert_0> because of the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it attempts to write to a sample test file. The application was not able to complete writing to the file for the given reason.
Response: Review the given reason and resolve the problem as necessary before retesting.

BFGWI0085E: The Web Gateway application could not read the sample file <insert_0> that it previously created. The sample file has a size of <insert_2>, which does not match the expected file size of <insert_1>.
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it creates a sample file of a known size and then attempts to read the file again. The application could not complete this test because the written file has a different size to the file that was read.
Response: Investigate why the file system is changing the size of the sample test file, and retest.

BFGWI0086E: The Web Gateway application could not read the sample file that it previously created, because the contents of the file have changed.
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it creates a sample file with known contents. The application could not complete this test because the contents of the written file do not match the expected contents.
Response: Investigate why the file system is changing the contents of the sample test file, and retest.

BFGWI0087E: The Web Gateway application could not read the sample file <insert_0> that it previously created because of the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it creates a sample file and then attempts to read the file again. The application could not complete this test because the created file no longer exists.
Response: Investigate why the file system is reporting the test file as missing, and retest.

BFGWI0088E: The Web Gateway application could not read the contents of the sample file <insert_0> due to the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test it creates a sample file and then attempts to read the file again. The application could not complete this test because it did not have permission to read the file contents.
Response: Investigate why the file system is not allowing the application to read the sample test file.

BFGWI0089E: The Web Gateway application could not complete reading the contents of the sample file <insert_0> due to the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it creates a sample file and then attempts to read the file again. The application could not complete this test because it could not complete reading the contents.
Response: Investigate why the file system is not allowing the application to complete reading the sample test file.

BFGWI0090E: The Web Gateway application could not delete the created sample file <insert_0> due to the following exception: <insert_1>
Severity: 20 : Error
Explanation: When the Web Gateway application performs an installation verification test, it creates a sample file and, on completion of the test, attempts to delete this file. The application could not complete the test because it was unable to delete the test file.
Response: Investigate why the file system is not allowing the application to delete the sample test file.

BFGWI0091E: Internal error. There was a request to perform an invalid test on testlet <insert_0>.
Severity: 20 : Error
Explanation: The Web Gateway application has an internal configuration error. The installation verification test is attempting to perform an unknown test.
Response: Investigate whether any of the configuration files are corrupted before retesting.

BFGWI0092E: The Web Gateway application could not complete the database check due to the following exception: <insert_0>. The problem occurred while attempting to access the Web Gateway file space database and requires investigation.
Severity: 20 : Error
Explanation: The Web Gateway application has successfully completed a number of database checks, but could not successfully access the Web Gateway file space database.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0093E: The Web Gateway application could not complete the database check due to the following exception: <insert_0>. The problem occurred while attempting to access the Web Gateway file space database and requires investigation.
Severity: 20 : Error
Explanation: The Web Gateway application has successfully completed a number of database checks, but could not successfully access the Web Gateway file space database.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0094E: The Web Gateway application could not start the database check because accessing the context of <insert_0> generated the following exception: <insert_1>.
Severity: 20 : Error
Explanation: The Web Gateway application could not start the database checks due to a problem in accessing the context.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0095E: The Web Gateway application detected a missing table <insert_1> or incorrect schema <insert_3> in context <insert_0>. The following exception was produced while attempting to access the database: <insert_2>
Severity: 20 : Error
Explanation: The Web Gateway application detected a problem while attempting to check that a database schema and table both exist.
Response: If the schema value is incorrect, then use the information about the Web Gateway installation verification application in the IBM MQ Managed File Transfer documentation to define the correct schema value. Otherwise investigate the reasons for this failure and consult the IBM MQ Managed File Transfer documentation for further assistance.

BFGWI0096E: The Web Gateway application detected a missing table <insert_0> in context <insert_1>. The following exception was produced while attempting to access the database: <insert_2>
Severity: 20 : Error
Explanation: The Web Gateway application detected a problem while attempting to check that a database table exists.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0097E: The Web Gateway application could not complete the database check due to the following exception: <insert_0>. The problem occurred while attempting to access the Web Gateway file space database and requires investigation.
Severity: 20 : Error
Explanation: The Web Gateway application has successfully completed a number of database checks, but could not successfully access the Web Gateway file space database.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0098E: The Web Gateway application could not complete the database check due to the following exception: <insert_0>. The problem occurred while trying to access the database and requires investigation.
Severity: 20 : Error
Explanation: The Web Gateway application has successfully completed a number of database checks, but could not complete a logger JPA access check.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0099E: Not authorized to perform this test.
Severity: 20 : Error
Explanation: The Web Gateway application has received a request to perform a installation verification. However the user does not have the necessary authority to perform this test.
Response: Check the permissions associated with the user ID. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0100E: The Web Gateway application has been asked to perform an unknown test named <insert_0>.
Severity: 20 : Error
Explanation: The Web Gateway application has receive a request to perform a installation verification. However the provided test name is unknown and so the test cannot be performed.
Response: Check any changes to configuration. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0101E: No user identifier present to determine the required file space name.
Severity: 20 : Error
Explanation: When a request for a file space is made, if the name is not specified then it is derived from the user identifier making the request. If no user identifier was specified for the request, then the file space name cannot be determined. For an application server that has been secured correctly this error will not occur because all requests for file space access are checked to ensure they originate from an authorized user.
Response: Ensure the Web Gateway is secured so that anonymous requests cannot be made. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0102E: No user identifier present to determine the MQMD user identifier.
Severity: 20 : Error
Explanation: When a request is made the identifier of the user making the request is used to look up an MQMD user identifier. If no user identifier was specified for the request and there is no default MQMD user identifier defined for the Web Gateway then the request will fail. For an application server that has been secured correctly this error will not occur because all requests for file space access are checked to ensure they originate from an authorized user.
Response: Ensure the Web Gateway is secured so that anonymous requests cannot be made. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0103E: The user authority ''<insert_0>'' specified for the file space ''<insert_1>'' is invalid.
Severity: 20 : Error
Explanation: User names can be set as absolute user names or as regular expressions. The user value specified contains characters which are not valid.
Response: Ensure that the user names specified for the file space contain valid characters and resubmit the request.

BFGWI0104E: Value ''<insert_0>'' for the defaultMQMDUserID property is too long.
Severity: 20 : Error
Explanation: The specified value for the 'defaultMQMDUserID' property of the Web Gateway application is not valid. If this property is set its value must be between 1 and 12 characters in length.
Response: Update or redeploy the Web Gateway application and specify a valid value for the 'defaultMQMDUserID' property. See the IBM MQ Managed File Transfer documentation for more information.

BFGWI0105E: URI is not valid: the file space name ''<insert_0>'' contains unsupported characters.
Severity: 20 : Error
Explanation: The request cannot be processed because the file space name contains characters which are not permitted.
Response: Consult the IBM MQ Managed File Transfer documentation and resubmit the command, specifying a file space name that only contains supported characters.

BFGWI0106E: The remote HTTP client application disconnected before the download request could be completed.
Severity: 20 : Error
Explanation: A remote HTTP client started downloading a file, but disconnected before the file was received.
Response: Ask the remote user to retry their request again if the file is required.

BFGWI0107E: The Web Gateway application attempted to communicate with the database through the connection <insert_0>. The following exception was produced: <insert_1>
Severity: 20 : Error
Explanation: The Web Gateway application failed to communicate with the named database connection.
Response: Investigate the reasons for this failure. If necessary consult the IBM MQ Managed File Transfer documentation.

BFGWI0108E: The following exception was caught during servlet initialization : <insert_0>
Severity: 20 : Error
Explanation: A servlet exception was detected during initialization. The servlet will continue to start.
Response: Investigate the reasons for the exception and correct as necessary before restarting the servlet.

BFGWI0109E: The following IOException was caught handling an uploaded file <insert_0>: <insert_1>
Severity: 20 : Error
Explanation: An IOException was detected while handling an uploaded file. The file might not have been written to the file system correctly.
Response: Investigate the reasons for the exception and correct as necessary before submitting another file upload request. Check that the temporary file upload location for the Web Gateway has enough disk space, and that the correct file system permissions have been configured for the application server user.

BFGWI0110E: The following IOException was caught handling an uploaded file <insert_0>: <insert_1>
Severity: 20 : Error
Explanation: An IOException was detected while handling an uploaded file. The file might not have been written to the file system correctly.
Response: Investigate the reasons for the exception and correct as necessary before submitting another file upload request. Check that the temporary file upload location for the Web Gateway has enough disk space, and that the correct file system permissions have been configured for the application server user.

BFGWI0111E: The following IOException was caught handling an uploaded file <insert_0>: <insert_1>
Severity: 20 : Error
Explanation: An IOException was detected while handling an uploaded file. The file might not have been deleted from the file system correctly.
Response: Investigate the reasons for the exception and correct as necessary before submitting another file upload request. Check that the correct file system permissions have been configured for the application server user.

BFGWI0112E: The following IOException was caught handling an uploaded file <insert_0>: <insert_1>
Severity: 20 : Error
Explanation: An IOException was detected while handling an uploaded file. The file might not have been deleted from the file system correctly.
Response: Investigate the reasons for the exception and correct as necessary before submitting another file upload request. Check that the correct file system permissions have been configured for the application server user.

BFGWI0113E: CSRF protection is enabled on the Web Gateway and the request did not specify the 'x-fte-csrf-token' HTTP header or 'csrf-token' HTML form property.
Severity: 20 : Error
Explanation: When CSRF protection is enabled, the Web Gateway requires requests to provide the value of the JSESSIONID as an HTTP header or HTML form property.
Response: Add the 'x-fte-csrf-token' header to the HTTP request or add the 'csrf-token' to the HTML form. Resubmit the request.

BFGWI0114E: CSRF protection is enabled on the Web Gateway and the value of the 'x-fte-csrf-token' header or 'csrf-token' HTML form property does not match the expected value.
Severity: 20 : Error
Explanation: When CSRF protection is enabled, the Web Gateway requires requests to provide the value of the JSESSIONID as an HTTP header or HTML form property.
Response: Ensure that the value specified for the 'x-fte-csrf-token' header on the HTTP request, or the value of the 'csrf-token' specified in the HTML form request, matches the value of the JSESSIONID for this session. Resubmit the request.

BFGWI0115E: The <insert_0> (current) and <insert_1> (old or deprecated name) headers have both been specified.
Severity: 20 : Error
Explanation: The request contains headers for both the current name and the old or deprecated name for a header. You can specify only one.
Response: Correct the request and resubmit.

BFGWI0116E: The Web Gateway cannot process the transfer request because an insufficient level of security has been configured.
Severity: 20 : Error
Explanation: The Web Gateway requires that JEE application security is enabled on the Application Server where it is installed. The transfer cannot be started.
Response: Enable JEE application security on the Application Server and restart the Application Server.

BFGWI9999E: <insert_0>
Severity: 20 : Error
Explanation: If this message does not give enough information, check the accompanying error messages for further information.
Response: For further information on resolving this error, see the problem determination information on the product Web site.