hexagon logo
Register Sign in
  • Replies 20 replies
  • Subscribers 32 subscribers
  • Views 363 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.
  • Well, so far no luck with the bat file. I can get it to open the code to the OLE, but not actually run it. Yet.

    I also found the original site for cypress express, and there isn't any command that will make PC DMIS wait with just a command like it would in vb6 or vb.net.

    Now, for all of you that are more familiar with working with PC DMIS, if I found the error that was making this box pop up, could I write a bit of code that address if error = serverbusy (example) then ..... do something?

    And then if that is possilbe, how do I find out that error code?

    Thanks for your advice and help.
  • has anyone used this?

    Syntax:

    Return Value =expression.WaitUntilExecuted (Command, Timeout)

    Return Value: This methods immediately returns FALSE if the part program is not executing. It returns TRUE if the specified Command executes before Timeout seconds pass. It returns FALSE if the Command does not execute before Timeout seconds pass. If Timeout is a non-positive value, and the Command never executes, this function never returns a value.

    expression: Required expression that evaluates to a PartProgram object.

    Command: This is an expression that evaluates to a Command object. This is the command that is waited for.

    Timeout: This is the number of seconds (a Long value) to wait for the command to finish execution. If you have a non-positive value, the method waits indefinitely.

    This method waits until the specified Command object executes, or until Timeout seconds pass.
  • Kelly, sounds like you know more about this stuff than me, and maybe you've got this figured out already, but just in case it helps, I found that I can pause pcdmis by using the sleep command in a batch file.
    sleep 1
    add however many milliseconds works for you.
  • Thanks Kevo.

    I know it has been a while since I was able to work on this. We had a rush at the end of 2013 to get our CMM computers updated to Windows7, then there were compatability issues...and so on and so forth. Slight smile

    Now that they seem to want to behave themselves, I have been back on this part of the project.

    What I ended up doing is redoing all my basic scripts into exe files and using the Insert > External Command which opens a box. Browse to find the file you want then use the No Display; Wait radio buttons to get rid of the box completely. It can sit on pause for hours and no boxes, no warnings. ONce it gets its input, it simply continues.

    If you need a free tool to make exe files, I have been using Visual Studio 2012 Express. It is pretty easy. Just remember to use the Windows Console settings.
  • Thanks Kevo.
    If you need a free tool to make exe files, I have been using Visual Studio 2012 Express. It is pretty easy. Just remember to use the Windows Console settings.

    Thanks for the tip about Visual Studio 2012 Express. Since we still have MeasureMax we already have VB6 which so far is meeting our needs which go beyond simple scripts and batch files.
  • A quick word about using Visual Studio to make the exe programs....

    Many commands do not behave as expected because cypress express is more like VB6, and VS seems to use .NET rather than anything else. So where possible use the enumeration codes. It runs a lot smoother that way. Slight smile
  • Next time you get the "Server busy" error, doublecheck the permissions for the registry key HKCR\PCDLRN.Application\CLSID. Make sure that the user account you are using when this error occurs have permissions to write to that registry key.

    I just had this particular error when switching between versions on Windows 7 and it was (seemingly) fixed by correcting the permissions to that registry key.
  • Well that is an interesting thing. I will double check on that...

    But since we run all the computers that use PCDMIS as admin, you'd think it would just let the program write to it.
  • I did get the chance to look into this, and I don't think that this is our problem. We can run PCDMIS normally just fine, but we can't do with the script. Now I take that script and run it as its own exe file, then it runs beautifully (except FCFs but that is another story). So I really think it has to do with how PCDMIS handles the basic script internally.

    Plus, when I went to the location you specified, it appears that we have permission.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement