Advice for dealing with some common problems that can arise when you start resources other then a broker or the Configuration Manager.
ServiceName - DLL initialization failure Initialization of the
dynamic link library c:\windows\system32\user32.dll failed.
The process is terminating abnormally.
If the check fails, your WebSphere MQ installation is incomplete. This error occurs typically because you have previously installed WebSphere Application Server, which installs an embedded WebSphere MQ component that does not support WebSphere Event Broker.
Uninstall WebSphere Application Server, then install the full WebSphere MQ product that is provided with WebSphere Event Broker.
If the Default Configuration wizard does not remove the default configuration completely, a Wizard failure window opens with instructions on where to find the wizard's log. Take the following steps:
mqsistop WBRK6_DEFAULT_CONFIGURATION_MANAGER
mqsistop WBRK6_DEFAULT_BROKER
mqsideletebroker WBRK6_DEFAULT_BROKER -w
The -w parameter deletes all files related to this broker from the associated workpath.
mqsideleteconfigmgr WBRK6_DEFAULT_CONFIGURATION_MANAGER -w -q -n
The -q parameter deletes the queue manager, so do not use this parameter if you have not already deleted the broker. The -w parameter deletes all files related to the Configuration Manager from the associated workpath and the -n parameter deletes the configuration repository.
db2 disconnect DEFBKDB6 db2 drop DEFBKDB6
mqsideletedb DEFBKDB6
endmqlsr -w -m WBRK6_DEFAULT_QUEUE_MANAGER endmqm -i WBRK6_DEFAULT_QUEUE_MANAGER dltmqm WBRK6_DEFAULT_QUEUE_MANAGER
If the Quick Tour is not displayed correctly through the information center, you can view it by opening this file in a browser that has the Adobe Flash Player installed: evtoolkit\eclipse\plugins\com.ibm.etools.mft.quicktour.doc_6.0.0\quick_tour\quick_tour.html.
BIP0832E: A class java.io.FileNotFoundException exception occurred which reported the following message: [filepath] (The process cannot access the file because it is being used by another process). Resolve the reason of error and try again.
S STU3053 $HASP100 STU3053 ON STCINRDR IEF695I START STU3053 WITH JOBNAME STU3053 IS ASSIGNED TO USER STU3 , GROUP STCGROUP $HASP373 STU3053 STARTED +(broker53) 0 BIP9141W: The component was started. +(broker53) 0 BIP2001I: The WebSphere Business Integration Message Broker service has started process ID 33554919. +(broker53.default) 0 BIP2201I: Execution Group started: process '67109 442 196'; thread '0'; additional information 'broker53', '76eb7f2d-e800-00 00-0080-974c271866d2', 'default', 'true', 'Q4A3', 'false', 'ARG5D651', 'ARGO53', '********', 'false', 'f9c27f2d-e800-0000-0080-974c271866d2' , '/local/argo/driver/drv3', '/local/argo/tgrp53/broker53'. +(broker53.default) 0 BIP9137I: A work manager has been registered by R 443 RMS registration services, work manager name is BIP.STU30532.006710919 6.IBM.UA .
D OMVS,U=STU3 BPXO040I 18.49.59 DISPLAY OMVS 446 OMVS 000E ACTIVE OMVS=(68,05) USER JOBNAME ASID PID PPID STATE START CT_SECS STU3 STU30531 0069 33554696 33554919 HR 18.49.15 2.217 LATCHWAITPID= 0 CMD=bipbroker broker53 STU3 STU30532 03FD 67109196 67109222 HR 18.49.23 19.816 LATCHWAITPID= 0 CMD=DataFlowEngine broker53 76eb7f2d-e800-00 STU3 STU3053 0036 33554768 83886483 HRI 18.49.08 .653 LATCHWAITPID= 0 CMD=bipservice Q4A3BRK AUTO STU3 STU30532 03FD 67109222 33554696 1W 18.49.23 19.816 LATCHWAITPID= 0 CMD=bipimain DataFlowEngine broker53 76eb7f2 STU3 STU3053 0036 83886483 1 1WI 18.49.08 .653 LATCHWAITPID= 0 CMD=/local/argo/driver/drv3/bin/bipimain bip STU3 STU30531 0069 33554919 33554768 1W 18.49.15 2.217 LATCHWAITPID= 0 CMD=bipimain bipbroker broker53
The infrastructure main program bipimain is the first process in every address space. It starts bipservice, bipbroker, DataFlowEngine, or bipuns as the second process in the same address space. For each execution group, an additional address space is started. In this example, only one execution group is available.
verbx vsmdata,'noglobal,jobname(vcp0brk2)'where vcp0brk2 is the name of the failing job.
BIP2604E: Node failed to open WebSphere MQ queue [queue name] owned by queue manager [queue manager name]This message is output every 30 minutes.
In this case, a message flow node fails to connect to the indicated WebSphere Event Broker queue manager that is associated with the input queue, because the serialization token that it passed is already in use within the queue sharing group.
This message is for information only. It indicates that serialization is occurring when two or more message flow input nodes try to connect to a queue manager to get messages from a shared queue.
BIP8026E: Unable to start the component. The component could not be started using the service userid that was supplied when the component was created. Ensure that the service userid and password are still valid. Ensure that the service userid has permission to access all of the products directories, specifically the 'bin' and 'log' directories. Check for system messages (on Windows NT this would be the application event log).
For example, if you specify NTSecurityDomainName (on the -d parameter on the mqsicreatebroker command) as NYBROKER on local system \\NYBROKER, the service user ID on the -i parameter on the mqsicreatebroker command cannot be nybroker.
Delete your User Name Server and re-create it using another user ID that has the correct authorizations.
ICH408I USER(TASKID1 ) GROUP(TSOUSER ) NAME(FRED (FRED) 959 /argo/MA11BRK/ENVFILE CL(DIRSRCH ) FID(01D7C7E2E3F0F8000F16000000000003) INSUFFICIENT AUTHORITY TO LOOKUP ACCESS INTENT(--X) ACCESS ALLOWED(OTHER ---) IEE132I START COMMAND DEVICE ALLOCATION ERROR IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=00A8. D J,BPXAS IEE115I 11.13.04 2001.212 ACTIVITY 601In this example, the started task ID does not have access to the file system component. The ICH408I message shows:
You can use this information to correct the permissions and then reissue, in this example, the start broker request. This type of message is produced if the user who is issuing the command (which might be to start the broker, or to submit JCL to start one of the utility jobs) does not have the correct file system permissions for the file system component. Use the ICH408I information to rectify the problem.
Another possible reason for authorization failures is inconsistencies in the RACF definitions for a user ID in the MVS image and the OMVS segment. You should also check with your system administrator that the RACF ID that is used on MVS has a corresponding OMVS image created.