IBM Support

Unable to access a data source from a TI process when the data source is located on a shared or other non-local drive

Troubleshooting


Problem

When creating TI processes, you will often use data sources for reading, inputting, or exporting data. Often, you might want to host these files on another machine than the TM1 server itself, and have the TI process work over the network. The TI process can sometimes throw an error such as:
Error: Prolog procedure line (0): Unable to open data source
This problem might occur even if you can view the "preview" section of the TI process correctly.

Diagnosing The Problem

1) First, try to use the same TI process with a data source local to the TM1 server you are working on. If this also does not work, there must be a local issue, and it must be resolved before trying to use networked data sources.
2) Try with another file over the networked data source, to see if the problem is limited to the specific file you are trying to use, or if all networked sources are showing the issue.
3) Have another TM1 server try to access the data source to check whether it is all machines being unable to access it, or only the one TM1 server cannot access it.

Resolving The Problem

If all networked data sources are failing to open from your TM1 server, there is likely something blocking the connection at the network level. This is most likely a firewall or other security software issue. You will need to work with your security team to ensure firewalls are opened, and security softwares are not holding any locks on the files you are trying to access.
If only one file is showing the issue, the most likely cause is a file permission issue. Ensure that the service account which is running your TM1 service has the proper rights to access the directory and file itself.
In case you cannot solve it with the above two methods, you may want to consider either using a local data source instead, or trying to troubleshoot the issue further using a third party tool such as Process Monitor. A tool like this can be used on both the source and target machines to identify exactly what account is trying to touch the file, and whether that file is locked by any other processes. This can help you identify where the cause of the issue is so that you can deal with it appropriately.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCTEW","label":"IBM Planning Analytics Local"},"ARM Category":[{"code":"a8m0z000000blxdAAA","label":"How To"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
24 December 2021

UID

ibm16537094