Sales Ledger Period End 'Tidy Transaction Process Failed' message

We have a site with the following problem

User is Opera 3 SQL (not SE), version 2.80.00. SL Period end stops with message 'Tidy Transaction Process Failed', click OK on this and it continues with the period end process. Doesn't crash or Error. It has moved the period on but if run list of invoices and credit notes
eceipts and adjustments reports for This period and they have not cleared

Took a backup prior to period end off site and restored, UDS went through fine and so did period end. Repeated on customer site - they still got the same issue.

Then tried company Z on their system, this fails also with same message which we presume now not data. Have restored on same version off site and with customer System folder and still works off site. On customer site have re-run the 2.80.00 program installation

Advised to try with AV disabled, IT company have uninstalled it - only tried Z but still failed

Has anyone else seen this before or have any suggestions please?

Regards

Kerry

Find more posts tagged with

Pegasus - Partner General Discussions

Accepted answers

All comments

steve-coe

Hi Kerry

I seem to remember this one from a while back, but when you mentioned Company Z did it too is strange.

Try moving the ?_SPL folder somewhere else while you run it, i assume it will have loads of files in it.

That worked on one of my sites but it is a while back now though.

alex

We have a site with the exact same problem! It was reported to us at the end of November and we thought it was a one-off. Reported again at the end of January and further investigation now shows it hasn't worked properly since the end of November. They are running Opera 3 SQL v2.80.50.

kerryh

We think happened December also, user doesn’t remember seeing message but noticed message at January period end and then realised This Period reports had December and January transactions

Kerry

richardd

This is usually an issue when Opera is trying to tidy / delete old invoice PDF folders but it can't because there is some other file in the folder. Easy way to confirm this is to up the number of years you keep the PDF images. By law you need 6 Years (72 periods). Up this to 99 and see if the period end works. If it does then you need to start trawling through the PDF folders looking for files which Opera did not create.

claire-craig

Hi Kerry, I have recently had an issue with a customer who is VFP getting problems with the Tidy Files and it was related to the period end trying to delete a PDF file in the A_PDF**** folder however there was nothing in the folder to delete, so it then threw up an error "GOT ERROR ERROR 1962 THE DIRECTORY IS NOT EMPTY"

When I read down the error file I was able to see it was trying to delete a PDF file in the A_PDFS1510 folder however there was nothing in this folder. The first folders in the A_PDF which had pdf's in it didn't start until A_PDF1601

To fix this we needed to replace the memo file on the sales transaction table for transactions before 01/01/2016 with no link to PDF's as there are NO pdf's in the A_PDF pre 2016 - once this was carried out, the sales period end has ran through successfully.

So maybe worth checking if you have invoice/credit note transactions on STRAN with something in st_memo which doesn't actually exist, start at the earliest dated invoices/credit notes.

How you then go about fixing in Opera3 SQL I'm not sure but I'm sure there is a wealth of expertise on here to help :-)

Regards

Claire

alan-bourke

I seem to remember that there can be an issue with hidden, read-only 'thumbs.db' files in the PDF folder tree, these are created in Windows if someone views the folder in thumbnail view.

unknown

The is also what I have normally come across, if you view the error log that Opera creates scroll through it, it should show you where it fell over i.e. the folder

kerryh

Out of interest did you upgrade to 2.80.00 in November or did you await the 2.80.50 release in December

Kerry

kerryh

Hi All

Many Thanks for all your comments,

We agree with the pdf issue as seen this before on foxpro but this usually crashes and we have to fix. However there is no crash or error plus also they don't use invoicingsop so there are no pdf images behind invoices so working very similar to purchase. purchase ledger period ends fine

Tried moving the spool folder and still the same issue

Checked pdf folder for thumbs.db as again we'd seen this before on foxpro and prevented period end running but can't locate any of these either

Also took full data backup including additional files so would like to think if issue in this folder it would replicate the problem with us but it works off site

Regards

Kerry

claire-craig

Hi Kerry, if it is also happening in Demodata could it be something within one of the other root folders or the system folder? Are you able like with VFP to run a repair and re-run the setup.exe of the Opera3 SQL 2.80 - not sure if that is feasible with Opera3 SQL?

alex

The customer was upgraded to v2.80.00 on 11/12/20 but they first logged the issue with us on 02/12/20 so prior to this upgrade. They were since upgraded to v2.80.50 on 23/12/20 and the problem has occurred again after that date.

alex

We've seen the error 1962 many times before and it is usually related to thumbs.db. When this issue occurs Opera crashes with a proper error log so you can see where the problem is.

This time there is no error so no error log. Customer gets a message on screen at the end of the period end process to say the 'Tidy Transaction Process Failed' and you click ok to it. Opera doesn't crash.

As far as we can tell the period end completes ok in the main except STRAN is not updated correctly. The creation date is not blanked out and the period end date is not populated. This is why the transactions continue to appear on the 'This Period' reports.

Our customer reported to us at the end of November so we simply fixed the data. They did not report an issue at the end of December but it must have happened as these transactions have not been updated in STRAN. They reported it again at the end of January.

They are running v2.80.50 now but when the problem first occurred for them they were running v2.74.00.

kerryh

Is your site a foxpro one or Opera 3 SQL?

Kerry

kerryh

Apologies, just looked back at previous messages and can see SQL

alex

It's Opera SQL

alex

kerryh

That's exact same message

Click OK, it continues with the other tidyupdate messages and completes. Period end moved on, TP reports still show data so we believe just stran not updating

Presumably for your user everything else continues to work and update okay without issues

Just trying to work out how best for the user to proceed

alex

Yes, click ok and the process completes and the user carries on. We are working on fixing the data (again) to update the required information in STRAN and have 3 weeks to work out what's causing the issue before they have to run the period end again!

We've just tested company Z on the customers system and the exact same thing happens.

alan-bourke

If anyone knows how to use SQL Server Profiler it might be worth starting the period end and running a Profiler trace, and checking if there are any database engine errors occurring.

alex

Hi Kerry,

Just wondering if you've got any further towards resolving this issue? Sadly we have not! We've ruled out at this point other software the customer has links into Opera but we're no further forward understanding what the problem might be.

Cheers,

Alex

kerryh

Hi Alex

Apologies for the delay. We have got no further forward with this. The end user was going to put a new server in shortly as the server software will be out of date later this year. They have brought this forward to tie in with the payroll upgrade. This week we are going to install SQL and Opera from scratch and see if this makes a difference

Will update you as soon as possible when we can see if this resolves the period end issue

Kerry

alex

Hi Kerry,

Thanks for post. I've just received an update from Pegasus advising the following:-

"Thank you for your update, this issue in Opera 3 SQL was caused by a particular command line in SQL, this has caused the error at Sales Period End, in older versions of the SQL Server, we will fix this so it does not cause issues in older versions of the SQL Server.

We have raised SCR OPERA - 3757 and I have added KB 2186525 which will be updated when it is fixed"

Our customer is running SQL Server 2014 v12.0.2000. I've asked Pegasus if upgrading them to 2017 would resolve the issue and I'm just waiting on a response.

Kind regards,

Alex

Copyright © 2025 Infor. All rights reserved.