Sage Performance issues on SBS 2003

rtl_support
rtl_support used Ask the Experts™
on
Experiencing performance issues on sage when run from an SBS 2003 server. I've checked perfmon, and cannot see any bottlenecks on the server. If I try to copy data from client to server, or server to client (using sage share) it completes very quickly (both client and server use gigabit nics). However if I try to run a reconcile the process can take approximately 40 minutes. If I run the same test using an XP workstation acting as a server the reconcile process runs in under 5 minutes. The server and the workstation (acting as server), and the workstation (acting as client) all sit on the same gigabit switch.

The server is a DC, and runs Exchange, and GFI mailessentials, and acts as a file server.

Does anyone know of any performance issues associated with sage and sbs 2003?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
What AV are you using? did you remember to set up exclusionss on the new server?
Bruce DenneySage 50 Consultant and Integrator

Commented:
As Jamie suggests check the AV on the server, this is the most common cause.  

You should also make sure the exclusions apply on the workstation to the mapped drive and/or the UNC path for the sage data.  

A quick test to eliminate AV as the cause is to just disable it on server and workstation.

There have been MARKED performance difference between using UNC paths and Mapped drives.  I would suggest testing this out in your environment.
Bruce DenneySage 50 Consultant and Integrator

Commented:
Which reconcile process? Vat Return, Bank account?

Try running a Transactional TB as a benchmark and see if there is a big different on that.

Modules>Financials>Reports>Trial Balance Reports>Transactional Trial Balance

Can you give the full long version number of the Sage application

Help>About
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

Author

Commented:
Hello, it is using AVG on the server, and I've set the exclusions. I've even tried disabling avg entirely at the service level. Still the same.

It was just a bank rec, and I've run the same process on the "client to server" and "client to client" setups, and the server always takes about 40 minutes and the client takes about 5 minutes.
Bruce DenneySage 50 Consultant and Integrator

Commented:
Can you try outputting the TB report to a PDF on the server.  

The reconciliation process on the bank account creates a PDF report in the attachments directory, well it does on recent versions.  I am thinking perhaps a possible issue is with the PDF driver.

Author

Commented:
I cant really, as its sensitive data, but doesn't the pdf driver use the local pc driver? Therefore if it was a problem it would have occurred on both setups, as the driver was always the same?
Bruce DenneySage 50 Consultant and Integrator

Commented:
I don't want you to post the pdf here, just run it as a benchmark (instead of the bank rec)

Did using a mapped drive have any difference to using a unc path?

Have you been able to find the full version number yet?

Author

Commented:
Oh, ok. Well my current benchmark is to look at the activity of a bank account. Which on the server takes 3-4 minutes, if run using the client pc as a server it takes about 5-10 seconds.

Both tests use a mapped drive as a reference in the company file.

The version number is 16.00.17.0154
Bruce DenneySage 50 Consultant and Integrator

Commented:
When you say "on" the server, I assume you me when run on a client where the data is on the server, not when you run Sage 50 on the server, please confirm that Sage 50 when run on the server "runs like the wind"


You should switch off / disable  SMB Block Signing

http://support.microsoft.com/kb/887429


You are missing Update 2 which is a "non automatic" update is resolves slow performance issues in the customer and invoicing module.

You description, very much suggests either the unc issue or some sort of network bandwidth issue.

Not sure if you have tried the unc issue yet.




Bruce DenneySage 50 Consultant and Integrator

Commented:
SMB Block signing only applies if you are running a Domain, if you run as a workgroup if shouldn't affect things.

Author

Commented:
Hello, yes sage data on server, app on client.

Already disabled smb signing as it is a domain system.

Don't think it's worth updating sage, as I know it works. Just not through the sbs server.

I've checked the bandwidth of the network, and when running the activity process it uses about half a mb per second.
Sage 50 Consultant and Integrator
Commented:
I suggest you apply update 2 as there are issues.

Have you compared UNC to mapped drive?

Try connecting to the server as a workstation rather than part of the domain.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial