TDM Portal: Publish Job failing with "The system cannot find the path specified"

book

Article ID: 197647

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Hi Team,

While trying to run the Publish job from TDM portal its failing with "c.c.t.p.l.TDMPublishLog:  java.io.IOException: The system cannot find the path specified" error.
Another thing i notice is there is no sync between TDM portal and Datamaker (Both installed in separate server).

Need your help in here. 

Please find below the Publish log

 at java.lang.Thread.run(Thread.java:748)
2020-08-18 19:21:11.386 UTC [INFO ] [taskExecutor-1           ] --- [U:][M:][P:]                  c.c.t.p.t.TDMPublishStatusSender:  Successfully sent status update for job 1813 to Job Engine Service, Status Code: 200
2020-08-18 19:21:11.386 UTC [INFO ] [taskExecutor-1           ] --- [U:][M:][P:]                            c.c.t.c.d.DBConnection:  Connection Pool: jdbc:sqlserver://svdABC:1433;database=gtrep;user=sa [max:20; busy:0; idle:5]
2020-08-18 19:21:11.386 UTC [ERROR] [taskExecutor-1           ] --- [U:][M:][P:]                      c.c.t.p.m.TDMPublishJobStart:  doPublish error, jobId=1813, Exception: The system cannot find the path specified
2020-08-18 19:21:11.386 UTC [ERROR] [taskExecutor-1           ] --- [U:][M:][P:]                           c.c.t.p.l.TDMPublishLog:  java.io.IOException: The system cannot find the path specified
 at java.io.WinNTFileSystem.createFileExclusively(Native Method)
 at java.io.File.createNewFile(File.java:1012)
 at com.ca.tdm.publ.utils.TDMPublishUtils.getBufferedFileWriter(TDMPublishUtils.java:92)
 at com.ca.tdm.publ.log.TDMPublishLog.writeLogBuffer(TDMPublishLog.java:147)
 at com.ca.tdm.publ.log.TDMPublishLog.logPublishPrequel(TDMPublishLog.java:139)
 at com.ca.tdm.publ.model.TDMPublishJobStart.doPublish(TDMPublishJobStart.java:510)
 at com.ca.tdm.publ.publthread.TDMPublishThread.run(TDMPublishThread.java:46)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)



Cause

 
  • Verify the Generator name to see if it has invalid characters  for eg : ReportsQA_8/20  ,   Slash is invalid name for filename in Windows OS. 
  • Verify if a scanner like Mcafee is deleting the jobs in the  C:\ProgramData\CA\CA Test Data Manager Portal\Jobs\ Job_XXX folder

Environment

Release : 4.7

Component : CA Test Data Manager

Resolution

  •  Check the permissions on  C:\ProgramData\CA\CA Test Data Manager Portal\Jobs\    folder
  • Use proper naming conventions for Generator.  We use Generator name in log filename and slash(/) is invalid character for file name in Windows OS.

             Log filename used is is C:\ProgramData\CA\CA Test Data Manager Portal\\Jobs\Job_1911\Job_1911_Data_Pool_ReportsQA_8/20.log  which is invalid. 

 

Here are some tips to troubleshoot:

**************************************

In the Portal browser, Click on F12 and see the network trace for that published job.  Download the HAR file , 

Open the Har file in Har viewer. 

Expand -  GET Job? https://svdABB04:8443/TestDataManager/origin=flow_origin)%2B(projectId=1822)

We were able to see that Data is being written to this folder

,"created":null},{"name":"Publish_TDSQA_EU_TDM_ReportsQA_8/18","jobId":1822,"description":"Publish to
 TDSQA_EU_TDM using ReportsQA_8/18","projectName":"ABCConnect","projectId":0,"versionId":null,"createdBy"
:"d440021","email":null,"scheduledTime":"2020-08-19T17:34:22Z","startTime":"2020-08-19T17:34:23Z","endTime"
:"2020-08-19T17:34:27Z","status":"Failed","type":"PUBLISH","parentId":0,"jobs":[],"duration":4140,"artifactLocation"
:"C:\\ProgramData\\CA\\CA Test Data Manager Portal\\\\Jobs\\Job_1822.zip",

 

For McAfee related issues, Use Process Monitor Tool -  the advanced monitoring tool for Windows that shows real-time file system info, 

Using this tool, we saw that  McAfee was scanning these files and deleting them

 

Work with your security team to have this resolved. 

Attachments