Page 1 of 1

TI Process: Unable to open data source

Posted: Sun Apr 13, 2014 12:32 pm
by Radhika
Hello All,

I have created a TI process to build a dimension from a CSV file, the source path for this file is stored in a cube of TM1. I have created a parameter in Prolog tab to store the path of this file, when I run the TI process it throws an error unable to open data source. I tried the below options

Created a new TI job - not working
Running TM1 Service under service account which has admin access.
Able to access the path of the source files from command prompt.

Please help me to resolve the issue

Thanks,
Radhika

Re: TI Process: Unable to open data source

Posted: Sun Apr 13, 2014 1:37 pm
by Wim Gielis
Hi

You are sure that you don't have a typo... We've all encountered this type of human errors in the past.
Did you do a AsciiOutput to guarantee the validity of the file path and filename?
Is the CSV file closed?

Re: TI Process: Unable to open data source

Posted: Sun Apr 13, 2014 6:27 pm
by Alan Kirk
In addition to what Wim said, is the CSV file on a local drive, or on a network share?

If it's on a network share then the fact that the account that you're using to run the server has local Admin rights is irrelevant; it would also need to have permissions to access that share. Similarly this would raise the question of whether you did the command prompt check on the server box that TM1 is running on, using the account that the TM1 server is running under. If you did it on your local machine, that doesn't guarantee anything. Remember that in checking access you need to look at everything from the server's point of view, not your own.

Re: TI Process: Unable to open data source

Posted: Mon Apr 14, 2014 1:26 am
by macsir
Maybe a snapshot from your TI interface can tell us.

Re: TI Process: Unable to open data source

Posted: Tue Apr 15, 2014 3:05 pm
by Radhika
Thank you all for your response.

@Wim, ASCII output gives me the exact file path.

@Alan, I have the CSV file on my local machine.

Here I have attached the screen shot of the Path, System Info Cube and the script in the metadata tab.


Thanks,
Radhika

Re: TI Process: Unable to open data source

Posted: Tue Apr 15, 2014 5:37 pm
by tomok
Radhika wrote:@Alan, I have the CSV file on my local machine.
Well, unless the TM1 server is also running on your local machine how do you suppose it's going to access the file? D:\GL Source Files sounds like a local drive letter. Is that the D: drive on the TM1 server, your local machine, or both?

Re: TI Process: Unable to open data source

Posted: Wed Apr 16, 2014 12:35 am
by macsir

Re: TI Process: Unable to open data source

Posted: Wed Apr 16, 2014 5:01 am
by Radhika
@tomok, both d rive and TM1 server are on my local machine.

Re: TI Process: Unable to open data source

Posted: Wed Apr 16, 2014 5:39 am
by macsir
Try this in your Prolog,

Code: Select all

Datasourcenameforserver = cImportFile;

Re: TI Process: Unable to open data source

Posted: Wed Apr 16, 2014 6:18 am
by Alan Kirk
Radhika wrote:@tomok, both d rive and TM1 server are on my local machine.
I think that this comes back to Wim's original question about whether you're certain that the file is closed. You'll get that error if you still have the file open in an application whuch has a lock on it, like Excel.

Re: TI Process: Unable to open data source

Posted: Wed Apr 16, 2014 11:20 pm
by macsir
I think that this comes back to Wim's original question about whether you're certain that the file is closed. You'll get that error if you still have the file open in an application whuch has a lock on it, like Excel.
No, Alan. The problem in his code is that he assigned PATH rather than FILE to datasourcenameforserver in his prolog. ;)

Re: TI Process: Unable to open data source

Posted: Wed Apr 16, 2014 11:24 pm
by Alan Kirk
macsir wrote:
I think that this comes back to Wim's original question about whether you're certain that the file is closed. You'll get that error if you still have the file open in an application whuch has a lock on it, like Excel.
No, Alan. The problem in his code is that he assigned PATH rather than FILE to datasourcenameforserver in his prolog. ;)
Quite right; I didn't look at his Word attachment before but the mistake is visible in there.