IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States   FIXES ARE AVAILABLE
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]

SUBSCRIBE
You can track all active APARs for this component.

APAR STATUS
 * CLOSED AS PROGRAM ERROR.

ERROR DESCRIPTION
 *  A PFBC file might fail to apply. Wsadmin will show an error
   similar to this:

   java.lang.Exception: java.lang.Exception: ADMG0660E:
   Properties File Validation during command
   applyConfigProperties failed.  See Report file for details.

   The report file will contain an error similar to this:
   Error=java.lang.NullPointerException
    at
   com.ibm.websphere.management.configservice.ConfigServiceHelper.g
   etConfigDataType(ConfigServiceHelper.java:235)
    at
   com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work
   spaceHelper.java:563)
    at
   com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator
   (WorkspaceHelper.java:584)
    at
   com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu
   tes(ConfigServiceImpl.java:2102)
    at
   com.ibm.ws.management.commands.properties.resources.common.Apply
   Properties.setProperties(ApplyProperties.java:240)

LOCAL FIX

PROBLEM SUMMARY
 *  ****************************************************************
   * USERS AFFECTED:  All users of IBM WebSphere Application      *
   *                  Server Property File Based Configuration    *
   ****************************************************************
   * PROBLEM DESCRIPTION: A Property File Based Configuration     *
   *                      (PFBC) file might fail to apply.        *
   ****************************************************************
   * RECOMMENDATION:                                              *
   ****************************************************************
   A recent (8.5.5.5) parser change introduced a problem where
   types that have default values noted in the file and are not
   Strings can be incorrectly processed.  For example:
   isolatedClassLoader=false #boolean,default(false)
   might be incorrectly processed, and as a result, the file
   might not apply.

PROBLEM CONCLUSION
 *  The parsing code is updated so the problem no longer occurs.

   The fix for this APAR is currently targeted for inclusion in
   fix pack 8.5.5.6.  Please refer to the Recommended Updates
   page for delivery information:
   http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]

TEMPORARY FIX

COMMENTS

APAR INFORMATION
 * APAR NUMBER
   PI37248

 * REPORTED COMPONENT NAME
   WEBS APP SERV N

 * REPORTED COMPONENT ID
   5724H8800

 * REPORTED RELEASE
   850

 * STATUS
   CLOSED PER

 * PE
   NoPE

 * HIPER
   NoHIPER

 * SPECIAL ATTENTION
   NoSpecatt / Xsystem

 * SUBMITTED DATE
   2015-03-18

 * CLOSED DATE
   2015-03-20

 * LAST MODIFIED DATE
   2015-03-24

 * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:

 * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:

FIX INFORMATION
 * FIXED COMPONENT NAME
   WEBS APP SERV N

 * FIXED COMPONENT ID
   5724H8800

APPLICABLE COMPONENT LEVELS
 * R850 PSY
   UP

Question:
Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written If you are trying to install Portal v8.5 on WAS 8.5.5.5 or less it may fail when running the manageprofiles.sh. You will get this exception; SEVERE
com.ibm.ws.profile.cli.WSProfileCLIAugmentProfileInvoker
executeWSProfileAccordingToMode
1
INSTCONFFAILED: Profile augmentation failed. For more
information, consult
/opt/IBM/WebSphere/AppServer8/logs/manageprofiles/portal01_create.log.

Answer:
The parsing code is updated so the problem no longer occurs.

   The fix for this APAR is currently targeted for inclusion in
   fix pack 8.5.5.6.


IBM Diagnosing a java.lang.StackOverflowError - United States StackOverflow; overflowing; recursion; recursively; jit; JustInTime; Hot; Spot; WebSphere; Just-In-Time TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Stack Overflow exceptions can occur when a thread stack continues to grow in size until reaching the maximum limit.

SYMPTOM
 A stack overflow can result from:

 * A deeply nested application
 * An infinite loop within an application
 * A problem in just-in-time (JIT) compiled code
 * Applications requiring a larger stack size, especially ones relying on XML, GUI, or java2D classes.
 * Native method calls

Stack overflow issues are frequently masked by Out of Memory exceptions. By resolving the memory constraints, the stack overflow can be resolved.
CAUSE
When a stack overflow occurs, the amount of stack space required by the program exceeds what is configured for the stack in the Java™ Virtual Machine (JVM) process, or the native stack size configured by the operating system.
Some applications require stacks that are larger than the default size; for example, a graphics-intensive Java program can require a larger stack, which may require an increase in the stack size to avoid StackOverflow.

DIAGNOSING THE PROBLEM
Look for either Out of Memory messages or java.lang.StackOverflow in the server logs. The process may continue to run after either of these messages are seen.

If a crash did occur, a javacore should have generated on IBM SDK. You will either see the signal as SIGSEGV, SIGILL, SIGABRT, or SIGBUS. Usually the current thread will indicate the following

pending=java.lang.StackOverflowError
RESOLVING THE PROBLEM

[/support/docview.wss?uid=swg21162896&aid=1]Explanations and Solutions
[/support/docview.wss?uid=swg21162896&aid=2]Detailed Configuration Options

Explanations and Solutions

Infinite Recursion
If an application is performing recursion, the maximum stack size can easily be reached and a Stack Overflow exception is thrown. The thread stack has a limited size and eventually its space will run out as the thread stack grows without bounds.

Some traits of recursion:
- Large thread stacks that appear to repeat
- An infinite loop that continuously spawns off threads
- Very large XML documents loaded into the Document Object Model (DOM)
- JSP or servlets calling itself (usually by executing forward or include to itself)
- Repeated calls in native functions

Increasing the thread stack size allows for larger thread stacks. However if the recursion continues to trigger a stack overflow, the next step is to identify what code is causing the recursion from javacores, thread dumps, or even system core files.

A thread stack that indicates it's too large to display can be an indicator of stack overflow. This is especially true if the stack appears to repeat (such as recursive method calls).

JIT/HotSpot Compiled Code

The JIT/HotSpot compiler (JIT) is designed to speed up the JVM execution times by compiling method calls. This can speed up execution time, but as more aggressive optimizations are used, this can inadvertently cause recursion, resulting in stack overflow or crash. The documents linked below explain how to debug JIT and HotSpot compiler issues:  * JIT Problem Determination for IBM SDK 5.0 and 6.0 using -Xjit [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21294023]
 * Debugging HotSpot failures on the Solaris and HP-UX operating environment [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21081179]

Depleted Native Stack
It is almost guaranteed that a crash will occur if the native stack runs out of space. System cores can be used to identify long and possibly recursively looping native thread stacks.

To resolve, increase the native stack size (usually by adjusting the operating system limit for stack size) to accommodate the recursive native calls; however, identifying the recursive native calls will help determine the root cause of the stack overflow.

[/support/docview.wss?uid=swg21162896&aid=3] Back to top

