Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All,
QlikView is not reading data through qvsource service from SFTP....!
whenever I run the generate loadscript in qvsource it is running fine (status OK and I can see that files are reading while generating load script) but whenever i copied the load script to qlikview it says <Status> field not found.
I checked all the services QVSource and QlikView services all are running fine and I tried by restarting all the services, still unsuccessful?
Every reload in qlikview pop up with an error fieldnot found. I rechecked, recopied load script, using the SFTP connection string as it is from qvsource. Using 1.4.9.5 version it is not the very latest one. It was working fine for last 6 months.
Please give me any suggestions!
Could you rename any instances of the table name
SFTPDownloadFile
to
SFTPDownload
And:
FTPDownloadFile
to
FTPDownload
We changed this in version 1.0.1 of the connector, the old name should have been automatically mapped but wasn't (this has now been fixed).
Whenever you get this 'field not found' error while your load script runs the first step is always to copy the WVSource request URL between the [...] brackets (it will probably start http://localhost:5555/QVSource/....] into a browser window address bar and run it, you should get a more helpful error message back. A typical reason is an expired licence but it could be something else.
Please see if this helps, I would also strongly recommend upgrading to the latest QVSource, we released an important update this week which fixes an SSL issue which may be affecting you.
Chris,
Thanks for the replay, here is error msg "Error requesting table SFTPDownloadFile for FileTransferConnector". Could you please explain me what the msg is about?
Licence is still valid.
We planned for up gradation but postponed because of some internal reasons.
Thanks,
Santosh
Could you rename any instances of the table name
SFTPDownloadFile
to
SFTPDownload
And:
FTPDownloadFile
to
FTPDownload
We changed this in version 1.0.1 of the connector, the old name should have been automatically mapped but wasn't (this has now been fixed).
Excellent! It's worked. Thanks Chris.
Sincerely,
Santosh
Great