Can you be more specific about the areas where Sage is running poorly?

Nearly everything. Loging into the system. opening of screens say one click to open purchase order entry screen, it takes about 2 minutes before it can open. a sage screen that keep moving appears

Check the PATH and the Customization Directories, you probably renamed the server and the old server is still referenced.

And confirm that anti-virus software is properly configured to only have the server check itself and for the workstations to not check the Sage binaries on the network.

how do i check the Path Jay? there is nothing under customization directories

how do i check the Path Jay? there is nothing under customization directories

Start/Run/CMD/Enter/PATH/Enter

i,ve checked the path and its showing me the below. i,ve run the path on the server which is \\server02 and also shows a path in the C drive


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\AccPacAdm1>path
PATH=\\server02\Progs\Sage\Sage Accpac\RUNTIME;C:\MSData\Shared Data;C:\Progs\Sa
ge\Sage Accpac\RUNTIME;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C
:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL
Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\
Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsof
t SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsof
t Visual Studio 9.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Micros
oft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\110\DTS\Binn\
;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Mi
crosoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\1
10\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft Visual Studio 1
0.0\Common7\IDE\PrivateAssemblies\;C:\Program Files (x86)\Microsoft SQL Server\1
10\DTS\Binn\

C:\Users\AccPacAdm1>

You have RUNTIME in there twice
- find out which is the correct folder for your runtime
- remove one of them
- also make sure you do not use UNC - use the drive letter (when you use UNC it sometimes does not start the services)

FYI, there is _nothing_ wrong with UNC, you don't have use drive letters.

it seems they are all pointing to one place

The fact that you have two PATHs to the programs means that at one time, the full application was incorrectly installed on the local C: drive. You need to (1) uninstall the local version, (2) edit the PATH to take out all references to Sage folders, then (3) re-run workstation setup.