[http://www.ibm.com/i/v14/rules/dotted_blue_rule_443.gif]

Detailed Configuration Options

Adjusting the Stack Sizes (Xss and Xmso) options
If this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources.

For every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow.

 * Maximum Thread Stack Size (-Xss)
 *
 *
 *
 *
 *  -Xss<size>
 *
 * <size>
 *
 * nn[k|m|g|K|M|G]
 *
 *
 *
 *
 *
 *
 * there is no distinction between native and thread stack sizes
 *
 * only
 *
 * HP-UX
 *
 *
 *
 *  -XX:MainThreadStackSize=<size>
 *
 *
 *
 *
 *
 *
 *
 * Initial Thread Stack Size (-Xiss)
 *
 * This is only for distributed platforms (AIX, Linux, Windows)
 *
 *
 *
 *
 *
 *  -Xiss<size>
 *
 * <size>
 *
 * nn[k|m|g|K|M|G]
 *
 *
 *
 *
 * Initial Native Stack Size (-Xmso)
 *
 * This is only for distributed platforms (AIX, Linux, Windows)
 *
 *
 *
 *
 *
 *
 *  -Xmso<size>
 *
 * <size>
 *
 * nn[k|m|g|K|M|G]
 *
 *
 *
 *

Default Values
This is a chart of default sizes for the various stack size arguments. This is subject to change due to upgrades of the SDK.

[/support/docview.wss?uid=swg21162896&aid=4]
Value [/support/docview.wss?uid=swg21162896&aid=4]
AIX [/support/docview.wss?uid=swg21162896&aid=4]
Linux [/support/docview.wss?uid=swg21162896&aid=4]
Windows [/support/docview.wss?uid=swg21162896&aid=4]
Solaris [/support/docview.wss?uid=swg21162896&aid=4]
HP-UX [/support/docview.wss?uid=swg21162896&aid=4]
Initial Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Maximum Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Native Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
256KB [/support/docview.wss?uid=swg21162896&aid=4]
256KB [/support/docview.wss?uid=swg21162896&aid=4]
32KB (32-bit)
256KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
512KB (32-bit)
1024KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
64KB (PA-RISC)
1024KB (Itanium) [/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=5] Back to top

Examples of Stack Overflow

Server Logs
These logs may contain references to StackOverflow, alongside other messages. Thread stacks may accompany these messages, indicating if there is a recursive call.
 * SystemOut.log example

 * [3/14/15 3:14:15:926 CST] 31415926 BaseMap W CWOBJ0006W: An exception occurred:
 *
 * com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.lang.StackOverflowError
 *
 * <<Thread stack may follow this message>>
 *

 *
 *
 *
 * SystemErr.log example

 * [3/14/15 3:14:15:926 PST] 31415926 SystemErr R Caused by: java.lang.StackOverflowError
 *
 *  at java.util.Hashtable.get(Hashtable.java:461)
 *
 *  at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServletRequest.java:1257)
 *
 *  at psdi.webclient.system.session.WebClientSession.applySkin(WebClientSession.java:295)
 *
 *  at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1177)
 *
 *  at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)
 *
 *  at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)
 *
 * ...
 *

 *

Javacore

In javacores, look for "StackOverflowError" in the thread name entry: 3XMTHREADINFO "ORB.thread.pool : 19" (TID:10167F78, sys_thread_t:E072BCE0, state:R, native ID:E06BEBA0) prio=5: pending=java.lang.StackOverflowError
System Dump (processed with jextract and DTFJ Dump Analyzer)

Look for this message near the end of a very large stack. This particular example had 1000 recursively called entries. Java stack frames dump is too long: <analyzererror>

Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK

Question:
completeness report causes StackOverflowError in Decision Center

When running the completeness report in Decision Center we sometimes get a StackOverflowError such as:

     ...
     Caused by: java.lang.StackOverflowError
         at ilog.rules.validation.solver.IlcIntScalProd.extract(IlcIntScalProd.java:89)
         at ilog.rules.validation.solver.IlcIntExpr.getPIntExp(IlcIntExpr.java:156)
     ...

Answer:
Adjusting the Stack Sizes (Xss and Xmso) options
If this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources.

For every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow.


IBM Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236) - United States  SECURITY BULLETIN

SUMMARY
 IBM MQ could allow an authenticated user to potentially cause a denial of service by issuing an incorrect saved channel status inquiry.

VULNERABILITY DETAILS

CVEID:CVE-2017-1236 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1236]
DESCRIPTION:IBM MQ could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry.
CVSS Base Score: 3.1
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124354 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124354]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)

AFFECTED PRODUCTS AND VERSIONS
IBM MQ 9.0.2 Continuous Delivery

IBM MQ Appliance 9.0.x Continuous Delivery

IBM MQ 9.0 LTS

IBM MQ 8.0

IBM MQ 8.0 Appliance

REMEDIATION/FIXES
IBM MQ 9.0.2 Continuous Delivery

Apply IBM MQ 9.0.3 Continuous Delivery release or later.

IBM MQ Appliance 9.0.x Continuous Delivery

Apply continuous delivery update 9.0.3 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=9.0.2&platform=All&function=all] or later.

IBM MQ 9.0 LTS

Apply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038].

IBM MQ 8.0

Apply Fix Pack 8.0.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg22005832].

IBM MQ Appliance 8.0

Apply Fix Pack 8.0.0.7 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=8.0.0.5&platform=All&function=all].

WORKAROUNDS AND MITIGATIONS
IBM MQ Appliance; Affected Queue manager must be restarted.

IBM MQ 9.0.2 CD : Restart the failed command server on the queue manager.

IBM MQ 9.0 LTS : Restart the failed command server on the queue manager.

IBM MQ 8.0 : Restart the failed command server on the queue manager.

GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
 Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.

IMPORTANT NOTE
 IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.

REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]

RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]

CHANGE HISTORY
 09 Jan 2018: Updated
06 Oct 2017: Updated at 9002 GA
15 Jun 2017: Original version published

*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.

Question: Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236) I need to understand details regarding Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236). Where can I find this information?

Answer:
CVEID:CVE-2017-1236 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1236]
DESCRIPTION:IBM MQ could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry.
CVSS Base Score: 3.1
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124354 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124354]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)


IBM How to troubleshoot the error "Failed to process response headers" - United States datapower; failed; parse; process; error; network; connection; persistent; headers; response headers; failed to process response headers; 7993; 7993; 7993; machine type 7993 TECHNOTE (FAQ)

QUESTION
 What does this error mean?

General error that is always seen:
[servicetype][error] wsgw(policyrule): tid(196761)[error][x.x.x.x]: Failed to process response headers

Specifically from a Web Service Gateway:
[ws-proxy][error] wsgw(Proxy): tid(1234567)[10.2.3.4]: Backside header failed to parse due to: Failed to process response headers
[ws-proxy][error] wsgw(Proxy): tid(1234567)[error][10.2.3.4]: Failed to process response headers

Additional log information might be seen while at the debug log level.

CAUSE
When you read this error, keep in mind that it is thrown from a rule within a policy of a service. This error almost always means that the policy did not receive any data. If you increase the logging from error to debug, you should see network failures surrounding the response header error.

In almost every event, this error is caused by a connection failure.
The error is correct, the service did not receive any response headers or data. The key to help confirm this is to increase the log level to debug. This will allow you to see the network debug errors around the context of the service error.

ANSWER
The classic causes of this are either of these two:

A slow response that causes the connection to timeout before receiving the response
A failed connection attempt due to a closed persistent connection or some other connection issue that prevents the WebSphere® DataPower device® from connecting to the backend. For example, a reused connection would be attempted and found to already be closed out by something outside of DataPower®.
An example of this is explained here:
http://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1 [http://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1]

There are a broad range of network errors that can trigger this to error. A packet trace is the key to capture the problem and confirm what type of failure is the cause. A log with event subscription of "all" "debug" will also help correlate and confirm the packet trace data.

In some cases, a simple work around to try is to lower the DataPower persistent timeout or disable persistent connections. If this does not prevent the problem, then analysis of the packet trace and error report are required.

Question:
How precise is DataPower's backside persistent timeout value related to intermittent "Failed to Process Response Headers" error messages?

I have a service on DataPower with a backside persistent timeout value set to 28 seconds. The actual backend device has a persistent timeout setting of 30 seconds.

Since my service is configured with a lower persistent timeout value than 30 seconds, why am I still seeing the following error intermittently?

Wed June 25 2009 09:20:02 [0x80000001][xsltmsg][error] mpgw (MyGateway): tid(8675309)[error][9.x.x.x]: Failed to process response headers

Answer:
In almost every event, this error is caused by a connection failure.
The error is correct, the service did not receive any response headers or data. The key to help confirm this is to increase the log level to debug. This will allow you to see the network debug errors around the context of the service error.


IBM Content Collector Configuration Store is corrupted - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 IBM Content Collector Configuration Store Service cannot be started successfully due to database corruption.

SYMPTOM
Cannot start the IBM Content Collector Configuration Store Service

CAUSE
Transaction log gets corrupted when IBM Content Collector server runs out of disk space.

RESOLVING THE PROBLEM

 1. Shutdown the IBM Content Collector Configuration Store Service if it is running.
 2. Make a backup copy of all files under the following directory:
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore

    C:\ProgramData may be hidden by default. Show hidden folders by changing the configuration in Folder and Search options > View tab > Hidden files and folders > Show hidden files, folders, and drives.
 3. Free up disk space on the drive
 4. Delete the following files:
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\*
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solmsg.out
    C:\ProgramData\IBM\ContentCollector\ConfigurationStore\solerror.out

    Important:
    Delete only the files under C:\ProgramData\IBM\ContentCollector\ConfigurationStore\logs\.
    Do not delete the folder itself.

 5. If restoring the configuration store to a previously backed up copy is required, run afuConfigStoreTool -backup to restore the backup copy. See production documentation for more information on running this tool. Otherwise, proceed to the next step.
 6. Restart IBM Content Collector services.

