Is there a particular reason you can't share that DMSECURITY file across all SB enabled accts?
On Tuesday, November 26, 2013, Israel, John R. wrote: > Kevin, > > I did an ESEARCH on the DM file, looking for E115. I did not find it in > MM, but did find it in the following: > _SB.GENERAL.S > _SB.LOGIN > _SB.SYSMENU > _SB.USER.CHECK > > I did not find it in _MM, but this still looks like progress. > > I do not have access to SB source code, but at least this is something I > can send back to Epicor, who can hopefully get with Rocket. > > JRI > > > -----Original Message----- > From: u2-users-boun...@listserver.u2ug.org [mailto: > u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King > Sent: Tuesday, November 26, 2013 12:36 AM > To: U2 Users List > Subject: [U2] Mysterious Error Message > > John, look for [E115]. That's how the error will appear in the SB+ > routines. I'm guessing that the problem is that RB is connecting to SB > through the install accounts but DMSECURITY is being referenced locally, > hence the checksum mismatch. > > On Monday, November 25, 2013, Israel, John R. wrote: > > > Yes - the LOGIN paragraphs are the same. > > > > Yes - the iConnect agents are essentially the same (paths are > > obviously > > different) and they are all enabled. The last change I made to > > iConnect was 3-4 weeks ago to map a new field and that worked (and is > > still working in LIVE). > > > > I have done an ESEARCH on all the BP files I can think of in Redback, > > iConnect & the Avanté account itself. Even looking through source > > codes and object code, I cannot find "RECORD CORRUPT" anywhere. Maybe > > I missed something, maybe it is more cryptic than I would expect, > > maybe something else. Bottom line: I do not have a clue what program > > is causing this, what "II" record it thinks is corrupt, etc. > > > > JRI > > > > -----Original Message----- > > From: u2-users-boun...@listserver.u2ug.org [mailto: > > u2-users-boun...@listserver.u2ug.org] On Behalf Of Cook, Amy > > Sent: Monday, November 25, 2013 1:17 PM > > To: U2 Users List > > Subject: Re: [U2] Mysterious Error Message > > > > Hi John, > > ok, so let's think this through... > > RedBack is using an iConnect agent to login through SB+ and execute > > the screen. > > That message is an SB+ message. > > > > So...my first question would be - are the LOGIN paragraphs the same > > between accounts where it's working and where it's not? > > The 2nd would be - is the iconnect Agent, as defined the Site setup > > the same between sites? Is that agent enabled? (I'm assuming the > > backend iConnect accounts are shared per realm?) > > > > -----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 8: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 > > > http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVd > > EThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63h > > OOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pY > > GjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr > > 3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKYuT > > _______________________________________________ > > U2-Users mailing list > > U2-Users@listserver.u2ug.org <javascript:;> > > http://cp.mcafee.com/d/5fHCMUi3zqbbPX332b39KVJ6WarZQrFCzASzt5d-Waq9EVd > > EThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIund-COOM > > qekT-LOrPbVEVjjWZOWbOt-ohpKqen4-mKDp5dmZSel3PWApmU6CQjr1KVKVI06vaAWv4P > > Yurjr8Y01MjlS67OFek7qUSCnrFYq6SQOXtfzgKgGT2TQ1hYGjFYjfNVJdIzM04SZtdwSq > > mMCCqnjh0q81IJivNBlKxEw6ENH4Qg3vQFF7PtPqo_5hhM8 > > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org <javascript:;> > > http://cp.mcafee.com/d/1jWVIgdEILfIcc8IcCXCQrEFLThKCqejqdQkTXEFECzASzt5d-WdSrCQrEFCzBZBxwQsCN6Fe4GhTPMkxFqtokrm-cGNVsSxFqtokrm-cGNVsTWrbb1EVjvW_9LcLCzBdfHTbEL9TVx5CVEVsjVqWtAkRrToVkffGhBrwqrjdI6XCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jrRQS3pFr2qpFtd41Ew6OR9_6lmW6y0qz6Ijh0d_iCAvdTdQUvY > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org <javascript:;> > 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
