An additional file not found
Hi all,
I've had some packages working for a long time now. Out of the blue, I'm getting the yellow triangle next to my packages that call to files on other servers.
I can browse to the files fine, see them and select them. However the triangle stays stating "An additional file not found" or "Server cannot find the following files". I know they are in the right location, as I'm browsing to them and selecting the files.
Heres a screeny of just one simple install that calls a batch file.
Can anybody see where I'm going wrong?
I thought at first maybe its a DNS issue and my PDQ server is failing to see the other servers, however I can contact them all fine.
Cheers, Stuart
Comments
Hi Stuart, this typically is an issue with DNS or permission errors if the warning persists. Do you have a large amount of files in your repository that need to removed?
What build are you currently running?
Your path to the file contains spaces, put him in " "
"\servername\Antivirus batch file...............bat"
Thanks for the replies guys.
I've cleared my unused files in the Repository apart from 49 files which I'm hesitant to remove. Shall I just remove them all - does this usually cause a problem?
NSlookup is making me think it's not a DNS issue, however I'm not ruling it out yet as our server and network team do like to make a sneaky change.
I tried with " " and without but to no avail.
My current build is 16.1.0.0 Enterprise mode. I can get around the issue by just copying the files it calls to my Repository, this just means that if somebody makes a change on the application server file that it's calling - I will have to know to copy it to PDQ Repository again.
Many thanks, Stuart
We've seen some other customers experience similar behavior with network paths becoming unavailable intermittently. You could try enabling Debug logging in Preferences->Logging and see if Event Viewer provides any more insight when you see these files becoming unavailable again in the future.
Have you tried to use the whole cmd line under "Command" instead only calling the bat in the step?
Or point with a install Step directly on the .bat?