act! 2005 diagnostics user’s guidedownload.act.com/actdiagusersguide.pdfact! 2005 diagnostics is a...

ACT! 2005 DiagnosticsUser’s Guide

®

ACT! 2005 DiagnosticsThe software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.

ACT7Diag (including any software and related documentation) is provided "AS IS". BEST SOFTWARE disclaims all express or implied warranties of any kind with respect to the utility, including but not limited to any implied warranties of merchantability or fitness for a particular purpose.

Copyright Notice

© 2005 Best Software SB, Inc.

Released: 3/2005 for ACT! (v7) for Windows and ACT! (v7) Premium/Professional for Workgroups. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without prior consent in writing from Best Software SB, Inc., 1505 Pavilion Place, Norcross, GA 30093 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 manual. However, Best Software makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. Best Software shall not be liable for any errors or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual or the examples herein. The information in this document is subject to change without notice.

Trademarks

ACT! is a registered trademark of Best Software SB, Inc. Best Software Insights For The Life Of Your Business is a trademark of Best Software, Inc. Palm OS is a registered trademark and Palm is a trademark of PalmSource, Inc. Microsoft, Outlook, and Windows are registered trademarks of Microsoft Corporation. All other trademarks are the property of their respective owners.

End User License Agreement

ACT! (v7) for Windows and ACT! (v7) Premium/Professional for Workgroups are protected by an End User License Agreement. To view the agreement, go to the Help menu in the product, click About ACT!, and then click the End User Agreement button.

Printed in the United States of America.

10 9 8 7 6 5 4 3 2 1

Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Chapter 1 ACT! 2005 Diagnostics Utility Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

The ACT! 2005 Diagnostics menu commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2 ACT7Diag Server option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Server Information panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Server Security panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Resetting the SQL password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Specifying how the SQL instance works on a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Assigning a static TCP/IP port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Configuring connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SQL Error Logs panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SQL Diagnostics panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Running SQLDiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Checking SQL permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Server Connections panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 3 ACT7Diag Databases Section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Viewing the Database List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Refreshing the list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Viewing the database grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Performing tasks from the Database List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Performing maintenance functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Performing reporting functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Viewing reports on database structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Viewing database reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Performing fixes related to Groups and Companies . . . . . . . . . . . . . . . . 16Performing fixes related to phone formatting 1. . . . . . . . . . . . . . . . . . . . . . 6Performing fixes related to Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Performing fixes related to Opportunities 1 . . . . . . . . . . . . . . . . . . . . . . . . 7

Viewing Audit logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Starting and Stopping the Local ACT7 SQL Instance . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

1

Introduction

The ACT! 2005 Diagnostics utility, or ACT7Diag, is a program installed with ACT! 2005.

ACT! 2005 Diagnostics is a tool used to help repair and maintain ACT! databases and manage some aspects of the local ACT! SQL Server instance. When launched, ACT7Diag works only on the local machine; it does not allow you to connect to remote SQL Server machine instances. Additionally, since this utility primarily provides low-level physical diagnostic and corrective actions against the SQL Server instance and its databases, most features and tasks do not require a user logon to the ACT! Framework or application.

This document describes the ACT! 2005 Diagnostics utility interface, the tasks you can perform relating to the server, and the tasks you can perform relating to the database. It also provides instructions for starting and stopping the SQL Server instance.

i

Chapter
1 ACT! 2005 Diagnostics Utility Interface
The ACT! 2005 Diagnostics utility interface includes up to four menu items (File, Actions, Tools, and Help) and two options on the navigation bar (Server and Database) as indicated in the following illustration.

When you start ACT7Diag, the Server Information panel appears. This is described in “Server Information panel” in Chapter 2 , "ACT7Diag Server option."

The ACT! 2005 Diagnostics menu commandsIn the ACT7Diag utility, the following commands are available from the menu bar.

File You can close the application using the Exit command or by clicking the red close button in the top right corner.

