DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: Component Busy Problem

  1. #1
    Cal Guest

    Component Busy Problem


    This is my first install using MTS. I exported the MTS package
    on the server and ran the client executable on the client
    machine. As far as I can tell, all the permissions are
    correct. When the app is started on the client only the splash
    screen shows. A window will eventually pop-up stating the
    component is busy along with command buttons for Switch-To,
    Retry and Cancel. I still suspect there is a permissions problem somewhere
    but as yet I haven't found it. Has anybody exprienced this type of problem?
    Any suggestions?


  2. #2
    Grant Guest

    Re: Component Busy Problem


    "Cal" <willcal@compuserve.com> wrote:
    >
    >This is my first install using MTS. I exported the MTS package
    >on the server and ran the client executable on the client
    >machine. As far as I can tell, all the permissions are
    >correct. When the app is started on the client only the splash
    >screen shows. A window will eventually pop-up stating the
    >component is busy along with command buttons for Switch-To,
    >Retry and Cancel. I still suspect there is a permissions problem somewhere
    >but as yet I haven't found it. Has anybody exprienced this type of problem?
    > Any suggestions?
    >


    I found the same in my experience, however after some unreasonable amount
    of time, the Component will "wake-up". You can check the MTS Explorer count
    of the components "Object", "Activate" and "In Call" status. You will find
    that the incrementation of "Object" and "Activate" is quick, but the "In
    Call" takes forever. Once this object has been created then, any subsequent
    instantisations are very quick. However, if you leave the component idle
    for about two minutes in my case, you're back to the lengthy wait. I'm playing
    with the Package's property ShutDownAfter time, which I thought was originally
    shutting it down, but I'm not so sure now, as I'm getting mixed results.
    I need some suggestions on this too, as I see another relevant discussion
    thread here regarding "MTS is slow at first use..." which doesn't answer
    my problems either, yet. Hope this is useful to you....

  3. #3
    Cal Guest

    Re: Component Busy Problem


    Thanks for responding Grant. I did finally fix the problem
    but I couldn't tell you what was wrong. The solution for me
    was to delete all the packages I was using on the server.
    Recreate and export them. I then ran the new client executable
    on the clients and it worked! I asked Deborah Kurata about this
    and she said that MTS is VERY picky about versioning and
    permission settings. It's possible that I had something set
    wrong, although after hours of searching I never found it. There
    still is a pause while MTS initializes but it's only about 10
    seconds. I think that's what the other discussion is on. (In my
    case the component never did respond at any time.)

    Cal

    "Grant" <gwoolley@contractors.co.nz> wrote:
    >
    >"Cal" <willcal@compuserve.com> wrote:
    >>
    >>This is my first install using MTS. I exported the MTS package
    >>on the server and ran the client executable on the client
    >>machine. As far as I can tell, all the permissions are
    >>correct. When the app is started on the client only the splash
    >>screen shows. A window will eventually pop-up stating the
    >>component is busy along with command buttons for Switch-To,
    >>Retry and Cancel. I still suspect there is a permissions problem somewhere
    >>but as yet I haven't found it. Has anybody exprienced this type of problem?
    >> Any suggestions?
    >>

    >
    >I found the same in my experience, however after some unreasonable amount
    >of time, the Component will "wake-up". You can check the MTS Explorer count
    >of the components "Object", "Activate" and "In Call" status. You will find
    >that the incrementation of "Object" and "Activate" is quick, but the "In
    >Call" takes forever. Once this object has been created then, any subsequent
    >instantisations are very quick. However, if you leave the component idle
    >for about two minutes in my case, you're back to the lengthy wait. I'm

    playing
    >with the Package's property ShutDownAfter time, which I thought was originally
    >shutting it down, but I'm not so sure now, as I'm getting mixed results.
    > I need some suggestions on this too, as I see another relevant discussion
    >thread here regarding "MTS is slow at first use..." which doesn't answer
    >my problems either, yet. Hope this is useful to you....



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center