A few of the more common error messages and issues and how to help fix them.

.
.
.
.
.
.
.
.
.
.
.
.

1. Cache is Damaged
Settings Table may be Corrupt WarningSettings Table may be Corrupt Warning

You are minding your own business, working along in iPoint and suddenly you get a pop-up error that says Cache is Damaged. You feel the panic beginning to settle in. “What am I supposed to do now!” you exclaim!

Never fear – iPoint is here! Take a deep breath – you’re okay.

The problem can be solved by deleting ALL the cache files located in:

  • Mac: ~/Library/Caches/FileMaker/DBCache also here: User/Library/Caches/com.filemaker.client.advanced12
  • Windows: %LOCALAPPDATA%\Temp\FileMaker\

.

Still doesn’t quite make sense? No worries, here are step-by-step instructions to help you save the day!

Detailed Instructions

Filemaker Cache Folder on WindowsFilemaker Cache Folder on Windows

For Windows:

  1. Click the Link button on the Cache is Damaged error
  2. Close Filemaker if open
  3. Click on the start/windows icon on the bottom left of your computer
  4. Type or copy/paste %LOCALAPPDATA%\Temp\FileMaker\
  5. Hit enter
  6. Delete everything in the folder
  7. Reopen FileMaker and iPoint. Your problem should be solved!

For Mac:

  1. Click the Link button on the Cache is Damaged error
  2. Close Filemaker If open (Press Command Q)
  3. Open Finder
  4. From the top menu choose Go and then choose Go To folder
  5. Type ~/Library/Caches
  6. Hit Enter
    1. Delete everything in the com.filemaker.client.advanced12 Folder
    2. Delete everything in the FileMaker folder
  7. Reopen FileMaker and iPoint. Your problem should be solved!
    .

For IOS:
Uninstall the app and reinstall it
If any of these steps fail to fix your problem, just do a quick phone call to support, and our crack team of experts will help you out!

2. Gibberish Text
Wingbat TextWingbat Text

When the text in iPoint looks like gibberish or symbols – yikes! Did aliens take over my computer!?

Not exactly…

Step-by-step guide

You can usually fix the issue by restarting FileMaker, but it may come back if the underlying issue isn’t resolved.

That usually comes from anti-virus blocking access to the dictionary. Make sure you have an exception in your antivirus for C:/Programs Files X86/Filemaker

In addition, there are a few other things that can be done to help prevent that.

  • Update to the latest version of Adobe Reader.
  • Delete the Windows font cache at C:\Windows\System32\FNTCACHE.DAT and restart the machine.
  • Disable Windows Font Cache Service from Control Panel\All Control Panel Items\Administrative Tools\Services
    • Find Windows Font Cache in the list
    • Right Click → Stop
    • Right Click → Properties→ Start Up Type → Disabled
  • Delete the Adobe cache inside C:\Users\\AppData\Local\Temp\acrord32_sbx\
  • Exempt the FileMaker folder from Virus Scans (C:/Program Files(86)/Filemaker for 32 bit FM, C:/Program Files/Filemaker for 64 bit)
  • Disable Sleep Mode

.

If the problem continually recurs on the same computer after doing all of the above, try closing iPoint at the end of each day. If it still recurs, shut down the computer each night and start it up each morning.

If the problem occurs throughout the day even when restarting the computer nighty, the final solution is to uninstall Adobe completely and to use a different program to view PDFs.
.
.

3. My Calendar is blank
Projects as ResourcesProjects as Resources

Make sure you don’t have Projects as Resources set

If your calendar is looking blank, no matter what view you’re looking at, you may want to check this quick setting.

Inside the Calendar > Gear Icon > Settings (tab) inside the pop-up menu > under Resource Settings > Projects as Resources: select No > Close

This is only used when viewing the calendar as a Gant chart to manage your projects. The calendar should refresh to use people as resources as normal.

Project as ResourceProject as Resource

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

4. Email: Server Busy error when sending email through Outlook.
Server Busy errorServer Busy error

The “Server Busy” error is typically caused by a mismatch in the bit-level of your Microsoft Outlook client and FileMaker, e.g. 32-bit FileMaker with 64-bit Outlook and vice-versa.

Outlook and FileMaker need to be the same bit type. So here is the fix:

  1. Click Here to learn how to see what Bit version of Outlook you are running.
  2. Un-install FileMaker from your computer.
  3. Click Here. to download the correct Bit version of FileMaker
5. Low On Disk Space – Purging!
Low on disk space

The “Low Disk Space” error occurs when your computer has less than 8GB of free hard drive space. This can typically be solved quickly by permanently deleting your trash or emptying your download folder.
If those options don’t work, you might check with your IT specialist to find what data or applications can be removed.

.
.

iPoint Version: 10.0330
Last modified: 31 Mar 2021

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.