| Author |
Message
|
| IbrahimM |
 Posted: Wed Jul 19, 2006 9:48 am Post subject: vb.net program could not find a definition |
 |
|
Newbie
Joined: 19 Jul 2006
Posts: 3
|
Our Environment;
Server: Win 2003
MQ Series 6 Server
Client Wnin2k Pro
MQ Series 6 Client
Dev Platform VS2005
Error Log on Server:
The requested operation failed because the program could not find a definition
of channel 'tstsvr01connect'.
Obviously, the client software is working with net 2.0 or the attempt to connect to the Que wouldn't even get to the server. (or at least it seems obvious to me )
The names are correct, case is correct. Client Channel just can't be found it seems. We are complete novices at MQ and are hoping that this is something real stupid and will be pointed out quickly by someone here 
The faileure is at this line of code:
MyQM = New MQQueueManager("QM_tstsvr01")
thanks for any help
Ibrahim |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jul 19, 2006 1:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Use the Search function for this forum - this has been discussed before in here. There have been problems reported with .NET 2.0 (which is not officially supported as I understand it). I think you need .NET 1.1 (but it's not really my thing)
I'd also not be too convinced that the error proves connection. If you'd got through to the queue manager I'd have hoped for a reason code...
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| IbrahimM |
| Posted: Thu Jul 20, 2006 3:40 am Post subject: |
|
|
Newbie
Joined: 19 Jul 2006
Posts: 3
|
I'm sorry, did I leave out the error number? here is the entire entry below:
7/19/2006 15:39:05 - Process(464.3) User(mqmsvc) Program(amqrmppa.exe)
AMQ9519: Channel 'NETINBOUND' not found.
EXPLANATION:
The requested operation failed because the program could not find a definition
of channel 'NETINBOUND'.
ACTION:
Check that the name is specified correctly and the channel definition is
available.
This is from the Errors directory of the Queuemanager on the server. Again, I repeat that the MQ Server is obviously getting the requests. It just can not find the named Queue Channel's definition it would seem. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 20, 2006 3:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Told you I would have expected some reason code....
(Disclaimer - I am not now nor have I ever been a .NET programmer. All comments should be viewed with that in mind.)
Am I correct in saying that NETINBOUND is the channel name specified in your application? How does this tally with the name 'tstsvr01connect' in the original post? Are the errors sourced from different locations?
Have you confirmed that the channel(s) is/are correctly defined within the queue manager and appears to be running (i.e. the actions in the error message)?
What connection method are you using within the .NET application? Am I correct in saying you are attempting a client binding here? Have you proved connectivity to the queue manager using the sample code (i.e. is there a general problem or a .NET one)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| IbrahimM |
| Posted: Thu Jul 20, 2006 12:11 pm Post subject: |
|
|
Newbie
Joined: 19 Jul 2006
Posts: 3
|
Thanks Vitor
Actually, what happened is that I misunderstod the purposes of the ClientConnection channel and the other Channels.
One I got it straightened out, everything started working. Boy I am a real NOOB when it comes to MQ!
We are happily putting and getting messages now. Simple ones, but it is a start. thank you for your time.
We are working in VS-2005. And this will work fine with the library provided even though it is a 1.1 build. The trick is that both runtimes have to exist on the machine. When the Net 2.0 application references the DLL, the dll is loaded with the 1.1 runtime if it is available.
Thanks
Ibrahim |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 20, 2006 2:27 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Well I'm glad it's working for you.
Edit the title of the thread to put "Solved" at the front and post a few words on what needed straightening out for the benefit of the next .NET guy who gets this error. Certainly your use of VS-2005 & .NET 2.0 will be of interest, as a quick search will show. Again with the well done 
You've clearly found the "Using .NET" manual, you might want to spin through the "Clients" manual as well which will give you further insights into the mysteries of the client calculations.
One day I must get into .NET 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
