MTS & VB

I have a dll which has been packaged in MTS and has been exported , and a EXE create object from the dll in a client machine , but why the system always prompt dialog saying some program is busy ,please switch the program to resolve the error?
JimsongAsked:
Who is Participating?
 
SpikeDogConnect With a Mentor Commented:
Sorry, misphrased my earlier comment. What I meant was that the MTS was unable to respond to your client.
That message you are getting is simply because your client has not received a complete response from the MTS object.
There are many possible reasons for this but over the last year or so I've seen dozens of these and generally they involve either a security issue (turning all security is the easiest option and is not as bad as it sounds) or there is a malfunction in the DLL.
Angel is right, any attempt to call code such as this will cause a problem.
Here, the easiest way to cope is to put in complete error handling and write to the event log (app.eventlog) any and all error info. Then if the MTS hangs your client you can go look for the problem on the MTS machine in the event viewer. Still, if you wait long enough you SHOULD get an error message from the client. Post this and I can probably help further. MTS is great - when it works.
0
 
SpikeDogCommented:
Hi JimSong.
Sounds like your MTS is having problems.
If you're getting a message box every time you try to do anything to your client exe telling you to Switch To or Retry then your client exe is still waiting for your MTS object to respond.
There are lots of possible reasons for this. Obvious ones include security settings and the possibility that your MTS DLL has hung.
Have a peek at the objects on your MTS and see whether the component is active and In Call.
The Transaction Explorer is under the Option Pack menu.

Most importantly, if you wait long enough your client will generate an error. If it handles it properly and you can get the error details that will set you in the right direction.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
Ensure that your DLL does not include any .Show vbModal or MsgBox code.
This will result in behaviour you report.
I don't think that MTS does actually have a problem, but this is not impossible at all...

0
All Courses

From novice to tech pro — start learning today.