Originally Posted by till
CReate the database user first with the api and then create the db and assign the db to the database user. If a database user exists already that you want to reuse, then you dont have to create a new one.
Our API scripts were creating the database first, and then the database itself.
Found the problem, we were not passing 'parent_domain_id' into sites_database_add(), as per the API examples.
Once we added 'parent_domain_id', the database would then get created successfully on the remote server.
Interestingly, all our existing databases (pre 22.214.171.124) do not have a 'parent_domain_id' relationship, and we can still update database passwords ok on remote server. Thanks for the backwards compatibility.