07-26-2011 06:37 AM
Loaded ACT to Server 2008 Service Pack 2. Installed using Terminal Server install from Control Panel and all appeared to go well. Started as Administrator and all seemed well.
Logged in as Standard user and it takes 4.5 mins to load ACT and bring up login screen for shared database. changed user to member of Administrators group but this made no difference.
Removed and reinstalled - no change
Created new user - no change
Tested on Demo database - no change
System Windows Server Standard
Service Pack 2
64 bit OS
Intel Xeon 3.6GHz x 2 processors
Appreciate any advice to resolve
07-26-2011 05:12 PM
I've encountered a similar situation where the clients brand new and highly spec'ed Terminal Server simply ran ACT! slowly.
What helped resolve it was giving the ACT! users (via a Windows Security Group) admin rights to the following:
Your mileage may vary, but I hope it helps you.
07-27-2011 03:51 PM
Ben appreciate the response and good advice but I believe have found the cause and answer for a totally different tact which raises more questions.
This site runs a proxy server and the IT guy opened all of the protocols and ACT loads fine for all users, in fact it seems faster on this server than most once this was done but he wants to lock down the system by limiting websites available to users.
He began by turning off HTTP, HTTPS, FTP and then SOCKS. With all but SOCKS ACT worked fine
So what SOCKS ports, website IP's, is ACT using at startup that the IT guy can whitelist is being used?
It seems that something has changed as another site with same IT guy is not experiencing this problem which seems strange being on the same version.
08-01-2011 07:41 AM
So does no one from Sage know the answer to what should be a fairly straightforward question?
08-29-2011 05:22 AM
so this problem still has no resposne from a Sage technical person and if an answer exists maybe it could be passed to a programmer to know what is going on here ????
08-30-2011 08:37 AM
My guess is it's simply Act.com.
Use this tool to analyze all traffic.
Filter it for ActSage.exe.
This will be different in different regions.
09-01-2011 07:01 PM
Appreciate treply and will go and test using the tool you suggested. What I can say is that it relates to some pages in the welcome page and some of the website references that are not resolved correctly.
Having spent some time on this and working with a network admin he suggests that there are errors in the references.