Since it's in the Redback log, that's where I'd be looking. -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Monday, November 25, 2013 9:06 AM To: U2 Users List Subject: Re: [U2] Mysterious Error Message
Sorry for the typo. We thought of looking for the program giving the error. We do not have the source code for it, so even if we found it as a string, we could not read the rest of the object code. Even so, I have tried doing an ESEARCH on some of the SB files, but I have yet to find it. JRI -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of George Gallen Sent: Monday, November 25, 2013 11:57 AM To: U2 Users List Subject: Re: [U2] Mysterious Error Message Given that Corrupt is missing a T (itself being corrupt?) I would think it's not an OS related message. Since your HPUX, can you do a file content find in unix for "RECORD CORRUP!" to find out where it's coming from? -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Israel, John R. Sent: Monday, November 25, 2013 11:46 AM To: U2 Users List Subject: [U2] Mysterious Error Message We use UniData/HPUX w/ SB and Redback. We are running Epicor's Avanté which uses iConnect. For arguments sake, I have 3 UniData accounts: TEST, PILOT & LIVE. I have 3 web sites (TEST, PILOT & LIVE) that connect as you would expect. 3-4 weeks ago, a change was made in Sales Order Entry in SB. I had to make a minor tweak for this to work via the web sites. All was good with all three web sites. Due to unrelated issues, our TEST account has a temporary stand-alone copy of DMSECURITY. Other people on my team have made a few changes in SB Sales Order Entry and asked that I verify that the web site still worked. One change was in TEST and another (untested) one was in PILOT. Order Entry was now failing on both web sites, but LIVE was still working. The change in PILOT was unrolled, but we still had the problem. The actual error we are getting in the Redback log is "II RECORD CORRUP! - CONTACT SYSTEM ADMINISTRATOR" If the problem were only in TEST, I would blame my local copy of DMSECURITY. Since the problem is also in PILOT but NOT in LIVE (which share the standard DMSECURITY file), this tells me it is not the DMSECURITY file, but rather something that is local to each account. Has anyone seen this before? Any thoughts or suggestions? JRI _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://cp.mcafee.com/d/k-Kr3x0p41ASyOY-OqenD4kPtPqdQkTXETjd79J6WarZQkQjhOrhKyC_t6XdPqdQkPhO-OMMqejozkD2l8XVUagQJeIadHv6loYKrgQJeIadHv6loYKrovhupd7ar_nVeZT3hOU_RXBQQhP79Lcnd7bXDbnhIyyHuWfaxVZicHs3jq9JcTsTsS03fBitfyp-fdFJAu00U9GX33VkDa3JsrjbJQ-d3rqptKDNEn8lrxrW0E-l9Q-9DUYSCShU02rvjpd79I5-Aq83iS4QPiWq81IJivNBlKxEw6ENH4Qg3vQFF7PtPvrjguueZ _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://cp.mcafee.com/d/5fHCNAq3zqbbPX9EVushjdTdEThjvKztcQsCQrEFLThjhd79J6WarZQrITdEThjd7bXb31EVdydis9kzLDwF3iQWMESJYplzOVJ3iQWMESJYplzOVJxZ5VAQsFLZvAXTsd7bz_nKnjh7csCYNsQsLKsJt6OaaJXEYG7DR8OJMddFCQPtPtPo0c-l9Q-9DUYSCShU03wCHIcfBisEeRNJcKTjUQdJFBSWv6xsxlK5LE2zVkDjUCvzPqrp7w09JZdAQsCMnWhEwdbojjdbFEw6OR9_6lmW6y0qz6Ijh0d_iCAvdTdTg5hgbhsZS93 _______________________________________________ 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