Actions The Actions menu is available only from the Database List view. The options for this menu are described in Chapter 2 , "ACT7Diag Databases Section."

Tools The functions described below are available from the Tools menu.

Adjust ACT! Timeout Values Allows you to adjust the length of time ACT! waits when attempting to execute database commands and connections before returning an error.

• DatabaseCommandTimeOut.Default: The default is 30 seconds. This is the number of seconds each query can take before timing out and generating an error. Most commands in ACT! observe this setting.

• DatabaseCommandTimeOut.Long: The default is 3600 seconds. This is the number of seconds that some process-intensive and/or batch-oriented commands can take before generating a time-out error. Examples are Database Maintenance tasks and some sync operations.

• DatabaseConnectionTimeOut.Default: The default is 30 seconds. This is the number of seconds allowed for a connection to be made to the SQL instance. On a local or high-speed network, connection time is typically a second or two. You may need to increase the interval if you run on a slower dial-up or other remote connection and begin having connection time-outs or other connection errors.

1

• Delete Preference: This option deletes the local ACT! 2005 Preferences files for the user currently logged into Windows.

Warning Deleting local preferences also resets ACT! Email folder information for the local Email database. This may cause any locally stored e-mail messages to be lost.

Help You can access the About ACT! 2005 Diagnostics panel from the Help menu. The About ACT! panel provides program and vendor information and a link to the ACT! Technical Support Web site.

The following items also are provided on the About ACT! 2005 Diagnostics panel.

Version This may or may not match the version of your ACT! 2005 application; either is acceptable.

Command Timeout (seconds) This is the number of seconds a task issued in ACT7Diag is allowed before stopping on its own. By default, this is 600 seconds (10 minutes), but you may need to increase the time for slower machines and/or if you have a very large database. If you receive time-out errors while running some tasks, close the ACT7Diag program, open the Act7Diag.exe.config file with Notepad, and then increase the CommandTimeout.Default value:

<add key="CommandTimeout.Default" value="600"/>

2 ACT! Diagnostic Tool User’s Guide

Chapter
2 ACT7Diag Server option
ACT! 2005 creates a named instance of “ACT7” during installation. The Server option of the ACT! 2005 Diagnostics tool lets you view that ACT! SQL Server instance and manage it, within limitations. When you select the Server option, the Server Information panel appears. You can select additional options (Server Security, SQL Error Logs, SQL Diagnostics, and Server Connections). These are described in the following sections.

Server Information panel

The opening panel, Server Information, displays pertinent local ACT7 SQL Server instance properties, including the server name, edition, version (typically including Service Pack level), collation (language and sorting), and service account (the Windows account context under which ACT7 is registered and runs):

3

Server Security panel

You can use the Server Security option to view and/or set security- and connectivity-related settings for the local SQL instance. By default, when ACT! installs the SQL Server instance, it is network-enabled (that is, it allows connection attempts from other machines). If this is not needed, you can disable network connections. For sync, you do not need to network-enable the remote database/machine, but you must network-enable the machine(s) listening for sync requests and hosting the parent/master database.

From this panel, you can reset the SQL password, enable or disable connections, specify a port, hide the SQL instance on a network, and so on. These options are explained in the following sections.

Resetting the SQL password The Reset SQL Password button allows the machine user to reset the local SQL password (sa) whenever he or she needs to, for example, for security reasons. It does not allow you to determine the SQL password, nor does it provide you with the SQL password.

The Server Security panel also specifies network connectivity configurations including the following:

• which TCP/IP port the SQL instance is listening on

• whether that TCP/IP port is dynamically or statically assigned

• whether the SQL instance "shows" itself to other machines on the network

• whether the SQL instance supports/allows network protocols allowing other machines to connect

Specifying how the SQL instance works on a LANWhen you click this button, the Microsoft SQL Server Network Utility dialog box appears. You can enable, disable, and configure whether and how your local SQL instance participates on a Local Area Network with other computers. You first must ensure that the ACT7 instance is selected as indicated in the following illustration.


