For the last month I have been tracking testing and documenting a problem with sending electronic statements. At some point during the process a security file is being corrupted and causing fatal exception errors. Running a recovery utility on the file corrects the problem until statements are generated again. What is frustrating to me is the fact that only 5 offices are experiencing this. I have tested the data in XP SP1-3, Vista, Server 2003, using pervasive versions 7.9, 8.6, 9.5, and 10.10. So far the error can not be recreated in house. QA now has me running PC audits on every computer at each of the 5 offices. Personally I think it makes more sense to only run on the server and any computer that is used to send statements. One thing I have done is set up a test database at one office to force the statement run over and over until the error occurs. (did I mention the errors do not happen with every statement run) All I can do now is present everything I have gathered to QA and let them deal with it. Once it is off my plate I will be so relieved.
If I can make it to Friday I will be having a girls lunch with some old friends that I have not seen in years. I can't wait to catch up.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment