🚀 go-pugleaf

I agree with Mike -- if you only have one user, why have it a server anyway?

At least as a diagnostic aid, you should move it to the workstation.  If the
problem still presents, perhaps Intuit is the right place to be looking for
help.  But it seems more likely to me you're dealing with a network that
isn't set up properly.  "Server Busy" messages can originate anywhere from
the server itself, through the protocol stacks, to the workstation itself.
To conclude automatically that it is an Intuit problem doesn't make a lot of
sense.

A 90mb QB file is pressing the limits of the software, however, and one must
question whether it is time for you to be considering moving on down the
road...

David


"Mike Block - Tax Cut C.P.A." <mblockNO_SPAM@blocktax.com> wrote in message
news:3ab86144.94833896@news.mindspring.com...
> Can you make her system an alternate server so she can run QB locally
> and others can access the file as occasionally needed>
>
> On Tue, 20 Mar 2001 17:21:02 -0500, Christopher <Tyr@Bigfoot.com> wrote:
>
> >I am late getting into this thread, however I must put my two cents
> >in....(whatever that is worth today)
> >
> >We run quickbooks 2000 pro over a 100TX network.  Our accountant uses
> >a new 1.1gig Pentium 3, 128meg memory, Ultra DMA100 7200rpm HD, Matrox
> >G200 8meg video card, and windows 2000 pro Os, etc....
> >
> >Our current file size is around 90meg.
> >
> >We have a problem everyday with program speed and errors.  Our
> >favorite error now is: "Server Busy".  We get this message every day.
> >She is only running Quickbooks, no one else is logged into the network
> >and there is nothing running on the server.  We have been trying to
> >troubleshoot this problem for months to no evail.  Intuit does not
> >admit there is a problem and simple through up their hands we we got
> >to the Vice presidents level.
> >
> >Infact, today I was standing over her and all that was running was
> >there stupid payroll update over the internet and it reported a server
> >busy message.   No windows were open in quickbooks and nothing else
> >was running on her machine.
> >
> >I have since hypothisized that the "Server Busy" message must be a
> >COM problem and that Quickbooks is not admitting to ther defect.
> >
> >At this point I would not recomend this product to anyone due to the
> >lack of knowledgable support or any support for that matter.  I am
> >truly frustrated!!!
> >
> >If anyone has any sugestions on this topic it would be estatically
> >recieved.
> >
> >TIA!!
> >
> >
> >
> >On Thu, 08 Mar 2001 01:40:50 GMT, r_brummel@NOworldnet.JUNKatt.net
> >wrote:
> >
> >>On Tue, 06 Mar 2001 06:19:45 GMT, "David Ray" <david@timecalc.com>
wrote:
> >>
> >>>>File opening should not be a slow process under NT.  If it is, it is
at
> >>>>least an indication that you are suffering some other network
difficulty OR
> >>>>the PC is just way, way too slow to be a server.
> >>
> >>If the "PC" is too slow to be a Server, then I guess it is just an
illusion
> >>that my client is actually doing work every day, using said Server.
Perhaps
> >>the solution to your 'puzzle'  is that economics play a role in what is
"too
> >>slow" versus what is "acceptable performance."
> >>
> >>As I noted, defragmentation created a great improvement. That was the
purpose
> >>of my post.
> >>
> >>>>The structure of NTFS is such that file opens and closes are faster
than
> >>>>with any other popular OS (other than Linux, maybe...)
> >>
> >>I never said it was slower than Apple or Netware. I just said it was
> >>sluggish. Note that NTFS is a file system, not an OS.
> >>
> >>>>
> >>>>
> >>>><r_brummel@NOworldnet.JUNKatt.net> wrote in message
> >>>>news:3aa9870f.24370559@news.mindspring.com...
> >>>>> I was stumped by a slow QB company file running from a slow 3-year
old
> >>>>> Server. But defragmenting the Server (NTFS drives) made a huge
difference;
> >>>>> while files still open sluggishly, once open they are adequately
> >>>>responsive
> >>>>> (ie no more sclerotic "Searching....." etc messages.) At least for
now.
> >>>>>
> >>>>> So, I recommend defragmenting, particularly NTFS. (I used Raxco's
Perfect
> >>>>> Disk, which was discussed in the comp.os.ms-windows.nt.admin.misc
forum (I
> >>>>> think).
> >>>>>
> >>>>> Richard Brummel
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>      Mike Block - Tax Cut CPA
>  World's #1 QuickBooks Top Tester
>     FREE  NetLedger accounting
>   FREE 462p QB books/error codes
> 100+ QB add-ons http://blocktax.com/
> QB no-spam news: biz.comp.accounting
> -----------------------------------
> Spam bait admin@localhost abuse@localhost
>  webmaster@localhost postmaster@127.0.0.1
>  enforcement@sec.gov cyberfraud@nasaa.org
>
>
>