[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-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
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] 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
> http://cp.mcafee.com/d/avndxMQrhpuvohvsppdTdEThjvKztcQsCQrEFLThjhd79J6WarZQrITdEThjd7bXb31EVdydis9kzLDwF3iQWMESJYplzOVJ3iQWMESJYplzOVJ51CP9EVjvW_cIzzhOUq
Re: [U2] Mysterious Error Message
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: U2 Users List
Subject: Re: [U2] Mysterious Error Message
Hi John,
ok, so let's think this throug
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: 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: T
Re: [U2] Working with accented characters
Any consideration of converting the accented character to an unaccented
character first?
Not perfect but it works 99% of the timeand then when you export the name
to another company
All they get are unaccented letters.
George
SUBROUTINE REMOVE.ACCENT(INDATA,OUTDATA)
*
UAE=CHAR(140):CHAR(198)
LAE=CHAR(156):CHAR(230)
DEGREE=CHAR(176)
*
NULL1=CHAR(128):CHAR(129):CHAR(130):CHAR(131):CHAR(132):CHAR(133):CHAR(134):CHAR(135):CHAR(136):CHAR(137)
NULL2=CHAR(139):CHAR(141):CHAR(143):CHAR(144):CHAR(145):CHAR(146):CHAR(147):CHAR(148):CHAR(149):CHAR(150)
NULL3=CHAR(151):CHAR(152):CHAR(153):CHAR(155):CHAR(157):CHAR(160):CHAR(161):CHAR(162):CHAR(163):CHAR(164)
NULL4=CHAR(165):CHAR(166):CHAR(167):CHAR(168):CHAR(169):CHAR(171):CHAR(172):CHAR(173):CHAR(174):CHAR(175)
NULL5=CHAR(177):CHAR(178):CHAR(179):CHAR(180):CHAR(181):CHAR(182):CHAR(183):CHAR(184):CHAR(185):CHAR(187)
NULL6=CHAR(188):CHAR(189):CHAR(190):CHAR(191)
NULLX=CHAR(186):CHAR(216):CHAR(222):CHAR(240):CHAR(247):CHAR(248)
*
UPA=CHAR(192):CHAR(193):CHAR(194):CHAR(195):CHAR(196):CHAR(197)
LWA=CHAR(224):CHAR(225):CHAR(226):CHAR(227):CHAR(228):CHAR(229)
RUA=STR('A',LEN(UPA))
RLA=STR('a',LEN(LWA))
UPE=CHAR(200):CHAR(201):CHAR(202):CHAR(203)
LWE=CHAR(232):CHAR(233):CHAR(234):CHAR(235)
RUE=STR('E',LEN(UPE))
RLE=STR('e',LEN(LWE))
UPI=CHAR(204):CHAR(205):CHAR(206):CHAR(207)
LWI=CHAR(236):CHAR(237):CHAR(238):CHAR(239)
RUI=STR('I',LEN(UPI))
RLI=STR('i',LEN(LWI))
UPO=CHAR(210):CHAR(211):CHAR(212):CHAR(213):CHAR(214)
LWO=CHAR(242):CHAR(243):CHAR(244):CHAR(245):CHAR(246)
RUO=STR('O',LEN(UPO))
RLO=STR('o',LEN(LWO))
UPU=CHAR(217):CHAR(218):CHAR(219):CHAR(220)
LWU=CHAR(249):CHAR(250):CHAR(251):CHAR(252)
RUU=STR('U',LEN(UPU))
RLU=STR('u',LEN(LWU))
SS1=CHAR(138):CHAR(142):CHAR(154):CHAR(158):CHAR(159):CHAR(199):CHAR(208):CHAR(209):CHAR(221):CHAR(223):CHAR(231)
SR1="SZszYCDNYBc"
SS2=CHAR(241):CHAR(253):CHAR(170):CHAR(215)
SR2="nyax"
*
EXPR1=UPA:LWA:UPE:LWE:UPI:LWI:UPO:LWO:UPU:LWU:SS1:SS2
EXPR2=RUA:RLA:RUE:RLE:RUI:RLI:RUO:RLO:RUU:RLU:SR1:SR2
NULCHARS=NULL1:NULL2:NULL3:NULL4:NULL5:NULL6:NULLX:DEGREE
*
LIN=INDATA
*
LIN=CHANGE(LIN,CHAR(223),"SS")
CONVERT EXPR1 TO EXPR2 IN LIN
CONVERT NULCHARS TO "" IN LIN
LIN=CHANGE(LIN,CHAR(230),"AE")
LIN=CHANGE(LIN,UAE,"AE")
LIN=CHANGE(LIN,LAE,"ae")
*
OUTDATA=LIN
RETURN
STOP
END
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bob Little
Sent: Monday, November 25, 2013 3:10 PM
To: U2 Users List [u2-users@listserver.u2ug.org]
Subject: [U2] Working with accented characters
To convert the first character of a regular ASCII string to uppercase, I'd use
OCONV("STRING",'MCT') so that "STRING" is output as "String". However, this
doesn't seem to work for Spanish accented characters. The machine is UV
11.1.11 with NLS enabled.
What is the most elegant way to convert a name, such as JOSÉ to José ? I'm not
a sys admin, so if it requires setting up an NLS map or something along those
lines, I'm probably out of luck.
bob little
applications architect
independent contractor
market america, inc.
1302 pleasant ridge rd.
greensboro, nc 27409
Phone: 336-698-4367
Cell: 248-675-5515
Skype: boblittle904
___
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] Working with accented characters
To convert the first character of a regular ASCII string to uppercase, I'd use
OCONV("STRING",'MCT') so that "STRING" is output as "String". However, this
doesn't seem to work for Spanish accented characters. The machine is UV
11.1.11 with NLS enabled.
What is the most elegant way to convert a name, such as JOSÉ to José ? I'm not
a sys admin, so if it requires setting up an NLS map or something along those
lines, I'm probably out of luck.
bob little
applications architect
independent contractor
market america, inc.
1302 pleasant ridge rd.
greensboro, nc 27409
Phone: 336-698-4367
Cell: 248-675-5515
Skype: boblittle904
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
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 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
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 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://
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
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://cp.mcafee.com/d/5fHCN8i6zqbbPX5SnNO9KVJ6WarZQrFCzASzt5d-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrjdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQzVKVKYuT
__
Re: [U2] Mysterious Error Message
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-Waq9EVdEThjvKztCVJ6WapEVvpood79IhGjxaAtYY58qmDm56RLzaIundEqmDm56RLzaIundFA63hOOqekT-LPatNPb9EVWZOW9EVhpVwsqemm3hOPORQr8FGTspVkffGhBrwqrhdFCXCXCM0pYGjFYjfNVJdIzM071dnoovaAVgtHzqptKDNErrjbJQ-d2V2Hsbvg57OFeDNc_7CQSOf00jr3wVUS2_id41Fr2qpFtd40SmFfUOGTgQg3koRyq81LWkQ
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-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
"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/signatures/HarrisSchools.jpg] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif]
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
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://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
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
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
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
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