RELATED INFORMATION
 IBM Content Collector Information Center [http://pic.dhe.ibm.com/infocenter/email/v4r0m0/index.jsp]

Question: ICC Configuration Store Service is hung? ICC Configuration Store Service is hung and is not responding to start or stop commands. This was observed due to a potential issue with server running out of disk space.  What is causing this?

Answer: Transaction log gets corrupted when IBM Content Collector server runs out of disk space.


IBM Identifying Indexing errors in Atlas database - United States  TECHNOTE (FAQ)

QUESTION
 How do I identify Indexing errors in Atlas database?

CAUSE
Sometimes encrypted and password protected documents cause document indexing errors

ANSWER

 1. Login to Atlas database as PSSAPL user
 2. Run select * from ctx_user_index_errors;
 3. Copy the value in the ERR_TEXTKEY Field
 4. Run select * from documentlibrary where rowid='<value from Step 3> ';
 5. This will list the document which has the indexing error

Question: How do I identify Indexing errors in Atlas database? How do I identify Indexing errors in Atlas database?

Answer:
Login to Atlas database as PSSAPL user
 2. Run select * from ctx_user_index_errors;
 3. Copy the value in the ERR_TEXTKEY Field
 4. Run select * from documentlibrary where rowid='<value from Step 3> ';
 5. This will list the document which has the indexing error


IBM DataPower Gateways Firmware Support Lifecycle - United States datapower;support;lifecycle;support lifecycle;maintenance;firmware;release;releases;firmware releases;upgrade;upgrades;features;defect NEWS

ABSTRACT
This document provides information on the IBM DataPower Gateway Firmware Support Lifecycle.

CONTENT
IBM® DataPower® Gateway is a purpose-built gateway that provides security, traffic control, mediation and optimized access to a full range of mobile, web, application programming interface (API), service-oriented architecture (SOA), B2B and cloud workloads. It supports multi-cloud deployment and is available in Docker container, Linux application, VMware virtual machine and physical appliance form factors.

IBM provides flexible support options to meet the needs of your business and minimize any business impact. The IBM DataPower Gateways end-of-service support policy applies differently between hardware and firmware.

Hardware

DataPower physical appliance hardware is supported for a minimum of five years, starting at the General Availability of the new product. Beginning with the 8436 models, standard appliance service and support is available for five years from the end-of-marketing (EOM) date as described in the IBM Appliance Support Handbook [http://www.ibm.com/support/customercare/sas/f/applhandbook/home.html].

For end-of-service information on physical appliances, see IBM DataPower Gateways End of Service dates [http://www.ibm.com/support/docview.wss?uid=swg21317845].

Firmware

Businesses are building modernized digital platforms to drive innovation and disruption within the industry. IBM DataPower Gateways are a core component in these platforms and it needs to deliver new business functionality to keep pace with business innovation.

Effective with DataPower Gateway firmware V7.6 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS217-265&appname=USN], DataPower introduces a Continuous Delivery (CD) model to accelerate delivery of new capabilities and meet market needs. DataPower CD will consist of two releases:

 1. CD release approximately once per quarter  * Only the most recent CD release is supported at a given time.

 2. Long Term Support (LTS) release every 12 months.  * LTS releases are for customer seeking enhanced stability and do not wish to upgrade on the CD schedule, while CD releases are intended for customers seeking the latest features.
     * The first LTS release post 7.6 GA will be within two years. Subsequent LTS releases will occur every 12 months.
     * LTS releases will be supported for a minimum of 2 years.

Firmware V7.6 and later have no extended support plan available for any release of DataPower Gateway. IBM will publish a notice of support discontinuance (end-of-service) for a LTS releases at least 12 months before the effective date.

Firmware V7.5 and earlier will remain on the traditional IBM DataPower Gateway support model where they will be supported for a minimum of 2 years. There is no extended support plan available for any of these releases. IBM will publish a notice of support discontinuance (end-of-service) for releases at least 12 months before the effective date.

Note: IBM DataPower Gateways customers can use the following table to track how long their version and release of a particular firmware level will be supported. By using the information in this table, customers can effectively plan their firmware investment without any gaps in support.

Release Support Model GA date End-of-service date Comment 7.7.0
7.7.1.0
7.7.1.1
7.7.1.2 CD 03/2018 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS218-018]
06/08/2018
06/29/2018
07/27/2018 06/08/2018
06/29/2018
07/27/2018
Planning Information 7.6.0 LTS 07/2017 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS217-265] Planning Information 7.5.0
7.5.1
7.5.2 Traditional 03/2016 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS216-024/index.html&lang=en&request_locale=en]
06/2016
09/2016 04/30/2019
04/30/2019
04/30/2019 7.5.x Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS918-054/index.html&request_locale=nul] 7.2.0 Traditional 06/2015 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS215-108/index.html&lang=en&request_locale=en] 09/30/2018 7.2.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] 7.1.0 Traditional 11/2014 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS214-394/index.html&lang=en&request_locale=en] 09/30/2018 7.1.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] 7.0.0 Traditional 06/2014 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS214-117/index.html&lang=en&request_locale=en] 09/30/2017 7.0.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS916-117/index.html&lang=en&request_locale=en] 6.0.2 (Common Criteria) Traditional 05/2015 6.0.1 Traditional 12/2013 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/649/ENUSA13-1105/index.html&lang=en&request_locale=en] 06/19/2016 6.0.1 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21882726] 6.0.0 Traditional 06/2013 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS213-172/index.html&lang=en&request_locale=en] 06/19/2016 6.0.0 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21882726] 5.0.0 Traditional 06/2012 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS112-064] 06/30/2015 5.0.0 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21677137] 4.0.2 Traditional 09/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS211-288/index.html&lang=en&request_locale=en] 11/30/2014 4.0.2 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21649637] 4.0.1 Traditional 06/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS211-141/index.html&lang=en&request_locale=en] 06/30/2014 4.0.1 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21642813] 4.0.0 Traditional 06/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS211-141/index.html&lang=en&request_locale=en] 09/30/2013 4.0.0 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21612021] 3.8.2 Traditional 12/2010 [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS211-284] 09/30/2013 3.8.2 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21612021] 3.8.1 Traditional 06/2010 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS210-108/index.html&lang=en&request_locale=en] 12/31/2012 3.8.1 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21511811] 3.8.0 Traditional 11/2009 [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS109-581] 09/30/2012 3.8.0 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21511811] 3.7.3 Traditional 04/2009 12/31/2011 3.7.3 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21457788] 1.0.0 Traditional 12/2008 12/31/2010 1.0.0 Announcement Archived 3.7.2 Traditional 12/2008 12/31/2010 3.7.2 Announcement Archived 3.7.1 Traditional 08/2008 08/31/2010 3.7.1 Announcement Archived 3.7.0 Traditional 07/2008 08/31/2010 3.7.0 Announcement Archived 3.6.1 Traditional 12/2007 12/31/2009 3.6.1 Announcement Archived 3.6.0 Traditional 10/2006 08/31/2009 3.6.0 Announcement Archived 3.5.1 Traditional 06/2006 02/28/2009 3.5.1 Announcement Archived
Notes:

 * For information on current DataPower firmware versions, see Supported Firmware versions and recommended upgrade levels for IBM DataPower Gateways ".
 * Refer to the Contact Support [http://www.ibm.com/support/docview.wss?uid=swg21236322] page for how to reach IBM DataPower Gateways Support.
 * Customers are responsible for completing migration activities to currently supported levels before a release level reaches end-of-support.
 * Short duration support extensions are available on a case-by-case basis, for an additional fee, immediately following the end-of-support for a specific firmware level. Extensions would be for a very limited time period with limited terms and conditions. An extension is intended to provide support while customers complete their migration to a supported release.

[https://www-prd-trops.events.ibm.com/sites/default/files/support/swg/swgtech.nsf/0/ec1cbaaf35990704852571f0006aa83d/Content/0.528A.jpg]

Question: Upgrading to 7.7.x while using APIC v5 with DataPower? We currently have API Connect v5 with DataPower 7.2.x. Considering 7.2 is going out of support, we would like to upgrade to the most recent version(7.7) to stay up-to-date. Are there any known issues or conflicts with this setup?

Answer:
Effective with DataPower Gateway firmware V7.6 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS217-265&appname=USN], DataPower introduces a Continuous Delivery (CD) model to accelerate delivery of new capabilities and meet market needs. DataPower CD will consist of two releases:

 1. CD release approximately once per quarter  * Only the most recent CD release is supported at a given time.

 2. Long Term Support (LTS) release every 12 months.


IBM How to override the directory location for IBM P8 Content Platform Engine (CPE) logs. - United States  TECHNOTE (FAQ)

QUESTION
 How to override the directory location for CPE logs.

CPE logs include perflog_config.properties, p8_server_error.log, p8_server_trace.log, GCD folder, pesvr_system.log, pesvr_trace.log and pedata folders. In some instances, it will also include the INSO folder, CSSTemp folders and perf.log.

ANSWER
Add the system property 'user.dir' in the JVM argument to the application server.
For example, if you want to change the log location to 'c:\logs'
A. JBoss Application Server:

 *
 *
 *
 *
 *
 *
 *
 *
 *

B. Oracle WebLogic Server:  *
 *
 *
 *
 *
 *
 *
 *
 *

C. WebSphere Application Server:  *
 *
 *
 *
 *
 *
 *
 *
 *

Question: Is it possible to move all the P8 logs out of the default location? We are looking to move all the P8 logs out of the default FileNet folder in Websphere. The trace log can be moved easily; however, the error log and PE logs also need to be moved.

Answer: Add the system property 'user.dir' in the JVM argument to the application server.


IBM How to format server trace using ARSTFMT on Content Manager OnDemand 8.5.x.x and 9.0.x.x  on Windows platform - United States server trace; ARSTFMT; Content Manager OnDemand TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Formatting CMOD V8.5.x.x and 9.0.x.x Server traces on Windows platform

SYMPTOM
CMOD Server trace output is unreadable

CAUSE
In CMOD V8.5.0.0 and later, the trace file is written in binary. To convert the trace file from its binary format, use the ARSTFMT command found in the bin directory of your OnDemand server V8.5 and later installation.

ENVIRONMENT
Windows

RESOLVING THE PROBLEM
Open command prompt - navigate to the CMOD\9.0\bin directory and issue ARSTFMT as follows:

arstfmt -i C:\Users\IBM_ADMIN\path\to\file -o C:\Users\IBM_ADMIN\path\to\file\name.txt

where the C:\Users\IBM_ADMIN\path\to\file is the unreadable trace file and C:\Users\IBM_ADMIN\path\to\file\name.txt is the name of the formatted trace file.

RELATED INFORMATION
 Enable ODWEK tracing [http://www-01.ibm.com/support/docview.wss?uid=swg21240220]
How to enable trace in Content Manager OnDemand server [http://www-01.ibm.com/support/docview.wss?uid=swg21330810]

Question: How can I format a trace for CMOD v9.0 on Windows? How can I format a CMOD trace on Windows?

Answer:
Open command prompt - navigate to the CMOD\9.0\bin directory and issue ARSTFMT as follows:

arstfmt -i C:\Users\IBM_ADMIN\path\to\file -o C:\Users\IBM_ADMIN\path\to\file\name.txt

where the C:\Users\IBM_ADMIN\path\to\file is the unreadable trace file and C:\Users\IBM_ADMIN\path\to\file\name.txt is the name of the formatted trace file.


IBM web server Plugin may need LD_LIBRARY_PATH when used with Apache 2.2 - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 IBM web server Plug-in provides the connection between the web server tier and the IBM WebSphere Application Server (WAS) tier.

When using Apache 2.2 web server on Linux operating systems, the IBM web server Plug-in may need to have the LD_LIBRARY_PATH environment variable set in a certain way, in order to be able to locate the IBM Global Security Kit (GSKit) libraries needed for SSL (HTTPS).

Without the GSKit libraries, the IBM web server Plug-in will be unable to initialize SSL, and will use only HTTP for connections to the WAS appservers.

SYMPTOM
During web server start-up, errors like the following will be logged into the Plug-in log file (http_plugin.log):

ERROR: lib_security: loadSecurityLibrary: Failed to load gsk library from /opt/IBM/WebSphere/Plugins/gsk8/gsk8_64
ERROR: ws_transport: transportInitializeSecurity: Unable to load security library
ERROR: ws_server: serverAddTransport: Failed to initialize security
ERROR: ws_server: serverAddTransport: HTTPS Transport is skipped

RESOLVING THE PROBLEM
To resolve the problem, you must set the LD_LIBRARY_PATH environment variable to point to the library directory of the GSKit that comes with the IBM web server Plug-in. The precise directory location will depend of the version of Plug-in, and on the bit depth being used (32-bit or 64-bit).

For example.....

If you installed the 32-bit Plug-in v7.0 and are using with a 32-bit Apache 2.2, use this:

export LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/lib/

If you installed the 64-bit Plug-in v7.0 and are using it with a 32-bit Apache 2.2, use this:

export LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/gsk7_32/lib/

If you installed the 64-bit Plug-in v7.0 and are using it with a 64-bit Apache 2.2, use this:

export LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/gsk7_64/lib64/

If you installed the 32-bit Plug-in v8.x and are using with a 32-bit Apache 2.2, use this:

export LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/lib/

If you installed the 64-bit Plug-in v8.x and are using it with a 32-bit Apache 2.2, use this:

export LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/gsk8_32/lib/

If you installed the 64-bit Plug-in v8.x and are using it with a 64-bit Apache 2.2, use this:

export LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/gsk8_64/lib64/

Please note that for Apache 2.2 on Linux, simply setting the LD_LIBRARY_PATH environment variable from the command line prior to starting the web server, MAY NOT WORK. In that case, you must set this variable as follows...

For SLES and SUSE Linux add the export command into the /usr/sbin/envvars file.

For RHEL Linux add the export command into the /etc/sysconfig/httpd file.

By adding the export command into the files shown above, it means that the environment variable will be set when the web server is started. That will enable the Plug-in to be able to locate the appropriate GSKit libraries and be able to initialize SSL transports.

RELATED INFORMATION
#Web server plug-in setupGSKitLibPath script contains in [http://www-01.ibm.com/support/docview.wss?uid=swg21441018]

Question:
Why Plug-in log file reports an error message after install & configure the WebSphere Plugin 8.5 version on a Apache 2.4 webserver.

During web server start-up, errors like the following will be logged into the Plug-in log file (http_plugin.log):

ERROR: lib_security: loadSecurityLibrary: Failed to load gsk library from /opt/IBM/WebSphere/Plugins/gsk8/gsk8_64 ERROR: ws_transport: transportInitializeSecurity: Unable to load security library ERROR: ws_server: serverAddTransport: Failed to initialize security ERROR: ws_server: serverAddTransport: HTTPS Transport is skipped

Note: This is an Apache 2.4 version on a Linux platform

Answer: To resolve the problem, you must set the LD_LIBRARY_PATH environment variable to point to the library directory of the GSKit that comes with the IBM web server Plug-in. The precise directory location will depend of the version of Plug-in, and on the bit depth being used (32-bit or 64-bit).


IBM NoClassDefFoundError running Java class selected from server plugin jar - United States wid; noclassdeffounderror; java; jar TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 The visual snippet editor allows you to search and find methods in classes available only on a restricted basis at runtime. A runtime exception occurs when the Java™ snippet calls a method in a class found in one of the plugin JARs in the server's plugins directory.

CAUSE
Some of the Java methods found in the JARs in the server's plugin directory are available to be called, but some of them are considered internal use only and an exception is thrown if you try to call them from user code.

DIAGNOSING THE PROBLEM
A runtime exception is detected in the server log naming a class and method called from a visual snippet in the application.

RESOLVING THE PROBLEM
The reason the method you selected in the snippet editor cannot be called in the JAR in the plugins directory is because of the architecture of the server. JARs in the plugins directory have a list that specifies what classes in the JAR can be called. This is called the exports list, and it is honored by the class loader the server uses. Classes not on the list are considered internal use only. Thus, not all classes in the server plugin JARs are available to be called by user code.

You can call any method when the JAR is in the server's library directorym because it is not being treated as a plugin and a different class loader is used, one which does not implement the exports list.

The snippet editor is not aware of this mechanism so it treats a plugin JAR the same as a regular Java JAR file. That is it allows you to select the (unavailable) class and method to call in your program. The resolution is to make sure that classes you call in plugin JARs appear on the exports list.

For example you may search for StringUtils and find the class org.apache.commons.lang.StringUtils in the WebSphere JAR plugin/com.ibm.ws.jpa.jar. This class is used internally by the plugin and it is not exported. In this case you must download the class you need directly from Apache and place the JAR in the server's classpath.

Question: WAS runtime classpath does not match WAS Server Runtime library in RAD  I've run into a classpath problem in WAS 8.0 for my web application. The problem is that it compiles fine i RAD but I get a NoClassDefFoundError in Runtime.

Answer: Some of the Java methods found in the JARs in the server's plugin directory are available to be called, but some of them are considered internal use only and an exception is thrown if you try to call them from user code.


IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.8-TIV-ITM_SQL-IF0001 - United States KOQ; OQ DOWNLOADABLE FILES

ABSTRACT
 This fix resolves the APARs and defects listed in the "Problems Fixed"

DOWNLOAD DESCRIPTION
Copyright International Business Machines Corporation 2016.

All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager for Microsoft(R) Applications:
Microsoft(R) SQL Server Agent, Version 6.3.1.8

Component ID: 5724B96MO

Interim Fix 0001, (6.3.1.8-TIV-ITM_SQL-IF0001)

Date: March 30, 2016

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices

1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.

2.0 Problems fixed
==================
2.1 APARS:
-------------------
APAR: IV79406
Abstract: Duplicated entries of SQL Server on TADDM portal.
Additional Information: SQL Server instance discovered from ITM
DLA and TADDM Sensor was not reconciling on TADDM
and duplicates were seen. The reason for duplicates
was that the DLA naming rules were not matching
with the Sensors naming rules.

APAR: IV82234
Abstract: False databases are reported as Suspected.
Additional Information: The data collected for Database Detail is written
in <InstanceName>_DBD_PREV file. Due to improper file handling the
collector logs were written into this file which was causing collector
logs to be seen on the portal and triggering false alerts.

2.2 DEFECTS:
-----------------
DEFECT: 138512
Abstract: Improvement of table detail (KOQTBLD) algorithm.
Additional Information: The Table Detail information is now sorted
based on COLL_TBLD_SORTBY.

DEFECT: 138519
Abstract: Default instance of SQL Server is identified as 'MSSQLSERVER'
instead of hostname.
Additional Information: The default instance of SQL server used to get
configured with hostname and not MSSQLSERVER.
In an environment, where there was default instance and
a named instance having same name as hostname had issues
in configuration.

DEFECT: 140838
Abstract: Collector process crashes when collecting Statistics Summary
attribute group.
Additional Information: There was an access violation exception as agent
is trying to read from the memory that is already freed up.

2.3 Superseded fixes
--------------------
None

2.4 APARs and defects included from superseded fixes
----------------------------------------------------
None

3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: Microsoft SQL Server agent prerequisites Document,
version 6.3.1 or from the following link:
http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=A54AA300920511E292EE9F030925FE1B&duComponent=Server_A5707A80920511E292EE9F030925FE1 [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=A54AA300920511E292EE9F030925FE1B&duComponent=Server_A5707A80920511E292EE9F030925FE1]

The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www-969.ibm.com/software/reports/compatibility/clarity/index.html [http://www-969.ibm.com/software/reports/compatibility/clarity/index.html]

3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is as follows:

Local Agent Upgrade:
- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.8

Remote Agent Upgrade:
- IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 with OS Support
- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.8
- Monitoring Agent for Windows OS, Version V6.23 Fix Pack 3

As this fix is cumulative, it can be installed on any fix level for this version,
release and mod level above the prerequisite.

4.0 Image directory contents
============================
This fix image contains the following files:

- 6.3.1.8-TIV-ITM_SQL-IF0001.README - This is the README file
- 6.3.1.8-TIV-ITM_SQL-IF0001.tar - Fix archive .tar format
- 6.3.1.8-TIV-ITM_SQL-IF0001.zip - Fix archive .zip format

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file
if you are working in a Windows(R) environment.

The fix archive file contains the following files:
6.3.1.8-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.tar
6.3.1.8-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.zip
6.3.1.8-TIV-ITM_SQL-IF0001/KOQ_winnt_tema_if0001.cab
6.3.1.8-TIV-ITM_SQL-IF0001/KOQ_wix64_tema_if0001.cab
6.3.1.8-TIV-ITM_SQL-IF0001/KOQWINNT.dsc
6.3.1.8-TIV-ITM_SQL-IF0001/KOQWIX64.dsc
6.3.1.8-TIV-ITM_SQL-IF0001/oq_dd.properties
6.3.1.8-TIV-ITM_SQL-IF0001/oq_dd_063108001.xml
6.3.1.8-TIV-ITM_SQL-IF0001/itmpatch.exe

5.0 Installation instructions
=============================
This fix can only be installed over an existing installation.
Use the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- With reference to this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Refer to section 7.0 entitled "Known problems and workarounds"
before installation.

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory
on the system that contains the agent code to be updated. For
the purpose of this README, the symbol <TEMP> represents the
fully qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the
supported platforms.

3. Use the "itmpatch" command to install the fix for that agent
platform. For more information on the "itmpatch" command, see
section 6.2.

On Windows systems, if the fix was expanded to
<TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001, the install command is:

For 32 bit Agent:
> <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001\KOQ_winnt_tema_if0001.cab

For 64 bit Agent:
> <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001\KOQ_wix64_tema_if0001.cab

Note : Use "itmpatch" command from <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001\
temporary directory.

5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory
on the IBM Tivoli Enterprise Monitoring Server system. For the
purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory.
Note: On Windows systems, this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the
supported platforms.

3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd addBundles" command, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/6.3.1.8-TIV-ITM_SQL-IF0001:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.8-TIV-ITM_SQL-IF0001

On Windows systems,
if the fix was expanded to <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.1.8-TIV-ITM_SQL-IF0001

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to
be added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see "IBM Tivoli
Monitoring Command Reference".

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> $CANDLEHOME/bin/tacmd updateAgent -t OQ -n <Managed system name> -v 063108001

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t OQ -n <Managed system name> -v 063108001

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (oq), not three characters (koq).
- The node (-n) for the "tacmd updateAgent" command is the
managed system name of the operating system (OS) agent to be
updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.

5. To check if Remote Agent Update is SUCCESS/INPROGRESS/FAILED use the command
>tacmd getDeployStatus <transaction id>

where transaction id is the id provided after updateAgent command.

5.4 Agent support update
------------------------
Use the following steps to update the Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file
6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to the
Tivoli Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers
or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Expand the archive file (koq_tems_teps_tepd_if0001.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop
using the "tar" command on UNIX systems or an
extract utility on Windows systems. This step creates a
directory structure that includes a subdirectory called CD-ROM,
with the necessary updates.

4. Use the Application Support Installer(ASI) script to launch either
GUI installation or silent installation of the application
support files.

Note: For IBM Tivoli Monitoring Version 6.3 or above, one
of the following additional steps must be performed.

1. Acquire a platform-specific pre-packaged JRE version
of the Application Support Installer (ASI). See IBM
Tivoli Monitoring Application Support Installer,
6.2-TIV-ITM_ASI-IF0002 at
http://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]
for download and installation instructions.

2. Specify the '-j javahome' parameter with the path to
a java(r) 1.5 or java 1.6 installation when running
the itmasi.sh or itmasi.bat script described below.

GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not
the component directory. The installer can install updates for
multiple components at the same time.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Agent support upgrade for IBM Tivoli Monitoring Version 6.3
or above on Linux, zLinux, Solaris and windows operating systems
requires the following files contained in interim fix
6.2-TIV-ITM_ASI-IF0002. This is applicable to both GUI and
silent installation option of agent support upgrade.
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
- Solaris: setupSolaris.bin
- Windows: setupwin32.exe

Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0002.README".

On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Required. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and
modified as per your environment.

-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.

5. The next panel presented by the Application Support Installer
asks for the selection of which Tivoli Monitoring components
you want to add application support to.
For this fix, the check boxes should be set as follows:

Unchecked - Tivoli Enterprise Monitoring Server(TEMS)
Checked - Tivoli Enterprise Portal Server(TEPS)
Checked - Tivoli Enterprise Desktop Client(TEPD)

Continue through the remaining GUI panels selecting the
Microsoft SQL Server 06.31.08.01 support to complete the
installation.

Note: When support is installed using CLI or GUI for any of the
above Tivoli Monitoring components, they are restarted.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed, it
must be restarted.

6.0 Additional installation information
=======================================
Any existing Microsoft SQL Server Agent instances should be restarted
after the installation of this fix.

6.1 Installation instructions for agent baroc file
--------------------------------------------------
Fix (6.3.1.8-TIV-ITM_SQL-IF0001) includes changes to the agent
baroc files which need to be reinstalled. If you have already
installed these baroc files, there are no additional installation
steps. If not, refer to IBM Tivoli Monitoring, Installation
and Setup Guide under "Installing monitoring agent baroc files
on the event server" in "Installing the IBM Tivoli Enterprise
Console Event Synchronization" section for more information.

6.2 Additional information on using "itmpatch" command
----------------------------------------------------
The "itmpatch" command has the following syntax.

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be
installed
-t Generates a report of the actions to be taken by the patch

For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification where
the fix is located. On Windows systems, this must include the drive
letter.

6.3 Verifying the update
------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli
Monitoring installation directory, the default location
is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t OQ

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t OQ

Note:
- The component (-t) for the tacmd "listSystems" command is
specified as two characters (OQ), not three characters (KOQ).

When the agent update is successful, the agent version is:
06.31.08.01.

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.
For the agent on Windows systems, the version number is
06.31.08.01.

2. To verify the agent support files were updated correctly, use
the "kincinfo" command on Windows systems or the "cinfo" command
on Linux or UNIX systems. The sample output below shows the
versions of the Tivoli Enterprise Portal Server, Tivoli
Enterprise Monitoring Server, or Tivoli Enterprise Portal
Desktop systems after this fix has been successfully applied.

Note: The displayed build date and installation date might not
be accurate. This is known problem.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

On Windows systems:
-------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

C:\Users\Administrator>kincinfo -i
************* Monday, March 21, 2016 6:18:11 PM *************
User : Administrator Group : NA
Host Name : ESX1-SQL-T-9 Installer : Ver: 063004000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
OQ TEMS App Support/Microsoft SQL Server Support
WINNT Version: 06.31.08.00 Build: 60071

OQ TEPS App Support/Microsoft SQL Server Support
WINNT Version: 06.31.08.01 Build: 60711

OQ TEPB App Support/Microsoft SQL Server Support
WINNT Version: 06.31.08.00 Build: 60071

OQ TEPD App Support/Microsoft SQL Server Support
WINNT Version: 06.31.08.01 Build: 60711

7.0 Known problems and workarounds
==================================
Abstract: itmpatch command fails during upgrade
Problem: When itmpatch command is executed, it fails while upgrading
agent fix pack. The following error message is
displayed:

Version 06.31.08.XX of product koq is currently installed.
The patch requires that you must have at least version
06.31.08.XX of product installed to apply this patch.
Workaround: Use the itmpatch.exe provided in patch file
6.3.1.8-TIV-ITM_SQL-XXXXXX.zip or
6.3.1.8-TIV-ITM_SQL-XXXXXX.tar file.

Abstract: English characters are getting displayed in Agent support
installer having Non-English language operating system.
Problem: In Non-English language operating system, when agent
support installer is executed it shows English characters.
Workaround: None

Abstract: Installing support for patch fails on ITM 6.3.0
Problem: When you try to install the support for this patch on ITM
6.3.0, the installation fails with following error:
The wizard cannot continue because of the following error:
could not load wizard specified in /wizard.inf (104)
Workaround: Use the pre-packaged binaries for itmasi available at:
http://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]

Abstract: Crash encountered in event viewer for koqagent.exe
Problem: Sometimes while stopping the koqagent process, the collection
process is not getting completed. When koqagent.exe stops, the
thread spawned by it gets terminated forcefully. Hence it's
causing a crash.
Workaround: None

Abstract: Application support installation fails on Non Windows OS.
Problem: While installing the application support on the machines
having Operating system other than windows, the support
installation using ASI fails if the temporary directory
where the patch files are extracted has spaces.
Workaround: Use the temporary directory without space.

Abstract: MSSQL Agent collector crashes.
Problem: Sometimes the job 'syspolicy_purge_history' fails and
the collector crashes.
Workaround: 1. Disable scheduling of system job 'syspolicy_purge_history'.
2. Disable detail trace logging.

Abstract: MSSQL Agent collector process keeps on restarting.
Problem: If the default instance is configured before patch upgrade then
after patch upgrade the collector process keeps on restarting
Workaround: In this patch, the name of default instance is changed from
HOSTNAME to MSSQLSERVER (Defect 138519). Hence, the previously
configured default instance with name as HOSTNAME will not
work properly. So, it is required to unconfigure default
instance (with name hostname) and configure it with name as
MSSQLSERVER.

Following are the steps to unconfigure and configure:
1. Open Manage Tivoli Enterprise Monitoring Services
(MTEMS) window.
2. Right click on template row and go to
"Configure Using Defaults".
3. Select the default instance with name as HOSTNAME
from 'Server To Monitor' list box and click on ">>" button
to unconfigure it.
4. Select the instance with name 'MSSQLSERVER' in
'Database Servers Available' list box and click on "<<" button
to configure this instance.
5. Set the configuration parameters and start the agent.

Abstract: KOQ.SAVE registry is created for 631FP8 agent
Problem: When a configured instance is un-configured or 631FP8 agent is
uninstalled, the KOQ.SAVE registry is created.
Workaround: In case of upgrade to 6318IF1, manually delete the
KOQ.SAVE registry.

8.0 Additional product information
==================================
None

9.0 Notices
===========
This information was developed for products and services offered in
the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom
or any other country where such provisions are inconsistent
with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply
to you.

Trademarks and service marks
----------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.

PREREQUISITES
- IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 with OS Support
- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.8

INSTALLATION INSTRUCTIONS
Please refer to the README contained in the 'Description' section above for general installation instructions.

DOWNLOAD PACKAGE

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.3.1.8-TIV-ITM_SQL-IF0001 30-Mar-16 English 37159939 FC [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Microsoft+Applications&function=fixId&fixids=6.3.1.8-TIV-ITM_SQL-IF0001&includeRequisites=1&includeSupersedes=0&downloadMethod=http] [ ]
PRODUCT ALIAS/SYNONYM
 SQL Agent

 [/support/docview.wss?uid=swg24041994&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24041994&aid=2]Problems (APARS) fixed
IV79406, IV82234

Question:
Unexpected instance name for SQL Server agent after FP10

Hello,

on a new server I have installed SQL Server agent 6.31 FP10 and then tried to create an instance. On the server we run a single instance of SQL Server (default instance) so I would expect it to be discovered with the server hostname as it was in the past. But the "Configure Database Agents” pane discovers and shows one instance with name “MSSQLSERVER” instead of the machine hostname.

There are no errors in the OQ_LocalConfig.log file. Why does it happen ?

Answer:
Abstract: Default instance of SQL Server is identified as 'MSSQLSERVER'
instead of hostname.
Additional Information: The default instance of SQL server used to get
configured with hostname and not MSSQLSERVER.
In an environment, where there was default instance and
a named instance having same name as hostname had issues
in configuration.


IBM ERRORCODE=-4499, The application server rejected establishment of the connection. - United States -4499; JCC; SQL State = 08004; Error Code = -4; 499 TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)

Attempt to connect to a database using Type 4 JCC driver fails with the following exception:

java.sql.SQLException:
[jcc][t4][2057][11264][3.53.95] The application server rejected establishment of the connection. An attempt was made to access a database, <database name>, which was either not found or does
not support transactions. ERRORCODE=-4499,
SQLSTATE=08004 DSRA0010E: SQL State = 08004, Error Code = -4,499

CAUSE
Using DCS DB alias or local alias name of the database in the connection string will cause this error.

RESOLVING THE PROBLEM

The URL format for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity is:

 *  "jdbc:db2://<server name>: <portnumber>/<database name>";

In the Type 4 JDBC JCC driver connection string used,
 *  If the connection is to a DB2 for Linux,Unix,Windows server, the database name should be the Target database name in the database server, it should not be the local alias name cataloged in the client.
 *  If the connection is to a DB2 for z/OS server, database name is the DB2 location name that is defined during installation. All characters in the DB2 location name must be upper-case characters. The IBM Data Server Driver for JDBC and SQLJ does not convert lower-case characters in the database value to upper-case for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity.
 * The location name can be found by executing the following SQL statement on the server:  * SELECT CURRENT SERVER FROM SYSIBM.SYSDUMMY1;

   The target database name can also be found from the DCS directory on the client using the command:  * db2 list dcs directory.

[/support/docview.wss?uid=swg21443723&aid=1] [/support/docview.wss?uid=swg21443723&aid=1]
For further discussion on this topic, visit this developerWorks forum thread:
https://www.ibm.com/developerworks/community/forums/html/topic?id=1cd04237-a9dd-4061-9c38-f9043786691a [https://www.ibm.com/developerworks/community/forums/html/topic?id=1cd04237-a9dd-4061-9c38-f9043786691a]
RELATED INFORMATION
 Type 4 JCC connection String: [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_r0052342.html]

Question:
What could cause a "Connection refused" to SQLDB/DB2 after some time? I have deployed an WAS Liberty/ JPA application. Everything is fine, and after a while (a day or 2), I get the connection refused exception: java.sql.SQLNonTransientException: [jcc][t4][2043][11550][4.14.103] Exception java.net.ConnectException: Error opening socket to server /XX.XXX.XXX.XXXon port 50,000 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499
Any idea what could cause this issue?

Answer: Using DCS DB alias or local alias name of the database in the connection string will cause this error.


IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575) - United States WMB IIB SECURITY BULLETIN

SUMMARY
 The MD5 “SLOTH” vulnerability on TLS 1.2 affects WebSphere Message Broker and IBM Integration Bus

VULNERABILITY DETAILS
CVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]
DESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.
CVSS Base Score: 7.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)

AFFECTED PRODUCTS AND VERSIONS
IBM Integration Bus V9, V10

WebSphere Message Broker V8

REMEDIATION/FIXES
For users of ODBC SSL using the DataDirect drivers:

You might be vulnerable to SLOTH vulnerability, if you have not applied APAR IT09602 released in August 2015. (Please refer the bulletin at
http://www.ibm.com/support/docview.wss?uid=swg21958955 [http://www.ibm.com/support/docview.wss?uid=swg21958955] for more details)

Product VRMF APAR Remediation/Fix IBM Integration Bus V10 IT09602 The APAR is available in fix pack 10.0.0.2 and above. IBM Integration Bus V9 IT09602 The APAR is available in fix pack 9.0.0.5 and above. WebSphere Message Broker

V8
IT09602 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT09602 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT09602]

The APAR is targeted to be available in fix pack 8.0.0.7. For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.

You should verify thst applying this fix does not cause any compatibility issues. The fix prevents the currently-practical SLOTH attack against the RSA-MD5 client authentication. IBM recommends that you avoid using ciphers which use an MD5 or SHA-1 signature hash.

The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :
http://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]

WORKAROUNDS AND MITIGATIONS
None

GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
 Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.

IMPORTANT NOTE
 IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.

REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] ACKNOWLEDGEMENT
Reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France

