TRUE Vanilla 10.9.2 & Composer 8.73

A co-worker and I just looked into this.. thankfully he's smarter than me. But here's what we found...

In Mavericks there appears to be an error/bug/feature in Mavericks that disallows the creation of a disk image using hdiutil in the methodology that JAMF uses with Composer if the DMG is over a certain size. Either 100MB or 128MB?

We were trying to create a DMG with Acrobat Reader that included some 'yes I have read the licenses etc' pieces and use it to apply to all users (hence the DMG), so I REALLY don't want it to be a .PKG. But the DMG process kept failing over and over with the same error.. the hdiutil error above, which ultimately was actually "error -5341". So in googling around, we came across an indication that it may be a default size issue. The command that Composer uses to create the DMG is akin to:

hdiutil create /Path/to/Desitnation.dmg -srcfolder /Library/Application Support/JAMF/Composer/Sources/Source-of-DMG/ROOT -volname Destination -gid 20 -mode 755 -puppetstrings -format UDZ0

And this fails.. theoretically because the source material is too large to squeeze into a 100+MB DMG (it's like 320MB).
After some fiddling and testing with formats and other parameters, we tried the above with a slight adjustment:

hdiutil create /Path/to/Desitnation.dmg -srcfolder /Library/Application Support/JAMF/Composer/Sources/Source-of-DMG/ROOT -volname Destination -gid 20 -mode 755 -puppetstrings -format UDZ0 **-megabytes 330**

Voila.. it worked. Disk Image created. As a control, he tried creating the same DMG using the Disk Utility.app (e.g., pointing it at the source folder that was failing and asking it to make a compressed image) and it also failed with the same/similar error 'Unable to create "ROOT." (error -5341)'.

Like I said.. thankfully he's smarter than I am. So, not a fix per se.. but something to lead us in a different direction.

I tried this for a wacom driver, and it returned hdiutil: create failed - function not implemented.
not much on google for that one.
I tried -megabytes 128 (folder is only 109mb) and 330, neither worked.

Trying Composer 9.3 and 10.9.2 - with bare metal wipe and reload.

I used a different 10.9.2 machine. Worked fine.

I'm getting a similar error when trying to use Composer to 'Convert to Source' a .mpkg file to create an installable package:

Command failed with error code (1): '/usr/sbin/installer'

Would this be related?

Was having this issue today trying to make a chrome.dmg. Using the pre-installed software option for Composer. After looking through this and some other threads and still getting errors even running hdiutil from terminal I decided to check hdiutil and noticed it was set as group > wheel. Decided to run it was root to test my hypothesis and sure enough root ran it w/o any error 5341.

So I went and added administrator to wheel group, reopened Composer and created the dmg without any error. Seems that only members of wheel can run /usr/bin/hdiutil

Runs fine for me, no errors. I'm logged in as a non-admin user on a test Mac running 10.9.2 (13C0121), latest Chrome, Composer version 9.31.

Don

Something really odd here (10.9.4, Composer 8.73, no antivirus):
I get the above error when trying to compose Swedish Firefox 30.0 as FEU, but not when doing the same with English FEU. Same naming convention ("Firefox_sv_install"/"Firefox_en_install"). So far, I've only managed to repeat it with these two programs, tried it on 2 computers, even reformatted one after it failed and had the same problems after a complete reinstall. This is nuts!
Tried it both as admin & non-admin as well. The difference in size is that the swedish version is about 1.5 MB bigger (149.2 vs 147.7 MB). But I tried a 190 MB app and that didn't give me the error.

Any suggestions?

//Martin

I've managed to clear up all the packaging issues I had by exempting the /Library/Application Support/JAMF folder from our antivirus scans.

Hi Franton!
Not running any antivirus on computers used for packaging, though... And I had the same problem on a completely virgin install of 10.9.4. I tried composing on a virtual 10.8.5 and that worked just dandy with the same Firefox...

I'm guessing everyone tried logging in as a local user (not an AD or OD user) when making the package?

@donmontalvo yes. I tried it on a computer with just an admin account, no imported settings, vanilla 10.9.4 installation, no binds whatsoever - US English firefox works, Swedish doesn't. Really odd quirk I must say.

I had this issue with Pep8. It's just a .app file in Applications too. Must be something within the app contents making it freak out? Maybe special char or file format or something within? All other software with composer has been fine. I was racking my brain over it for hours lol. pkg file worked but not dmg

anyone still dealing with this?

I'm having this problem with an adobe cs6 package using composer 9.65

Not using any antivirus, it's a fresh install of 10.9.5

edit: for what it's worth, UDZO is with an O, not a zer0... D:

Seems that using hdiutil on my own works. Didn't need to specify MB. Just ran

hdiutil create /path/of/wat.dmg -srcfolder /Library/Application Support/JAMF/Composer/Sources/sourc-of-wat.dmg/ROOT -gid 20 -mode 755 -puppetstrings -format UDZO

Just ran across this myself for the first time today while trying to make a DMG from a folder using Disk Utility (first time since upgrading to Yosemite). Using the -size option with hdiutil worked for me. Creating a .Trash folder as suggested elsewhere did not. Has anyone filed a bug report with Apple?

I've run into this issue when trying to make a '.dmg' of any Adobe suite products. I mean, the whole thing at once...not just an individual app from within the suite. I've made .dmg packages for CS6, Creative Cloud 2013, Creative Cloud 2014, & now, Creative Cloud 2015. These '.dmg's have been in the 11 - 14 GB range....and Composer fails every time...at the very end....with the exact same error code 1 from hdutil.

So, the 'hdutil error code 1' has been a part of Composer since I started working with JAMF software (8.6 series) and this has never been fixed to date and I'm currently on version 9.65 getting ready to go to 9.73. I had called for assistance in the past on this and the JAMF techs told me 'We have no way of testing this'...I'm thinking ...um...'30-day trial' ??? You can get the whole thing and see just how many apps there are and how big the suite is. On top of that...they want to schedule my time on the phone to work on my machines to do their tech support work. What? I'm wearing 3 hats at my job and don't have time to do more of 'other peoples work'....Especially JAMF's tech support work. Crazy.

The solution I've found is slightly creative but straight forward and works like a charm 'every' time. ....unlike this crazy JAMF Composer stuff....and the Non support on this front by JAMF techs or development.

Solution = Gui version of Apple's Disk Utility. That little item under the 'File' menu that says 'Disk Image from Folder'... Yeah, it's nice AND it works... You have to make an adjustment of directory/folder names...but it goes like this:

1) Open JAMF Composer and go through the initial process of 'New' then 'New & Modified Snapshot'...give it the Name you want(you'll need this info later)...let's call it--> 'YourPackageName' ...Let the Snapshot finish.

2) Go through the process of installing the Adobe suite of whatever you got. We have an Enterprise account here at the University and we use the 'Creative Cloud Packager' to make 'licensed' installers. Be sure to make any and all adjustments you need plus testing...including reboots if you have to. I found I had to hack this 'Creative Cloud App' install dialog that would come up every time you opened Adobe InCopy CC 2015. Once I dealt with that I was golden as far as 'user' dialogs are concerned.

