Package returned error code 9009?

Hi Raiden, 

Have you tried running a test package to install on the same target computer(s)? 

Just something simple like Flash, or Java, just to see if it goes through. 

According to their website, Kaspersky supports remote administration via command line, however, I'm wondering if your antivirus is blocking PDQ in the first place. Are you running the endpoint version of it? if so, you may want to try placing the PDQ box in the exception's list. 

Also, does it have any type of "tamper protection" settings? This may be preventing you from running a remote force of updates. 

Hi ToF,

Thanks for the reply :)

I have been doing some further playing this afternoon and if I schedule a deploy task on my local LAN this and others tasks I have created have successfully completed, and returned as successful however, computer on my WAN get the 9009 error message.

I did remote onto a couple of machines on my WAN while I ran the deploy task, I could see the task did execute and complete successfully on the computer end but I still get this returned 9009 error code back on PDQ Deploy.

As for the Kaspersky we are running we are running Enpoint Business v6.0.4.1224 with Administration server v8.0

Hmmm... Interesting. 

You may want to take a look at this documentation from AA in regards to firewall settings that needs to be allowed. 

http://support.adminarsenal.com/entries/21531976-firewall-ports-and-exceptions

The computers that are on the WAN are behind a router/firewall? Perhaps some type of port forwarding needs to be done to get the correct reading? 

Error codes can vary depending on the application.  9009 can mean that a path cannot be found or be an issue with DNS resolution, but it may have a specific meaning to the app in question.  Can you attach the batch file you're deploying?  If it contains sensitive information you can send it to support@adminarsenal.com for review.

Hi TOF,

I know our desktop machines have the windows firewall disabled but we do have a firewall on our MPLS line which links our external sites to the main office.

I will read the post you gave me and hopefully it will list what ports I need to open which I will do in the morning.

Hi Adam,

I looked at the DNS and we have no issues either site to main office or main office to site.  I did some tests and the file path can be seen externally by the DNS name and by the PDQ Deploy machines IP?

As for the batch file code, here it is, very simple and the recommended syntax from Kaspersky.  There are two different scripts one for x86 and one for x64.  Here is both.

c:
cd\
cd "C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4"
avp.com update
exit

c:
cd\
cd "C:\Program Files (x86)\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4"
avp.com update
exit

Much appreciated

Raiden

Thanks for the batch file.  There are a couple of possibilities.

First, the error 9009 may be a success or other status code that you can ignore. You may be getting that return code when you run it manually but you just don't see it.  Return codes are hidden by default on the command-line. To see the return code when your run it manually, change the batch file like this:

c:
cd\
cd "C:\Program Files\Kaspersky Lab\Kaspersky Anti-Virus 6.0 for Windows Workstations MP4" 
avp.com update
echo %errorlevel%

You should see the return code from the command printed on the last line of the output.  If you're getting 9009 and the command runs successfully then you can add 9009 to the Success Codes of the package and it will be treated as a success.

Second, the error only happens when it runs remotely.  This is usually due to the background process not running in an interactive profile.  Depending on the cause it's just a matter of setting up the environment properly.  The program is probably writing some information to the command-line which you can't see in PDQ Deploy (we're fixing this in a future release).  You can still get the output by adding a file redirect to the package in the Parameters section:

> c:\avp-output.txt 2>&1

This will create a text file on the target computer with all of the output, including any error messages. Note, this file is on the target computer, not the PDQ Deploy console computer.  Hopefully the cause of the problem will be easier to discover there.

Hi Adam,

Thanks for this I will try it in the morning and report back.

The strange thing for me is this, when I run the same batch file in my office on my local LAN I don't get the error but get successful, it only seems to be machine at remote location across our WAN.  If the batch was not executed correctly I would have thought I would see the error locally as well as remotely?

I remote accessed to my office and changed some firewall settings but it didn't make any difference to the external machine I still got the 9009?

That does narrow it down a bit.  Do you use the same credentials when installing over the WAN?  

One possibility... net helpmsg 9009 > DNS server not authoritative for zone.

As described here http://forum.sysinternals.com/psexec-target-cmd-returns-error-code-9009_topic18945.html

The hint here is that you try the deployment using psexec from pstools (http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx) and check if you get the same 9009 result. This way we can eliminate if the problem is within PDQ Deploy or somewhere else.

yes, we are all on the domain and I am using my domain admin account.

.

Update:

Right I have just remotely connected to the office and setup a new deploy task using the additional Parameters that Adam kindly supplied, although the task failed again, I could see in the outputted text file why it had failed. 

This particular machine had an issue with using an outdated license file because the needed agent was not installed.  This prevented the task from running as you only get updater tasks by having the agent installed, with a valid license key and our current desktop policy applied.

I sorted out all the above and ran the task again and this time i got SUCCESSFUL?  excellent.

Now i doubt the above will be the same for all the other machines but at least I can view the outputted error file to point me in the right direction.

I will do the others tomorrow morning when I am back in the office and report my findings.

At least one thing has been proven is that I have now had a successful deploy to a machine on our WAN.

Thanks for all the help guys

RK

Excellent, I'm glad you got it working.  It'll be nice when we get the output within PDQ Deploy because it'll make it much easier for you to get the output.