CHANGE HISTORY
 23 Jan 2016 - Original version Published

*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.

RELATED INFORMATION
 A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977747]

Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Not Applicable AIX, HP-UX, Linux, Solaris, Windows 10.0, 9.0
PRODUCT ALIAS/SYNONYM
 WMB IIB

Question: Help with Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WMB & IIB (CVE-2015-7575) I need to understand details regarding Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575). Where can I find this information?

Answer:
CVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]
DESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.
CVSS Base Score: 7.1
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N)


IBM .NET API error when installing IBM Content Collector (ICC) 4.0.1 - United States ICC; .NET API; CPE 5.2.1.2 TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 A .NET API error is thrown when attempting to install ICC 4.0.1. The error claims that either an incorrect version of the IBM FileNet P8 Content Processing Engine (CPE) .NET API 5.2.1.2 is installed or that it is missing some components.

CAUSE
A corrupt installation of the CPE 5.2.1.2.

DIAGNOSING THE PROBLEM
1. Check in "Programs and features"
2. .NET API will not be listed there

RESOLVING THE PROBLEM
Re-installing the CPE 5.2.1.2 .NET API will solve this issue:

1. Copy the software on a local disk.
2. Start the re-installation of the .NET API.
3. Select all sub-components of .NET framework 45 that were not listed before (select them all if unsure).

