Event ID - 7886

Event Id7886
SourceWebSphere MQ
DescriptionUnable to create queue manager FOOQueue manager FOO could not be created. WebSphere MQ returned error 71.
Event Information
CAUSE:
The MUSR_MQADMIN userid under which WebSphere MQ was running had been granted full control of ""C:\Program Files\IBM\WebSphere MQ"" and its subdirectories, but no authority to the higher level directories.

RESOLUTION:
Add MUSR_MQADMIN to the Administrators group.
Additional information:
In addition to the errors in the WebSphere MQ error log, FDCs are also generated. You can check the FDC to see if it matches the one below.
WebSphere MQ First Failure Symptom Report
=========================================
1.Date/Time :- Wed January 08 14:56:43 EST 2003
2.Host Name :- JTF (NT Version 5.0 Build 2195: SP2)
3.PIDS :- 5724B4101
4.LVLS :- 530
5.Product Long Name :- WebSphere MQ for Windows
6.Vendor :- IBM
7.Probe Id :- XC207001
8.Application Name :- MQM
9.Component :- xxxInitialize
10.Build Date :- Jun 17 2002
11.CMVC level :- p000-L020617
12.Build Type :- IKAP - (Production)
13.UserID :- MUSR_MQADMIN
14.Process Name :- C:\Program Files\IBM\WebSphere
MQ\bin\amqmsrvn.exe
15.Process :- 00001268
16.Thread :- 00000002
17.Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC
18.Minor Errorcode :- OK
19.Probe Type :- MSGAMQ6119
20.Probe Severity :- 2
21.Probe Description :- AMQ6119: An internal WebSphere MQ error
has occurred (WinNT error 5 from
RegQueryValueEx.)
22.FDCSequenceNumber :- 0
23.Comment1 :- WinNT error 5 from RegQueryValueEx.
24.Comment2 :- Access is denied.
Reference LinksEvent ID:7886 Of Source ID:WebSphere MQ

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.