Quote Originally Posted by linder View Post
Hello,

please see the attached screenshot. You only have to use SB10.EXE /C to start the command line compiler from the Windows CMD prompt. You can change the compiler.txt log file location to see what is going wrong.

Does this help?

Friedrich
No sir. Already done that...
Current command line being used is:
>> SB10.EXE /c "C:\Projects\BuildServer\SetupBuilderInstallers\EN ERCALCForRevitSetup.sbp" /LX "C:\Temp" /CV PRODUCTVER "1.2022.10.16" <<


And SB10.exe location is in the path environment variable, and SB10 reports it was called in the command shell text, but nothing else happens. No errors, no logfile, and no output.