During the next installation of ICC there are no further errors regarding missing components.

Question: A .NET API error is thrown when attempting to install ICC 4.0.1 A .NET API error is thrown when attempting to install ICC 4.0.1. The error claims that either an incorrect version of the IBM FileNet P8 Content Processing Engine (CPE) .NET API 5.2.1.2 is installed or that it is missing some components.  How do I fix this?

Answer:
Re-installing the CPE 5.2.1.2 .NET API will solve this issue:

1. Copy the software on a local disk.
2. Start the re-installation of the .NET API.
3. Select all sub-components of .NET framework 45 that were not listed before (select them all if unsure).

During the next installation of ICC there are no further errors regarding missing components.


IBM Using the "reinitialize" CLI command to reconfigure an appliance. - United States datapower; init; initialize; reinitialize; reinit; reset; factory settings; settings; 7993; 7993; 7993; machine type 7993 DPRecovery TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 If you need to reconfigure an IBM WebSphere DataPower SOA appliance you can use the "reinitialize" CLI command.

RESOLVING THE PROBLEM
Note: The appliance should NOT be initialized if sitation described in the technote exists - http://www-01.ibm.com/support/docview.wss?uid=swg21659259 [http://www-01.ibm.com/support/docview.wss?uid=swg21659259] - appliance gets into Fail-Safe mode. It may be necessary to return the appliance to IBM for repair.
The reinit CLI command will allow you to reconfigure an IBM WebSphere DataPower SOA appliance. The reinit CLI command will allow you to delete (not erase) all existing configuration and data from an IBM WebSphere DataPower SOA appliance.

