Showing posts with label Performance. Show all posts
Showing posts with label Performance. Show all posts

A Spring Clean for your system and Outlook

As many of you will know, systems slow down with use and can cause many issues in Sage ACT!. Consequently, I recommend running an occasional maintenance of your system to deal with these before they become a noticeable problem.

With March 20th being the Vernal Equinox (first day of Spring, at least in the Northern Hemisphere) I thought this would be a good time to recommend a Spring Clean routine.

Many of these function are much easier if you have installed Xobni. I highly recommend this product for any Outlook user. There is a free version (Plus) for Outlook only or a paid version (Pro) that will link Gmail, Blackberry, Android and iPhone. You should install the latest 2.x (Pro) or 1.x (Plus) on a system that meets the requirements.

Although the steps below are generally safe, some systems are corrupted to the point of irreparability. Neither GL Computing nor Xobni is responsible for any data loss or other damage that may occur. We recommend that you perform regular full backups of your system, so that if anything should go wrong you can always revert to a good copy. For more about backup, see this article for Windows 7 or this article for Windows XP.

You should back up your ACT! databases, Outlook files and system first.

Not all steps are required and the technical difficulty level of each step is listed from easy to advanced.

 

1. Before You Start: Create a Restore Point (Easy)

To create a restore point
  1. Open System by clicking the Start button Picture of the Start button, right-clicking Computer, and then clicking Properties.
  2. In the left pane, click System protection. Administrator permission required If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
  3. Click the System Protection tab, and then click Create.
  4. In the System Protection dialog box, type a description, and then click Create.

For more information about System Restore, see What is System Restore?

 

2. Back up Xobni Data (Easy) – Xobni Pro user

Xobni Cloud is included with Xobni Pro, which keeps your Xobni data backed up and synchronized across multiple instances of Xobni. To ensure that your data is up-to-date, please perform the following step:

In Outlook, select Xobni > Update Xobni Cloud

 

3. Apply Microsoft Updates (Easy)

Make sure that your system is up-to-date by running Windows Update

  Click the Start button, click All Programs, and then click Windows Update


Apply latest service pack for your version of Office.

 

4. Microsoft Office Repair (Easy)

Lot of issues are caused by corrupt Microsoft Office components. This can happen when one component overwrites another component, for example when multiple versions of Office are installed (say, 2007 and 2010). Microsoft recommends to keep all Office components the same version.  You may see COMexception errors in the InspectorX report in these cases. If you just installed the latest service pack in the previous step, you may skip Office repair.

To repair, please try these steps:

  1. Click Start > Control Panel -> Add or Remove Programs (XP) / Uninstall a program (Vista/Win7)
  2. Scroll down the list and select the version of Microsoft Office you are running
  3. Click the Change button 
  4. Select Repair
  5. Click Continue

 

5. Disable Add-ins (Easy)

In order to eliminate conflicts with other add-ins, please disable all Outlook add-ins using Inspector X:

  1. Restart your computer 
  2. Click Start menu > All Programs > Xobni > Diagnostics > Xobni InspectorX
    (Vista/7 users right-click to "Run as Administrator")
    If you don't have the latest version of Xobni installed, you can download InspectorX and extract the contents to your Desktop or other convenient location:
    For Outlook 2003, 2007, and 2010 32-bit: InspectorX.zip
    For the 64-bit version of Outlook 2010: InspectorX_x64.zip
    Right-click the InspectorX.exe file and select Run as Administrator
  3. In Inspector X, select the Plugins menu > Disable all Plugins except Xobni

You can re-enable the add-ins you need once stability has been confirmed by using the Plugins > Plugin Manager menu option.

 

6. Repair the Outlook data files (Easy)

This is arguably the most important step (with or without Xobni)! If you are experiencing stability or indexing issues, for example, if emails or contacts are missing information, showing up as "Empty", "No subject", or "Message body unavailable", this step will help you resolve this. If you use IMAP, please see this article as well. Make sure to complete all steps.

Warning: If you are storing .pst files on a network share, do not run scanpst. It is unsupported by Microsoft and can cause irreversible data loss! 

  1. Restart the computer (if you have not already). 
  2. Run InspectorX: Click Start > All Programs > Xobni > Diagnostics > Xobni InspectorX
    Or, download the latest version of InspectorX:
    Most people (those with Outlook 2003, 2007, and 32-bit 2010) will need the 32-bit version: InspectorX.zip
    If you have the 64-bit version of Outlook 2010, use the 64-bit version: InspectorX_x64.zip
    Extract the contents to a folder and run InspectorX by double-clicking the InspectorX.exe file 
  3. Select  Special > Automatically Repair All Outlook Data Files

    InspectorX_ScanPST

    This process may take from several minutes to several hours, depending on your data. It is recommended not to use the computer at this point, as it is very i/o intensive. The process may appear to be not responding, so please by patient. Do not attempt to click on the buttons - it is all automatic.

  4. If Xobni is currently installed, please clear the Xobni data files:  

    Select Special > Clear Xobni Data Files...

    Note: This will remove any customizations or merging, although InspectorX will create a backup copy of the Xobni folder named "xobni.bak" in case you need to revert. Xobni recommends to back up your Xobni data using Xobni Cloud, which comes with Xobni Pro.  

  5. Start Outlook

  6. After Xobni does the initial indexing, start a full index operation:

    Select Xobni > Index Outlook Mail

    index_mail

    If you use Xobni Plus 1.x, you may need to re-activate  by selecting Xobni > Options > Xobni Plus > Activate.

 

7. Registry Cleanup (Easy)

  1. Download CCleaner
  2. Install CCleaner
  3. Launch CCleaner
  4. Click on the Registry button on the left
  5. Click "Scan For Issues..."
  6. After scan is complete select "Fix selected issues...". CCleaner asks to make a backup of your registry. Choose a backup destination and click “Save.”
  7. After doing so click "Fix All Issues"
  8. When that is done, you can quit CCleaner
  9. Repeat as necessary (at least once a month)
 

8. Scan Disks for Errors (Easy)

  1. Double-click My Computer, and then right-click the hard disk that you want to check.
  2. Click Properties, and then click Tools.
  3. Under Error-checking, click Check Now. A dialog box that shows the Check disk options is displayed
  4. Use one of the following procedures:
    • To run Chkdsk in read-only mode, click Start.
    • To repair errors without scanning the volume for bad sectors, select the Automatically fix file system errors check box, and then click Start.
    • To repair errors, locate bad sectors, and recover readable information, select the Scan for and attempt recovery of bad sectors check box, and then click Start.
 

9. Defragment your Disks (XP Only) (Easy)

Disks get fragmented over time, and Windows XP leaves it to the user to defragment them (Vista and 7 have automatic defragmentation). Fragmentation, in which files are not stored in contiguous blocks, will make your system slower over time and you should ideally perform this weekly.

  1. Open My Computer.
  2. Right-click the local disk volume that you want to defragment, and then click Properties.
  3. On the Tools tab, click Defragment Now.
  4. Click Defragment.

 

10. Repair System Files (Easy)

In order to repair the Windows system files, please follow these steps:

1. Open a command window as Administrator:
Start > All Programs > Accessories > Command Prompt
(Vista/Win7: Right-click and select Run as Administrator)

2. In the command prompt, type:

sfc /scannow

 

11. Fix mapi32.dll (Medium)

If you see MAPI errors in the InspectorX report, it is commonly because another add-ins has overwritten the default mapi32.dll. To repair this library, please follow these steps:

XP: Download and run xpmapifix.bat.

Vista/Win7: Download mapifix.bat, then right-click it and select Run as Administrator.

If you wish to run the commands manually, follow these steps:

XP:

1. Open a command prompt as Administrator:

Start > All Programs > Accessories > Command Prompt (Vista/Win7, Right-click and select Run as Administrator)

2. Run the following commands:

ren %windir%\System32\mapi32.dll mapi32.dll.bak
fixmapi

You may copy the text above, then right-click in the window to paste.

Vista/Win7:

1. Open a command prompt as Administrator:

Start > All Programs > Accessories > Command Prompt (Vista/Win7, Right-click and select Run as Administrator)

2. Copy the following commands:

takeown /f %windir%\System32\mapi32.dll
cacls %windir%\System32\mapi32.dll /g %username%:c
ren %windir%\System32\mapi32.dll mapi32.dll.bak
fixmapi

3. Right-click in the window to paste the commands.

 

12. Reinstall .NET Framework (Advanced)

Xobni depends on the Microsoft .NET framework, which may become corrupted over time. You can repair your .NET framework by removing it completely and installing from scratch. Make sure to complete the backup steps (#1 and #2) prior to starting this process.

Windows XP
  1. Restart your computer.
  2. Download and run the Brute Uninstaller. (Vista and Windows 7 users, please right-click to "Run as Administrator")
  3. Click Start > Control Panel -> Add or Remove Programs / Uninstall a program
  4. Scroll down and remove each and every .NET framework entry, including service packs and hot fixes that have the word ".NET" in the program name.
  5. After every trace of .NET has been removed from your machine please restart your computer.
Vista/Win7
  1. Restart your computer.
  2. Download and run the Brute Uninstaller. (Vista and Windows 7 users, please right-click to "Run as Administrator")
  3. Click Start > Control Panel > Add or Remove Programs / Uninstall a program
  4. Scroll down and remove each and every .NET framework entry, including service packs and hot fixes that have the word ".NET" in the program name.
  5. After every trace of .NET has been removed from your machine 
  6. Click Start > Control Panel > Programs > Programs and Features
  7. Find the product named Microsoft .NET Framework 3.5.1 and uncheck the box
  8. Please restart your computer.
Trouble removing .NET?

If you are experiencing problems during the uninstall steps, please download the .NET cleanup tool:

  1. Double-click the .zip file to see the contents (or extract to a folder)
  2. Double-click cleanup_tool.exe to run the tool
  3. Select .NET all versions
  4. Click on "Cleanup Now"
Re-install .NET:

Download and install .NET 3.5 from Microsoft's download link.

If you had .NET 4 installed, please install from this link.

Download the latest version of Xobni

Please use this link.

 

13. Create a New Outlook Profile (Medium)

If all else fails, please follow these instructions on how to create a new Outlook Profile. It's totally safe. You can always revert to your old profile. Please refer to this article for instructions. If you use Google Apps, please see this article.

 

Attachments:

Reprinted with permission (with minor changes and edits) from:
https://support.xobni.com/entries/198041-how-can-i-improve-the-reliability-and-performance-of-my-computer-without-purchasing-a-new-one

Quick tip to improve speed on ACT! Premium for Web

A user recently pointed out to me that the favicon.ico file used by ACT! Premium for Web is about 300KB.

For those who don’t know, the favicon.ico is an optional file that can be included on a web site and shows as a logo in web browsers next to the URL, the Browser tab and in bookmarks.

For more information, see: http://en.wikipedia.org/wiki/Favicon

This file loads with every page, increasing the bandwidth. Consequently, these should be kept as small as possible.

The file on an APFW server is /APFW/images/favicon.ico

If you are using ACT! Premium for Web, you might find an improvement by using an ICO editor to reduce the file size… this is especially important if supporting clients on slower connections or if you have a lot of users.

If you don’t have an ICO editor, feel free to download a small ACT! favicon I created:

www.glcomputing.com.au/ACT-favicon.zip

Extract the favicon.ico to the folder I mentioned above on your server. It’s not too pretty, but as it’s under 4KB will save nearly 300KB per page

It’s not a huge improvement, but every bit helps, right?

Technorati Tags: ,,,,

Which MS SQL versions should you use with ACT! 2010 (#ACT2010)

There have been some changes to the supported SQL versions with ACT! 2010 and some users may need to look at which version to use in order to maximise the performance or scalability of ACT!

The standard ACT! by Sage 2010 only supports SQL 2005 Express as per: ACT! 2010 System Requirements

The Premium and Corporate versions support SQL 2005 Standard and now even MS SQL 2008. For a full list of supported versions, see:

While ACT! is only shipped with MS SQL 2005 Express, you can set the Premium version up with SQL 2008 Express (x32 or x64)’ and the Corporate versions with those and also SQL 2005/2008 Standard (x32 or x64)

Note: You must purchase SQL CALs for Standard separately from Microsoft

But, should you change the version of SQL and, if you chose to, how do you do it? To make this decision, you should have a look at these:

From these, you will note that the advantages of Standard over Express are:

  • Express is limited to a 4GB database size – There are very few users that will reach this limit. It’s only the ACT! ADF that’s limited, it doesn’t include attachments
  • Express is limited to 1 CPU and 1GB RAM – If your server machine doesn’t have multiple processors and 3GB (or more) RAM, you will not see a benefit to ACT! in using the Standard version. But, on a machine suitably configured, there will be a performance advantage in using Standard.
  • Changing to Standard on a suitable server should definitely be considered for 25 or more users.

Here are some useful ACT! Knowledge Base articles on installing ACT! with different editions of SQL:

There are a couple of additional points to note:

  • While having Standard (2005 or 2008) on the server and Express on the workstations is ok. If you upgrade to SQL 2008, you must also upgrade all systems sharing the database via Sync to 2008
  • You can upgrade the SQL 2005 instance of ACT7 to SQL 2008, you can’t upgrade to the x64 versions. You would need to uninstall the ACT7 instance and manually create one using the x64 edition of SQL.
  • While I have not tested these personally, I have been told by Sage that there is no noticeable advantage to ACT! in using SQL 2008 or the x64 versions. So the only reason to implement these would be to comply with a current infrastructure where these are already implemented.
  • While the Enterprise editions are not officially QA tested or supported, I have heard from a number of users that these work with the Premium and Corporate versions of ACT! as per the SQL Standard editions with the additional performance levels they provide. The same applies to using SQL 2008 Express with the standard version of ACT! by Sage – not supported, but should work if required.

Improve calendar performance in ACT! and other applications

Microsoft have a hotfix for Windows systems that will improve application that uses UTC dates and times - including Outlook, the Windows Event Viewer and many third-party applications.

Most date and time stamps that are created and displayed in Windows and in many applications are stored as UTC. Then, they are rendered in local time by using system APIs. Examples of these include Windows file time stamps, Outlook sent and received dates, and event logging time stamps.

Not all built-in, Windows-based applications use these newly updated APIs. However, they are available to all applications, including third-party applications. These functions are useful in many scenarios, such as a user auditing scenario in which the ability to use DST rules for previous years on a current Windows service pack is important.

Generally, if an application requires historically accurate time stamps, these functions should be used.
This update improves the performance of the functions, and enables historically accurate time-stamp lookup functionality where the application uses these APIs

Tests that have been conducted with an ACT! by Sage database have found loading 16,000 activities reduced in time from 4 minutes to 9 seconds!

The update applies to the following Windows operating systems:

  • Windows XP Service Pack 3 (SP3)
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows Vista Service Pack 1 (SP1)
  • Windows Server 2008

You can read more about this update and obtain it from this Microsoft knowledge base article: Description of updates to APIs that enable Windows-based applications to retrieve historically accurate time stamps

If you download it, feel free to post here with any tests to verify improvements.

* With thanks to Sage’s Benjamin Lederer for directing me to this.