| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| VB.NET client problems |
« View previous topic :: View next topic » |
| Author |
Message
|
| mangoMan |
 Posted: Thu Oct 16, 2003 2:19 pm Post subject: VB.NET client problems |
 |
|
Acolyte
Joined: 16 Oct 2003
Posts: 69
|
My client application is written in VB.NET and it is using the MQ ActiveX control. But for some reason I get the 2058 error. I have have specified MqType=2 in the configuration properties build section. Am I missing something. Does MqType not work with .NET interop thing?
I don't see the problem because when I use the amqsputc application I am able to connect to the QM on the server box, I have also sucessfully run amqsputb, but when I run my client app I get 2058 which I have looked up in manual as qm name error. And when I tried using "" for QMgr name I got a 2059. I am confused. I think that my app is running as the server app and that might be the problem.
Any help would be greatly appreciated.
Thanks! |
|
| Back to top |
|
 |
| wih |
| Posted: Sat Oct 25, 2003 5:09 pm Post subject: VB.NET ActiveX 2058 |
|
|
Newbie
Joined: 25 Oct 2003
Posts: 2
|
I just started using MQ, and I am using the ActiveX control. I am using it in PowerBuilder, VB 6 and VB.NET. The only language that is giving me trouble is VB 6. When I try to do a GET() from the queue object, I get a system error that the language does not support the command. I copy/pasted the code into a .NET app, and it works fine. My application is purely on the client side. My server is on an Enterprise Server.
The only catch I ran into was if I tried to change my queue manager. I would get a 2058 if I did not reboot. Don't forget to set the environment variable MQSERVER= (Start/Control Panel/System/Advanced tab/Environment Variables... It can be set at the system level or current user level (I am assuming Windows 2000 or higher). The format of the variable is channel name / protocol / address(port). For example, and Enterprise Server setting could be:
MQSERVER=MQST.OSG/TCP/MFAFDDI(1414)
The Queue Manager name used in your VB application must be defined to use the channel set in the MQSERVER variable.
Good luck. |
|
| Back to top |
|
|
| JasonE |
| Posted: Mon Nov 03, 2003 8:38 am Post subject: VB.net client problems |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
The ActiveX class use a method known as 'late binding' when deciding which MQSeries API module (either MQM.dll or MQIC32.dll) to use. This mathod takes the approach that, if MQM.dll is present in the path, the application must be running as a server side application and as such uses MQM.dll otherwise it assumes that the application was meant to run as a client side application and uses MQIC32.dll.
This is documented on the AccessQueueManager method of the MQSession class here in the MQSeries manual 'Using the Component Object Model Interface'.
This can be overridden using the undocumented environment variable, GMQ_MQ_LIB which should be set to the full path of the dll to use (either MQIC32.dll or MQM.dll). |
|
| 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
|
|
|
|