When the reinitialize command completes, your network IP configurations, user accounts and other configuration options, are no longer accessible.

You will only be able to connect to the appliance using the serial connection.

You will need to configure your Ethernet and all other settings again using the information in the product information center available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html].

Important points:

 * Make sure you have a working serial connection to the appliance.

 * The admin password will revert to the initial value of "admin" after the command executes.

 * A firmware image must be on the appliance prior to running the command. The firmware image used for the last upgrade of the device is removed from the file system automatically when the device reboots. Use DataPower's File Management WebGUI option to confirm you have an image or use these CLI commands:
   xi52# configure
   xi52# dir image:
   If an image file is not found, you will need to load a firmware image to the appliance into the image:/// directory. For example: you can use the WebGUI file management options or from the Control Panel, choose the System Control icon, the under Boot Image, choose the firmware file upload options.

 * Use the DataPower File Management to confirm you have sufficient file space. If you don't have sufficient file space, you can delete domains or other files to free up file space to allow the firmware image to be loaded to the appliance.

 * reinit is a CLI command available in the config-flash# mode, for example:

   xi52# configure terminal
   Global configuration mode
   xi52(config)# flash
   Flash configuration mode
   xi52(config-flash)#
   reinit <filename>

   Where <filename> represents a firmware image contained within the image:/// directory. This will be the firmware image which will be installed during the reinit process. For more CLI commands, refere to the following doc link:
   http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/nav/4_4 [http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/nav/4_4]

 * After the appliance reboots:  *  If the firmware image used was for V5 or newer, you will need to accept the license at first logon to the WebGui Configure the appliance per the instructions in the appliances configuration guide. This and other documentation on the appliance is available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html].

