correction: i didn&#39;t adequately test what happens if the user_proj_map_db was not defined in the universe file; here&#39;s the changes:<div><div><br></div><div><div>157         # BEGIN ADD USER&#39;S PROJ</div><div>158         try:</div>

<div>159             conn = sqlite3.connect(self.app.config.user_proj_map_db)</div><div>160             c = conn.cursor()</div><div>161             c.execute(&#39;SELECT PROJ FROM USER_PROJ WHERE GID=?&#39;, [job_wrapper.user_id])</div>

<div>162             row = c.fetchone()</div><div>163             c.close</div><div>164             native_spec += &#39; -P &#39; + row[0]</div><div>165         except:</div><div>166                 log.debug(&quot;Cannot look up proj of user %s&quot; % job_wrapper.user_id)</div>

<div>167         # /END ADD USER PROJ</div><div><br></div><div>also, in the config, define a default instead of using None:</div><div>        self.user_proj_map_db = resolve_path( kwargs.get( &quot;user_proj_map_db&quot;, &quot;database/user_proj_map.sqlite&quot; ), self.root )</div>

<div><br></div></div></div><div>one last note: there doesn&#39;t seem to be any error displayed to the user if the job cannot be scheduled because the galaxy user doesn&#39;t have permissions to use the user&#39;s project (although there is a log entry), but the job will never be scheduled.  so be sure the galaxy user has permissions to submit to all possible projects.</div>