It appears there may be a fix coming out in 11.1.10 later this year. Take my words with a grain of salt however, as I don't primarily deal with the current UniVerse releases.
-----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Wednesday, October 17, 2012 2:42 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] Universe 11 on Windows; BASIC STATUS command aborting process When you say "was", is there a patch? -----Original Message----- From: Daniel McGrath <dmcgr...@rocketsoftware.com> To: U2 Users List <u2-users@listserver.u2ug.org> Sent: Wed, Oct 17, 2012 1:38 pm Subject: Re: [U2] [UV] Universe 11 on Windows; BASIC STATUS command aborting process There was a known issue whereby doing a STATUS call on a file that no longer has a valid owner will cause an access violation. As you are iterating over every file, this seems like a plausible cause. Tom's Hardware seems to have some help in finding files with invalid owners: http://www.tomshardware.com/forum/199123-46-find-files-valid-owner Regards, Dan McGrath Product Manager -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson Sent: Wednesday, October 17, 2012 2:23 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UV] Universe 11 on Windows; BASIC STATUS command aborting process I have a verb I wrote, which select all files in an account, including those which are just pointers to OS level directories, and for each run it runs the BASIC STATUS command to retrieve the INODE (and other things). The process aborts part way through with no message, it just kicks my session off so I have to logon again. Looking in the errlog (Universe' generic error log file) there is no error there either, related to me. (Just other users.) Using RAID, I can step through the program. It opens the file fine and I can see the pointer details in the debugger, but as soon as it hits the line with the STATUS on it, it blows my session away. No error message. I can list all the records in the file just fine, right to the end with no errors. But if I try ED filename TESTRECORD It aborts my session immediately, with no error message. It seems odd to me that permissions by themselves could cause that sort of response. I would have expected something more along the lines of "You do not have permission to edit this record...." or something nice. Any thoughts? _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
