error 1603 when pushing software

[dokopnyi]

I have created a package for Dell DDPE (Credant) encryption and we are receiving an error 1603 when trying to run it. I am pretty sure it has to do with the syntax of the parameters, as I have spent all day yesterday tweaking them to no avail.

Currently, the package is an .exe file, which calls back to the MSI located within the setup package using /v. There is also additional information called to the MSI within the package.

I have attached a sample from Dell denoting what we need to use when deploying this package silently:

DDPE_XXbit_setup.exe /s /v"SERVERHOSTNAME=server.organization.com POLICYPROXYHOSTNAME=rgk.organization.com MANAGEDDOMAIN=ORGANIZATION DEVICESERVERURL=https://server.organization.com:8443/xapi/ /l*v DDPE_EE-097.log /norestart /qn"

Is there a way to formulate this to work with Lansweeper correctly?

Please help! Thanks!

[Susan_A]

We received and answered this question via email as well. Below is a copy of the response we sent yesterday.

Anything that runs from Command Prompt should work in Lansweeper as well. We cannot tell just by looking at the syntax provided whether your command is "correct". You should run it directly in Command Prompt on a client machine first, replacing any parameters in the command with your own values. Only when the command works in Command Prompt will it work in Lansweeper as well.

The error 1603 you are getting is a generic error indicating that a fatal error occurred running the command. You'll most likely get the same error running the command in Command Prompt, confirming that the issue is not Lansweeper related. We notice you posted your question on our forum as well, where another forum user linked to this article. It provides some information on debugging error 1603 messages.

[crashff · Accepted solution]

This might help you find the problem:
http://blogs.msdn.com/b/astebner/archive/2005/08/01/446328.aspx