hexagon logo
Register Sign in
  • Replies 2 replies
  • Subscribers 10 subscribers
  • Views 60 views
  • Users 0 members are here
Options
Related

Datapage anomaly

TCeckels
Usually I can get Datapage to run thru the basics for me so I can at least get a .txt report out to the girl in engineering but yesterday it started freaking out on me and I'm not real sure why.....

I started running my 6 pcs thru the machine as usual but when it reached the end of the first part and I hit the yes button to save the stats, it told me that "XXX directory was not available". Well that's BS cuz I'm looking at the directory, but I didn't know what else to do so I hit ok AND THEN it started saving data......data from a previous job I'd run last week???? It went thru and save all 6 of these parts from a different job AND THEN it started to save the part that I'd just run?!?! WTH.....

not wanting to mess with it at that point, just trying to get the parts out and go home, I checked datapage and the file was there and looked to be whole so I decided to run part #2. At the end of part # 2 it went thru the whole routine again, saving all 6 parts from the previous job before saving part #1, again from the current job and then saving part #2..........
it went thru this whole process for all 6 parts, saving everything, everytime. What the heck is going on?????
I know it's not realistic but just once I'd like to have a whole week go by without any PC-DMIS glitches......


Tc
Parents
  • What has happened is that you have somehow included a stat command & directory in a program that does not exist. When this happens, the file, XSTATS11.TMP does NOT get emptied. It leaves ALL gathered data in it so you can 'fix' the bad directory command (by either making the database directory OR changing the path in the XSTATS11.TMP file) so that you don't lose any data. You will continue to get this error until you either edit the XSTATS11.TMp file to fix the bad path OR, since you obviously do NOT need the data that is in the XSTATS11.TMP file, just DELETE the XSTATS11.TMP file. ALL this file does is hold the data until you tell Pcdmis to UPDATE the stats. It will be located in the instlal directory of Pcdmis. Just delete it and release the stress. I am guessing that it gave you a -127 error. This will solve all your problems, just not like a big glass of Tequila, but it will sure help!

    yeah, Matt, it was the 127 error and deleting the Xstats11.tmp file was the fix. I ran the part again after deletion and everything was coposetic. After thinking a bit I'm pretty sure I know what I did to screw it up too, but I'm not up for trying to do it again to prove my point<g> I'll just try to do it the right way from now on.

    thanks for the help once again.

    Tc
Reply
  • What has happened is that you have somehow included a stat command & directory in a program that does not exist. When this happens, the file, XSTATS11.TMP does NOT get emptied. It leaves ALL gathered data in it so you can 'fix' the bad directory command (by either making the database directory OR changing the path in the XSTATS11.TMP file) so that you don't lose any data. You will continue to get this error until you either edit the XSTATS11.TMp file to fix the bad path OR, since you obviously do NOT need the data that is in the XSTATS11.TMP file, just DELETE the XSTATS11.TMP file. ALL this file does is hold the data until you tell Pcdmis to UPDATE the stats. It will be located in the instlal directory of Pcdmis. Just delete it and release the stress. I am guessing that it gave you a -127 error. This will solve all your problems, just not like a big glass of Tequila, but it will sure help!

    yeah, Matt, it was the 127 error and deleting the Xstats11.tmp file was the fix. I ran the part again after deletion and everything was coposetic. After thinking a bit I'm pretty sure I know what I did to screw it up too, but I'm not up for trying to do it again to prove my point<g> I'll just try to do it the right way from now on.

    thanks for the help once again.

    Tc
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement