Created On: 30 March 2011
Problem:
When using Fileshare as a Windows service on recent Windows operating systems, you will encounter a situation where clients cannot connect to servers that are started as services. This is because of enhanced system security that has been implemented by Microsoft and that prevents individual users of a system gaining access to shared memory segments that have been allocated by other users applications.
Resolution:
System services are usually started by the system ID, not by a user ID. The security measure is intended to prevent accidental data loss, which is why CCI complies with the system default behaviour. However if you wish to specifically allow cross-user connections, you will need to enable the following option in your CCI.INI configuration file:
[ccismem-base]
use_global_namespace=yes
This must be present in the configuration of both Fileshare Server and Fileshare Client. Unless the user wishes to protect against accidental access between users, it is recommended that the CCI.INI file is placed in the %SystemRoot% directory where it will be visible to both Fileshare server and all Fileshare Client applications.
[ccismem-base]
use_global_namespace=yes
This must be present in the configuration of both Fileshare Server and Fileshare Client. Unless the user wishes to protect against accidental access between users, it is recommended that the CCI.INI file is placed in the %SystemRoot% directory where it will be visible to both Fileshare server and all Fileshare Client applications.
Incident #2490591
Old KB# 33802
#EnterpriseServer
#Server
#COBOL
#Enterprise
#StudioEnterpriseEdition
#netexpress