Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
LGNiceguy
Contributor
Contributor

Could not Touch Target File

We have QLikview publisher and now it appears that after some time our schedule reloads are failing with the following error. We are running on Windows server 2012. I have verified that the service account has access to write in any folder on the machine that it would care to. I receive the following in the logfile

Error Exception=System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated. || at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess) || at System.Security.Principal.NTAccount.Translate(Type targetType) || at System.Security.AccessControl.CommonObjectSecurity.ModifyAccess(AccessControlModification modification, AccessRule rule, Boolean& modified) || at System.Security.AccessControl.CommonObjectSecurity.AddAccessRule(AccessRule rule) || at QVBWrapper.Document.CopyPermissionsToEmptyFile(ILogBucket i_LogBucket, String i_SourceFilename, String i_DestinationFileName)
20181205T124019.556-0500 Error Could not touch target file
20181205T124019.572-0500 Information Closing the document.
20181205T124020.228-0500 Information Closed the QlikView Engine successfully. ProcessID=7916
20181205T124020.228-0500 Error The task "Reload VW Merge_Salesforce Pipeline_splits" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: Could not touch target file || at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- End of inner exception stack trace --- || at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

Any help would be appreciated. If it is not using the service account how can I determine what account it is using when running a reload?

18 Replies
hopkinsc
Partner - Specialist III
Partner - Specialist III

You can check which account is running the distribution service from windows services. 

That account would need full permissions on the source folder and the folder publisher is publishing to 

LGNiceguy
Contributor
Contributor
Author

Ok I thought that was the case and that account has permission to write to the folder and I have been able to add files suing that account. 

Thanks for you response.

hopkinsc
Partner - Specialist III
Partner - Specialist III

Is the file open anywhere else? maybe try and kill all QVBs and restart the services in case the file is locked by something?

 

LGNiceguy
Contributor
Contributor
Author

THat has been done also as the server has been restarted . This has been an on-going issue for a month or so. I am just taking time today to try and figure out a solution.

hopkinsc
Partner - Specialist III
Partner - Specialist III

Do you have a document log (it should be in the same folder as the source QVW), what does the error say in that?

What is the full path of your source QVW, if its in any 'system' folders then that may cause a problem.

Does the reload work if running from the same location but using QV Desktop (not through the QMC)?

hopkinsc
Partner - Specialist III
Partner - Specialist III

Also, are you using section access?

LGNiceguy
Contributor
Contributor
Author

The document log looks ok i do not see any errors. There are no system folders in the path to these files as they are on a seperate drive in their own folder. yes the reload works using the desktop.

LGNiceguy
Contributor
Contributor
Author

no we are not using section access

hopkinsc
Partner - Specialist III
Partner - Specialist III

OK, so no section access and the reload works in the client. How was the last reload attempt done, QMC or client? The reason i ask is I'm wondering if the reason the doc log looks ok is because it was last done in the client?

If it errors in the QMC the doc log should show that too. 

at the moment it does sound permissions related. 

Can you log onto the server as the service account and try a manual reload from the client?