Next Numbers Issue

graham_jones

Active Member
Hello List,

We are B7332/SP11.3 CO on AS400, NT4 with fat clients.

For a couple of days now we have been experiencing problems relating to next
numbers. When trying to add address book records and forcing the system to
generate the next AB number we get Error: Next Number Failure and the help
text advises us to verify the calling process to X0010. This is spread
across ALL environments including pristine!!! JDE are stuck on this at the
moment.

As usual any help very gratefully received.

Regards,

Graham.
Graham Jones
JDE Systems Manager
Park Group Plc.
(0151) 653 1700 ext 1109
[email protected]


***** DISCLAIMER ***** This communication contains information which is
confidential. It is for the exclusive use of the intended recipient. If you
are not the intended recipient, please note that any distribution, copying
or use of this communication or the information in it is prohibited. If you
have received this communication in error, please notify us by email or by
telephone on 0151 653 1700 and then delete the email and any copies of it.
*****
 

lerwick

Member
Hi,

Can you see a lock on the NN file using WRKOBJLCK? It would seem really
strange that all your environments could be using the same NN file though.
We had problems with client access on a single PC locking NN file when it
wasn't up to the current SP level.

regards, Lerwick
Alstom NZ
 
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C04991.14C27DF0
Content-Type: text/plain;
charset="iso-8859-1"

We had the exact same problem in house here, not sure if our fix will help
since we're B7332 sp10.3 NT/SQL7.0.

We found there were actually two separate problems. The first, check your
permissions for the Next Numbers table in SQL, as well as the AB table. If
the appropriate SQL account doesn't have access, it will give you that
error. (We had SQL'd some tables and didn't set the permissions after we
changed the db_owner property) The second fix we found is to get a working
client and export the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\. Next, go into a client you are
having problems with and delete EVERY SINGLE JDE ODBC entry (You may have to
clean out all entries but the defaults, it depends on the system). Next,
import the Registry file, and voila, it works (At least for us....) We had
some VERY weird errors for awhile, but doing that seems to clear it up
whenever it pops up. I'm not sure why it worked for us, (or even what the
problem was!!) but give it a go. Hope that helps, and good luck!

- Scott
 

Guest

Guest
Date: Wed, 8 Nov 2000 00:23:22 -0800 (PST)
To: [email protected]
From: lerwick <[email protected]>
Reply-to: [email protected]
Subject: RE: Next Numbers Issue ~~608:659

Hi,

Can you see a lock on the NN file using WRKOBJLCK? It
would seem really
strange that all your environments could be using the
same NN file though.
We had problems with client access on a single PC
locking NN file when it
wasn't up to the current SP level.

regards, Lerwick
Alstom NZ




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Ca
t=0&Board=OW&Number=659

----- End forwarded message -----
 
Top