Hmm, based on that error, it looks like the script is having a problem with line 149, the launchctl command to load the AppleFileServer daemon-
/bin/launchctl load /System/Library/LaunchDaemons/com.apple.AppleFileServer.plist;;
I tried the same command by itself in Terminal on my 10.7 machine and also got the "nothing found to load" error. In looking at the actual plist, I'm not sure what the issue might be
Edit: Taking another look, it seems if you add the force flag, -F to the launchctl command, it appears to work. In other words, change that line 149 to read:
/bin/launchctl load -F /System/Library/LaunchDaemons/com.apple.AppleFileServer.plist;;
After doing this, running:
sudo launchctl list | grep AppleFileServer
returns-
- 0 com.apple.AppleFileServer
Prior to that, the same command returned nothing.
II don't have a setup where I can verify if the services are properly enabled, so I would test this out, see if its actually turning it on, and test thoroughly before trying to push it to anything. I don't know that using the force flag is really a recommended way to do it, but at first glance it does seem to override whatever is keeping the process from starting up.