Day End Processing Error

[erprider]

Hi Guys

When i am doing day end i am getting an error "Hi Guys


"Day end processing couldnot process all the trasactions due to error"

i have shown some last few line of my Rvspy:
[1ec0] AP0022: APIBD [13:06:32.26].Unload
[1ec0] AP0402: APIBHO [13:06:32.26].Close(view=0x0244171C)
[1ec0] CS0012: CSOPTFD [13:06:32.26].Close(view=0x024451AC)
[1ec0] 0 <==[13:06:32.26;t=0;ovh=0] {}
[1ec0] CS0012: CSOPTFD [13:06:32.26].Unload
[1ec0] 0 <==[13:06:32.28;t=16;ovh=0] {}
[1ec0] AP0402: APIBHO [13:06:32.28].Unload
[1ec0] AP0021: APIBH [13:06:32.28].Close(view=0x02446594)
[1ec0] 0 <==[13:06:32.28;t=0;ovh=0] {}
[1ec0] AP0021: APIBH [13:06:32.28].Unload
[1ec0] AP0023: APIBS [13:06:32.28].Close(view=0x038CB184)
[1ec0] 0 <==[13:06:32.28;t=0;ovh=0] {}
[1ec0] AP0023: APIBS [13:06:32.29].Unload
[1ec0] 0 <==[13:06:32.29;t=2438;ovh=928] {}
[1ec0] PO0335: PODEPR [13:06:32.29].Unload
[1ec0] LT0999: LTDAYND [13:06:32.29].Cancel(view=0x023A300C)
[1ec0] 0 <==[13:06:32.29;t=0;ovh=0] {}
[1ec0] LT0999: LTDAYND [13:06:32.29].Close(view=0x023A300C)
[1ec0] 0 <==[13:06:32.29;t=0;ovh=0] {}
[1ec0] LT0999: LTDAYND [13:06:32.29].Unload
[1ec0] 9903 <==[13:06:32.31;t=64156;ovh=38916] {**ERROR**}
[1ec0] IC0275: ICDEND [13:06:37.10].Close(view=0x0235C7D4)
[1ec0] IC0380: ICOPT [13:06:37.10].Close(view=0x0235CFB4)
[1ec0] 0 <==[13:06:37.10;t=0;ovh=0] {}
[1ec0] IC0380: ICOPT [13:06:37.10].Unload
[1ec0] 0 <==[13:06:37.10;t=0;ovh=0] {}
[1ec0] IC0275: ICDEND [13:06:37.10].Unload






Please assist me, Thanks

 

[Jay Converse]

Those lines mean nothing, they're simply the UI closing down. Look for the last ERROR after a .Insert or a .Update.

 

[erprider]

Thanks for reply!

Then what's the solution for this day end processing error

will you suggest me?Db dump/Db load does it make any sense?

 

[Jay Converse]

No, it doesn't make any sense at all. First you need to look at the log and figure out what the error is.

 

[DjangMan]

Typically once an error condition is met (and not finding a record is not always a true error condition) then the views start to .unload.

 

[erprider]

Thnks for comments Djangman..

as if now I couldnt figure out why its occurs.

 

[erprider]

Well i dump that data in my laptop again i perform the dayend processing with rvspy run .I noticed that .unload doesnt exist compare to previous rvspy and current one .under below

[b1c] LT0999: LTDAYND [10:00:48.62].Cancel(view=0x026CA85C)
[b1c] 0 <==[10:00:48.62;t=0;ovh=0] {}
[b1c] LT0999: LTDAYND [10:00:48.62].Close(view=0x026CA85C)
[b1c] 0 <==[10:00:48.62;t=0;ovh=0] {}
[b1c] 9903 <==[10:00:48.64;t=69391;ovh=38174] {**ERROR**}
[b1c] IC0275: ICDEND [10:01:04.17].Close(view=0x0096A174)
[b1c] IC0380: ICOPT [10:01:04.18].Close(view=0x026C50DC)
[b1c] 0 <==[10:01:04.18;t=0;ovh=0] {}
[b1c] 0 <==[10:01:04.20;t=15;ovh=0] {}

 

[Jay Converse]

Look higher up in the log.

 

[erprider]

Well i took a recent rvspy in that log .unload hasnt appear
its say like .Close

so if any idea ? it would be grateful thanks

 

[ettienne]

Why are you looking for .Unload????
To quote tuba: "Look for the last ERROR after a .Insert or a .Update.

 

[erprider]

Thanks for the reply!
Yes looked after an error it says ICDEND .closed ICOPT .closed,seriously i dont understand that spy
Well Is there anyway to trace the problem? SQL Profiler? something.

 

[Jay Converse]

Rvspy is the only way to trace the problem, and we have given you all the correct answers.

 

[ettienne]

We all use RVSpy to diagnose problems and it works very well.
There will be more than one ERROR logged, some errors are not actually errors, so you need to distinguish between actual errors and non-errors. You are looking at the non-errors, look higher up in the log file, a true error normally occurs after a .Insert or a .Update
I normally start at the end of the log file and search backwards for ERROR. Ignore any errors associated with .Close, .Unload, .Fetch

 

[DjangMan]

You'll see something like (this is not an actual rvSpy log):
ICITEM.Put(fields =1) 'A11030'
ICITEM.Read
ICITEM {* ERROR *}
ICITEM.Unload
... and so on...

This would tell me that Accpac was looking for item A11030 in the ICITEM table and couldn't find it there. So I'll start looking in ICITEM and find out why that item isn't there. OR I'll see who was looking for that item (by scrolling up the rvSpy log). Perhaps this is an old order or someone deleted the item or the item is inactive or I have database corruption. This is the sort of investigation that Ettienne, Tuba2007 and I do all the time. The reasons change for every situation and the logs are invaluable in tracking down these issues.

 

[erprider]

Thnk you very much Djangman.. for the explanation let me scrutinize that as well. Well one quick question do you think a FIXIT Professional Tool(Musick Internation) would be helpful whenever a dayend issue araise? Perhaps a dayend process issue is really pathetic.


Thanks

 

[Jay Converse]

Fixit professional _might_ be useful, but it's highly likely it's not.

 

[ettienne]

FWIW I never use Fuxit...

 

[DjangMan]

Tuba, Ettienne and I don't use FixIt because we've been digging around the Accpac tables for years. You still haven't determine what your actual error is. It might be quite simple and not worth the expense of FixIt.

 

[erprider]

Well why asked is? i have that tool. our company purchase that but honestly i havent use it before.I havent come across how to use it as well.

 

[Jay Converse]

OK, whatever, this thread is getting really boring. Go ahead, run Fixit and see what happens to your day-end error, we're not stopping you.