Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.9.1 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

impossible deployement package

impossible to deploy a package regardless of the method

ocs server 2.8.x by debian paquet > ssl ok 

agent 2.8.x

ssl communication ok

inventory ok

download package ok

administrator profile

for installation:

method 1 msi file:

run a command> msiexe.exe / i a.msi / quiet

return> error code exit 1

method 2:

.exe or msi file

action> run file

name> a.exe or a.msi

result> DOWNLOAD => Executing action <LAUNCH> for package <1641730804> for ever then error time out

ocs is driving me crazy

thx

==============================================================================

Starting OCS Inventory Package Download and Setup Tool on Monday, January 10, 2022 16:59:15.

DOWNLOAD => Running OCS Inventory Download Version 2.8.0.1

DOWNLOAD => Using OCS Inventory FrameWork Version 2.8.0.1

DOWNLOAD => Using network connection with Communication Server

COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>

DOWNLOAD => Using Communication Provider <OCS Inventory cURL Communication Provider> Version <2.8.0.1>

DOWNLOAD => Starting new period of 10 cycles

DOWNLOAD => Flushing package queue

DOWNLOAD => Parsing directory <C:\ProgramData\OCS Inventory NG\Agent\download> for packages

DOWNLOAD => Verifying package <C:\ProgramData\OCS Inventory NG\Agent\download\1641730804>

DOWNLOAD => Package <1641730804> verified and added to process queue

DOWNLOAD => Processing packages for cycle 1 on Monday, January 10, 2022 16:59:15

DOWNLOAD => Downloading package fragment <1641730804-1>

COM SERVER => Initializing cURL library for getFile

COM SERVER => Using cURL without server authentication

COM SERVER => Disabling cURL proxy support

COM SERVER => Enabling cURL SSL server validation support using CA Bundle <cacert.pem>

COM SERVER => Sending fileGet request to URL <HTTPS://parc.mv-tech.fr/download/1641730804/1641730804-1>

COM SERVER => fileGet response received <HTTP Status Code #200>

COM SERVER => Cleaning cURL library

DOWNLOAD => Pausing for fragment latency (10 seconds)

DOWNLOAD => Pausing for cycle latency (60 seconds)

DOWNLOAD => Processing packages for cycle 2 on Monday, January 10, 2022 17:00:32

DOWNLOAD => Building package <1641730804>

PACKAGE => Verifying fragment files of package <1641730804>

PACKAGE => Checking free disk space for package <1641730804>

PACKAGE => Building ZIP for package <1641730804>

PACKAGE => Verifying ZIP signature for package <1641730804>

DOWNLOAD => Package <1641730804> built successfully

DOWNLOAD => Executing action <EXECUTE> for package <1641730804>

PACKAGE => Executing command <msiexec.exe/i a.msi /quiet> for package <1641730804> on <Monday, January 10, 2022 17:00:33>

PACKAGE => Package <1641730804> successfully executed. Command exit code is <1>. Package return code is <EXIT_CODE_1>

PACKAGE => No post execution command provided for package <1641730804>

ERROR *** DOWNLOAD => Will not register package <1641730804> in history: result <EXIT_CODE_1> not a success

DOWNLOAD => Sending result code <EXIT_CODE_1> for package <1641730804>

DID_CHECK => Read DeviceID <AV-PC-2022-01-05-17-56-16> and MACs <30:00:20:52:41:5300:FF:9C:C3:C3:9708:60:6E:50:1B:8F00:E0:4C:68:46:3B00:50:56:C0:00:0100:50:56:C0:00:08> in file <ocsinventory.dat>

COM SERVER => Initializing cURL library for sendRequest

COM SERVER => Using cURL without server authentication

COM SERVER => Disabling cURL proxy support

COM SERVER => Enabling cURL SSL server validation support using CA Bundle <cacert.pem>

COM SERVER => Sending HTTP Post request to URL <https://parc.mv-tech.fr/ocsinventory>

COM SERVER => HTTP Post response received <HTTP Status Code #200>

COM SERVER => Cleaning cURL library

DOWNLOAD => Result code request successfully sent

DOWNLOAD => Pausing for fragment latency (10 seconds)

DOWNLOAD => Pausing for cycle latency (60 seconds)

DOWNLOAD => Processing packages for cycle 3 on Monday, January 10, 2022 17:01:43

==============================================================================

Starting OCS Inventory Package Download and Setup Tool on Monday, January 10, 2022 17:34:10.

DOWNLOAD => Building package <1641730804>

PACKAGE => Verifying fragment files of package <1641730804>

PACKAGE => Checking free disk space for package <1641730804>

PACKAGE => Building ZIP for package <1641730804>

PACKAGE => Verifying ZIP signature for package <1641730804>

DOWNLOAD => Package <1641730804> built successfully

DOWNLOAD => Executing action <LAUNCH> for package <1641730804>

PACKAGE => Launching command <bat.cmd> for package <1641730804> on <Monday, January 10, 2022 17:35:28>

in OCS Inventory NG agent for Windows by (160 points)
recategorized by

2 Answers

0 votes

hi 

I solved my problem after dozens of tries. the syntax was bad. I post here for those who are having difficulty

for exe

install.cmd or install.bat >

alzip-8.51.exe /qn /S /sAll /rs /l /msi /qb- /norestart EULA_ACCEPT=YES REMOVE_PREVIOUS=YES DISABLE_ARM_SERVICE_INSTALL=1 UPDATE_MODE=0

------------------------------------------------------------------------

for msi quotes is very very important

install.cmd or install.bat >
msiexec /i "winzip.msi" /quiet
exit 0
-----------------------------
 
by (160 points)
0 votes
Be carefull, if you enter 'exit 0' at the end of a cmd script, you are sure the script end well and the timestamp of package is added to 'history' file ... but this is NOT the result of real command !

Maybe, when you test your cmd script (it's essential to test before deploy), after the msiexec, you can add 'echo %errorlevel%' to look the error code of msiexec command ?
by (3.3k points)
 
Powered by Question2Answer
...