To disallow connections from other computers

1 In the Enabled protocols box, select Named Pipes, and then click Disable.

2 In the Enabled protocols box, select TCP/IP, and then click Disable.

3 Click OK.

You will be warned that you need to stop and restart the SQL instance for these changes to take effect. See ““Starting and Stopping the Local ACT7 SQL Instance.”“

Assigning a static TCP/IP portUsually, you will not need to assign a static TCP/IP port for your SQL instance. Some situations (for example, if you are setting up Internet sync) require that you assign a static TCP/IP port for the machine hosting the Publishing (or Parent) database.

Note Assigning a port number of zero (0) causes SQL Server to automatically assign the TCP/IP port on the next start-up of the SQL Server instance. Assigning a specific non-zero number creates a fixed port assignment. You must ensure that the port number is not being used by another process or service.

To hide this SQL instance on the network

• On the TCP/IP Value Setup screen, select the Hide Server check box.

This suppresses the broadcasting and listing of this SQL instance from other machines on the network.

ACT7Diag Server option 5

Configuring connectivityWhen you click the Client Network Config button, the Microsoft SQL Server Client Network Utility dialog box appears. You can configure how this machine attempts to connect to this and/or other machines running a SQL Server instance.

Note Ensure that the Enable shared memory protocol check box is selected. This allows the best (and absolute) connection to your own local SQL instance when running both ACT! and ACT7Diag. This is critical if you have disabled network protocols with the Server Network Utility, as described under “Specifying how the SQL instance works on a LAN” in “Server Security panel.”

The Enabled protocols by order box should list TCP/IP and Named Pipes, generally in that order.

SQL Error Logs panel

You can use SQL Error Logs to view the error logs generated by the SQL Server. Both system- and user-defined errors and events are recorded to these logs. The logs can help you diagnose problems related to SQL Server. Each event is recorded with a timestamp, and the logs are "cycled" each time the SQL service is started. By default, the current and last six error logs are retained.


To view a log

1 Click the View Logs button.

2 Select the log file you wish to view, and then click Open.

Note The current log file is named ERRORLOG; earlier log files will have a numeric extension.

SQL Diagnostics panel

You can use SQL Diagnostics to perform two tasks (SQL Diag and Check SQL Permissions) to help diagnose problems that could be related to the SQL Server instance.

The SQLDiag utility, provided by Microsoft, interrogates the ACT7 SQL Server environment and configuration and the Windows and machine environment (similar to msinfo.exe). The Check SQL Permissions task can assist in verifying failed operations such as performing a File > Save As and creating a new Remote Sync database.

Running SQLDiagWhen you click the Run SQLDiag button, SQLDiag produces a text file with information about the SQL configuration and environment and the machine and Windows operating system. The resulting file is stored on the Windows Desktop. This is typically used to submit a problem to Technical Support.

Checking SQL permissionsSome operations, including File > Save As and creating a Remote Sync Database, require interaction between the SQL Server and the Windows OS. The dialog box that appears allows you to select the folder (on the local machine) that may have been specified for the database location during the operation.

To check SQL permissions

1 On the Check SQL Server Permissions form, select the desired folder, and then click the Check button.


2 Ensure that the Environment Path value includes C:\Program Files\Microsoft SQL Server\80\Tools\Binn\.

3 Ensure that each line in the Permission Results box displays Successfully created.

If other results appear, you may have Windows permissions issues, or you may need to restart your system. A system restart is most likely if you are running a VMWare machine. Contact ACT! Technical Support if you continue to get other results.

Server Connections panel

The SQL Connections panel displays the connections to the local ACT7 SQL Server instance. The current connection used by ACT7Diag does not display in this grid.


The grid has the following columns.

COMPUTER The name of the machine with the connection.

DATABASE The name of the physical SQL Server database on the local machine the user is currently logged on to.

LOGIN The date and time when the connection was first established.