The command is documented in the information center. This and other documentation on the appliance is available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html].

If your appliance has the optional RAID (hard drives) reinitialize the RAID using the information in our RAID technote [http://www.ibm.com/support/docview.wss?uid=swg21358544].

If your appliance has the optional HSM, reinitialize the HSM following the instructions in our HSM book or infocenter for your release of the product. These are available on our library page [http://www.ibm.com/software/integration/datapower/library/documentation/].

Cross reference information Segment Product Component Platform Version Edition Business Integration IBM DataPower Gateway Virtual Edition Business Integration IBM DataPower Gateways

Question: How do I downgrade an IBM Gateway, DataPower, appliance to a lower major firmware release? I would like to know the proper, and supported, method to downgrade an appliance to prevent any issues or problems.

Answer: The reinit CLI command will allow you to reconfigure an IBM WebSphere DataPower SOA appliance. The reinit CLI command will allow you to delete (not erase) all existing configuration and data from an IBM WebSphere DataPower SOA appliance.


IBM Security Bulletin: The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings (CVE-2016-6080) - United States WMB IIB SECURITY BULLETIN

SUMMARY
 The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings.

VULNERABILITY DETAILS
CVEID: CVE-2016-6080 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6080]
DESCRIPTION: The WebAdmin context for WebSphere Message Broker allows directory listings, which could disclose sensitive information to the attacker.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117560 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117560] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)

