We are using ACCPAC OE 5.2 and have been experiencing problems with it for the past while. What is happening is that the day end stops responding or seems to stop causing the user to do crtl-alt-del and stops the process. We believe that this is causing transction history and details to not match. I have been asked to see if there is a way of seeing if an invoice or other OE transactions are still trying to be processed. Any help would be appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
OE Entry day end problems
- Thread starter dbant2003
- Start date
jayconverse
MIS
STOPS RESPONDING DOES NOT MEAN NOT PROCESSING!
If you are a technical user, you should understand this. If you have been End-tasking, you have likely corrupted your data.
Run RVSPY during Day-end to show that lots of processing is going on.
Jay Converse
IT Director
Systemlink, Inc.
If you are a technical user, you should understand this. If you have been End-tasking, you have likely corrupted your data.
Run RVSPY during Day-end to show that lots of processing is going on.
Jay Converse
IT Director
Systemlink, Inc.
- Thread starter
- #4
The problems that we are experiencing with running a day end are still occurring. The Day End can take anywhere from greater than four hours to a matter of minutes. This was never a problem until we converted from pervasive sql to sequel server database. The transactions details and history do not match especially when the process stops repsonding. We have told the person that does a day end to let the process continue until it is finished or gives an error message. This occurred yeterday and we looked into the deatils and history and the amounts are different or not even there. We have no idea yet as to why this occurring any help would be appreciated
- Thread starter
- #5
I am wondering if anybody can explain why day ends time lenght to complete very from time to time. As a day end is started it can take a couple of minutes to hours to complete. When the day end is working it also slows down our system so much that it is frustrating to have to wait in order for even a screen change to take palce. A day end was started this morning at approximately 7:45 am and it is still running. The IT Department is having a very difficult time in trying to figure this out. Any help or suggestions would be very much appreciated. Thnak you.
- Thread starter
- #7
We had data integrity problems and a database corruption problem The database has been repaired and was supposed to have cleared up the problems. It hasn't improved anything as of yet and data integrity processes with out any errors identified.
Ahhh, that may help explain the problems....
Even though the integrity check does not report a problem it does not mean there are'nt any. Typically a data repair would mean fixing the database till there are no errors reported.
Have you done a dum and load on the data?
Even though the integrity check does not report a problem it does not mean there are'nt any. Typically a data repair would mean fixing the database till there are no errors reported.
Have you done a dum and load on the data?
- Thread starter
- #9
Here is an error from a day end that was just performed and did not complete. The error message states: Internal error. Cannot read OESHCD (1146 OEPOSTI1.C. Day End Processing could not process all transactions. Can someone tell me what this all means. Thank you.
jayconverse
MIS
I've been seeing that error periodically at one of my clients, and I haven't figured it out yet. If you run day-end again, the error goes away, and day-end completes.
Jay Converse
IT Director
Systemlink, Inc.
Jay Converse
IT Director
Systemlink, Inc.
- Thread starter
- #11
We have been looking at changes we have done that may be causing these OE Day end problems. We purchased a Customer Name change product for ACCPAC. We decided to change our numbering scheme for customer, vendors, and inventory numbers so that all our companies were the same. As I said we looked back to when the problems started and coincidently it was when we made these changes to the customer numbers/inventory numbers. The product for changing the customer number was called Customer Number Change Version 5.1A. We were wondering if it was this that is causing the problems with day end processing and whether anybody has experienced any problems after using it.
jayconverse
MIS
I have 20 customers who use that product, and none have reported any problems.
Jay Converse
IT Director
Systemlink, Inc.
Jay Converse
IT Director
Systemlink, Inc.
jayconverse
MIS
Let's see, about 4 have O/E too, and they haven't said anything.
Jay Converse
IT Director
Systemlink, Inc.
Jay Converse
IT Director
Systemlink, Inc.
- Status
Similar threads
- Locked
- Question
- Locked
- Question