LAST ACTIVITY The date and time of the last activity or command.

CPU TIME A measurement of how busy the connection is.

DISK I/O A measurement of the disk resources used by this connection since the connection was established.

BLOCKED The connection number of a connection that is blocking the current connection. This usually is zero (0).


Chapter
3
ACT7Diag Databases SectionYou can use the Databases option of the ACT! 2005 Diagnostics tool to manage the physical SQL Server database(s) on your machine. These tools range from disconnecting databases (detaching or un-registering) from the ACT! SQL Instance to performing in-depth maintenance. When the Database List task is selected, the Actions menu becomes available, as described in the following sections.

Viewing the Database List

This panel lists all databases registered to the ACT7 SQL Server instance. You can perform a variety of actions on an ACT! database.

To work with an ACT! database

• Select a row, then select the Actions command.

Note Some SQL Server system databases are listed in addition to ACT! databases. They include: master, model, msdb, and tempdb. Generally, no action will need to be taken with these databases, but they are critical to the operation of the SQL instance. Some actions are available for these databases; others are not.

Refreshing the listYou can use the Refresh button to update the list with changes made from other machines and with changes made while running Act7Diag on this machine.

11

Viewing the database gridThis grid includes the following columns.

DATABASE The physical name of the SQL database; generally the same name as the .pad file used to reference and access the database.

STATUS This usually shows ONLINE. If the SQL Server cannot bring a database online (for example, when one or both of the database’s .adf/.alf files have been moved, renamed, or deleted), the value is SUSPECT.

DB SIZE The approximate size in megabytes (MB) of the database file (.adf).

DB VERSION The schema version of the ACT! database. This matches the Schema Version found in the Database Info panel in the ACT! application.

SYNCING If the database is not set up to sync, this shows N/A; if the database is a top-level parent database, it shows Publisher; and if the database is remote, it shows Subscriber. For a remote subscriber database that syncs with handheld devices (Palm or Pocket PC), Publisher/Subscriber appears .

LOCK This displays Locked or Unlocked for an ACT! database and nothing for a non-ACT! database. This represents a lock issued in the ACT! application.

CREATE DATE The date and time that the database was created.

DATABASE FILE LOCATION The folder location of the database's .adf file.

Performing tasks from the Database ListFrom the Database List subsection, you can select and perform the tasks/actions described in the following sections.

Performing maintenance functionsCheck Database This process scans and verifies the physical structure of the database for damage. It includes data, indexes, and procedural objects within the database. This requires exclusive use of the specified database and will kill (disconnect) any connections.

Repair Database This attempts repair of any physical damage or inconsistency found in the internal structure of the database. If the Check Database task (or Database Maintenance > Check & Repair) returns an error, run Repair Database. This requires exclusive use of the specified database and will kill (disconnect) any connections.

Unlock Database This unlocks an ACT!-locked database, which is useful if you cannot unlock a local database through the ACT! application.

Reindex Database This performs a comprehensive and exhaustive re-index of all tables and indexes in the database. This requires exclusive use of the specified database and will kill (disconnect) any connections.

Detach Database This detaches the database from the ACT! SQL Instance. This requires exclusive use of the specified database and will kill (disconnect) any connections. To re-attach an ACT! database to the ACT! SQL Instance, open the database from the ACT! 2005 application or double-click the .adf file.

Delete Database This deletes the selected database. This option is available only if the database is listed as Suspect. To delete an online, non-Suspect database, use either the Delete


Database task under the Database Maintenance option in the ACT! application, or first detach the database from the ACT! SQL instance, and then delete the physical .adf and .alf files.

Note Before detaching or deleting a database, we strongly recommend that you first back up the database.

Performing reporting functionsACT7Diag offers various reports relating to database structure, synchronization, and so on. The following section describe these reports.

Viewing reports on database structureACT7Diag includes two reports (Fields Summary and Fields Detail) relating to the structure of the database. Each report contains a header section showing the machine name, local date and time, and ACT! schema version and database file location. The report contains a full listing of fields and their attributes for the five high-level ACT! entities:

• Contact

• Secondary Contact

• Group

• Company

• Opportunity

Fields Summary Report This displays the current fields in the selected database. Each field is shown on one line.

Fields Detail Report This displays most details of the current fields in the selected database. Each field has a few lines showing the pertinent attributes. This is more comprehensive than the Summary Report.

ACT7Diag Databases Section 13

Viewing database reportsAct7Diag offers additional reports to support and provide additional functional areas of the ACT! application and database. These reports can be used for informational or troubleshooting purposes as needed and may be requested by Technical Support to help resolve issues.

Sync Configuration Report This report provides an overview of all sync-related configurations, metadata, and structure within the sync family. It contains various sections including those listed below.

SYNC ROLE Indicates whether the current database is a Publisher, Subscriber, or both.

SYNC-RELATED DATABASE SETTINGS Provides the current sync-related configurations and/or settings for this database.

SYNC TABLES ANALYSIS Provides a current usage count for all sync-related tables for internal support purposes.

SYNC DATABASES Lists all databases within the current sync family, including handheld devices (Palm, Pocket PC). Provides the general sync-related configuration settings and values, including Status and Syncset used.

DIRECT SYNC RELATIONSHIPS Lists the databases *directly* related to the current database, including (as applicable) its parent database and any child/remote databases including handheld devices.

SYNCSETS Lists all Syncsets defined for this sync family, including those designated for handheld devices. Also provides the number of databases currently using the Syncset.


Sync Preview Report This report provides a general idea of the changes that have occurred since a given database last synchronized successfully. This report only lists direct child/remote databases as well as itself (if the current database is a remote/child database). The volumes are provided by table domain and by the physical table in that domain (to assist with troubleshooting). Those relate to the ACT! areas represented in the ACT! application and are the same domains as those shown in the Sync Logs and from the Help > About > Database Info command when depicting records synchronized and database size.

Database Rebuild These functions are available to rebuild and repair various areas of foundational ACT! data, objects, and other metadata to support the ACT! Framework and/or application. These actions are intended to be reactive/corrective, not proactive, measures. They are generally safe to run at any time and do not offer choices or require user intervention.

Rebuild actions and the scenarios to run them follow.

Rebuild Schema This rebuilds the representational schema metadata of the database. Schema refers to the layout of the database and allows proper and consistent viewing from the ACT! application and other supported areas.

When/why you would run this: If errors appear indicating that a column cannot be found, or if you believe a column to be missing or that it is showing incorrect attributes, etc.


Rebuild Security This rebuilds the User and Teams tables in the database based on known static rules as employed by the ACT! definition.

When/why you would run this: If contact access appears to be incorrect (for example, users who belong to the Administrator or Manager security Roles cannot view non-private contacts, etc., or if users other than the Record Manager can view private data, etc.).

Rebuild OLE/DB Report Objects This rebuilds the read-only SQL Views of the ACT! database that are used by the ACT! OLE/DB Provider. Third-party software products such as Crystal Reports and Excel can access these Views through an OLE/DB connection.

When/why you would run this: If View tables do not appear or the field list or some tables does not appear to be correct, the database may be missing fields that were added or removed as a customization.

Rebuild Sync Objects This rebuilds the sync logging triggers and other configuration and reporting data in the database. It also performs any log and/or data corrections that may be required. Sync logs are purged as allowed and the Sync Log Retain Date advanced if possible.

Specifically the tasks that "Rebuild Sync Objects" will perform are:

• Rebuild and maintain sync schema metadata

• Regenerate all sync logging triggers on all sync-eligible tables

• Re-enable or disable all sync logging triggers (based upon whether or not the database is sync-enabled)

• Purge any/all aged sync transaction log records (based on sync expire days and last sync dates of all active directly-related databases)

• Detect and correct any data inconsistencies found in the sync transaction logs