3) In Composer...click the button 'Create Package Source'. Let it do it's thing...once that finishes go ahead and check the directories it has included and make sure you only have the things you want/need. From here...you're done with Composer...so go ahead and quit. If you try to 'Build as DMG' at this point...enter the 'hdutil error code 1'.

4) Navigate to the Composer created directories for the package: /Library/Application Support/JAMF/Composer/Sources/'YourPackageName'/ROOT/'YourPackageDirectoryListHere'
...what I do is to trade/swap folder names of ROOT & 'YourPackageName' ...looks like this:
...Composer/Sources/ROOT/'YourPackageName'/'YourPackageDirectoryListHere' ....with me?

5) Use the GUI version of Apple's Disk Utility: File-->New-->Disk Image from Folder ....in the dialog navigate to the 'YourPackageName' folder....click the 'Image' button. Let it finish. Voila. Drop that thing into JAMF Casper Admin and on up to your server. From here it's up to you if you want to 'Index' it. Takes quite a while to do that...but is handy if you need to 'uninstall' it later.

That's it. I've included a screen shot of my work. Yeah, it took '11' tries to get it right with CC2015...& only '5' tries with CC2014. It's been a real journey with Adobe & JAMF on this for sure!

Enjoy, ~Patrick

I've just had this same error today from Composer 10.0.0 running on macOS High Sierra 10.13.1.

The package was a simple one. Single file in a DMG which is called 'iPhone10,4_11.1.2_15B202_Restore.ipsw'

It turned out that the issue was the comma (,) in the file that I was dragging in to the sources in composer, which is then the name that composer tries to give the DMG. Removed the comma and everything works fine.

It's amazing to realise the value of the history. It's 2019 and suddenly I'm seeing this exact problem.

Thanks to everyone's contribution, it was relatively easy to figure out my cause was from the Microsoft Defender real-time protection scan. After disabling it temporarily, Composer was able to create the dmg just fine.

Same here on Catalina (10.15.1) using Composer 10.16.1. Sophos Antivirus was the problem

Yep, I'm also suddenly seeing this on Trend AV as well for some reason.

Hello.

Same issue with McAfee and Composer 10.26

I've had to just disable real time scanning on any device with Trend as it often stops composer from working.