Never had an issue with this before, but today when I tried to create a new installation package, no .msi file was created. I’ve searched the drive and even changed the destination folder during the creation process to no avail. No errors reported and it shows as created in the console. I’ve manually ran mirror.exe, rebooted, check the db connection, etc. I’m sure it’s a user error issue on my part and I’ve searched the forums for quite a while… I’m stuck. Any ideas?
Thanks all
I’m sorry but I really don’t know what might be wrong. All I can say is that is ‘shouldn’t’ be avast as all it does is scan and alert to infection but not plock and I presume that isn’t happening ?
Have (or did) you another AV installed in this system, if so what was it and how did you get rid of it ?
As strange as this may seem the two (or remnants) AVs could clash, e.g. fight over control of the scan of a newly created file and this could show itself in that way, nothing done.
did u use the console while it was installed on a different computer then the AMS server itself?
I found out that when i give a path for the MSI file to be put away in, that path will be on the AMS server, not on the workstation where u are using the console…
maybe thats the problem, if not maybe u can check the logs that are under the VIEW menu in the console
I used the console on the actual server and I see nothing in the logs. The server is running :-[ Windows 2000, has never had another AV app on it, and only runs ADNM. It’s just weird as nothing has changed on the server, no hardware, config, permissions, etc. and going through the package creation process, everything looks normal. But when I go to the directory where it should have been placed, or for that matter search the whole server for the filename, nothing. Thank you very much for the replies…
Hi,
maybe it’s stupid, but you can try to use the full path and filename. Test with something easy like “c:\avast_install.msi”
Just tried it to no avail. 
I have to say, this is the first issue I’ve ever had with Avast in 5 years of using it. And the jury is still out on if it’s even an Avast issue. Odds are it’s me, just can’t seem to find out where.
Thanks for the response, -P
i just created an MSI for my server and i didnt find it either
tho the job happely ran…
so i checked the pathname from the package where i want it to be created and i wrote this: d:\tmp\packagename.msi
what i meant to write was: d:\temp\packagename.msi
the directory tmp didnt excists, and dispite that the job had ran succesfully no package was created at the location i specified…
with other words: make sure the path that you try to write the package on the AMS server has to excist…
I did try that but just in case tried again to 2 different drives (boot and a secondary) on the server into folders with wide open permissions, even in the root folder of the drives. Still no workie…
Maybe it’s time for me to open up a support ticket…
I had similar problem some time ago. I used network path for msi package and behaviour was the same. Problem was in user rights.
Check if your computer account has write permission on that directory. If not, add write permission for account %Servername%$ (it is not default) After adding permission for server account, ADNM created msi package in network directory as well as in local dir.
Not a permissions issue. I even logged into the server as Administrator. Every location on the server that I’ve tried has write permissions. Weird…
But ADNM works under System account not admins account. Check write permissions for computer account again (use effective permission tab)
IF it is a rights issue, try to give (temp) everyone write access to that folder u try to create in…
see if it works good then
Checked the above suggestions and still no go. Just uninstalled and reinstalled ADNM and still the same issue. How and why it just started happening out of no where is a mystery… I appreciate the suggestions so far, great community here. -P
maybe the downloaded files dont excist anymore?
if it runs with nothing it creates nothing…
maybe u threw it away or uninstalled and the mirror process doesnt suck them back in again?
(im starting to run out of ideas)