AFFECTED PRODUCTS AND VERSIONS
WebSphere Message Broker V8

REMEDIATION/FIXES

Product VRMF APAR Remediation/Fix WebSphere Message Broker V8 IT16698 The APAR is available in Fix Pack 8.0.0.8
https://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925]

For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.
The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :
http://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]

WORKAROUNDS AND MITIGATIONS
None

GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
 Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.

IMPORTANT NOTE
 IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.

REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]

RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]

CHANGE HISTORY
 1 Dec 2016 - Original version published

*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.

PRODUCT ALIAS/SYNONYM
 WMB IIB

Question:
Help with Security Bulletin: The WebAdmin context for WMB V8 allows directory listings (CVE-2016-6080)

I need to understand details regarding Security Bulletin: The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings (CVE-2016-6080). Where can I find this information?
  0

Answer:
CVEID: CVE-2016-6080 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6080]
DESCRIPTION: The WebAdmin context for WebSphere Message Broker allows directory listings, which could disclose sensitive information to the attacker.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117560 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117560] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)


IBM Generating Java diagnostic dumps for IBM Integration Bus - United States mqiinfo; java dumps; java core; core; force TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Use the procedures below to collect java diagnostics dumps from IBM Integration Bus (IIB).

Java diagnostic dumps contain:
- all Java threads running in a process (Java core or javacore files)
- objects populating the heap space (Heap dump or heapdump files)
- tracepoint information (Snap trace or snaptrace files)
- internal system information (System dump)

These files can be used to diagnose problems such as lock conditions, loops, or memory allocation in Java code.

Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.

RESOLVING THE PROBLEM

JAVACORE DUMP INSTRUCTIONS

New javacore dump commands have been made available from IIB v10.0.0.9, onwards.
- The new procedure uses the mqsichangeproperties command.
- The old procedure uses a custom message flow, and is only applicable for operating systems that use the IBM JRE.

Note:
Collection of Java core dumps is an invasive activity and will impact the performance of the Integration Server process.

JAVA DUMP COMMAND FOR IIB V10.0.0.9+
Use this command to generate a Java dump on IIB v10.0.0.9+:
mqsichangeproperties <Int.Node> -e <Int.Server> -o ComIbmInternalSupportManager/Java/JVM -n dump -v <dump_type>

The following dump types are supported:

All Platforms

-v heap Produces a Java Heap dump

IBM JRE Platforms (All platforms except HP and Solaris) -v core Produces a javacore -v system Produces a system dump -v all Produces a heapdump, javacore, and system dump
Dump files are output to $MQSI_WORKPATH/common/errors

JAVA DUMP PROCEDURE FOR IIB PRIOR TO V10.0.0.9
Use this procedure to create an IIB message flow that will trigger a Java dump for an Integration Server:

1. Create a new message flow containing an Input node and a JavaCompute node.
2. In the JavaCompute node, call the method 'com.ibm.jvm.Dump.JavaDump()'.
3. Deploy your message flow to the target Integration Server.
4. Recreate the conditions that necessitate the Java dump.
5. Invoke your message flow by sending a message to the Input node.
6. The dump files should be output to $MQSI_WORKPATH/common/errors.

Note:
This procedure requires the use of the IBM JRE.
Therefore, it is not suitable on Solaris or HP platforms which do not use the IBM JRE.

RELATED INFORMATION
 Triggering a java dump [http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.win.70.doc/diag/tools/javadump_trigger.html]
Enabling a java dump [http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.lnx.70.doc/diag/tools/javadump_enable.html]

PRODUCT ALIAS/SYNONYM
 WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI IIB

Question:
How can I obtain a Java thread dump against an execution group in IIB v10?

This Q&A is abstracted from a PMR

How can I obtain a Java thread dump against an execution group in IIB v10?

Answer:
Use this command to generate a Java dump on IIB v10.0.0.9+:
mqsichangeproperties <Int.Node> -e <Int.Server> -o ComIbmInternalSupportManager/Java/JVM -n dump -v <dump_type>


IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States   A FIX IS AVAILABLE
Fixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]

SUBSCRIBE
You can track all active APARs for this component.

APAR STATUS
 * CLOSED AS PROGRAM ERROR.

ERROR DESCRIPTION
 *  During Portal Start-Up following error is shown:
   --------------------
   0000005e MBeanStarter  E com.ibm.wps.

   scripting.server.MBeanStarter loadExtensions failed to load
   extension:
   key: ServerExt.applications / value:
   com.ibm.wps.scripting.server.
   ApplicationServerExtensions

LOCAL FIX
 *  1) open the WAS admin console
   2) navigate to Resources > Resource environment providers > WP
   ScriptingService > Custom properties
   3) you should see an entry with the name
   "ServerExt.applications" and value
   "com.ibm.wps.scripting.server.ApplicationServerExtensions"
   4) delete this entry, save and restart the server.

PROBLEM SUMMARY
 *  A code fix for this issue is integrated into the WebSphere
   Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal
   8.5.0.0 available from Fix Central:

   http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent
   =ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al]
   l&platform=All&function=aparId&apars=PI31198

PROBLEM CONCLUSION
 *  Added a task to remove the outdate resource environment
   provider entry.

TEMPORARY FIX

COMMENTS

APAR INFORMATION
 * APAR NUMBER
   PI34677

 * REPORTED COMPONENT NAME
   WEBSPHERE PORTA

 * REPORTED COMPONENT ID
   5724E7600

 * REPORTED RELEASE
   850

 * STATUS
   CLOSED PER

 * PE
   NoPE

 * HIPER
   NoHIPER

 * SPECIAL ATTENTION
   NoSpecatt

 * SUBMITTED DATE
   2015-02-10

 * CLOSED DATE
   2015-03-10

 * LAST MODIFIED DATE
   2015-03-10

 * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:

 * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:

FIX INFORMATION
 * FIXED COMPONENT NAME
   WEBSPHERE PORTA

 * FIXED COMPONENT ID
   5724E7600

APPLICABLE COMPONENT LEVELS
 * R850 PSY
   UP

Question:
Error: "MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION" occurs at portal startup

We are using Portal Server 8.5 and when starting the Portal server we see following error:

0000005e MBeanStarter E com.ibm.wps.scripting.server.MBeanStarter loadExtensions failed to load extension: key: ServerExt.applications / value: com.ibm.wps.scripting.server.ApplicationServerExtensions

How can we resolve this error without installing a fix?

Answer:
1) open the WAS admin console
   2) navigate to Resources > Resource environment providers > WP
   ScriptingService > Custom properties
   3) you should see an entry with the name
   "ServerExt.applications" and value
   "com.ibm.wps.scripting.server.ApplicationServerExtensions"
   4) delete this entry, save and restart the server.