Trying to post a large GL Journal, 80000 lines approx, posting fails when two thirds of the way through posting. Version 3.01.B of Attain on MS SQL Server, Windows 2000 Server. Any ideas, user said something about overflow error ???
Hello, Please could you give us some further details? You say that Attain returned an error message saying that there was an overflow error, please could you post the error message for us to see? Overflow errors will usually let you know the value Attain is unable to handle so that you can identify the field, global or local variable it is unable to pass it through. Hope this is of some assistance. -------------------------------- Edward Bloomfield Navision Support Consultant Cambridge Online Systems Limited www.cambridgeonline.net
This is probably a problem with a single transaction in your journal. The easiest way to find it is to turn on the debugger and see the line the error is occurring on.
[User cleared the error message so we don’t know full details. However if we try to split the journal, say into 3 x 30000 lines and post Navision now hangs and the job has to be terminated. Seems like some sort of memory threshhold such as transaction log size exceeded. We posted a similar journal recently which had 35K lines and had no problems.]Originally posted by EBloom: Hello, Please could you give us some further details? You say that Attain returned an error message saying that there was an overflow error, please could you post the error message for us to see? Overflow errors will usually let you know the value Attain is unable to handle so that you can identify the field, global or local variable it is unable to pass it through. Hope this is of some assistance. -------------------------------- Edward Bloomfield Navision Support Consultant Cambridge Online Systems Limited www.cambridgeonline.net
[/quote]
Hello Damian, Does the original error message re-occur if you attempt to post the whole journal again? You could try posting the journal in smaller blocks (Say 10,000) lines to see if it is a specific line that Attain is having a problem with. Attain may be struggling with a problematic entry, and the memory issue is merely a symptom of the problem or it may be just a strain on the available memory, as you suggest. -------------------------------- Edward Bloomfield Navision Support Consultant Cambridge Online Systems Limited www.cambridgeonline.net
Problem seems to be memory related. When journal posted during offpeak time it worked successfully.