Getting Started with FastworksProject in Microsoft Project 2003 Professional

Troubleshooting FastworksProject with Microsoft Project 2003 Professional

1. Confirm compatibility

• Check version: Ensure your FastworksProject add-in explicitly supports Microsoft Project 2003 Professional. If documentation is unavailable, assume incompatibility and try running in a supported environment or compatibility mode.

2. Verify installation

• Add-in presence: In Project, open Tools → Add-Ins and check for FastworksProject.
• Reinstall: Uninstall the add-in, restart Windows, then reinstall using administrator privileges.
• Permissions: Run Project as administrator during install and first run.

3. Check registry and file locations

• DLL and COM registration: If FastworksProject uses COM/DLLs, re-register relevant DLLs with regsvr32 and confirm registry keys under HKLM\Software\Microsoft\Office\ or HKCU\Software for add-in entries.
• File paths: Ensure add-in files are in expected Program Files folders and not blocked by Windows (right-click → Properties → Unblock).

4. Resolve startup and load failures

• Disabled items: In Project, check Tools → Options → Add-Ins and Disabled Items; re-enable if listed.
• Load behavior: Examine the add-in LoadBehavior registry value (should be 3). If not, set it to 3 after confirming the file path is correct.

5. Fix crashes and performance issues

• Safe mode test: Start Project in Safe Mode (win+R → winproj /safe) to see if core Project is stable.
• Conflict isolation: Disable other add-ins and test FastworksProject alone.
• Memory and resources: Close other apps; ensure system meets minimal RAM/CPU needs for Project 2003.

6. Address data sync and functionality errors

• Logs and error messages: Collect any log files FastworksProject produces and note exact error text.
• Data integrity: Run Project’s built-in file recovery (File → Open → select file → Open and repair) if project files seem corrupted.
• Version mismatch: Ensure project file formats (.mpp) are supported by the add-in—save in lower compatibility mode if needed.

7. Network and licensing issues

• Network resources: If FastworksProject accesses a server, verify network connectivity, DNS, and that required ports are open.
• Licensing: Confirm license keys are valid and entered correctly; try reactivating the product.

8. Update and patch

• Service packs: Install Office/Project 2003 service packs and Windows updates that affect Office COM and security.
• Add-in updates: Check for the latest FastworksProject patches; if none exist for 2003, consider upgrading Project or the add-in.

9. Collect troubleshooting information

• Essential details: Gather Project version and service pack, OS version, FastworksProject version, exact steps to reproduce, screenshots, and log files.
• Reproduce consistently: Note whether the issue happens on other machines to determine if it’s environment-specific.

10. When to escalate

• Vendor support: If local troubleshooting fails, contact FastworksProject support providing the collected details and any crash dumps.
• Upgrade path: If the add-in is unsupported on Project 2003, plan migration to a supported Project version or migrate projects to a compatible format.

If you want, I can generate a short checklist or an email template to send to FastworksProject support with the required troubleshooting details.