Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Since upgrading to TOS 7.1.1 I am unable to initiate the property file and load the information into my project.
In tFileInputProperties the filename path = "../../SETTINGS/branch.Properties"
I have never had any issues previously but when trying to run the same project (exported from 6.5 > 7.1) the file will not load.
Exception in component tFileInputProperties_1 (BRANCH)
java.io.FileNotFoundException: ..\..\SETTINGS\BRANCH.Properties (The system cannot find the path specified)
If I enter the full path "C:/SETTINGS/branch.Properties" then it works.
Any ideas?
Thanks in advance.
Just in case this helps anyone, I figured out the isssue and created a workaround
In my earlier thread I used the below......which always worked
6.5 propery file path = "../../SETTINGS/x.Properties"
When upgrading to Talend 7.1 this stopped working.
The solution was to add an extra / at the beginning of the string
7.1 property file path = "/../../SETTINGS/x.Properties"
However, I also figured that although that solves my issue on my local machine (laptop running talend 7*) the new path failed on the server once the project was published (Windows Server 2012 R2). The server only recognises the previous naming convention used in 6.5.
So in all my projects, I have applied the below logic where it will try one format and then the other.
Local = "/../../SETTINGS/x.Properties"
Server = "../../SETTINGS/x.Properties"
Hello,
Is there any a permissions issue for 7.1.1? Are you able to load file when create a new job in v 7.1.1( In tFileInputProperties the filename path = "../../SETTINGS/branch.Properties")
Sabrina
Best regards
Sabrina
Hi Sabrina,
There are no permission issues, same install procedure, no elevated privileges.
Only difference is the version of TOS that I am running.
I have now created a new project directly in 7.1.1 and added the components.
I receive exactly the same issue.
Can you replicate the error?
Old workspace = C:\talend\TOS_DI-Win32-20181026_1147-V7.1.1\workspace\PBZ
New workspace = C:\talend\TOS_DI-Win32-20180116_1512-V6.5.1\workspace\PBZ
Hello,
Is there any difference for administrator( domain admin or local admin)?
Best regards
Sabrina
Hi,
I don't have access as administrator within my organisation.
Although I have 3x types of accounts that I can use on the domain......
The absolute path works for all accounts and there are no restrictions on the folder (C:\Settings).
It's only when using the relative path it can't locate the file.
Works with 6.5 but just not with 7.1
Just in case this helps anyone, I figured out the isssue and created a workaround
In my earlier thread I used the below......which always worked
6.5 propery file path = "../../SETTINGS/x.Properties"
When upgrading to Talend 7.1 this stopped working.
The solution was to add an extra / at the beginning of the string
7.1 property file path = "/../../SETTINGS/x.Properties"
However, I also figured that although that solves my issue on my local machine (laptop running talend 7*) the new path failed on the server once the project was published (Windows Server 2012 R2). The server only recognises the previous naming convention used in 6.5.
So in all my projects, I have applied the below logic where it will try one format and then the other.
Local = "/../../SETTINGS/x.Properties"
Server = "../../SETTINGS/x.Properties"