Page 1 of 1

Sage line 50 creates faulty CSV files

Posted: 09 Nov 2011, 15:04
by sandy
I use Sage line 50 version 12.01.0070 on Windows XP home edition V5.1. I think it is 32 bit. When saving Sage reports as PDF, CSV and txt sometimes they save right first time but often there is no creation date or file size is zero. Sometimes repeating the save puts things right. What is the solution, please?

Re: Sage line 50 creates faulty CSV files

Posted: 09 Nov 2011, 17:18
by brucedenney
If you are seeing a 0 file size, this is normally, because you have opened (and locked) the file before sage has finished running the report (it goes to save the file and it can't open the file to write it because you have it open already)

Try waiting a while... before opening.

Re: Sage line 50 creates faulty CSV files

Posted: 10 Nov 2011, 11:19
by sandy
I usually run the report, print it, save as PDF, save same report as CSV with slightly different file name, alt&tab to folder and read the size without opening the file. I saved reports without a problem for years and used to save all the reports I wanted without looking at the folder until I started to find zero files. I think the first dodgy report files were created in 2009. I have had this version of sage since 2006. I have just done a test. I ran the report, did not print, saved as CSV then as PDF with different file name. Ran the same report again saved as PDF and saved again as PDF also with different file names, waited over 1 minute and alt&tabbed to folder and just looked at the result. Test 1 128KB. Test 2 102KB. Test 3 0KB, test 4 0KB. I have noticed that the larger the file and the more files I save in the session the more likely 0 files seem to be.

Re: Sage line 50 creates faulty CSV files

Posted: 11 Nov 2011, 22:45
by brucedenney
So the issue is intermittent sometimes its saves fine and other times it doesn't

This applies to saving as PDF files, does this also apply to saving as other types of files?

The intermittent nature is a little worrying, what anti virus are you running?

Have you configured it to have the "Sage" exclusions?

Re: Sage line 50 creates faulty CSV files

Posted: 12 Nov 2011, 12:25
by sandy
Yes it is intermittent. I have had the problem with PDF, CSV and TXT files. The Anti Virus was Norton until July. Now Microsoft Security Essentials. I have not noticed any difference between what happens now and what happened with Norton. I have not configured the Anti Virus or the Windows Fire Wall to exclude Sage. I have tried to think what changed in 2009. I did instal Iolo Drive Scrubber. I don't use it often. I used the deep clean once or twice in 2009 but not since.

Re: Sage line 50 creates faulty CSV files

Posted: 14 Nov 2011, 11:47
by brucedenney
Did Norton un-install properly?

I have seen it fail to fully uninstall itself many times.

Look in program files for Symantec and/or Norton Folders to make sure that it is fully removed.

-------

Where are you saving the files?

Could this be linked to the place you are saving the file to:- Local C:Disk, a network file share, a USB Stick ...

-------

Drive Scrubber

I have not encountered this before, but it sounds like it is "watching" the disk, so there is potential for it to interfering with things.

Can you deactivate / uninstall it and see if the problem goes away?

---------

Final suggestion.

Run Hijack this and post the log file back here. you can download it from the link below.
http://download.cnet.com/Trend-Micro-Hi ... 27353.html

Re: Sage line 50 creates faulty CSV files

Posted: 17 Nov 2011, 15:19
by sandy
Thank you.
A few Norton files were left behind. I have deleted them .
The files are saved to My Documents on the C drive.
I have disabled the Drive Scrubber incinerator.
Something has changed. Although 3 out of 8 test files showed zero size initially, after I closed and later re-opened the folder, the correct size was showing. I could live with that. I could just look at the folder after I have saved all the reports for the month. I'll see how I get on with the November reports.