| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| amqtcert failed after migrate to MQ 6. |
« View previous topic :: View next topic » |
| Author |
Message
|
| DTran |
 Posted: Wed Feb 13, 2008 2:43 am Post subject: amqtcert failed after migrate to MQ 6. |
 |
|
Acolyte
Joined: 11 May 2006
Posts: 62
Location: Amsterdam
|
Hi all,
I have tried to migrate the SSL certs but it fails every try, could some one help me out? This is my situation. I have a queue manager and i use MO71 to monitor all other qmgrs. Both are secured with SSL. On version 5.3 it works fine, but after migration it failed.
H:\>amqtcert -l -a
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
QUEUE MANAGERS:
Queue Manager Name: AMSTERDAM
Expiry Time: 365
Migration Status: Failed
Password: ********
CLIENTS:
Client Certificate Store: c:\certificates\prod\key
Expiry Time: 365
Migration Status: Failed
Password: ********
The Transfer Certificates (amqtcert) command has completed.
qmgr is not running
H:\>dspmq -m AMSTERDAM
QMNAME(AMSTERDAM) STATUS(Ended immediately)
when i try to migrate:
H:\>amqtcert -g "c:\program files\ibm\websphere mq\qmgrs\AMSTERDAM\ssl\key" -w "
c:\program files\ibm\websphere mq\qmgrs\AMSTERDAM\ssl\key" -p ****** -m AMSTERDAM
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
AMQ9750: File 'c:\program files\ibm\websphere mq\qmgrs\AMSTERDAM\ssl\key.kdb'
already exists.
AMQ9750: File 'c:\program files\ibm\websphere mq\qmgrs\AMSTERDAM\ssl\key.sth'
already exists.
Certificate migration has completed with some failures. The number of
certificates migrated was 0.
The Transfer Certificates (amqtcert) command has completed.
After that I start the qmgr and check the cert again, and it failed
H:\>strmqm AMSTERDAM
WebSphere MQ queue manager 'AMSTERDAM' starting.
5 log records accessed on queue manager 'AMSTERDAM' during the log replay phase.
Log replay for queue manager 'AMSTERDAM' complete.
Transaction manager state recovered for queue manager 'AMSTERDAM'.
WebSphere MQ queue manager 'AMSTERDAM' started.
H:\>amqtcert -l -a
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
QUEUE MANAGERS:
Queue Manager Name: AMSTERDAM
Expiry Time: 365
Migration Status: Failed
Password: ********
CLIENTS:
Client Certificate Store: c:\certificates\prod\key
Expiry Time: 365
Migration Status: Failed
Password: ********
The Transfer Certificates (amqtcert) command has completed.
What have i done wrong 
thnx for your time
Tran
_________________
There are 10 types of people in this world - those who understand binary and those who don't |
|
| Back to top |
|
 |
| starship |
| Posted: Mon Feb 18, 2008 8:07 pm Post subject: |
|
|
Apprentice
Joined: 07 Dec 2005
Posts: 33
Location: INDIA
|
Hi,
Please tell me, which version of MQ are you migrating ie. 6.0.0.0 or 6.0.2.1.
Also when you are trying to migrate manually, the only file which should exist in the C:\Program Files\IBM\Websphere MQ\Qmgrs\QMNAME\ssl is key.sto.
You may copy the other files (eg Key.kdb..etc) from the above directory and move them to some temp folder.
After you have only key.sto, then try with Manual Migration command.
Cheers |
|
| Back to top |
|
|
| DTran |
| Posted: Thu Feb 21, 2008 4:18 am Post subject: |
|
|
Acolyte
Joined: 11 May 2006
Posts: 62
Location: Amsterdam
|
Hi starship,
I try to migrate to version 6.0.2.3 and I did tried to migerate with only key.sto in the folder and it didn't help. I have raise a pmr at IBM hopefully I will get the answer soon.
_________________
There are 10 types of people in this world - those who understand binary and those who don't |
|
| Back to top |
|
|
| starship |
| Posted: Tue Feb 26, 2008 1:15 am Post subject: |
|
|
Apprentice
Joined: 07 Dec 2005
Posts: 33
Location: INDIA
|
Hi,
Please advise us of what solution you get from IBM.
6.02.3 shouldn't have any problem, 6.0.2.1 did have problem because it used to corrupt the key.kdb.
regards
Akshat |
|
| Back to top |
|
|
| DTran |
| Posted: Wed Mar 12, 2008 6:12 am Post subject: |
|
|
Acolyte
Joined: 11 May 2006
Posts: 62
Location: Amsterdam
|
Well, I got the reply back from IBM.
All yo need to do is re-import the signer certificate to the personal certificate again and it should works. Still I don't know if it is a bug in the amqtcert or because I am using Windows. 
Once I got my hands on the AIX machine I will try the migration again
_________________
There are 10 types of people in this world - those who understand binary and those who don't |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
