Sage 300

Sage 300 2014 in terminal server environment. When posting AR receipts with large $$ checks paying many invoices (200+), getting ""accpac a/r receipts entry has stopped working"" error. Any ideas on cause/fix? Session appears to have plenty of resources available.

@PhilMcIntosh - look at the SQl server settings. This is usually the issue when posting large set of transactions. Run Profiler when starting the batch posting routine and you should see where it hangs.

@LloydSmith - Now I am told it happens in the actual entry process. Does that make any difference in your recommendation?

@PhilMcIntosh -not at all. Is your client using National Accounts for this process. Usually when we see something where a large set of data is being pulled and there is a slowness, it's almost always related to the SQL server configuration.

The SQL trace showed a number of queries taking 5-10 minutes to run, but when I ran them the next morning in SQL Manager (copied and pasted from the trace results) they were virtually instant...

The the fun begins. You have to check the connection between SQL and Sage. Look at the page file on the server. You may want to consider clearing this file out if it's large.

So they need more RAM on the SQL box? Or the network is falling down?

How much RAM is on SQL now? How is SQL configured to use memory?

48GB installed, SQL limit is 40GB

main Sage 300 DB is 258GB, other DB in use for in-house operations program is 54GB

How about the log file and what is the Restore setting on the database- Simple?

Log file is 30GB, recovery model full - they take incremental backups every couple of hours

Phil - I would never use full for the recovery model with Sage as to how all of the relational tables and I've never known anyone to successfully restore Sage using that model.