Hi.

I have created a package that runs a .cmd file to deploy an .exe file silently (with a response file)

When i deploy it, the application installs successfully to the target machine, however in 'Software Centre' it just says 'Installing' as if its still installing and eventually says 'Failed' with 'Error: 0x103(259)'

Do i need to send something back to SCCM to say the application has installed successfully? i.e. something in the .cmd file? Or does this error relate to something else?

Cheers

Neil

The return code of the batch is returned to ConfigMgr so no special considerations here. What's the content of the cmd?

This seems to be a common issue with Autocad and Autodesk, where the application returns that code but appears to be successfully installed. If you're sure it's installed properly you can configure SCCM to interpret 259 as success, but it's probably worth looking at the installation log files for the program to really make sure.

Reference: https://social.technet.microsoft.com/Forums/systemcenter/en-US/fbccc114-3605-4363-b983-b2f7b02fe266/program-exit-code-259-in-sccm-cllient

Also, why would you use a batch file for this instead of just putting the proper command-line in the program?

Hi

Content of the .cmd file is:

saw-install.exe -silent W:\Treasury\Software\SWIFT\Swift_Standards_2014\win32\silent.properties.install.saw

Hi - i tried just using the code form my .cmd file "saw-install.exe -silent W:\Treasury\Software\SWIFT\Swift_Standards_2014\win32\silent.properties.install.saw" direct in the command line, but i was getting a different error "0x87D01201(-2016407039)"

Error 259 generally mean the installed timed out.

Part of you problem is you are pointing to a mapped drive that doesn't exist under the system account. include the answer file with the source files and it should work better.

0x87D01201 = "The content download cannot be performed because there is not enough available space in cache or the disk is full."

That error had nothing to do with using a cmd or not.

What's the W drive? Are you running the program as the local user? If not, the W drive is most likely not valid as the program will run as local System which can't see drivers mapped by other users.

hi - instead of using the cmd file i just used the command in the Package and it installed correctly - thanks for your help on this

• Marked as answer by NeilVMo 17 hours 52 minutes ago