hexagon logo
Register Sign in
  • Replies 20 replies
  • Subscribers 32 subscribers
  • Views 362 views
  • Users 0 members are here
Options
Related

Server Busy Error

kellyh
Every once in a while during my OLE, I get a server busy message with three buttons, switch to, retry, and cancel (greyed out).

I have read that using the App.OLEServerBusyTimeOut = 9999999 would increase the time to a point that this error would not occur, but when I tried it, I still go the error.

Anyone have a idea of how to suppress this error message?

Thanks.
  • So I found some stuff on google, but none of it seems to work. I have tried:

    App.OLEServerBusyTimout = 99999999
    App.ObjApp.OLESeverBusyTimout = 99999999
    App.OLEServerRaiseError = True
    App.OLEServerRaiseError = False
    App.OLERequestPendingTimeout = 0
    App.OLERequestPendingTimeout = 9999999

    I really thought that this would be an easy fix. Hah! I was wrong.
  • What is PC-DMIS doing at the time you get this message?

    I assume the server busy message comes from PC-DMIS?
  • Yes, the server busy message comes from PC DMIS and is waiting for the operator input in WinSPC. I would like to be able to tell PCDMIS to be patient and it will be its turn when the operator is done in WinSPC, but it doesn't quite work that way.

    And I found one that gave me an error that the command doesn't work Afx...shoot, now I don't remember that command. I suppose it doesn't matter much since it wasn't a recognized command.

    So, if you have any ideas, I would welcome them because I keep finding the same things over and over.

    Thanks.
  • Are you calling this WinSPC from your script or is it called by the EXTERNAL command in PC-DMIS?

    Is it this you were referring to? (Afx...)
    http://support.microsoft.com/kb/248019
  • Yes, that is the code that I meant and couldn't remember.

    WinSPC is called from the script which is inserted into the PCDMIS program by inserting a basic file (drop down menu insert -> basic script, then F3 to unhighlight it and make it functional).

    Since the computer can only do what it is programmed to do, there has to be a way to suppress that, so when the operator enters the information (notes on parts that are out of spec), then PCDMIS simply waits and resumes when WinSPC is ready.

    I did go through the PCDMIS book (the one found in a folder) and the help files but did not find a command that is in the PCDMIS library. So it might be a matter of figuring out how to tell PCDMIS to do this.

    Thanks again for helping out.
    Are you calling this WinSPC from your script or is it called by the EXTERNAL command in PC-DMIS?

    Is it this you were referring to? (Afx...)
    http://support.microsoft.com/kb/248019
  • Try running the WinSPC part using the EXTERNAL command in PC-DMIS.
    That function has the "WAIT" parameter, which I assume should work better than calling WinSPC from a script, where you don't have the needed parameters (wait for process to finish). When it returns, continue the script - you might have to split the script into two parts, one handling stuff before the WinSPC call and one part handling stuff after WinSPC is finished.
  • OK, here is how the script works, first it collects the variables for the data that is collected during the running of the cmm. Then it opens WinSPC and places those variables in the proper "slots" and closes WinSPC and PCDMIS to finish. Could I just run it as an external command? And to set it up, I simply browse for the location the script is in, keep the display function checked, and then click the button next to the wait parameter? And theoretically that will get rid of the server busy box that is so annoying?
  • If you're gonna run your script as an external command, I think you would need to change the BAS to a VBS in order to be able to use the WAIT parameter. The EXTERNAL command is for spawning a process outside the PC-DMIS process and wait for that process to finish before continuing with the partprogram.
  • The external command function requires a .exe file or a .bat file. From the research I have been able to do, I think I can run my app through a .bat file and use that to piggy back the code into PCDMIS. I will let you know as events unfold. Of course there is the whole thing that something looks simple, but ends up being much more complex than I think it will be.
  • Of course there is the whole thing that something looks simple, but ends up being much more complex than I think it will be.

    You got that right! Stuck out tongue closed eyes
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement