Error message when creating package with ocspackager 2.1.0.1

Hi,

I have the same problem with the same versions of OcsPackager2.1.0.1.exe and OCS-NG-Windows-Agent-Setup.exe (2.1.0.1)". I'm also running Windows 7 (Pro Service pack 1, 64bit). I haven't tried on any other computers.

I would also like to add that I'm not clear on the "Command Line Options" as there seems to be an error in the documentation for the "/server" command line switch.

On the web page http://wiki.ocsinventory-ng.org/index.php/Tools:Packager the example is:
 " On “Command line options” line you should enter all the needed options for the Ocs Agent setup program (e.g. /server:my_server /pnum:8081 /S). Do not forget to specify the /S option for a silent installation. "

On the Web page http://wiki.ocsinventory-ng.org/index.php/Documentation:Administration#Uploading_Agent_for_deployment_through_launcher_.E2.80.9COcsLogon.exe.E2.80.9D.
 the details are:
"/SERVER=IP_ADDRESS Use Communication Server address “IP_ADDRESS” "

I have tried /server: and /SERVER= . I have tried IP and URL of my server thinking that the error may be in some way related to an incorrect command switch.

Further to what my situation;

I'm not using a Certificate file, I am not using any plugins, Command line is /SERVER=my_severs_IP /S (and the various server variants I mentioned), my domains login and password, PsExec.exe from package: 2.44. I have tried saving in network locations and local to the PC. The OCS exe files are located on a network file share and I an executing them from there.

Thanks in advance.

Paul

Hello,

We seem to encounter the exact same issue in our company.
We tried launching the packager as admin both under Seven and XP, nothing does the trick.

Despite of the error a package is created but once installed on a computer it doesn't seem to upload any inventory result to the communication server...

Will keep on trying,

Regards,

Sam

Hi.

Could you please try the attached packager version 2.1.0.2 ?

If you encounter error building package, could paste here packager detail log (right click on detail listbox, and select "copy detail to clipboard) ?

If you encounter error while running created package, could you paste here ocspackage.log file created into user's temp directory ?

Regards

Hi Didier and thanks for your help.

I still had the same problem using the 2.1.0.2 packager.

See the attached packager log.

Best regards.

Hi Neutro,

Ok, find the problem. There where an error flag not cleared before copying resulting package to destintaion folder.

Could you try attached version 2.1.0.3 ?

Regards

Didier,

Problem solved with 2.1.0.3.

Thank you very much!

Regards.

I am having the same problem using packager 2.1RC1 and the one that dliroulet posted above but continue to get the same error. This is the log file:

Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp
Using file <C:\Download\OCS\Packager\Unzipped\OCSNG-Windows-Packager-2.1RC1\OCS-NG-Windows-Agent-Setup.exe> as OCS Inventory NG Agent Setup file
OCS Inventory NG Agent for Windows version is <2.1.0.3>
Using < /S /NOSPLASH /SERVER=http://hades.cts.cwu.edu/ocsinventory> as OCS Inventory NG Agent setup command line options
Using <$PROGRAMFILES\OCS Inventory Agent> as OCS Inventory NG Agent installation Folder
Using <$APPDATA\OCS Inventory NG\Agent> as OCS Inventory NG agent data folder
Using <> as certificate file to include
Create folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\OcsData
Copy failed
Using <> as Label text
Not using Microsoft SysInternals PsExec.exe tool
Create folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\OcsPlugins
Extracting NSIS compiler
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS
Extract: COPYING... 100%
Extract: NSIS.chm... 100%
Extract: NSIS.chw... 100%
Extract: NSIS.exe... 100%
Extract: makensis.exe... 100%
Extract: makensisw.exe... 100%
Extract: nsisconf.nsh... 100%
Extract: uninst-nsis.exe... 100%
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS\Bin
Extract: GenPat.exe... 100%
Extract: LibraryLocal.exe... 100%
Extract: MakeLangId.exe... 100%
Extract: RegTool.bin... 100%
Extract: zip2exe.exe... 100%
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS\Contrib
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS\Contrib\Graphics
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS\Contrib\Graphics\Checks
Extract: big.bmp... 100%
Extract: classic-cross.bmp... 100%
Extract: classic.bmp... 100%
Extract: colorful.bmp... 100%
Extract: grey-cross.bmp... 100%
Extract: grey.bmp... 100%
Extract: modern.bmp... 100%
Extract: red-round.bmp... 100%
Extract: red.bmp... 100%
Extract: simple-round.bmp... 100%
Extract: simple-round2.bmp... 100%
Extract: simple.bmp... 100%
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS\Contrib\Graphics\Header
Extract: nsis-r.bmp... 100%
Extract: nsis.bmp... 100%
Extract: orange-nsis.bmp... 100%
Extract: orange-r-nsis.bmp... 100%
Extract: orange-r.bmp... 100%
Extract: orange-uninstall-nsis.bmp... 100%
Extract: orange-uninstall-r-nsis.bmp... 100%
Extract: orange-uninstall-r.bmp... 100%
Extract: orange-uninstall.bmp... 100%
Extract: orange.bmp... 100%
Extract: win.bmp... 100%
Output folder: C:\Users\PruittJ\AppData\Local\Temp\nsoB31F.tmp\NSIS\Contrib\Graphics\Icons
Extract: arrow-install.ico... 100%
Extract: arrow-uninstall.ico... 100%
Extract: arrow2-install.ico... 100%
Extract: arrow2-uninstall.ico... 100%
Extract: box-install.ico... 100%
Extract: box-uninstall.ico... 100%
Extract: classic-install.ico... 100%
Extract: classic-uninstall.ico... 100%
Extract: llama-blue.ico... 100%
Extract: llama-grey.ico... 100%
Extract: modern-install-blue-full.ico... 100%
Extract: modern-install-blue.ico... 100%
Extract: modern-install-colorful.ico... 100%
Extract: modern-install-full.ico.....

I'm using 2.1RC1 and Agent Packager 2.1.0.3 and am having this problem "Error writing All-In-One Installer package into folder".

I've tried with older versions of the client and the problem persists.

I really need to make a packager.

Fixed in rev 224.

Copy always success, but sometimes, success check returns failed.

Included in 2.1.1 release