Anyone Managesoft Expert here?
Hi Guys,
In my office, we use Managesoft deployment solution to deploy packages. I am stuck with a pakcage (trend micro client 10.1 sp1).
Error-1316. A network error occured while attempting to read from the file.
I tried googling, but cant find anything. If anyone has any infomation regarding this, please share it.
Thanks,
In my office, we use Managesoft deployment solution to deploy packages. I am stuck with a pakcage (trend micro client 10.1 sp1).
Error-1316. A network error occured while attempting to read from the file.
I tried googling, but cant find anything. If anyone has any infomation regarding this, please share it.
Thanks,
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
It normally means exactly what it says. Have you tried PSExec'ing to one of the machines exhibiting this behaviour?
Posted by:
dnmech
13 years ago
Ian,
Could you please be more elaborate in what you are suggesting?
On the machines Trend Micro 8.0 is intalled, i am not upgrading it by using the upgrade table, the managesoft does it automatically, it is searching for the older msi in the same distribution folder in which the new msi is kept.
Thanks,
DN
Could you please be more elaborate in what you are suggesting?
On the machines Trend Micro 8.0 is intalled, i am not upgrading it by using the upgrade table, the managesoft does it automatically, it is searching for the older msi in the same distribution folder in which the new msi is kept.
Thanks,
DN
Posted by:
anonymous_9363
13 years ago
What I meant was, have you tried taking the deployment system out of the equation?
The simplest way to do that is to use the SysInternals tool, PSExec, to remotely execute the MSI from its source. If that fails in the same way, you have a network problem, rather than anything specific to the deployment mechanism. You can then try copying the source folder to the target and executing the install from the local folder.
As with most things, it's just a question of eliminating things one-by-one.
The simplest way to do that is to use the SysInternals tool, PSExec, to remotely execute the MSI from its source. If that fails in the same way, you have a network problem, rather than anything specific to the deployment mechanism. You can then try copying the source folder to the target and executing the install from the local folder.
As with most things, it's just a question of eliminating things one-by-one.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.