Re: [U2] Mysterious Error Message

2013-11-27 Thread Israel, John R.
I have rebuilt the checksums on the user and for the accounts in DMSECURITY.

This has been escalated to Rocket.

Thanks for all the help - I will post the solution when I get it.  This has put 
a REAL cramp in our making changes.

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 5:04 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

If I recall, the checksum itself is account specific. So if the checksum were 
being calculated for one account but accessing sb resources/processes from 
another, could that be triggering the checksum mismatch?

On Tuesday, November 26, 2013, Israel, John R. wrote:

> Kevin,
>
> This is a temporary situation for testing an unrelated issue.  When 
> THAT issues is resolved, I will go back to a single, common DMSECURITY.
>
> This is NOT the problem - PILOT and LIVE are both using the same 
> DMSECURITY file - PILOT has the problem, but LIVE does not.
>
> The problem is either a local file OR something in DMSECURITY that 
> itself is account specific.
>
>
> 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 9:52 AM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> 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:
> > >

Re: [U2] Mysterious Error Message

2013-11-26 Thread Kevin King
If I recall, the checksum itself is account specific. So if the checksum
were being calculated for one account but accessing sb resources/processes
from another, could that be triggering the checksum mismatch?

On Tuesday, November 26, 2013, Israel, John R. wrote:

> Kevin,
>
> This is a temporary situation for testing an unrelated issue.  When THAT
> issues is resolved, I will go back to a single, common DMSECURITY.
>
> This is NOT the problem - PILOT and LIVE are both using the same
> DMSECURITY file - PILOT has the problem, but LIVE does not.
>
> The problem is either a local file OR something in DMSECURITY that itself
> is account specific.
>
>
> 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 9:52 AM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> 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 sit

Re: [U2] Mysterious Error Message

2013-11-26 Thread Israel, John R.
Kevin,

This is a temporary situation for testing an unrelated issue.  When THAT issues 
is resolved, I will go back to a single, common DMSECURITY.

This is NOT the problem - PILOT and LIVE are both using the same DMSECURITY 
file - PILOT has the problem, but LIVE does not.

The problem is either a local file OR something in DMSECURITY that itself is 
account specific.


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 9:52 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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, 

Re: [U2] Mysterious Error Message

2013-11-26 Thread Kevin King
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://

Re: [U2] Mysterious Error Message

2013-11-26 Thread Israel, John R.
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
> U2-Users@listserver.u2ug.org
>
> http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVd
> EThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63h
> OOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pY
> GjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr
> 3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH
> ___
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
>
> http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVd
> EThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundE

[U2] Mysterious Error Message

2013-11-25 Thread Kevin King
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
> U2-Users@listserver.u2ug.org
>
> http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH
> ___
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
>
> http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKYuT
> ___
> 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


Re: [U2] Mysterious Error Message

2013-11-25 Thread Kevin King
I believe the program that generates that message is MM in DM. The error
signifies that the calculated checksum in the DMSECURITY record is not
correct for the version of SB+ in use.

On Monday, November 25, 2013, Israel, John R. wrote:

> Amy,
>
> I do have a pointer to ECL_PHPARMS.
>
> Putting a DEBUG in IILOGIN would not work for StoreFront because  have no
> session to interact with the debugger, just a browser.  However, that gives
> me a few idea.  I build a log that tracks how far I get and when I fail to
> get to a certain point, narrow my search around there.  Might still bang
> into a program that I have no source to, but it's a start.
>
> Let me do some more digging.
>
> What I really need is to know which program is read and using DMCONT ERROR
> F115!  From that, I could back track to the problem.
>
>
>
> 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 4:40 PM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> We
> The difference is, when you come in through RedBack it's using the agent
> itself, so it sees it as a phantom user.
>
> It may be easiest to stick a debug in IILOGIN - check around line 46 (in
> our version), for comment: 'Check for iConnect Phantom processing'. This
> would also make sense in that both test and pilot in the same realm are not
> working, since IILOGIN is in BP. However...if you already compared live to
> pilot, then I guess that goes out the window.
>
> Any chance your VOC pointer to ECL_PHPARMS is missing? I think that all
> those pointers are established when you 'share' the data account from
> either the iconnect progs account or the dfl-progs account, but I don't
> remember which. Assuming you retained your VOC when you created your
> test/pilot accounts, that should not have changed. But it's something to
> look at...
>
>
>
> -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:54 AM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> Amy,
>
> Yes, I am using iConnect's SB login/pw as soon as UniData/SB launches and
> I get right in.  I looked at the date stamp on the iConnect data and it has
> not been touch in a LONG time.
>
> What is different between this and running it on-line?
>
> Since I can get in that way w/o any problems, why is SB thinking there is
> a problem?
>
>
>
> 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 2:39 PM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> Yes, agreed. So you're using the sb+ uid/pw of the iconnect service
> manager?
>
> -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:36 AM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> Amy,
>
> Yes, both look good.
>
> Based on the 1st word in the message ("II"), this really looks like a SB
> error.
>
> I get NO errors if I login manually using the Redback UNIX login, cd to
> the TEST account, launch UniData (udt), and type in the iConnect login/pw.
>  That is as close to simulating iConnect as I can think of.
>
>
> 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:40 PM
> To: U2 Users List
> Subject: Re: [U2] Mysterious Error Message
>
> is WW.SB.RB cataloged in pilot and test?
> Is BP IILOGIN the same?
>
> If yes to both, take redback out of the picture, along with the screen
> changes (it's not making it to the screen yet...) Do you get the same
> message when you login through SB+, with the same user that the iConnect
> agent logs in with?
> (make sure that user group is allowing it to get into the pilot/test
> accounts)
>
> -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 10:28 AM
> To: U2 Users List
> Subject: Re: [U2] 

Re: [U2] Mysterious Error Message

2013-11-25 Thread Israel, John R.
Amy,

I do have a pointer to ECL_PHPARMS.

Putting a DEBUG in IILOGIN would not work for StoreFront because  have no 
session to interact with the debugger, just a browser.  However, that gives me 
a few idea.  I build a log that tracks how far I get and when I fail to get to 
a certain point, narrow my search around there.  Might still bang into a 
program that I have no source to, but it's a start.

Let me do some more digging.

What I really need is to know which program is read and using DMCONT ERROR 
F115!  From that, I could back track to the problem.



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 4:40 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

We
The difference is, when you come in through RedBack it's using the agent 
itself, so it sees it as a phantom user. 

It may be easiest to stick a debug in IILOGIN - check around line 46 (in our 
version), for comment: 'Check for iConnect Phantom processing'. This would also 
make sense in that both test and pilot in the same realm are not working, since 
IILOGIN is in BP. However...if you already compared live to pilot, then I guess 
that goes out the window.

Any chance your VOC pointer to ECL_PHPARMS is missing? I think that all those 
pointers are established when you 'share' the data account from either the 
iconnect progs account or the dfl-progs account, but I don't remember which. 
Assuming you retained your VOC when you created your test/pilot accounts, that 
should not have changed. But it's something to look at... 



-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:54 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Amy,

Yes, I am using iConnect's SB login/pw as soon as UniData/SB launches and I get 
right in.  I looked at the date stamp on the iConnect data and it has not been 
touch in a LONG time.

What is different between this and running it on-line?

Since I can get in that way w/o any problems, why is SB thinking there is a 
problem?



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 2:39 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Yes, agreed. So you're using the sb+ uid/pw of the iconnect service manager? 

-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:36 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Amy,

Yes, both look good.

Based on the 1st word in the message ("II"), this really looks like a SB error.

I get NO errors if I login manually using the Redback UNIX login, cd to the 
TEST account, launch UniData (udt), and type in the iConnect login/pw.  That is 
as close to simulating iConnect as I can think of.


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:40 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

is WW.SB.RB cataloged in pilot and test?
Is BP IILOGIN the same? 

If yes to both, take redback out of the picture, along with the screen changes 
(it's not making it to the screen yet...) Do you get the same message when you 
login through SB+, with the same user that the iConnect agent logs in with? 
(make sure that user group is allowing it to get into the pilot/test accounts)

-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 10:28 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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: U

Re: [U2] Mysterious Error Message

2013-11-25 Thread Cook, Amy
We
The difference is, when you come in through RedBack it's using the agent 
itself, so it sees it as a phantom user. 

It may be easiest to stick a debug in IILOGIN - check around line 46 (in our 
version), for comment: 'Check for iConnect Phantom processing'. This would also 
make sense in that both test and pilot in the same realm are not working, since 
IILOGIN is in BP. However...if you already compared live to pilot, then I guess 
that goes out the window.

Any chance your VOC pointer to ECL_PHPARMS is missing? I think that all those 
pointers are established when you 'share' the data account from either the 
iconnect progs account or the dfl-progs account, but I don't remember which. 
Assuming you retained your VOC when you created your test/pilot accounts, that 
should not have changed. But it's something to look at... 



-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:54 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Amy,

Yes, I am using iConnect's SB login/pw as soon as UniData/SB launches and I get 
right in.  I looked at the date stamp on the iConnect data and it has not been 
touch in a LONG time.

What is different between this and running it on-line?

Since I can get in that way w/o any problems, why is SB thinking there is a 
problem?



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 2:39 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Yes, agreed. So you're using the sb+ uid/pw of the iconnect service manager? 

-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:36 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Amy,

Yes, both look good.

Based on the 1st word in the message ("II"), this really looks like a SB error.

I get NO errors if I login manually using the Redback UNIX login, cd to the 
TEST account, launch UniData (udt), and type in the iConnect login/pw.  That is 
as close to simulating iConnect as I can think of.


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:40 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

is WW.SB.RB cataloged in pilot and test?
Is BP IILOGIN the same? 

If yes to both, take redback out of the picture, along with the screen changes 
(it's not making it to the screen yet...) Do you get the same message when you 
login through SB+, with the same user that the iConnect agent logs in with? 
(make sure that user group is allowing it to get into the pilot/test accounts)

-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 10:28 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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 Redb

Re: [U2] Mysterious Error Message

2013-11-25 Thread Israel, John R.
Amy,

Yes, I am using iConnect's SB login/pw as soon as UniData/SB launches and I get 
right in.  I looked at the date stamp on the iConnect data and it has not been 
touch in a LONG time.

What is different between this and running it on-line?

Since I can get in that way w/o any problems, why is SB thinking there is a 
problem?



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 2:39 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Yes, agreed. So you're using the sb+ uid/pw of the iconnect service manager? 

-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:36 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Amy,

Yes, both look good.

Based on the 1st word in the message ("II"), this really looks like a SB error.

I get NO errors if I login manually using the Redback UNIX login, cd to the 
TEST account, launch UniData (udt), and type in the iConnect login/pw.  That is 
as close to simulating iConnect as I can think of.


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:40 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

is WW.SB.RB cataloged in pilot and test?
Is BP IILOGIN the same? 

If yes to both, take redback out of the picture, along with the screen changes 
(it's not making it to the screen yet...) Do you get the same message when you 
login through SB+, with the same user that the iConnect agent logs in with? 
(make sure that user group is allowing it to get into the pilot/test accounts)

-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 10:28 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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

Re: [U2] Mysterious Error Message

2013-11-25 Thread Cook, Amy
Yes, agreed. So you're using the sb+ uid/pw of the iconnect service manager? 

-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:36 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

Amy,

Yes, both look good.

Based on the 1st word in the message ("II"), this really looks like a SB error.

I get NO errors if I login manually using the Redback UNIX login, cd to the 
TEST account, launch UniData (udt), and type in the iConnect login/pw.  That is 
as close to simulating iConnect as I can think of.


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:40 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

is WW.SB.RB cataloged in pilot and test?
Is BP IILOGIN the same? 

If yes to both, take redback out of the picture, along with the screen changes 
(it's not making it to the screen yet...) Do you get the same message when you 
login through SB+, with the same user that the iConnect agent logs in with? 
(make sure that user group is allowing it to get into the pilot/test accounts)

-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 10:28 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH

Re: [U2] Mysterious Error Message

2013-11-25 Thread Israel, John R.
Amy,

Yes, both look good.

Based on the 1st word in the message ("II"), this really looks like a SB error.

I get NO errors if I login manually using the Redback UNIX login, cd to the 
TEST account, launch UniData (udt), and type in the iConnect login/pw.  That is 
as close to simulating iConnect as I can think of.


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:40 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

is WW.SB.RB cataloged in pilot and test?
Is BP IILOGIN the same? 

If yes to both, take redback out of the picture, along with the screen changes 
(it's not making it to the screen yet...) Do you get the same message when you 
login through SB+, with the same user that the iConnect agent logs in with? 
(make sure that user group is allowing it to get into the pilot/test accounts)

-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 10:28 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJ

Re: [U2] Mysterious Error Message

2013-11-25 Thread Israel, John R.
Dave,

Yes, I understood (or assumed) that the "II" was the SB+ system, just not WHY 
it thought something was corrupt.

I found the error message just like you said in DMCONT ERROR.  I have never 
seen this before.  The record looks like a bunch of generic error messages that 
can be used as needed.

I just tried logging in as rbadmin (the Redback UNIX id), cd'ed over to the 
TEST.DATA account, typed udt, then used the iConnect login/pw for SB.  I got in 
just fine.  Not sure if that was a good thing or a bad thing.

Now the question is: what conditions are occurring via the web site (w/ the 
error) that I have not been able to replicate manually?



JRI


-Original Message-
From: u2-users-boun...@listserver.u2ug.org 
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Davis
Sent: Monday, November 25, 2013 1:39 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

"II" is whatever SB+ system it is logging into.

Whatever SB+ user is being used to log in doesn't have access to the account.

The message is stored in the ERROR item of the DMCONT file - attribute 115 - so 
you won't find that using ESEARCH on a BP file.

Haven't used redback so I don't know what that uses to log into SB.  Have used 
remote processes though - and get these kinds of errors sometime if the user or 
group security tree doesn't allow us to get into where we are trying to go.


-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 1:28 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIun

Re: [U2] Mysterious Error Message

2013-11-25 Thread Cook, Amy
is WW.SB.RB cataloged in pilot and test?
Is BP IILOGIN the same? 

If yes to both, take redback out of the picture, along with the screen changes 
(it's not making it to the screen yet...)
Do you get the same message when you login through SB+, with the same user that 
the iConnect agent logs in with? 
(make sure that user group is allowing it to get into the pilot/test accounts)

-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 10:28 AM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKYuT
___
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


Re: [U2] Mysterious Error Message

2013-11-25 Thread Dave Davis
"II" is whatever SB+ system it is logging into.

Whatever SB+ user is being used to log in doesn't have access to the account.

The message is stored in the ERROR item of the DMCONT file - attribute 115 - so 
you won't find that using ESEARCH on a BP file.

Haven't used redback so I don't know what that uses to log into SB.  Have used 
remote processes though - and get these kinds of errors sometime if the user or 
group security tree doesn't allow us to get into where we are trying to go.


-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 1:28 PM
To: U2 Users List
Subject: Re: [U2] Mysterious Error Message

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
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKYuT
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users



Dave Davis
Team Lead, Research & Development

P: 614-875-4910 x108
F: 614-875-4088
E: dda...@harriscomputer.com
[http://www.harriscomputer.com/images/

Re: [U2] Mysterious Error Message

2013-11-25 Thread Israel, John R.
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
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCNEp4zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKnZbpJhF-VsH
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKYuT
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] Mysterious Error Message

2013-11-25 Thread Cook, Amy
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
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


Re: [U2] Mysterious Error Message

2013-11-25 Thread Woodward, Bob
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


Re: [U2] Mysterious Error Message

2013-11-25 Thread Israel, John R.
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


Re: [U2] Mysterious Error Message

2013-11-25 Thread George Gallen
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://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] Mysterious Error Message

2013-11-25 Thread Israel, John R.
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://listserver.u2ug.org/mailman/listinfo/u2-users