When/why you would run this: If it appears that some data is not syncing properly, or if you receive error messages during sync. This also is useful if the Sync Log Retain Date does not appear to be resetting properly (based on normal operation and with consideration of related database expiration days).

Database Fixes This option contains various items that could need correction. Most options will not require an ACT! user login, but some will. Run these actions when conditions exist such as those describe below.

Performing fixes related to Groups and Companies

Recover Groups By default, each new ACT! database contains one Group and one Company record, named Untitled. These two records are owned by the first "user" in the database, ACT! System. If the user modifies that first record and makes it Private, the record disappears and is not retrievable. This task marks those two records as non-Private so the user can set the Record Manager accordingly.

When/why you would run this: If you have modified the Untitled Group and/or Company record by making it Private and not changing the Record Manager to someone other than ACT! System. In this case, no users would be able to view that Group and/or Company record.

Performing fixes related to phone formatting

Apply Phone Masks This task attempts to correct incorrectly formatted phone record values. It recognizes phone records whose format does not appear to match the specified Phonemask, then applies the correct format to the number value. It uses the Phonemask that was selected for each phone number in the database, simply re-applying that Phonemask to ensure conformance. This process does not process phone numbers input as "freeform".


When/why you would run this: If you converted from earlier versions of ACT! 2005 (such as the initial 7.0 release) and phone values are not properly formatted. Or if you have entered phone data with a particular mask in place, then changed that mask to a different format, you should run this task for all previously entered numbers so they are formatted correctly.

Performing fixes related to Activities

Change Timezone Requires an ACT! Administrator login. This task allows the user to change the Activity records for the user(s) selected to the Timezone selected. The criteria used for Activity ownership is the Organizer field.

This task was introduced to correct Activity data whose time zone information and handling changed in ACT! 7.0.1. Use caution when running this task, since the changes are far-reaching (across all Activities, both cleared and uncleared, in which the User selected is the Organizer) and cannot be undone.

When/why you would run this: If you have updated from version 7.0 of ACT! 2005 to a later version (7.0.1 or later) and now some (or all) of the Activities appear at the incorrect time, usually off by an hour.

Fix Recurring No Enddate This change addresses issues with users whose Windows time zone is set to a positive GMT time zone, such as Russia, Germany, and France. During conversion of an earlier version ACT! database (before 7.0), some recurring (and non-recurring) Activities were not properly converted. This fixes those issues by properly setting the recurring end value.

When/why you would run this: If you have converted from an earlier version of ACT!, such as 6.0, and one or more client machines are set to a positive GMT time zone value. In such a case, the user may see an error message similar to "The maximum end date for a (none) recurring activity starting on 16.07.2002 is 01.06.2073". Some Activities may not appear on the calendar.

Performing fixes related to Opportunities

Fix Editdates This change addresses issues with users whose Windows time zone is set to a positive GMT time zone, such as Russia, Germany, and France. During conversion of an earlier version ACT! database (before 7.0), some Opportunity records were not properly converted with their datetime values, specifically the record editdate. This fix sets the editdate on the Opportunity to match the value of the createdate if it is empty or not set.

When/why you would run this: If you have converted from an earlier version of ACT!, such as version 6.0, and one or more client machines are set to a positive GMT time zone value. In such a case. the user may see an error message similar to "Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter Name: Ticks". Opportunity records will not load properly.


Viewing Audit logs

Each ACT! database contains an internal Event Log that can capture many actions that occur in ACT!. For many administrative, defining, and/or database-wide actions that can occur, it is often best to review those events chronologically.

The Audit Log panel allows you to view those events by Event Type. It shows who performed the action (for a non user-specific system event, the USER will be ACT! System) and when the action occurred. Some Event Types populate values in the OLDVALUE and NEWVALUE columns, such as Database Config - Setting Modified, but many do not.

Note Not all Event Types are logged. Some have been reserved for future use. In future releases, more Event Types may be included and/or some may be removed.

