FileMaker cannot share or be a client of a file
For “FileMaker cannot share or be a client of a file because the networking stack could not be initialized.” error.
Resolution for Windows:
Please check to make sure that your server.pem file [located in the root folder of where FileMaker Pro/FileMaker Pro Advanced, i.e. C:\Program Files\FileMaker\FileMaker Pro] is around 5 KB.
If it’s any smaller than that, then chances are that file is corrupt and can cause this error message to appear. You may be able to copy the server.pem file from a working FileMaker Pro computer to the computer exhibiting the issue and test. Reinstalling the application should also create a non damaged server.pem file.
If that is not the case, it appears that Winsock2 may be corrupted on the computer and needs to repaired. Winsock2 is an API for applications to utilize the Windows TCP/IP stack.
To repair this corruption, please refer to the following Microsoft Knowledge Base article. http://support.microsoft.com/kb/811259
For further information and support, please contact Microsoft Technical Support.
Resolution for Mac OS:
This issue can appear when FileMaker Pro is installed while logged in under an external account in Mac OS X. An example of this account could be a LDAP, Open Directory or Active Directory account. To resolve this issue you will need to reinstall FileMaker Pro using a local/Mac OS X account. The steps for doing this are listed below:
Remove your FileMaker Pro folder by moving it to the trash. The Default location for this folder is the Applications directory.
** If you have Activated your FileMaker product, please be sure to Deactivate your software by going to the Help Menu > Deactivate before deleting your FileMaker installation.** Click here for more information
Log out of the machine and log in with a Mac OS X user account. If you’re not sure what accounts are local and what are not please contact your network administrator.
Run the FileMaker Pro installer and re-install. Reboot and apply updates, if any.