Resolving problems when running commands

Use the advice that is given here to help you to resolve common problems that can arise when you run commands.

About this task

Scenario: You are running commands and a pop-up window is seen that states mqsisetsecurity.exe has stopped working. Clicking the details in the pop-up window shows that the MSVCP120.dll file is missing.
Solution: Download and install the Microsoft Visual C++ 2010 Redistributable Package.

Scenario: An error message is generated when you back up or restore an integration node:
- The following message is returned when you run the mqsibackupbroker command:
```
BIP1253E Failed to backup the integration node 'integrationNodeName' (error 'error_code')
```
- The following message is returned when you run the mqsirestorebroker command:
```
BIP1262E Could not delete the existing configuration of integration node 'integrationNodeName'.
```
Explanation: Both backup and restore commands require read/write access to the files that contain integration node configuration data. Access has failed and the command cannot complete its operation successfully.
Solution: Typically, you might see one of these errors if you are running the backup or restore command against an active integration node, and a conflict of access has occurred.
If your integration node is active, use the mqsistop command to stop the integration node, and try the operation again.
You might also see one of these errors if the directory to which the command is writing, or from which it is reading, is temporarily inaccessible because of communications or authorization problems. Check that your user ID has access to the directory that you specified in the command.

Scenario: A ReportEvent () message is generated whenever you attempt to run any mqsi* command,
The ReportEvent () message is followed by the result of the command itself.
Explanation: The Windows Application Log has become full.
Solution: Clear the Windows Application Log from the Event Viewer.

Scenario: You want to run an mqsi* command on AIX® with Stack Execution Disable enabled, but the command times out even if the -w option is set to 360.
Explanation: mqsi* commands attempt to create a JVM with Java™ Native Interface (JNI) calls. Because of Stack Execution Disable, the JVM creation fails.
For more information about Stack Execution Disable, see IBM® SDK, Java Technology Edition, product documentation online.
Solution: Use the sedmgr command to create exemption records from Stack Execution Disable.
For example, for mqsilist:
```
sedmgr c exempt install_dir/server/bin/mqsilist
```
The following commands might be affected by this issue:
- biphttplistener
- bipbroker
- bipservice
- mqsideploy
- mqsilist
- mqsimode
- mqsireloadsecurity
- mqsireportresourcestats
- mqsiwebuseradmin

Scenario: A BIP1939 message is generated whenever you attempt to run an mqsi* command where a URL and password were specified on the -i parameter to connect to a remote host name. The user name and password are correct, and the password contains non-alphanumeric characters.
Explanation: The entered password contains URI Reserved characters. You cannot use URI Reserved characters within the URL.
Solution: Convert URI Reserved characters to their equivalent percent-encoded format, and run the command again.
For example, @ becomes %40.

Scenario: A BIP2212 message is generated whenever you attempt to run an mqsichangeproperties or mqsireportproperties command for a valid resource manager.
Explanation: The specified resource manager requires WebSphere® MQ, but it is not available.
There are a number of features in IBM Integration Bus that require a WebSphere MQ installation, and for a queue manager to be associated with the integration node. For more information, see Enhanced flexibility in interactions with WebSphere MQ.
Solution: If you have not already done so, install WebSphere MQ, and specify a queue manager to associate with the integration node.
You can associate a queue manager with an existing integration node by running mqsichangebroker.