Allday Consulting's Peachtree and QuickBooks Support Boards

I installed peachtree on windows server 2000. The server will be used to store company files.
I also installed peachtree on a workstation, but after installation, when I try to run the application,
a window pops up and says , "Your database engine on SERVER is unavailable,... etc."
Can I get help on this? my workstations are all running on Windows Vista.

Please help me on this.

This is usually a firewall blocking access to the database (Pervasive) server files over the network.

http://www.peachtree.com/support/firewa ... l_tips.cfm Firewall Tips

http://www.peachtree.com/support/vista/ Issues with Vista

This may help, as well

Here is an excerpt from Peachtree's Knowledgebase related to configuring Firewalls.

What processes do I need to allow through my firewall to ensure that Peachtree will operate correctly?

Question
What processes do I need to allow through my firewall to ensure that Peachtree will operate correctly?



Answer
Most firewalls will prompt you for access when Peachtree is opened for the first time. It is important to allow all processes from Peachtree through your firewall. If any processes are blocked, Peachtree will not operate correctly.

In the event that you block a Peachtree process from running, you will need to go into the exceptions or permissions area of the firewall and allow full access to the process. (Consult your firewall’s documentation if unsure how to add exceptions/permissions.) If you are not sure which firewall program you are using Click Here .Peachtree processes that must be allowed through the firewall:

For Peachtree Accounting 2008

Peachtree processes that must be allowed through the firewall:

PEACHW.EXE or Peachtree Accounting for Windows 2008 (located off the installed program path).
W3DBSMGR.EXE or Pervasive.SQL 9.1 Workstation Engine (typically located at C:\pvsw\bin\w3dbsmgr.exe)
W3LGO103.EXE (typically located at C:\pvsw\bin\w3lgo103.exe)
peachpim15.exe or Peachtree Accounting Component (located at C:\Program Files\Common Files\Peach\V1500\ peachpim15.exe)
peachupdate15.EXE or Peachtree Online Update Component (located at C:\Program Files\Common Files\Peach\V1500\peachupdate15.exe)
AIS2.SERVER.CONSOLE.EXE or AIS 2.1, Server Console (located at C:\Program Files\Sage Software\Integration Services\bin\AIS2.Server.Console.exe)
PeachtreePrefetcher.exe (located off the installed program path).



For Peachtree Accounting 2007

PEACHW.EXE or Peachtree Accounting 2007 (located off the installed program path).
W3DBSMGR.EXE or Pervasive.SQL 9.1 Workstation Engine (typically located at C:\pvsw\bin\w3dbsmgr.exe)
W3LGO103.EXE (typically located at C:\pvsw\bin\w3lgo103.exe)
pHttpXfr14.exe or Peachtree Accounting Component (located at C:\Program Files\Common Files\Peach\V1400\ pHttpXfr14.exe)
OUDOWNLD14.EXE or Peachtree Online Update Component (located at C:\Program Files\Common Files\Peach\V1400\oudownld14.exe)
AIS2.SERVER.CONSOLE.EXE or AIS 2.1, Server Console (located at C:\Program Files\Sage Software\Integration Services\bin\AIS2.Server.Console.exe)


You may not be prompted for all the processes the first time you open Peachtree. The two primary processes that must be allowed upon opening Peachtree are PEACHW.EXE and W3DBSMGR.EXE.

IMPORTANT: Once these processes have been allowed through the firewall, you will need to STOP and RESTART the Pervasive.SQL 9.1 Workstation engine on BOTH the server and the workstations for the changes to take effect, to do this follow these steps:

Pervasive.SQL Configured as a Service

If the computer in question is acting as the Peachtree or Quantum data server, Pervasive.SQL is typically configured to run as a service. Follow these steps to turn off the Pervasive.SQL Workgroup Engine:

In Windows XP, select Start, and then Run.
In the Open box, type SERVICES.MSC and select the OK button.
The Services console will load. In the Services console, right-click on Pervasive.SQL Workgroup engine and select Stop.

A progress bar will indicate that Windows is shutting down the Pervasive.SQL service. This may take a few moments, depending on the speed of your system.

To restart the Pervasive.SQL engine as a service:

In Windows XP, select Start, and then Run.
In the Open box, type SERVICES.MSC and select the OK button.
In the Services console, right-click on the Pervasive.SQL Workgroup Engine service, and select Start. This will restart the Pervasive. SQL service.


Pervasive.SQL Configured as a Startup Process

If the computer in question is a Peachtree or Quantum workstation, Pervasive.SQL is typically configured to run as a startup process. Follow these steps to turn off the Pervasive.SQL Workgroup Engine startup process:

When Pervasive is run as a startup process, it will place an icon in the Windows taskbar next to the time, indicating that the database engine is running.
Right-click on this icon and select Stop Engines and Exit.

This will shut down the Pervasive.SQL database engine.

To restart the Pervasive.SQL engine as a startup process, restart the Peachtree application.

Thanks for the quick response to my post.

I have tried everything that you've said. However, I still get the same error.

I enabled the applications needed to go through the firewall, I stopped and started the database manager.
I do not see the icon that should appear beside the time for the database.
when I check the services, PSQL has already started.

Is it just me, or there really is something on setting up the network for peachtree users?

The only other thing I can think of would be to edit your HOSTS file. These basic instructions work in both XP and in Vista.

http://www.graphicengineer.com/blog/200 ... -on-vista/

If that doesn't work, please consider giving us a call for tech support. Ask for Agnes, she's our resident Peachtree/network guru, she's been supporting it for over 20 years now. Please keep in mind that we do need to charge for phone support.

edit: Turns out Agnes is out at a client's for the rest of this week. Lori is available, however, and she's got a decade+ of Peachtree support experience, as well. I'm our "rookie" in that regard, only 4 years -- but networking is not exactly my forte.