Error 112: Not Enough Disk Space for Package
We are currently running Deployment Server and in the process of deploying automation partitions to all of our workstations (no DHCP). The partition loads fine on all of our machines except one subset which are all the same hardware with the same load (Windows XP). Wnenever I create the package and deploy it by either drag and dropping it or creating a job and assign it to one of these machines, I automatically get the subject error.
Although our loads are slightly different, our security settings are the same across the board (so I believe). There is plenty of disk space on the systems. This seems to be not only a problem with the automation package but any application package deployed to the workstations.
So far I have re-created the packages, deployed with the "Run directly from server option" and re-verified the disk space.
Any suggestions would be greatly appreciated.
tks..
George
Other automation partitions
Not sure if this is actually a problem, but I heard it could be. If the computer previously has an automation partition or an OEM partition it, might fail on the computer. Again, I don't know if it would be giving you the error message you are recieving. To check this go to the disk manager. If Disk 0 has two partitions or if there is an unlabeled partition you have an automation or OEM partition.
Some other possible reasons
The error descibed can also be caused by wrong rights, or a wrong formatted harddisk.
Regards
Erik
www.DinamiQs.com
Regards
Erik
www.DinamiQs.com
Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)
Thanks Spazzen, I did check
Thanks Spazzen,
I did check that in we only have the single partition.
Thanks Erik, We have been
Thanks Erik,
We have been able to push the partition to other machines (same domain) with the same credentials with no problem. All of the hard drives are formatted NTFS. We also defragged them to see if there was a problem with contigous space...thanks again for the assist.
You mentioned subset...
Are they also on a separate network subnet? It could be that that a different subnet could have restrictions that the rest of the LAN is not imposing on traffic and so the error might be the closest one that can be reported. To test, change one of them to a different subnet and see if that changes any result.
Hope that helps.
Shansen
Would you like to reply?
Login or Register to post your comment.