Can I get FileMaker Pro 8.5 Win to use TCP on a Terminal Server?
The client uses FM Pro. They will be between offices for a few months. My feeling is that they would get better performance with FileMaker Pro running on a Terminal server on a Windows 2003 server, rather than having their 10 users trying to connect directly over the Internet.
They have version 8.5 at the moment.
They are unable to connect to a FileMaker server via TCP. The error message appears:
"FileMaker cannot share or be a client of a file because the networking stack could not be initialized'
Thanks.
Larry
They have version 8.5 at the moment.
They are unable to connect to a FileMaker server via TCP. The error message appears:
"FileMaker cannot share or be a client of a file because the networking stack could not be initialized'
Thanks.
Larry
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It appears that there will be too much testing for me to solve this. I appreciate the advice.
ASKER
The FileMaker site had one article I found about this. I tried the "Fix It For Me" option, but that didn't help.
http://help.filemaker.com/app/answers/detail/a_id/213/kw/network%20stack%20error
--------------------------
ISSUE:
I am having problems with a computer on my network not working with FileMaker Pro. When I try to go to Open Remote, I am receiving the following error
"FileMaker cannot share or be a client of a file because the networking stack could not be initialized."
I have already tried uninstalling and reinstalling FileMaker Pro, but it did not make a difference.
Resolution for Windows:
Check to make sure the server.pem file size [located in the root folder of where FileMaker Pro/FileMaker Pro Advanced, i.e. C:\Program Files\FileMaker\FileMaker Pro] is around 5 KB. To check the size of the file, hover over the file name.
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.