| Author |
Message
|
| bkissinger |
 Posted: Wed Mar 10, 2004 8:41 am Post subject: amqdnet.dll installation problem |
 |
|
Newbie
Joined: 10 Mar 2004
Posts: 6
|
Hi,
we installed the WebsphereMQ-Client-Software 5.3 for Windows2000, which comes along with a file
amqdnet.dll, which contains the .net classes for WebsphereMq.
Unfortunately we could not register the dll in the global assembly cache with gacutil. We got the message "Strong name signature could not be verified. Was the assembly built delay-signed?".
Installing the dll in the GAC is required and is described in the README of the Client-Software.
How can this problem be solved?
Greetings,
Bernd |
|
| Back to top |
|
 |
| brad_blackmon |
| Posted: Wed Mar 10, 2004 9:25 am Post subject: |
|
|
Newbie
Joined: 04 Mar 2004
Posts: 4
Location: Washington, D.C.
|
Which service pack are you running? I have CSD05 installed, and the following works fine:
| Code: |
C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin>gacutil /i "C:\Program Files\IBM\WebSphere MQ\CSD05\pgm\bin\amqmdnet.dll"
Microsoft (R) .NET Global Assembly Cache Utility. Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.
Assembly successfully added to the cache |
|
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Mar 10, 2004 2:09 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
This is a bug of the fixpack 5 client MACV install image, and is (will be?) fixed in the fixpack 6 client install image when it is released (it might be released already, I dont know).
As a workaround, copy from the unpacked source tree the amqmdnet.dll into the bin directory, then it will register ok. This ONLY affects client only installs from the client install package directly at the fp5 level (ie not client installs from server cds and then upgrades) |
|
| Back to top |
|
|
| MikeClark |
| Posted: Thu Mar 11, 2004 10:38 am Post subject: Huh? |
|
|
Apprentice
Joined: 17 Feb 2004
Posts: 27
Location: Olympia, WA
|
| JasonE wrote: |
| This is a bug of the fixpack 5 client MACV install image, and is (will be?) fixed in the fixpack 6 client install image when it is released (it might be released already, I dont know). |
I checked yesterday and the note on this bug says the note will be modified when a fix is available, so apparently it isn't fixed yet.
| JasonE wrote: |
| As a workaround, copy from the unpacked source tree the amqmdnet.dll into the bin directory, then it will register ok. This ONLY affects client only installs from the client install package directly at the fp5 level (ie not client installs from server cds and then upgrades) |
Not sure what you mean. Copy amqmdnet.dll into which bin directory, and it will register OK? Do you mean that I'll be able to put it into the gac?
Presently, the amqmdnet.dll file is in the program files\ibm\webspheremq\bin file, and that is where I point the reference to in the project. When I run the app I get a machine.config error saying "The check of the signature failed for assembly 'amqmdnet'".
_________________
"...a long habit of not thinking a thing wrong, gives it a superficial appearance of being right..." [Tom Paine] |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Mar 12, 2004 4:25 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
If you download macv you get a self extracting and then launching exe. After the self extract, you have in eg. c:\program files\ibm\source an extracted install image. In there is a bin directory with amqmdnet.dll which is fine. During install, MSI attempts to modify the dll which causes problems because of the strong signing.
Therefore copy the unmodified source amqmdnet.dll into the client bin directory after install. You can then put it into the GAC without problems |
|
| Back to top |
|
|
| MikeClark |
| Posted: Fri Mar 12, 2004 5:31 pm Post subject: |
|
|
Apprentice
Joined: 17 Feb 2004
Posts: 27
Location: Olympia, WA
|
Yes! That did it. Thanks very much!
For anyone coming afterwards who might not catch this at the right point (as I did not the first time)...
Run the self-extract, but when it comes to the point of asking if you want to install it, click Cancel. You can then run
| Code: |
| gacutil /if [path_to_dll]\amqmdnet.dll |
And it will successfully install it into the GAC, as stated.
_________________
"...a long habit of not thinking a thing wrong, gives it a superficial appearance of being right..." [Tom Paine] |
|
| Back to top |
|
|
| JasonE |
| Posted: Sun Mar 14, 2004 2:29 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
np. The only comment I would say is that it would be better if you cancel, then rather than register the dll from the unpacked directory, you copied it over the corrupted version in the bin directory, and registered it there.
Dont forget any fixpack install needs you to manually re-register this dll in the GAC. Fixpack installs dont suffer from the corruption problem though and hence the version in the bin directory post-fixpack install should register just fine.
Any new version of the MACV support pack will have this fixed, and as I thought before, the fp6 one does in fact have this fix in it when it gets released. |
|
| Back to top |
|
|
| sywahu |
| Posted: Wed Jul 14, 2004 2:21 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2004
Posts: 9
|
Jason - We are just installing CSC07 on our machine.
In your experience, do we still need to do the gacutil business? Or does the install handle everything smoothly now?
Cheers
Sy. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Jul 14, 2004 3:21 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Nope - the 5.3 fixpack installer cannot cope with .net assemblies and so after every fixpack you will need to manually register.
This should be resolved if/when we ever ship a new release of MQ, as I understand it, not before. (But dont hold me to this).
Its as frustrating to me as it is you - so many of the problems we see relate to people not reregistering! |
|
| Back to top |
|
|
|
|
