USER TERMINALS CRASHING, SLOW RESPONSE SPEEDS
Interprise Suite Community
 Home          Members     Calendar     Who's On

Welcome Guest ( Login | Register )
        


12»»

USER TERMINALS CRASHING, SLOW RESPONSE SPEEDS... Expand / Collapse
Message
Posted 8/28/2009 4:31:54 PM Post #254
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Recently I started work with a company using Interprise.
We have approx. 5-6000 stock items in database, separate server managing email/net etc. have just spent lots of money installing new server to fix speed problems.
I was amazed to see how slow the response at the terminal level was, 5 seconds to add a stock item to an order, 12 secs. to display an invoice to print, 15 secs to display an item number that has several possibilities etc. etc.
Worse, it routinely crashes terminals at the site, often 4-5 times per day (not every terminal).
Sometimes whilst entering a sales order, the client list fills the screen, and so on with many problems.
It is a nightmare. We are waiting for the "upgrade fix" that has been promised, which is apparently being written in the Philippines, and I believe we do not even have a dealer/distributor in our country now, only a 'reseller'.
Are we alone in this? do we need someone to properly configure our server and PCs? or is this all sounding very familiar?
HELP please.
Posted 8/31/2009 1:27:11 AM Post #255
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Hi

What version are you running? Also what hardware you got in the terminals, what version of SQL server you running on the server / clients and what hardware? How are your server, terminals connected together ( LAN / Internet and what speed). Are you using any cache databases on your clients? Also how big is the main database / log files roughly?

Thanks
Matt
Posted 9/1/2009 4:42:03 AM Post #259
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Thanks Matt,
I will get back to you

DB
Posted 9/5/2009 9:54:40 AM Post #262
 

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member
Hi
Some of the issues you describe are associated with earlier releases of IS. Even the later or current release can give such results if not configured correctly.
If you let us know the version number you are running, and the specs etc as per Matt's post we should be able to give you some useful feedback.
Cheers
Antony
Posted 9/18/2009 4:23:16 AM Post #272
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Thanks,
I am waiting for a response to those questions, as soon as I get them I will post again, meantime we waste hours each day with terminal crashes and very SLOW response times.

thanks
Posted 9/18/2009 7:19:19 AM Post #273
 

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member
We have similar issues. By chance do you have any general configuration suggestions on how to improve the performance of IS.

Cheers

Posted 9/19/2009 7:08:08 AM Post #274
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Hi

I have a few:

Change dbase recovery model to simple ( Be aware of backup implications ! http://msdn.microsoft.com/en-us/library/aa173563(SQL.80).aspx)

Shrink, Rebuild Index, Reorganise index, logs and databases using an SQL daily maintenance plan. Especially check your log file sizes as they can get really large (100gb!! + ) and are largely pointless if you have a proper backup schedule.

Make sure you are at least using SQL server standard ( http://www.microsoft.com/Sqlserver/2005/en/us/compare-features.aspx ) well worth the investment if you are using the database a lot.

Optimize SQL server memory settings, processor affinity and etc.

Use a cache database, really speeds things up.

Improve network speeds between server and clients.

Get a better server, use Server 2008 (x64 if possible) at least Intel x3320 or better at least, 4gb ram min and a descent raid array.
Could split Dbase and Web Server if running a real monster of a website.

Matt
Posted 9/24/2009 2:09:48 AM Post #278
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Hi Antony,
I FINALLY have answers to the configuration questions you raised. They are:
We are running Interprise Suite 2007 SP5.3)

Hardware in the terminals, version of SQL server:
DL 180G5 (on terminal server) was 2GB ram (now 4GB)

Backend – ML150 G3 3GB ram
SQL Server 2005 Service Pack 3 2005.90.4035 workgroup edition.

The server, terminals connected together via 100MB LAN
ADSL2+ Internet remote (theoretically)

No cache databases on clients.

The database is no bigger then 2GB. The log is no bigger then 1GB

We have now replaced/exchanged all hardware and found no difference to the performance so can conclude it is to do with the software and / or its configuration.

It is not uncommon for every terminal in the company to crash 5-6 times per day, and very slow response times.
Appreciate any help we can get!
thanks David
Posted 9/28/2009 3:41:57 AM Post #279
 

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member
Hi Duke
Sorry for delay been away from the office - I feel your pain on this

Nothing obviously wrong in your hardware setup. What have your IS support said - I'm sure lots of us here would love to know their responce?

What effect does load have on your timings? Say you do the same tests when no other users are on the system.
Are you running a website off the system or is it just the account apps?

I have a decent live dev server that you are welcome to test against - to try and narrow down where the issue is.
Cheers
Antony
Posted 9/28/2009 5:09:54 AM Post #280
 

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie
Hi Antony,

the 'dealer' keeps assuring us that the 'soon to be available' software upgrade will alleviate these problems, but they have been saying that for 3-4 months now - all coding is being done in the Philippines it seems.
Not sure how much beta testing has been done, I'm guessing we are about to do that for them!
System load has NO affect on the performance at all. Even at 6pm, with only two users on-line, the system constantly crashes the terminals.
No, we do not run our web site on the system at all.
We have noticed that if a terminal crashes, then it is most likely that several others will too. Converting orders to invoices and/or printing invoices seems to be the most common action prior to crashes. Generally though the whole system is woefully SLOW at even the simplest tasks. Just composing a simple invoice initially takes 12-14 seconds!
Search of the data base for a product code can take longer.
We surely can't be alone in this mess.

HELP!!!
« Prev Topic | Next Topic »

12»»

Reading This Topic Expand / Collapse
Active Users: 0 (0 guests, 0 members, 0 anonymous members)
No members currently viewing this topic.
Forum Moderators: Bill Dimes, John Grande, BJ Dimes, Terry Palmer

Permissions Expand / Collapse

All times are GMT -8:00, Time now is 5:34pm

Powered By InstantForum.NET v4.1.4 © 2012
Execution: 0.031. 10 queries. Compression Disabled.
Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Sign up for our Email Newsletter

Links to our Sponsors

DimeSoft Business Solutions Logo Interprise Suite Plugins Logo Logo Ad

Recent DimeSoft Blog Posts

Recent InfoSourcing Blog Posts

Recent Premier Blog Posts