Error in logs: kernel[0]: Validation failed, dataSuffix

First of all, please check your disk for any errors. Please run Repair Disk in Disk Utility (on your Macintosh HD). If the errors are bad, probably you need to restart your Mac and then hold CMD+R until logo appears, then you should re-run Disk Utility.

You can also try some 3rd party software for recovering the files for iWork like Stellar Phoenix Macintosh.

If this doesn't work, please open Console to check the logs or do it manually from the Terminal:

$ tail -f /var/log/system.log

and run Pages/Numbers again.

This should point you to the specific error which you can look for.

If you don't have any errors and your disk is clean, then you can try to Reinstall it via App Store:

Here's how to reinstall an application from the Mac App Store:

1. Open the App Store application. (It's on the Dock, or in the Applications folder.)

2. Hold down the Option key and click Purchases.

3. An Install button appears next to the missing application.

4. Click Install.

The "missing" application won't be missing for much longer. It's now downloading to your computer! When the download is finished, you'll be able to find the application in Launchpad and the Applications folder.

Source: http://www.macinstruct.com/node/412

Another method you can try is the suggestion from this thread:

Open App Store, go to Purchases page, re-download thee apps. You will first need to drag the iWork folder to the Trash.

If you still can't download it from App Store, you can try from re-download it from torrent (you should have a proper licence). But if you'll download the older version and it still doesn't work (which will show some missing frameworks, file images, etc.), then you'll have to do the upgrade first via App Store.

If none of above will work, try to remove cache and setting files from your Home Folder:

~/Library/Caches/com.apple.iWork.*
~/Library/Caches/com.apple.helpd/Generated/com.apple.iWork.*
~/Library/Preferences/com.apple.iWork.*
~/Library/Preferences/ByHost/com.apple.iWork.*
~/Library/Application Support/iWork

You can list them by the following command:

find ~/Library -iname \*iwork\*

Advanced troubleshooting

If none of above will work, then you can try to debug wtf is going on by:

1. First run in Terminal dtruss command to listen for e.g. Pages execution:

   sudo dtruss -fn Pages
   

2. Run e.g. Pages

Dtruss should show you some debugging stuff. If there is too much going on, you can log it to the file by:

sudo dtruss -fn Pages 2>&1 | tee dtruss.log

To filter only file operations, you can try:

sudo dtruss -f -t lstat64 -n Pages

or the easiest way by running OSX pre-defined dtrace script:

sudo filebyproc.d | grep -i iWork

This would give you some idea what files could be wrong/missing during the start.

As workaround, InjectEventHandler handler can be removed or commented out from Info.plist from the files:

/Library/ScriptingAdditions/SIMBL.osax/Contents/Info.plist
/Library/ScriptingAdditions/MySpeed.osax/Contents/Info.plist

Source: https://code.google.com/p/simbl/issues/detail?id=7

In example:

--- a/Info.plist
+++ b/Info.plist
@@ -37,8 +37,6 @@
                <key>Context</key>
                <string>Process</string>
            </dict>
-           <key>SIMeleop</key>
-           <string>InjectEventHandler</string>
        </dict>
    </dict>
 </dict>

Or you can also try to set ThreadSafe to true: E.g.

<key>OSAXHandlers</key>
<dict>
    <key>Events</key>
    <dict>
        <key>sysodlog</key>
        <dict>
            <key>Handler</key>
            <string>DisplayDialogEventHandler</string>
            <key>ThreadSafe</key>
            <true/>
            <key>Context</key>
            <string>Process</string>
        </dict> 
...

Handler dictionary keys:

ThreadSafe - A boolean; is the handler thread-safe? (Event handlers only.)

ThreadSafe OSA and AppleScript in Mac OS X v10.6 are thread-safe. If a script is executed on a background thread and invokes an event handler that is not thread-safe, it will be called on the main thread, which is slower than directly invoking it on the calling thread and may reduce application responsiveness to user input. Ideally, all handlers should be thread-safe. Some inherently cannot be; for example, almost anything that displays UI must be executed on the main thread. You are encouraged to either verify that your event handlers are thread-safe or update them to make them thread-safe.

If the value of this key is true, then the handler may be executed on a non-main thread and it may be executed concurrently from multiple threads. If false, it will only be executed on the main thread. This key is required for event handlers, and must not be present for coercion handlers, which are required to be thread-safe. If a coercion handler cannot be made safe to run on background threads, the handler must arrange to execute the coercion on the main thread, such as using by using libdispatch and the main dispatch queue.

Read more: http://developer.apple.com/library/mac/technotes/tn1164/_index.html#//apple_ref/doc/uid/DTS10003003-CH1-MAC_OS_X_V10_6__SNOW_LEOPARD__AND_LATER__INFO_PLIST

Related issues:

https://code.google.com/p/simbl/issues/detail?id=7 https://code.google.com/p/simbl/issues/detail?id=38

Other:

https://code.google.com/p/simbl/issues/detail?id=14 https://code.google.com/p/simbl/issues/detail?id=66 https://code.google.com/p/simbl/issues/detail?id=67 https://code.google.com/p/afloat/issues/detail?id=43