sage act! premium web administrators guide
TRANSCRIPT
Sage ACT! Premium 2011
Sage ACT! Premium 2011 Web Administrator's Guide
Copyright © 2010 Sage Software, Inc. All Rights Reserved.
Sage, the Sage logos, ACT!, and the Sage product and service names mentioned herein are registered trademarks or
trademarks of Sage Software, Inc. or its affiliated entities. Microsoft SQL Server, Windows Vista and the Windows logo are
trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks
are the property of their respective owners.
Released BETA/2010 for Sage ACT! Premium 2011
Version: UA13-BETA1
This material may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium
or computer-readable form without prior consent in writing from Sage Software, Inc., 1715 North Brown Road Lawrenceville,
GA 30043 ATTN: Legal Department.
ALL EXAMPLES WITH NAMES, COMPANY NAMES, OR COMPANIES THAT APPEAR IN THIS MANUAL ARE FICTIONAL AND DO NOT
REFER TO OR PORTRAY IN NAME OR SUBSTANCE ANY ACTUAL NAMES, COMPANIES, ENTITIES, OR INSTITUTIONS. ANY
RESEMBLANCE TO ANY REAL PERSON, COMPANY, ENTITY, OR INSTITUTION IS PURELY COINCIDENTAL.
Every effort has been made to ensure the accuracy of this material. However, Sage Software, Inc. makes no warranties with
respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose.
Sage Software, Inc. shall not be liable for any errors or for incidental or consequential damages in connection with the
furnishing, performance, or use of this material or the examples herein. The information in this material is subject to change
without notice.
End User License Agreement
This product is protected by an End User License Agreement. To view the agreement, go to the Help menu in the product, click
About Sage ACT! Premium, and then click the View End-User License Agreement link.
Published by
Sage Software, Inc.
8800 N. Gainey Center Drive, Suite 200
Scottsdale, AZ 85258
(480) 368-3700
10 9 8 7 6 5 4 3 2 1
Contents
Introduction i
Getting Started 1
Planning Your Installation 3
About Installing Sage ACT! Premium (Web client) in Single or Multiple Web Server Configurations 4
About User Preferences 5
About the ASP.NET Process and User Impersonation Accounts 6
Creating aWindows Impersonation User Account 6
Configuring Access to Sage ACT! Premium (Web client) 7
Setting Up Sage ACT! Premium Web Access 7
How Users Access Sage ACT! Premium Via TheWeb 9
Access From Inside a Common Network 9
Access From Outside a Common Network 9
Setting Up Shared User Preferences Across Web Servers 9
Integrating Sage ACT! Premium (Web client) with Other Applications 11
Editing the Web.config File for Outlook Integration 11
Installing Components to Use Microsoft Outlook 11
Installing Components to Use Microsoft Word 12
Troubleshooting Sage ACT! Premium (Web client) 13
IntroductionWelcome to Sage ACT! Premium 2011. Sage ACT! Premium is the #1 selling Contact and Customer
Manager in the world.
Sage ACT! Premium (Web client) lets users access Sage ACT! Premium databases using a supported
browser. It is important that you review the full system requirements and supported compatibility list at
www.act.com/2011systreq/act.
Whether you are installing Sage ACT! Premium (Web client) 2011 for the first time (New User) or
upgrading from an earlier version (Upgrade User), this guide provides the information to:
l Organize and plan for a Sage ACT! Premium (Web client) installation.
l Configure user access to a Sage ACT! Premium (Web client) database.
l Manage and secure the software.
IMPORTANT:
New Users: See the Installing Sage ACT! 2011 for New Users guide alongwith this Web
Administrator's guide to complete your Sage ACT! Premium (Web client) 2011 installation. The
installation guide provides the steps to install, register, and activate a Sage ACT! Premium 2011
installation and is includedwith the software as a printed guide or available as a PDF on the Sage ACT!
Premium 2011 DVD.
Upgrading Users: See the Upgrading to Sage ACT! Premium 2011 from ACT! versions 2005 (7.x) -
2010 guide alongwith this Web Administrator's guide to complete your Sage ACT! Premium (Web
client) 2011 installation. The upgrading guide provides the steps to install and upgrade your database
and is available as a PDF on the Sage ACT! Premium 2011 DVD.
Browser Requirements to Access Sage ACT! Premium (Web client)
Users can access the Sage ACT! Premium (Web client) software through Microsoft Internet Explorer® or
Mozilla® Firefox®* browsers. Some Sage ACT! Premium (Web client) features are not available
depending on your browser choice. The following sections describe the requirements and the feature
limitations for each browser.
*Mozilla and Firefox are registered trademarks of the Mozilla Foundation.
Internet Explorer Requirements and Limitations
The requirements for Internet Explorer are:
Override automatic cookie - Enable the option.
First-party and Third-party Cookies - Enable the Accept option.
Trusted Sites zone - Your Sage ACT! Premium (Web client) site domain must be added to the Trusted
Sites zone. This ensures the application will function properly. Some features, such as pop-upwindows,
may not work correctly if your Web site is not in the Trusted Sites zone.
Web Help on Windows Server® 2003 or Windows Server 2008 - To use the Help on the Sage
ACT! Premium server application on these operating systems, ensure the "about:internet" site is added
to the Trusted Sites zone or your local intranet zone. This Help file is an uncompiledWebHelp system
which includes the Mark of the Web (MOTW) setting in each Help topic (.htm). The MOTW setting has
the "about:internet" text for each Help topic.
ActiveX® security - To use the Word Processor for creating documents and templates for
correspondence, you must configure ActiveX® security to allow users to install two ActiveX controls —
TX Text Control and Common Dialog. TX Text Control installs with Sage ACT! Premium and has the same
security setting as Sage ACT! Premium. Common Dialog is part of the Microsoft security zone which
some users may need to install. Default browser settings typically prompt users to install ActiveX
controls. You can safely manage these ActiveX controls in one of two ways:
l If your users maintain default browser settings, the Sage ACT! Premium (Web client) software
prompts them to install one or both of these ActiveX controls. Inform users that it is safe to
Sage ACT! Premium 2011 Web Administrator's Guide i
install these controls.
l If your client-side Web security policies prohibit the installation of ActiveX controls, you may add
both the domain associated with your Sage ACT! Premium (Web client) server installation and
Microsoft.com to the Trusted Sites zone in Internet Explorer. Configure Internet Explorer to
prompt users when installing ActiveX controls only for sites in the Trusted Sites zone. Doing this
bypasses the ActiveX security constraints only for the necessary controls.
The limitations in Internet Explorer are:
l Users cannot access the View Source function.
l Users cannot access the right-click shortcut menu.
Note: On Windows Vista®, if Web client users on Internet Explorer plan to use the Outlook Integration
component or save word-processor documents and templates locally, they must add the Sage ACT!
Premium (Web client) site to the Trusted Sites zone. For more information about security zones, see
Internet Explorer Help.
Firefox Requirements and Limitations
The requirements for Firefox are:
l Accept cookies from sites and Accept third-party cookies options must be selected - To
check your settings, click Tools>Options. Select the Privacy panel. From the Firefox will list, select
Use custom settings for history.
l Enable Enable JavaScript™ option is selected - Under Tools>Options, click the Content
panel. Ensure the Enable JavaScript option is selected.
l Pop-up windows is allowed - Under Tools>Options, click the Content panel. By the default, the
option to Block pop-upwindows is selected. Click Exceptions and add the Sage ACT! Premium (Web
client) site domain to the list.
The limitations with Firefox are:
l Users cannot use Outlook integration functionality which includes Outlook calendar and contact
synchronization and use of Smart Tasks.
l Users cannot use the Sage ACT! Premium Word Processor functionality.
l Users cannot use Mail Merge functionality.
ii Sage ACT! Premium (Web client) 2011
Getting StartedIn this section, you will learn about:
l Installation checklists for New and Upgrading users.
l How to plan your installation, including common configuration scenarios and suggestions.
l About the ASP.NET Process and user impersonation account.
l About installing Sage ACT! Premium (Web client) in single or multiple Web server environments.
l About user preferences.
Installation Checklists
The following installation checklists outline the tasks you must complete to install and configure Sage
ACT! Premium (Web client) 2011 for New Users (no version of the software exists) or Upgrading Users
(a previous version exists).
New Users need the Installing Sage ACT! 2011 for New Users guide as well as this Sage ACT! Premium
2011 Web Administrator's Guide.
Upgrading Users need the Upgrading to Sage ACT! 2011 from ACT! versions 2005 (7.x) - 2010 guide as
well as this Sage ACT! Premium 2011 Web Administrator's Guide.
New Users Checklist
Task Document Refer to Section
1Determine whether you will use a single-server or multiple-server configuration.
Sage ACT! Premium2011 WebAdministrator's Guide
"Planning YourInstallation" on page 3.
2 Prepare to install.Installing Sage ACT!Premium 2011 forNew Users
"Preparing to Install"
3Install, register, and activate Sage ACT!Premium (Web client).
Installing Sage ACT!Premium 2011 forNew Users
"Installing the Software"
4 Create a databaseInstalling Sage ACT!Premium 2011 forNew Users
"Creating a Database"
5 Add users to the database.Installing Sage ACT!Premium 2011 forNew Users
"Adding Users"
6Install other software to use with Sage ACT!Premium (Web client).
Installing Sage ACT!Premium 2011 forNew Users
"Installing OtherApplications"
7Create a Windows Impersonation useraccount.
Sage ACT! Premium2011 WebAdministrator's Guide
"Creating a WindowsImpersonation UserAccount" on page 6.
8Configure access to your Web site andprovide users with access information.
Sage ACT! Premium2011 WebAdministrator's Guide
See "Configuring Accessto Sage ACT! Premium(Web client)" on page 7.
9Integrate Sage ACT! Premium (Web client)with other applications.
Sage ACT! Premium2011 WebAdministrator's Guide
"Integrating Sage ACT!Premium (Web client)with Other Applications"on page 11.
Sage ACT! Premium 2011 Web Administrator's Guide 1
Upgrading Users Checklist
Task Document Refer to Section
1 Prepare your database for upgrading.Upgrading to SageACT! 2011 from ACT!versions 2005 - 2010
"What You Should KnowBefore You UpgradeYour Database"
2 Prepare to install.Upgrading to SageACT! 2011 from ACT!versions 2005 - 2010
"Preparing to Install"
3Install, register, and activate Sage ACT!Premium (Web client).
Upgrading to SageACT! 2011 from ACT!versions 2005 - 2010
"Installing, Registeringand Activating SageACT! 2011"
4 Upgrade your database.Upgrading to SageACT! 2011 from ACT!versions 2005 - 2010
"Upgrading YourDatabase"
5Install other software to use with Sage ACT!Premium (Web client)
Upgrading to SageACT! 2011 from ACT!versions 2005 - 2010
"Installing OtherSoftware"
6If needed, create a Windows Impersonationuser account.
Sage ACT! Premium2011 WebAdministrator's Guide
"Creating a WindowsImpersonation UserAccount" on page 6.
7Configure access to your Web site andprovide users with access information.
Sage ACT! Premium2011 WebAdministrator's Guide
"Configuring Access toSage ACT! Premium(Web client)" on page 7.
8Integrate Sage ACT! Premium (Web client)with other applications.
Sage ACT! Premium2011 WebAdministrator's Guide
"Integrating Sage ACT!Premium (Web client)with Other Applications"on page 11.
2 Sage ACT! Premium (Web client) 2011
Planning Your Installation
Planning Your Installation
To determine whether you will install the Sage ACT! Premium (Web client) software and database
together on one server or install them on separate servers, consider the following:
l The number of users requiring access to the database as well as the number of users accessing
the Sage ACT! Premium (Web client) site.
Note: For scalability recommendations, review the system requirements at
www.act.com/2011systreq.
l The frequency and intensity of users working with the software and of other services running
on the server.
l Whether users need access from both inside and outside your network. If access is required
from outside the network, two possible server/database configurations are:
l Install Sage ACT! Premium (Web client) in a workgroup using a single server configuration
where the Web server also hosts Sage ACT! Premium (Web client) databases.
l Install using a multiple server configuration where you have aWeb server hosting the Sage
ACT! Premium (Web client) software and IIS and a database server hosting the Sage ACT!
Premium (Web client) database (including the software to manage the database). You then
connect to the database from the Web server. (Recommended for more than 30 users).
Note: Both server configurations are discussed later in this guide.
Configuration Suggestions
The following are suggestions for configuring Sage ACT! Premium (Web client). Actual results may vary
depending on the size of your database and network configuration.
Some configuration suggestions are:
l Host the application server on a dedicated instance of SQL Server.
l OneWeb server can scale up to 100 users.
l One database server can scale up to 400 users.
l The database server should have 2 gigabytes (GB)memory for every 50 users in the database.
The Hard Drive speed is most important on this computer. With faster hard drive speeds, users
may experience better performance. This computer can also take performance benefits if you
use 64-bit SQL Server and have quad core processors.
l The application server should have 2GBmemory for every 50 users in the database. CPU and
memory are most important on this computer. With more memory, users may experience
better performance.
l If possible, distribute mail merge and reporting tasks. On the client machine, mail merge can be
the most performance consuming task. On the database server, reporting can be intensive. It is
recommended that you run reports during a time when users are not logged on, such as at
night.
l If possible, put the Sync server on an outfacingmachine and not on the samemachine as the
database. Internet sync is recommended because it is already running IIS, but you can have
both Internet and Network sync set up to act as a safeguard or as a way to balance load. Sage
ACT! Internet and Network Synchronization services are discussed in the Installing Sage ACT!
2011 Guide and Help.
Sage ACT! Premium 2011 Web Administrator's Guide 3
About Installing Sage ACT! Premium (Web client) in Single or Multiple WebServer Configurations
This section explains the differences between and recommendations for installing Sage ACT! Premium
(Web client) in single or multiple Web server environments.
Single Server Configurations
You can install Sage ACT! Premium (Web client) using a single-server configuration where the Web server
also hosts Sage ACT! Premium (Web client) databases.
To deploy Sage ACT! Premium (Web client) in a single-server configuration, the impersonation user
account you create should:
l Be added to the local Administrators group on the server.
l Have permission to access all Sage ACT! Premium databases and database supplemental files on
the server.
Multiple Server Configurations
For scalability and enhanced performance, you can configure Sage ACT! Premium (Web client) to use
multiple servers. The most common types of server configurations used are:
l OneWeb server and one database server.
l Multiple Web servers (with or without a database server).
l One or more Web servers runningmultiple application pools.
For a multiple-server configuration, the impersonation user account you create should:
l Be a standard domain user.
l Be added to the local Administrators group on all servers that are part of the Sage ACT! Premium
(Web client) deployment.
l Have permission to access the database supplemental files for your Sage ACT! Premium (Web
client) database on the database server.
l Have permission to access all Sage ACT! Premium (Web client) files on the Web server.
You may have two or more instances of Sage ACT! Premium (Web client) hosted on oneWeb server. In
such cases, you can use virtual directories or application pools to distinguish and secure each Sage ACT!
Premium (Web client)Web site.
Multiple Virtual Directories
You can create multiple virtual directories within your default Web site. For example, you may have two
directories — Sales and Service. Web client users access the sites using a URL followed by the virtual
directory name (for example, http://domain.com/sales). You point each virtual directory to the Sage ACT!
Premium (Web client) installation directory. (The installation directory differs for your operating system).
Note: For more information about configuring Sage ACT! Premium (Web client) usingmultiple virtual
directories, see the Knowledgebase Article #14868.
Recommendations When Installing Sage ACT! Premium (Web client) inMultiple Server Configurations
The following are recommendations when installing Sage ACT! Premium (Web client) in a multiple-server
configuration:
4 Sage ACT! Premium (Web client) 2011
About User Preferences
l Use multiple application pools if using a single Web server for more than 50 users.
l You may have two or more instances of Sage ACT! Premium (Web client) hosted on oneWeb
server. In such cases, you can use virtual directories or application pools to distinguish and
secure each Sage ACT! Premium (Web client) site. You should also isolate any supplemental
data for each Web site.
l Disable all unnecessary Windows services on the Web server, such as Network News Transfer
Protocol (NNTP) or File Transfer Protocol (FTP).
l Allow access through the firewall only to the Web server. Do not allow access to the database
server. See your firewall documentation for instructions.
l When usingmore than oneWeb server, set user preferences to be shared across Web servers.
For more information, see "About User Preferences" in the next section.
About User Preferences
Sage ACT! Premium (Web client) stores user preferences in a WebPreferences.xml file on the Web
server that hosts Sage ACT! Premium. Preferences let users customize name and salutation settings,
change background colors and fonts, create custom spelling check dictionaries, and set other options
for how they use Sage ACT! Premium (Web client). In some cases, you may want to distribute Web
requests across multiple Web servers. This results in each Web server having a unique set of stored
user preferences. If a user changes a preference when logged onto server 1, that change will not be
reflected on server 2.
To prevent users from experiencing preference differences, you can set up a shared location to store
user preferences. Then, when a user logs on, their user preferences will be the same nomatter what
server responds to their logon request.
Note: If the shared preference storage location is offline when a remote user logs on to Sage ACT!
Premium (Web client), the software uses the preferences that are stored locally on the remote
user’s system for the duration of the session.
The steps to set up a shared location for user preferences is explained later in this guide. For more
information, see "Setting Up Shared User Preferences Across Web Servers" on page XXX.
Sage ACT! Premium 2011 Web Administrator's Guide 5
About the ASP.NET Process and User Impersonation Accounts
Sage ACT! Premium (Web client) uses ASP.NET impersonation to allow secure access to the database and
other files. An impersonation account is required to let users who do not have access to the network,
impersonate a user who does. Once you create an impersonation user account, you then configure the
software to use that account. This gives an ASP.NET application access toWindows resources using the
account you provide.
Creating a Windows Impersonation User Account
The following explains how to create an impersonation user account.
Note: The steps may differ according to your operating system.
Create a Windows impersonation user account
1. On the server desktop or from the Windows Start menu, right-clickMy Computer. Then, click
Manage.
Note: On Windows Server 2008, use the Server Manager>Configuration menu to access Local
Users and Groups.
2. In the Computer Management (or Server Manager) dialog box, expand Local Users and
Groups.
3. Click theUsers folder.
4. To create the user account, from the Actionmenu, clickNew User.
a. Type aUser name (the user’s logon name, for example, "actimpersonator") and a Full name
(this can be the same as the User name).
b. Type a password and confirm it.
c. Clear theUser must change password at next logon check box.
d. Click Create. Then, click Close.
Note: Remember the User name and password because you will need it later when you set up
access to a Sage ACT! Premium (Web client) database.
5. To add the user to a group that has access permissions, right-click on the name of the user you
created. Click Properties.
a. In the Properties dialog box, click theMember Of tab. Click Add.
b. In the Select Groups dialog box, in the Enter the object names to select box, type the
wordAdministrators.
c. Click Check Names to resolve the Administrator’s group. (The group name will appear
underlined.)
d. ClickOK.
6. Close all dialog boxes.
6 Sage ACT! Premium (Web client) 2011
Configuring Access to Sage ACT! Premium (Web client)Before your users can access Sage ACT! Premium (Web client), you must use the Web Site
Administration tool to configure access to the database andWeb site. You must also ensure the user's
Web browser meets the requirements for your Web site and accessing features in Sage ACT! Premium
(Web client).
This section explains:
l About the Web Site Administration tool and how to set up Sage ACT! Premium (Web client).
l How users access Sage ACT! Premium (Web client).
l Setting up shared user preferences across Web servers.
About the Web Site Administration Tool
TheWeb Site Administration tool has four tabs you use to configure Sage ACT! Premium (Web client):
l Web Server tab – Test your ASP.NET user account configuration.
l User Account tab – Specify and test the impersonation user account.
l Add/Remove Database tab – Assign a Sage ACT! Premium (Web client) database to a virtual
directory. You can also remove access for a database on this tab.
l Options tab – Change the session timeout limit for all users.
The Web Site Administration tool does the following:
l Encrypts the user name and password.
l Sets up ASP.NET impersonation using the specified user.
l Verifies that the impersonation user can access the required Sage ACT! Premium files and
folders.
l Verifies that the ASP.NET process account has access to the registry key required to run Sage
ACT! Premium.
The default virtual directory is called "apfw". Users access Sage ACT! Premium by adding this virtual
directory name to the URL of your Web server. For example, if the name of your Web server URL is
"salesweb," users access the software at "http://salesweb/apfw ." Assigning databases to this virtual
directory gives users a database to log on to when they access the software. You can test whether your
configuration can access the files and folders required for Sage ACT! Premium. You should do this
whenever you change the configuration.
Setting Up Sage ACT! Premium Web Access
The next section includes the steps to configure access to Sage ACT! Premium (Web client) using the
Web Site Administration tool. You do not need to exit the tool to access the tabs during the configuration
process.
You must validate that an ASP.NET process account exists and is correctly configured on your Web
server.
Note: To access this feature, you must be runningWindows as an administrator or disable User
Access Control (UAC).
Test your ASP.NET user account
1. From the Toolsmenu, clickWeb Site Administration.
2. On theWeb Server tab, click Test. Amessage appears.
l If the test is successful, clickOK.
l If the test is not successful, an error message appears. This may indicate that an ASP.NET
process account does not exist or is incorrectly configured. ClickOK to close the message. For
more information, see "Troubleshooting Sage ACT! Premium (Web client)"
Sage ACT! Premium 2011 Web Administrator's Guide 7
Note: The system displays an informational message if SharePoint® software exists on the Web
server. You may need tomodify your Web configuration. See Microsoft online Help or the Sage
ACT! Premium Knowledgebase for more information.
3. Correct any errors and repeat step 2 until the Web server test is successful. The test must be
successful before you can access the User Account tab.
You must specify and test the ASP.NET impersonation user account before you can set up a virtual
directory and database.
Specify and test the impersonation user
1. On theUser Account tab, click Edit.
Note: You may receive an error message if the Web Site Administration tool is unable to access
the Windows domain, the Windows User Name does not exist, or you entered an invalid password.
Check with your system administrator, correct the errors, and try again.
2. From theWindows Domain list, select the domain for your impersonation user. (Your domain
may already appear in the list).
3. Type the Windows impersonation user account user name and password. ClickOK.
4. Click Test. A message appears.
l If the test is successful, clickOK.
l If the test is not successful or the ASP.NET process account does not have the required access
to the registry key, an error message appears. This may indicate that the impersonation user
does not have the required access to files and folders. ClickOK to close the message. For more
information, see "Troubleshooting Sage ACT! Premium (Web client)"
5. If necessary, correct any errors and repeat the steps until the test is successful. The test must be
successful before you can access the Add/Remove Database tab.
Next, you must assign a Sage ACT! Premium database to a virtual directory.
Assign a database to a virtual directory
A list of available virtual directories appears in the Virtual directories box.
Note: Only virtual directories associated with a Sage ACT! Premium (Web client) installation
appear. In environments where you host multiple installations of Sage ACT! Premium (Web
client), the list may have more than one virtual directory.
3. In the Virtual directories box, select the virtual directory to configure. Click Add.
4. Browse to the Sage ACT! Premium database to associate with your selected virtual directory. Click
OK.
5. When prompted to log on, enter your user name and password. ClickOK.
6. A Test is Successful message should appear. If it does not appear, click TestDB.
l If the test is successful, clickOK.
l If the test is not successful, an error message appears. This may indicate that the
impersonation user account does not have the required access. ClickOK to close the message.
For more information, see "Troubleshooting Sage ACT! Premium (Web client)"
Changing the Session Timeout Limit
If desired, you can change the default session timeout limit which controls how long users can be idle and
remain logged on to the Sage ACT! Premium (Web client)Web site. The default setting is 20 minutes. For
security purposes, we recommend amaximum limit of two hours.
Change the session timeout limit
1. On theOptions tab, from the Session timeout list, select a timeout limit.
2. Click Apply.
8 Sage ACT! Premium (Web client) 2011
How Users Access Sage ACT! Premium Via TheWeb
3. If a message appears, click Yes to continue.
4. Click Close.
Microsoft IIS services are automatically restarted so the new session timeout limit can take
effect.
How Users Access Sage ACT! Premium Via The Web
In order for users to access Sage ACT! Premium (Web client), you must add them as users to the
database and assign them a user role. (You can also set a temporary password that each user must
change when they log on to the Web site for the first time). For more information on adding users, see
the section "Adding Users" in the Installing Sage ACT! 2011 for New Users Guide or Help.
Then, you provide your users the Web address to access Sage ACT! Premium (Web client). This address
consists of the virtual directory name appended to your site URL.
Access From Inside a Common Network
If the Web server and users are on a common network, users can access the software using the
network computer name of the Web server. In the two examples below, that name is “salesweb” and
“teamwebserver.”
Examples are:
l http://salesweb/apfw, where “salesweb” is your site URL, and “apfw” is the virtual directory
name
l http://teamwebserver/apfw
Access From Outside a Common Network
Users cannot use the network machine name to access the software from outside the common
network. Instead, you must provide an external IP address or a URL for a registered domain name. In
the examples below, that information is "12.129.78.35" or "www.sage.com."
Examples are:
l http://www.xxx.com:8080/apfw, where "www.xxx.com" is your site domain name and "8080"
is the port number used to access the site
l http://12.129.78.35/act, where "12.129.78.35" is the external IP Address
l http://www.sage.com/apfw
Note: An external IP address or URL is also required to use Outlook integration from outside the
network. For more information, see "About Outlook E-mail Integration" in Help.
Setting up external Internet access to the Web site for the software requires additional configuration.
Refer to Microsoft IIS Help or contact your network administrator or ISP for assistance.
Setting Up Shared User Preferences Across Web Servers
The following explains how to set up a shared location to store user preferences for Sage ACT! Premium
(Web client) users. You would want to do this if you distribute Web requests across multiple Web
servers. This results in each Web server having a unique set of stored user preferences. If a user
changes a preference when logged onto server 1, that change will not be reflected on server 2. When a
user logs on, their user preferences will be the same nomatter what server responds to their logon
request.
Set up shared user preferences
1. Identify the Web servers that host Sage ACT! Premium.
2. Verify that the impersonation user is the same for each Web server in the cluster.
3. Select a computer that all of the Web servers can access (for example, Preference_Server).
Sage ACT! Premium 2011 Web Administrator's Guide 9
a. On this computer, create and name a folder to store the shared preferences. (For example,
SharedPrefs.)
b. Share the folder you created. Grant Change and Read permission to your impersonation user
account.
4. On aWeb server in the cluster, locate and open theweb.config file for the APFW virtual directory.
By default, this file is located at \\Program Files\ACT\ACT for Web\APFW.
Note: You can open the web.config file in Notepad. If you have the Folder Option set to Hide
Extensions for known file types, this file appears as "web".
a. In the web.config file, locate the Preferences Shared Network Folder entry shown below.
...
<!--
Shared network folder to store preferences (cluster setup)Leave this value empty if single web
server
-->
<add key="PreferencesSharedNetworkFolder" value="" />
b. Edit the entry by inserting the UNC path to your shared folder between the quotation marks
following value=. For example, if your server name is Preference_Server, and your folder name
is SharedPrefs, then you would insert \\Preference_Server \SharedPrefs, as shown below.
... <!-- Shared network folder to store preferences (cluster setup) Leave this value empty if
single web server --> <add key="PreferencesSharedNetworkFolder" value="\\Preference_
Server\SharedPrefs" /> ...
c. Save and close theweb.config file.
5. Repeat Steps 4a-c on the remainingWeb servers in the cluster.
Note: If all Web servers in the cluster use the same configuration, you can copy the web.config file
modified in Steps 4a -c to the other Web servers. Alternatively, you can use the Windows Distributed
File Services (DFS) to replicate one web.config file across all Web servers. See Windows documentation
for instructions on using DFS.
10 Sage ACT! Premium (Web client) 2011
Integrating Sage ACT! Premium (Web client) with OtherApplications
You can integrate Sage ACT! Premium (Web client) with Microsoft Outlook, Word, and Excel. Integration
with Outlook andWord requires some configuration by the Administrator and users. Integration with
Excel does not require configuration.
This chapter explains how:
l The Administrator must edit the web.config file to allow users access to Outlook from outside the
network.
l Users must download components to integrate with Outlook andWord.
Editing the Web.config File for Outlook Integration
The following explains how to edit the web.config file to allow Sage ACT! Premium (Web client) users
access to Outlook from outside the network.
Note: You must also configure your firewall to permit access from outside the network. For more
information, see your firewall documentation.
Edit the web.config file
1. Open Notepad.
2. From the Filemenu, clickOpen.
3. Navigate to the APFW folder on the server where Sage ACT! Premium (Web client) is installed.
Select theweb.config file. ClickOpen.
4. Locate the Act.Web.OutlookWebServiceAddress parameter, which looks similar to the
following:
<add key="Act.Web.OutlookWebServiceAddress" value="http:/
/www.xxx.com:8080/apfw"/>
5. Replace the text following "value=" with the IP address or domain name for the Sage ACT!
Premium (Web client) site.
6. From the Filemenu, click Save.
After you edit the web.config file, users can download and install the Outlook integration components as
described in the next section.
Installing Components to Use Microsoft Outlook
The following explains how users need to install components to integrate Microsoft Outlook features
such as adding Sage ACT! Premium address books in Outlook and recording histories.
Install components to use Microsoft Outlook
1. Close Outlook.
2. Open Sage ACT! Premium (Web client).
3. From the Toolsmenu, click Preferences.
4. Click the E-mail hyperlink.
5. In the E-mail Preferences dialog box, in theMicrosoft Outlook integration box, click the
Download button.
Note: If users cannot download the integration component, check to see if the Sage ACT!
Premium site's URL is added to your Trusted Sites zone.
Sage ACT! Premium 2011 Web Administrator's Guide 11
6. When askedwhether to run or save the file, click Run. When the security warning appears, click
Run again.
7. Select the folder to extract (unzip) the files to. ClickOK.
8. When the success message appears, clickOK.
9. In theOpen File - Security Warning dialog box, click Run.
The InstallShieldWizard checks your system for supported Outlook versions, verifies that you
have not already installed the program, and checks for enough space on your hard drive for the
program.
10. When theWelcome page appears, read the text. ClickNext.
The wizard installs the program. If needed, click Next.
11. Click Finish.
12. ClickOK.
After installing the integration components, users can add up to three Sage ACT! Premium (Web client)
databases as address books in Outlook. Users can also set options for recording history and attaching
Outlook messages to Sage ACT! Premium (Web client) contacts. For more information, see Help.
Installing Components to Use Microsoft Word
The following explains how users need to install components so they can use Microsoft Word to create
letters and other documents from Sage ACT! Premium (Web client).
Install components to use Microsoft Word
1. Close Word (if it is open).
2. Open Sage ACT! Premium (Web client).
3. From the Toolsmenu, click Preferences.
4. Click theWord Processor hyperlink.
5. In theWord Processor Preferences dialog box, selectMicrosoft Word from the list.
6. Click theDownload button.
Note: If users cannot download the integration component, check to see if the Sage ACT!
Premium (Web client) site URL is added to your Trusted Sites zone.
7. When askedwhether to run or save the file, click Run. When the security warning appears, click
Run again.
8. Select the folder to extract (unzip) the files to. ClickOK.
9. When the success message appears, clickOK.
10. In theOpen File - Security Warning dialog box, click Run.
The InstallShieldWizard checks for Outlook versions, verifies this is the first install of the program,
and checks for hard drive space for the program.
11. When theWelcome page appears, read the text. ClickNext.
The wizard install the program.
12. Click Finish.
13. ClickOK.
12 Sage ACT! Premium (Web client) 2011
Troubleshooting Sage ACT! Premium (Web client)This appendix helps you identify solutions to:
l Web Site Administration tool errors.
l General configuration issues or errors.
Troubleshooting Web Site Administration Tool Errors
This section describes how to troubleshoot error messages receivedwhile configuring your software. When
troubleshooting, you may also refer to the Web Site Administration tool log file (AFWAdminLog.log) and the
validation log file (validate.txt). These files may provide information about user permissions and errors
displayed in the tool, such as ASPNET and HTTP errors. The Web Site Administration tool must be closed to
create an updated log file. Log files are located in: <ACT! installation path>\ACT\ACT for Web\Logs.
Additional information for troubleshooting the Web Site Administration tool is provided in the Sage ACT!
Premium Knowledgebase.
Tip: To bypass errors in the Web Site Administration tool, hold down the SHIFT or CTRL key and click
another tab. For example, you may want to view information on another tab before completing the
configuration.
Web Server and User Account Tabs
Microsoft SharePoint software detected. Additional configuration may be required to enableSage ACT! Premium (Web client) to run.
Cause:
l Harpoon was detected on the Web Server. Some installations of
SharePoint modify the default Web site and ASP.NET service
configuration.
Solution:
l You many need to perform additional steps for the Sage ACT! Premium
Web site to function. See the Sage ACT! Premium Knowledgebase.
The ASP.NET process account does not exist or is not configured properly.
Causes:
l The ASP.NET service is not available.
l Non-default IIS settings, such as an assigned IP address or host headers
are configured.
l Read permissions are not set.
Solutions:
l Verify that the ASP.NET service is available.
l Verify the configuration of the ASP.NET process account.
l Manually configure users and permissions as described in Knowledgebase
Article #14867.
Sage ACT! Premium 2011 Web Administrator's Guide 13
User Account Tab
Unable to retrieve Windows domain information at this time. This information is required to editthe Windows User Account. Please check with your network administrator and try again later.
Cause:
l TheWindows domain information is unavailable
Solution:
l See your network administrator to verify you have access to the domain.
The ASP.NET process does not have permission to access or run Sage ACT!
Premium (Web client).
Cause:
l The ASP.NET process account does not have the permissions on the Web
server to run Sage ACT! Premium (Web client).
Solution:
l This account requires Read permission for the registry key that contains
the encrypted impersonation user credentials. Verify the correct account
for your Web server configuration.
The impersonation user account does not have access to files and folders
required to run Sage ACT! Premium (Web client) on your Web server.
Cause:
l The Access to program files and folders or registry permissions required
to run Sage ACT! Premium (Web client) has not been granted to the
impersonation user account.
Solution:
l Verify that the user is at least a domain user and part of the local
Administrators group, and then set the appropriate permissions to the
Sage ACT! Premium (Web client) files and folders on the server.
The Windows user account information you have entered is invalid. Please check
the user name and password and try again.
Causes:
l TheWindows user name or password you entered does not exist in the
selectedWindows domain.
l The option to force users to change their password at logon has been
selected.
Solutions:
l Verify that you entered the correct user name for the selected domain. If
you did, you may need to create a user. For more information, see
"Creating aWindows Impersonation User Account"
l For the impersonation user account, clear the User must change
password at next logon check box.
14 Sage ACT! Premium (Web client) 2011
Troubleshooting Sage ACT! Premium (Web client)
Add/Remove Databases Tab
The impersonation user account does not have access to the database you
selected.
Cause:
l The impersonation user specified on the User Account tab does not have
permission to access the program files and folders or registry permissions
required to run Sage ACT! Premium (Web client).
Solution:
l Verify that the user has the appropriate permission to access all Sage
ACT! Premium (Web client) files and database supplemental files on the
server.
The Web page fails to load after selecting a Web site and virtual directory.
Causes
l Various.
Solutions:
l If you are testing aWeb site that was working previously, execute the
tests on the Web Server and User Account tabs to determine the cause
of the issue. Your Web server configuration may have changed, for
example:
l The password for the impersonation user account was changed or has
expired.
l New software or services, such as SharePoint or Active Directory, were
installed on the Web server.
l The application pool where the Sage ACT! Premium (Web client)
virtual directory runs wasmodified.
l If you just created the impersonation user account, you may not have
cleared the option to force the user to change the password at the next
logon. Clear the User must change password at next logon check box.
l If you just successfully executed the tests on the Web Server and User
Accounts tabs, restart IIS on the Web server as described in
Knowledgebase Article #16515.
Troubleshooting General Errors and Issues
This section describes how to troubleshoot general issues and errors with regard to installation,
configuration, security, and so on.
Sage ACT! Premium 2011 Web Administrator's Guide 15
Troubleshooting Sage ACT! Premium (Web client)
General Errors and Issues
Problem:
l To continue with the installation, you receive a prompt to let
Sage ACT! Premium (Web client) switch your 64-bit IIS and
ASP.NET applications to 32-bit compatibility mode. You do not
want to automatically switch the mode. The Web page fails to
load after selecting a Web site and virtual directory.
Reason:
l Automatically switching the mode will cause other Web applications on
your computer to run in 32-bit mode. If those applications require 64-bit
mode, they will cease running; if not, they should continue running,
however, they will have less RAM to access.
Solution:
l Set up oneWeb server to run the Web application that requires 64-bit
IIS and ASP.NET. Set up a secondWeb server to run Sage ACT! Premium
(Web client), Internet Synchronization and any other 32-bit IIS and
ASP.NET applications.
Problem:
l Sage ACT! Premium (Web client) Help is not opening when
you click Help topics or the Help menu.
Reason:
l Sage ACT! Premium (Web client) Help is a Web-Help help system
containing the Mark of the Web (MOTW) setting in each Help topic
(.htm). On some server operating systems using Internet Explorer, a
blank page appears when Help is accessed.
Solution:
l Add the about:internet site to your Trusted Sites zone or your local
intranet zone. The about:internet setting refers to the MOTW security
setting for each WebHelp help topic.
Problem:
l You receive the message: "Web site is not running."
Reason:
l IIS may not be running.
Solution:
l Verify that IIS and the default Web site are running.
Problem:
l Errors appear on a remote browser, but not while using the
browser on the server.
Reasons:
l Pop-up blockers are enabled.
l TheWeb site is not a trusted site on client computers.
l Your Internet security software does not allow access.
16 Sage ACT! Premium (Web client) 2011
Troubleshooting Sage ACT! Premium (Web client)
Problem:
l Errors appear on a remote browser, but not while using the
browser on the server.
Solution:
l Disable pop-up blockers in Internet Explorer.
l Add the Web site to the list of trusted sites on all client computers.
l Shut down the Internet security software to allow access.
Problem:
l You receive the message: "Error reading the password from
the registry."
Reasons:
l Insufficient rights to the HKLM\Software\AspNet Process key in the
registry.
l Insufficient rights on the database folder.
Solutions:
l Various. See Knowledgebase Article #15164.
Problem:
l You receive the message: "400 - Bad Request" or "404 - File
not found"
Reason:
l TheWeb Site Administration tool tests the site using "localhost."
Solution:
l If the Sage ACT! Premium (Web client) site is configured to use an IP
address, it will not use "localhost".
Problem:
l You receive the message: "500 - Internal server error".
Reason:
l Windows Server 2003 contains a section of IIS that deals with Web
service extensions.
Solution:
l Make sure that ASP.NET version 2.0.50727 is set to Allowed.
Problem:
l You can access the Web site internally, but not externally.
Reason:
l Your router may not be configured correctly.
Solution:
l Ensure your router is forwarded to port 80. For more information, see
your router documentation.
Sage ACT! Premium 2011 Web Administrator's Guide 17
Troubleshooting Sage ACT! Premium (Web client)
Problem:
l You receive the message: "403 - Forbidden".
Reason:
l You do not have permission to access a file.
Solutions:
l Ensure the impersonation user is a Windows Administrator.
l If you created a custom virtual directory, ensure the Read and Run
Scripts (such as ASP) are enabled. See Knowledgebase Article #14868.
18 Sage ACT! Premium (Web client) 2011
Troubleshooting Sage ACT! Premium (Web client)