| Author |
Message
|
| Lindy |
 Posted: Tue Apr 15, 2008 11:55 am Post subject: MQv6.0 AMQ4733 error on XP Pro SP2 |
 |
|
Novice
Joined: 08 Apr 2008
Posts: 19
|
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Apr 16, 2008 12:49 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Any orphan Registry entries from the last uninstall/reinstall attempts?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Lindy |
| Posted: Wed Apr 16, 2008 4:27 am Post subject: exerk |
|
|
Novice
Joined: 08 Apr 2008
Posts: 19
|
Can't say I've ever seen this either. I cleaned up the registry remnants from v6.1 and previous attempts at 6.0.
Also tried installing from the command line with the "ignore" GSKit variable as shown in another item I found here in the forum.
http://www.mqseries.net/phpBB2/viewtopic.php?t=41307&sid=c340efa058ea37f93e8001d4f6ff92e9
I got past the GSKit noise but now it's hanging when registering dotnet.
1: 19:27:44 MQCA iwiRegisterDotNet info: Property 'AMQPGMFOLDER' value 'D:\Program Files\IBM\WebSphere MQ\'; from CustomActionData
1: 19:27:44 MQCA iwiRegisterDotNet info: Property 'AMQREMOVE' value '0'; from CustomActionData
1: 19:27:44 MQCA iwiRegisterDotNet info: Property 'AMQTEMP' value 'C:\DOCUME~1\GKLARM~1\LOCALS~1\Temp'; from CustomActionData
1: 19:27:44 MQCA iwiRegisterDotNet info: Calling dotNet registration utility: 'D:\Program Files\IBM\WebSphere MQ\bin\amqidnet.exe' with parameters '/c "D:\Program Files\IBM\WebSphere MQ\bin\amqidotn.txt" /l "C:\DOCUME~1\GKLARM~1\LOCALS~1\Temp\amqidotn.log"'
1: 19:27:44 MQCA iwiRegisterDotNet info: Launching process 'D:\Program Files\IBM\WebSphere MQ\bin\amqidnet.exe' '/c "D:\Program Files\IBM\WebSphere MQ\bin\amqidotn.txt" /l "C:\DOCUME~1\GKLARM~1\LOCALS~1\Temp\amqidotn.log"'; dir 'D:\Program Files\IBM\WebSphere MQ\bin'. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 16, 2008 4:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
OK...a few questions:
1. Which Windows OS and Service Pack?
2. Anything in Event Viewer related to the install?
3. Is the laptop stand-alone or subject to domain policies?
There is also the possibility that some left-over files remain from the last install/uninstall. When I've had problems in the past I have:
1. Cleared out all orphan Registry entries (back it up first!)
2. Removed any WMQ-related environment variables
3. Removed any files starting 'amqi...' from the C:\DOCUME~1\<USER>~1\LOCALS~1\Temp\ directory (moved or renamed, not deleted)
4. Rebooted
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Lindy |
| Posted: Wed Apr 16, 2008 6:23 am Post subject: |
|
|
Novice
Joined: 08 Apr 2008
Posts: 19
|
exerk,
I'm going to try your recommendations. If you have any additional thoughts based on the information below, by all means let me know.
Thanks
In the meantime, here's answers to your questions:
1 Windows XP Build 2600: Service Pack 2
3 Standalone
2 Yes, some application log Errors pointing to several FDK files in the MQ errors directory
An internal WebSphere MQ error has occurred.
An error has been detected, and the MQ error recording routine has been called.
Details of the error have been stored at D:\Program Files\IBM\WebSphere MQ\errors\AMQ2900.1.FDC. A synopsis is given in the data section below. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
In summary:
Four FDC files where generated at the same time with the same info below followed by a hex dump
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (WinNT error 3 from CreateFile.) |
| FDCSequenceNumber :- 0 |
| Comment1 :- WinNT error 3 from CreateFile. |
| |
| Comment2 :- The system cannot find the path specified. |
| |
| |
+-----------------------------------------------------------------------------+
| Major Errorcode :- MPERF_UNABLE_READ_FIRST_COUNTER |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ7894 |
| Probe Severity :- 2 |
| Probe Description :- AMQ7894: Unable to read the "Performance\First |
| Counter" value for WebSphere MQ services. Status code: 2. |
| FDCSequenceNumber :- 1 |
| Arith1 :- 2 2 |
| |
+-----------------------------------------------------------------------------+
There were two other files in the error dir from when I ran the GSKit technote solution 1
FDC file
Major Errorcode :- rrcE_SSL_REGISTRY_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9748 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9748: A problem occurred accessing the Windows |
| registry. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2 2 |
| Comment1 :- RegQueryValueEx |
| |
| |
+-----------------------------------------------------------------------------+
AMQERRLOG file
4/15/2008 17:11:04 - Process(5172.1) User(gklarmann) Program(runmqckm.exe)
AMQ9748: A problem occurred accessing the Windows registry.
EXPLANATION:
An attempt to access a key or value or data field in the Windows registry key
failed. The failure may be due to part of the registry being in an invalid
state or may be due to insufficient authority to access that part. The
WebSphere MQ error recording routine has been called.
ACTION:
If 'RegQueryValueEx' includes the name of a Windows call, consult the Windows
reference manual to determine the meaning of status 2 for that call. Use the
standard facilities supplied with your system to record the problem identifier,
and to save the generated output files. Contact your IBM support center. Do not
discard these files until the problem has been resolved.
----- amqxfdcp.c : 735 --------------------------------------------------------
4/15/2008 17:11:04 - Process(5172.1) User(gklarmann) Program(runmqckm.exe)
AMQ6183: An internal WebSphere MQ error has occurred.
EXPLANATION:
An error has been detected, and the WebSphere MQ error recording routine has
been called. The failing process is process 5172.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
----- amqxfdcp.c : 779 -------------------------------------------------------- |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 16, 2008 6:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You are doing the install as an Administrator, right?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 16, 2008 6:41 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Lindy wrote: |
Major Errorcode:- xecF_E_UNEXPECTED_SYSTEM_RC
Comment1:- WinNT error 3 from CreateFile.
Comment2:- The system cannot find the path specified.
Major Errorcode:- MPERF_UNABLE_READ_FIRST_COUNTER
Probe Description:- AMQ7894: Unable to read the "Performance\First Counter" value for WebSphere MQ services. Status code: 2.
Major Errorcode:- rrcE_SSL_REGISTRY_ERROR
Probe Description:- AMQ9748: A problem occurred accessing the Windows registry.
AMQ9748: A problem occurred accessing the Windows registry.
EXPLANATION:
An attempt to access a key or value or data field in the Windows registry key failed. The failure may be due to part of the registry being in an invalid state or may be due to insufficient authority to access that part. |
Were these cut during the last install attempt?
One other thing I forgot to put in my list of things (apologies!), so reproduced in full below:
1. Cleared out all orphan Registry entries (back it up first!)
2. Removed any WMQ-related environment variables
3. Removed any files starting 'amqi...' from the C:\DOCUME~1\<USER>~1\LOCALS~1\Temp\ directory (moved or renamed, not deleted)
4. Removed any users/groups created during the install
5. Rebooted
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Lindy |
| Posted: Wed Apr 16, 2008 6:47 am Post subject: |
|
|
Novice
Joined: 08 Apr 2008
Posts: 19
|
jefflowrey,
Yes, I'm using administrator.
exerk,
Yes, snippets (except the registry ones) are from last attempt. Registry ones are from a prior attempt to execute a "solution" from the AMQ4733 technote
All,
I'm looking at path and it seems I have some env remnants pointing to the C: drive while I'm trying to install to D:
I'll let you know how it comes out.
Thanks |
|
| Back to top |
|
|
| Lindy |
| Posted: Wed Apr 16, 2008 9:52 am Post subject: |
|
|
Novice
Joined: 08 Apr 2008
Posts: 19
|
| Does anyone have a definitive list of all the registry entries made by MQ v6.0 & v6.1? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Apr 16, 2008 6:35 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
|
| Back to top |
|
|
| Lindy |
| Posted: Thu Apr 17, 2008 6:50 pm Post subject: |
|
|
Novice
Joined: 08 Apr 2008
Posts: 19
|
Thanks to all who helped me out with this issue. As promised, here's the solution from working w/ IBM Tech Support.
Hopefully this will help the next person with the same issue. Key points in bold
To get MQ out of Purgatory (remnants installed but not fully installed according to add / remove software)
Next, please follow the link to download and run this tool AFTER backing up the registry to cleanup the last MQ install: http://support.microsoft.com/kb/290301
After running ms installer cleanup, remove files left over and cleanup MQ path values and env vars
Next remove the RUNMQDNM entries from the registry <didn't do this>
Next, Follow these instruction:
2) At the point where/if it hangs first record and then change the registry key
HKCR\CLSID\CLBVersion to a value of hex 14 <had to reboot machine and complete following steps>
Before installing, to get past the GSKit7win.exe amq4733 error by skipping GSKit in normal install and installing manually afterwards:
1) Install MQ with AMQINSTALLGSKIT set to '0'. (ie <Installable_Path>\setup.exe AMQINSTALLGSKIT=0)
2) Before proceeding with the Prepare Websphere MQ Wizard, install GSKit manually according to the instructions provided below:
2.1) Unpack the GSKit.exe to a temp folder as below :
\MSI\gskit\gsk7win.exe -f "Destination_Path"
So all the files will be extracted to the Destination_Path folder. Here we assume Destination_Path as
"C:\Temp\gskit".
2.2) Install the GSKit using the following command (from the Destination_Path as in step 1):
setup.exe AMQWMQ60 "C:\Program Files" -SMS -s -f1"C:\Temp\gskit\setup.iss" 1>"C:\Temp\amqt0001.txt" 2>&1'; dir 'C:\Temp\gskit'
3) Copy the string value of 'InstallPath' at HKLM->Software->IBM->GSK7->CurrentVersion to the String value of
'GSKitPath' at the registry key HKLM->Software->IBM->MQSeries->CurrentVersion.
To get past the dotnet registration hang issue
Started Distributed Transaction Coordinator service. (was not runnng)
Started COM+ Event System. (was not running)
Started ASP.NET State Service (was not running)
Shut down all Windowed applications.
Cleaned out %TEMP% folder of log files from previous installs.
Uninstalled Eclipse which was installed from previous install attempts.
Launched install.
Reinstalled Eclipse.
Installed MQ 6.0 (it went smoothly this time).
Installed FixPack 6.0.2.3 .
4) After that I changed the registry key back to it's original value
that you noted above |
|
| Back to top |
|
|
|
|
