Hi Emelda

Please confirm the following:
Have you perhaps restarted the local PC on which this error was observed on?

'Access Violation errors are normally due to some kind of temporary low PC memory related issues and a restart may resolve it.

Kind Regards

Bennie 

We have several times, we even tried restoring the data on different machines - we are suspecting the data to be too large.

Thanks Emelda

Please confirm the following:

1. Current sizes of the company DB' MDF and LDF file sizes 

2. Is the client running MS SQL Express or Standard or Enterprise

3. Evolution version?

4. MS SQL Server/Express version?

1. Current sizes of the company DB' MDF and LDF file sizes

MDF = 61.1gb; LDF = 18.7gb

2. Is the client running MS SQL Express or Standard or Enterprise

SQL Standard Edition

3. Evolution version?

Sage Evolution 10.1.3.007

4. MS SQL Server/Express version?

2017

Thanks Emelda

Find attached an article on how to shrink the company DB's LOG file.

When done, please carefully test the outcome and then provide feedback.

6787.SHRINKING THE SQL LOG FILE NEW.pdf

Good day. Unfortunately that did not work :(

Thanks Emelda

Please also confirm:

1. Are all users on the network observing the same error?

2. Is Evolution locally installed on each PC or is it accessed via a DRP/Terminal Server connection?

3. If you run the Age Analysis report for only one customer and for one period, is the same error observed? Or is the error only observed when you widen the report range? E.g. running for MANY or all customers over several months? 

4. Please confirm again the current size of the Evolution company Database LDF file after the shrink has been completed.

Kind regards

Bennie 

1. Are all users on the network observing the same error?

Yes - including on a test server.

2. Is Evolution locally installed on each PC or is it accessed via a DRP/Terminal Server connection?

It is locally installed.

3. If you run the Age Analysis report for only one customer and for one period, is the same error observed? Or is the error only observed when you widen the report range? E.g. running for MANY or all customers over several months? 

For one customer or a smaller group it runs well. If you run the report, for all customers, straight to print without previewing first it runs well. However when you run for all customers and preview first then the problem appears.

4. Please confirm again the current size of the Evolution company Database LDF file after the shrink has been completed.

684mb

Thanks Emelda

Please run the following SQL script in the company database:

select * from postar

Now check how many records are fond in the postar table.

3 849 309 rows

Thanks Emelda

Wow!, 3.8 million records is really a lot!

And that I believe to be the reason for the Access Violation error - which is always some kind of indication of some kind of internal inefficiencies preventing the execution of the task, in this case running the report. 

Therefore, please do the following:

1. Backup the company

2. Restore the backup as DEMO

3. Locate-, login to the DEMO company and run a Customers/Sales | Maintenance | Purge Transactions

4. Purge all transactions before 1 Jan 2018

5. Again check how many records remain in the POSTAR table

6. Now test your reporting query and advise the outcome.

Kind regards

Bennie 

I did mention in the beginning that we are suspecting that the data is too large. However we will do as you have said in the test server and advise.

Excellent, thanks Emelda

Unfortunately the purge did not resolve the issue.

I will try to purge 2 more years and advise.

Purge all transactions before 1 Jan 2020, still did not resolve the error

Hi Emelda

And after the latest purge, how many records still remain in the POSTAR table?

772 126 rows

Thanks Emelda

Please also confirm:

1. Are all users on the network observing the same error?

2. Is Evolution locally installed on each PC or is it accessed via a DRP/Terminal Server connection?

3. If you run the Age Analysis report for only one customer and for one period, is the same error observed? Or is the error only observed when you widen the report range? E.g. running for MANY or all customers over several months? 

4. Please confirm again the current size of the Evolution company Database LDF file after the shrink has been completed.

1. Are all users on the network observing the same error?

Yes - in this case even on the client server as well as our internal test server

2. Is Evolution locally installed on each PC or is it accessed via a DRP/Terminal Server connection?

It is locally installed

3. If you run the Age Analysis report for only one customer and for one period, is the same error observed? Or is the error only observed when you widen the report range? E.g. running for MANY or all customers over several months?

The error is observed when you preview for all customers - by group or by customer range doesn't produce that error.

4. Please confirm again the current size of the Evolution company Database LDF file after the shrink has been completed.

576KB

Thanks Emelda

Ok, let's handle this query in a more formal way. Therefore, please do the following:

1. Log this query with Sage Evolution Support using the link below but please request that  the new query be sent for my attention and I will then continue on this matter.

2. Please also include all of my questions and your answers in the query logging so we don't have to start from the beginning again.

I may then also later require a company DB upload.

Kind regards

Bennie 

Done. HD14410739

Thanks Emelda

I received the new incident (support ticket) and ill soon follow up with you again

Kind regards

Bennie 

Please will you help me, how did you resolve the access violation error in Sage 200 evolution v10

Hi Moreblessing

Can you please confirm the following?

1. Sage Evolution version and build? 

2. Are all users observing the same error?

3. Was it working fine earlier? 

4. if Yes, what recently changed on the network? E.g. an Evolution Server change, Evolution upgrade etc. 

5. Is the same error observed in all companies?

6. Are you running the Age Analysis report with the option to 'Print Transactions" when the error is observed or even without that option selected? 

Kind Regards

Bennie