Note As a part of Database Maintenance, aged Event Log records are purged from the database. This currently is not configurable and is set to 45 days for most Event Types (records older than 45 days before today are deleted).

If Tech Support requests you to, you can send the Event Log records to an XML file.

To export Event Log records to XML

1 Click the Export button.

2 If necessary, limit the scope of log entries by date to help reduce the number of resulting entries and file size.

The resulting file is placed on the Windows Desktop with the name:

[database_name] - Database Audit Logs.XML


Starting and Stopping the Local ACT7 SQL InstanceDuring installation, the ACT7 SQL Server instance is configured to start automatically when Windows starts. Running the local SQL instance is required for the following three scenarios:

• To create a new database

• To open and use a local database

• To run ACT! E-mail and store POP3 account items in a local store

If none of these scenarios apply, you can configure Windows not to automatically start the SQL instance on Windows start-up. Not running the local SQL service can improve overall system performance by using less memory and resources. The easiest way to manage services is from the Services panel in Windows.

To display the Services panel

• Click Start, click Run, type services.msc, and then click OK.

To stop a service

• From the Services panel, right-click the MSSQL$ACT7 row, then click Stop.

To start a service

• From the Services panel, right-click the MSSQL$ACT7 row, then select Start.


Index

AAbout ACT! 2005 Diagnostics panel 2Actions menu 1Apply Phone Masks task 16Audit Log panel 18

CChange Timezone task 17Check Database maintenance function

maintenance functionsCheck Database 12

Check SQL Permissions task 7Client Network Config button 6command timeout 2connections

disallowing 5

Ddatabase

fixes 16rebuild and repair functions 15rebuilding 15

database grid 12Database List 12

maintenance functions 12Database List task 11databases

SQL Server system 11Databases section 11Delete Database maintenance function 12Detach Database maintenance function 12disallowing connections from other computers 5displaying the Services panel 19

EEnable shared memory protocol check box 6error logs

viewing 7Event exporting to XML 18Event Log 18

Ffailed operations

verifying 7Fields Detail Report 13Fields Summary Report 13Fix Editdates task 17Fix Recurring No Enddate task 17fixing databases 16

Mmaintenance functions 12

Delete Database 12Detach Database 12Repair Database 12Unlock Database 12

menu commands 1menu items 1

Nnavigation bar 1

Ppreferences

deleting 2

Rrebuild actions 15rebuilding and repairing databases 15Recover Groups task 16Refresh button 11Reindex Database maintenance function

maintenance functionsReindex Database 12

Repair Database maintenance function 12reporting functions

database reportsdatabase reports 14

Field Summary 13Fields Detail Report 13Sync Preview 15

reportsFields Detail 13Fields Summary 13Sync Configuration 14

reset SQL Password functionSQL password

resetting 4running SQL instance 19

SServer Information panel 1Server Network Config button 4Server section 3Server Security command 4services

starting 19stopping 19

Services paneldisplaying 19

21

SQL Connections command 8SQL Diag task 7SQL diagnostics

Check SQL Permissions 7SQL Diag 7

SQL error logs 6SQL instance

absolute connection 6connectivity settings 4diagnosing problems 7hiding on network 5managing from Server section 3participating on a LAN 4running 19showing to other machines 4starting and stopping 19supporting/allowing connections from other

machines 4viewing properties 3

SQL Server databasemanaging 11

SQL Server system databases 11starting services 19starting SQL instance 19static TCP/IP port 5

stopping services 19stopping SQL instance 19Sync Configuration report 14Sync Preview report 15

TTCP/IP port

assigning a port number of zero 5assigning static 5checking to see if assigned dynamically 4listening by SQL instance 4

timeout values 1Tools menu 1

UUnlock Database maintenance function 12Untitled Company record 16Untitled Group record 16

XXML event logs 18

Zzero port number 5


act! 2005 diagnostics user’s guidedownload.act.com/actdiagusersguide.pdfact! 2005 diagnostics is a...

Documents