TM1 Forum

Hi Guys/Ladies

Of this morning I can't seem to load new data, I keep getting the error message : Error: Prolog procedure line (0): Unable to open data source "Current Month\Issues 08-09.csv".

The path to the file is correct and the preview within TI as well. All permissions are correct, I can even open the file.

Does anyone have any ideas, please!

Thanx!

Usually there are two problems

1.A user has the file open and so the TI process cant open it
2.Path or permissions are not correct, remember it's the path from the servers view point not the client. So just becuase you cane see it in the TI preview pain it does not mean the sever can

HTH

Steve Rowe wrote: 2.Path or permissions are not correct, remember it's the path from the servers view point not the client. So just becuase you cane see it in the TI preview pain it does not mean the sever can

To expand on this, it's generally a good idea to use UNC paths (\\server\folder\folder) rather than mapped drives (N:\folder).

Also, as Steve alludes to, if you're running TM1 as a service/application then the security that is applied is the security settings for the user that the service/application is running as.

Martin

The source file is not open while running the TI process. I am also using the correct server path and not a mapped drive.

The server however is started as a service. Where can I have a look at the security settings that you mentioned above?

par3 wrote:The source file is not open while running the TI process. I am also using the correct server path and not a mapped drive.

The server however is started as a service. Where can I have a look at the security settings that you mentioned above?

You can check on the server in the services list under which account the TM1 Service is running. If this is a local system account it will not have access to files that are not on the same machine as the TM1 service. If it is a domain user you need to check the access rights of this user.

Michel

The service is started as a local account. All the data files is on the same server as well. Any other ideas?

long shot, but try using a file where the full file path has no spaces in it. i remember some time ago having issues with a TI and it turned out to be spaces in the file name, although it's not always a problem...

Hi

If possible I would try logging on with the same account that the server is running under and check that you can access that file, or at least check that the user id has local admin rights on the server. We has a case recently where everything failed, and it turned out that someone in IT had been 'tidying up' security. Is this a file that you have been able to access before and now cannot access, or is it a new file?

Regards

Paul

If you have checked out file permissions and file paths and everything seems to check out then a file lock is looking more likely as your cause.

The file doesn't have to be open in another application to prevent TI being able to open it, the OS just needs to think that some other application has a lock on the file even when it really shouldn't. I would check to make sure this is not the case. In the past I have found this can be a common cause of TI not being able to access text sources, especially CSV files created or edited from within MS Excel. It can be very irritating as sometimes the only remedy is to restart either TM1 or the server itself if all other methods of disconnecting the locking thread fail.

Paul,

This is not a new file, and we have been loading it before. Only since we have started the server as a service are we experiencing this problem.

I'd strongly suspect that the rights of the account the service is running under are not sufficent. If it's just the LocalSystem account then this is proabaly the issue.

Cheers,

I found a problem with Excel 2003 saving my CSV file without quotes around the values, so when previewing everything was fine but when TI actually tried to load the data it was Unable to open datasource. All I did was erase the " (double Quote character) from Quote Char Options box.

I had same issue this morning. It turned out to be an read right issue. The service account can't read the file because the OS security. The only way to check that is using the service account to login into the machine and try to open the file from there.