The error message indicates, Port 1717 is not available for use on your machine.
You can Kill the Job Running on the port
netstat -ano | findstr :yourPortNumber
taskkill /PID typeyourPIDhere /F
More about it:
Your installed package metadata is out of date relative to your API version. The activateRSS key is required in InstalledPackage metadata post API version 43.0; see the Metadata API reference.
You can manually add this key to the XML source of the installedPackage-meta.xml files.
Metadata API Settings entities won't ...
Unfortunately, this is not possible. All dependencies must be resolvable to another package member. This is the same basic rules as Managed Packages for the AppExchange. The theory is that these packages must be installable in any org, and must therefore be complete enough to be deployed as such.
The main way around this is to start with a single, massive ...
You have to have a Partner Business Org ("PBO") for this. Please follow the instructions provided by Salesforce here:
... you log a case in the Partner Community to have a Partner Business Org (PBO) provisioned for you.
You'll probably want to talk to them about how to transfer the environment hub to the PBO too, if that is even possible.
The easiest way I’ve found to do this is:
sfdx force:source:retrieve -m CustomObject
If you need it, include the -u option with your target username. This command pulls down all metadata of the type CustomObject. If you want one specific object, add a colon and then the object’s API name:
sfdx force:source:retrieve -m CustomObject:Account
Do you have translations? Sometimes if things get out of sync the translations can throw these errors. If you can, delete out the translations for the object, or at least make sure that they’re all in there.
Specifically, page layouts all get translated, and if the page layout translation is wrong, the whole thing fails to deploy.
Wildcard doesn't work with object in visual studio code for some reason you have to list out each object you want to retrieve in the package.xml file.
Here is an example:
Probably a bit late but better than never.
You can use sfdx force:mdapi:deploy -d data/standard-object-stub/ -w 1 -u $SCRATCH_ORG_ALIAS with a package.xml that references a Case.object file with the following content in a objects subfolder before you deploy your sources
<?xml version="1.0" encoding="UTF-8"?>
I have tried the same with below package.xml in my sandbox and i am able to get the metadata.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
If you have correctly installed VS Code, SFDX CLI and the SF VS Code Extensions then you might just want to try restarting your machine. I have had this same issue occur to me twice on 2 different machines and each time I have only restarted my machine and the issue goes away.
I hope this works for you!
If you're invoking the job via the command line in Windows, then you can specify parameters in the command line. To parameter for Data Access name is dataAccess.name. To learn more, check out the Data Loader Process Configuration Parameters page.
There are 2 different config files. One for the CLI configs (the one you referenced) and one for the scratch org configuration. This last one has a default and is a different file under the config folder called project-scratch-def.json. You can have many files for different scratch org configurations in a single project. When you create a scratch ORG you are ...
The -r or --instanceurl param is just supposed to point to the right endpoint environment. I don't think you can achieve what you're looking for within the CLI command itself.
Official Documentation for auth:web:login doesn't give URL param options as an example, nor suggests that this could be done
-r | --instanceurl INSTANCEURL
- The ...