After the Administrator has defined a file system root location in Cognos Configuration\Edit Global Configuration on the General tab, the value of this parameter is not picked up in Cognos Connection\IBM Cognos Administration\Configuration\Set file location properties. This only occurs when the file system location is created on a server other than the BI content manager box. As a result, the file system location URI looks like the following as per the format required in Cognos Configuration: file:\\//servername (or ip address)/shared drive name. A Test Connection succeeds in Cognos Configuration, the configuration is saved and the server is restarted, but this value is still not picked up in Cognos Connection
Cognos system administrator (this is the role type in Cognos namespace) logs into Cognos Connection. Browse to Cognos Administration\Configuration tab\Dispatcher and Services. In Define file system locations properties, File System Root Location shows "no parameter value is entered".
The Namespace configured in Cognos Configuration is not sourced from the same authentication, or the two authentication sources are not from the same domain.
BI server is installed on Windows XP
Cognos Authentication is sourced from a local NTLM for testing
Network authentication is sourced from an Active Directory
There is no domain defined for NTLM source
Diagnosing The Problem
1. Configure a shared drive on the BI cm box where the users are sourced from the local NTLM namespace
2. save the configuration and restart the cm server
3. log into cognos connection using a NTLM user account. Make sure this user has server administrator's privilege in cognos namespace.
4. Configure the Files system location. The value of the root location is displayed
This proves the permission isn't sufficient for this local NTLM user account to access the share opened on another server
Resolving The Problem
Configure the same authentication in Cognos Configuration as used within this NTLM network on which it is deployed.
15 June 2018