4.0 Serialization error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 4.0 Serialization error

    Ok I have tried everything... I call up a program that previously ran in 4.0 and get the Serialization error. ERROR: ALT
    It wont open up the program..
    if I am going to have to rewrite this program... is there anyway to see it in notebook or some other form so I dont have to recreate the wheel

    I have moved the probe file out, I have tried a back up copy, I have tried to rename the part file, I have tried to not use the textonly report, I used a diff report, I have just run out of ideas,, I tried it in operator mode, I tried my magic dust... shoot I even kicked the stupid computer..

  • #2
    I've had this problem a number of times, finally learned my lesson and keep a backup of all current programs. As far as I know once this occurs there is no way to recover that file.
    "A good design is the one that allows engineers the ability to change gracefully what they forgot to do right the first time!!!"

    Comment


    • #3
      Sorry, I was never able to recover either. You have to re-create the file from scratch.

      It happens to me when PC-DMIS fails during a Save. If I get the PCDLRN error during that sequence, all is lost.

      There were earlier posts that if you use XP service pack 2, you need to install a HotFix. I did that on mine, didn't help much. Maybe something for you to try.

      The Ctrl+S key is NOT enough. What I have to do EVERY night now, is take all my active programs, and do a SAVE AS to another location. That way, I loose only less than 1 day's worth of work, when buddy Serialization roars its ugly head again.

      This is a major problem in this version of PC-DMIS. I am considering going to V4.1. Maybe this problem will go away.


      Jan.
      ***************************
      PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
      Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

      Comment


      • #4
        Have you tried a completly new probe file with different name & deleting the current probe file from your harddrive.
        sigpic.....Its called golf because all the other 4 letter words were taken

        Comment


        • #5
          Originally posted by bw_bob
          Have you tried a completly new probe file with different name & deleting the current probe file from your harddrive.
          If it's the same problem we have here there is no way to recover, since there is no access to the file at all. It seems to happen after we run approx. 30 parts but not everytime.
          B&S claims it's a Windows problem but we still get the error even with the hotfix.
          I do exactly what Jan does and always save a backup copy of my programs just in case.
          "A good design is the one that allows engineers the ability to change gracefully what they forgot to do right the first time!!!"

          Comment


          • #6
            Originally posted by bboyd
            If it's the same problem we have here there is no way to recover, since there is no access to the file at all. It seems to happen after we run approx. 30 parts but not everytime.
            B&S claims it's a Windows problem but we still get the error even with the hotfix.
            I do exactly what Jan does and always save a backup copy of my programs just in case.

            Lets say that pc-demons is on the c drive. just go to the c drive go into your directory and delete the probe file and results file.Then try to open your program file and create a new probe file.
            Last edited by bw_bob; 08-16-2006, 11:33 AM.
            sigpic.....Its called golf because all the other 4 letter words were taken

            Comment


            • #7
              Probe file

              Originally posted by bw_bob
              Lets say that pc-demons is on the c drive. just go to the c drive go into your directory and delete the probe file and results file.Then try to open your program file and create a new probe file.

              Are you saying that the probe file is corrupt and is causing the error?
              If that was true, wouldn't that effect all the programs that share that probe file? (it doesn't)
              "A good design is the one that allows engineers the ability to change gracefully what they forgot to do right the first time!!!"

              Comment


              • #8
                Originally posted by bboyd
                Are you saying that the probe file is corrupt and is causing the error?
                If that was true, wouldn't that effect all the programs that share that probe file? (it doesn't)
                I cannot answer that question. All i know in the past when we would get serialzation errors it was 99% of the time the probe file. Only my suggestion.
                Thats another reason i never use the same probe file twice.I create a new probe file for every program. May take longer, but i've not had that problem in years.
                sigpic.....Its called golf because all the other 4 letter words were taken

                Comment


                • #9
                  Originally posted by bw_bob
                  I cannot answer that question. All i know in the past when we would get serialzation errors it was 99% of the time the probe file. Only my suggestion.
                  Thats another reason i never use the same probe file twice.I create a new probe file for every program. May take longer, but i've not had that problem in years.
                  I will try that next time and see what happens
                  Thx
                  "A good design is the one that allows engineers the ability to change gracefully what they forgot to do right the first time!!!"

                  Comment


                  • #10
                    Well I can tell you now that you mention it I did get a PCDMIS error and PCDMIS logged off automaticaly when I was running the program. So I guess I will have to conceed that the program is most likely corrupt... oh well
                    I can tell you when I first started using PCDMIS 6 or 7 years ago I always got tons of errors.. I bet its been 3 years since that has happened and we use the CMM constantly for 3 shifts. But ever since I started using version 4.0 I have been getting PCDMIS errors and it shuts down... I bet it has happened 20 times

                    Comment


                    • #11
                      Originally posted by Shipwreck
                      Well I can tell you now that you mention it I did get a PCDMIS error and PCDMIS logged off automaticaly when I was running the program. So I guess I will have to conceed that the program is most likely corrupt... oh well
                      I can tell you when I first started using PCDMIS 6 or 7 years ago I always got tons of errors.. I bet its been 3 years since that has happened and we use the CMM constantly for 3 shifts. But ever since I started using version 4.0 I have been getting PCDMIS errors and it shuts down... I bet it has happened 20 times

                      My fault for not asking if it was 4.0, read the previous threads on 4.0
                      There is nothing good said about that version
                      B&S does not even like it. If you can go to 4.1 and your problems will probably go away.
                      sigpic.....Its called golf because all the other 4 letter words were taken

                      Comment


                      • #12
                        When I install 4.0 last week my probe file got corrupted. Had to delete all the probes and start over.

                        Comment

                        Related Topics

                        Collapse

                        Working...
                        X