Yep. Those being unset will definitely cause the error you are seeing.  ... View more

You don't say how they're trying to create the Cube (hoping you mean register) - but my hunch is you're missing write member metadata on the parent folder or write metadata on the Schema.   http://support.sas.com/documentation/cdl/en/bisecag/67045/HTML/default/viewer.htm#n0bxpw0fyk4srkn1xp0yhc2gvq4g.htm     ... View more

Start with http://support.sas.com/rnd/migration/utility/upgrade.html#from93   and the linked docs. The specific instructions for running the SMU are covered in the 'Create the Migration Package' section of the 'Performing Pre-migration Tasks' chapter.  ... View more

Is the agent running successfully on the compute tier? Look in Web\SASEnvironmentManager\agent-5.8.0-EE\log\agent.log for additional information ... View more

If you had a foundation services directory, but not foundaiton, I'd be suspicious this server was configured as a middle-tier machine - not a compute or standalone foundation install. Verify the plan file (and machine of the plan being selected) matches the software you expect to be laid down. If this is a multi-server environment, it could be you need to connect to a different machine to see SASFoundation, it isn't installed on every server in the topology.  ... View more

Are you launching setup.exe with the additional 'Run as Admninistrator' option? If you're launching it from a command line window, be sure that cmd.exe was launched with 'Run as administrator'. Even if you're an admin on the box, Program Files is treated specially and you cannot write there without manually elevating permissions for the process attempting to perform the write. The easiest thing may be to just point -responsefile somewhere else, the location is unimportant, just so long as it's accessible, and is where you point -responsefile to when you're trying to replay the deployment.   It sounds like you're following along with "Automating the SAS Installation on Multiple Machines"  from the  SAS(R) 9.4 Intelligence Platform: Installation and Configuration Guide http://support.sas.com/documentation/cdl/en/biig/69172/HTML/default/viewer.htm#n05023intelplatform00install.htm Which should be all you need.  ... View more

On your second machine, are you pointing to a shared output location, the smu package output copied from the metadata server SMU run or a blank output directory? You'll see an error like this when the SMU detects no metadata server present in the SMU output location, and the current machine isn't the metadata server.    From the Appendix 1 of the guide Mark linked:   "On SAS multiple-machine deployments, the migration utility must be able to write to (and read from) its output directory. We recommend that the utility output directory be on shared network storage accessible to every SAS machine in the deployment."   And from the smu.properties.template   # The migration package output directory. It will be # created if this is being run against the metadata server # tier. Otherwise, it should already contain the results # from your metadata server tier run and any other upstream # tiers. The results from every tier of your deployment # should be included in the same migration package. ... View more