Skip to main content

Some common SPFX solution deployment errors like - Component ID {0} exists in solution {1} already

In this article, we are going to learn about some common error we faced while developing and deploying the SPFx solution. There are several mistakes we make while working with the exsisting code, I will be sharing the solution to get rid from those errors.

Error 1 :

When you create a solution and run with the gulp everything seems fine but when you deploy the package to app catalog you see these errors :

Component ID {0} exists in solution {1} already



Component ID {0} exists in solution {1} already. And having some correlation ID


A solution with the same product ID already exists.  Please upload the file with the same name and replace the existing solution


This error stated that you are using the solution with same id which is already deployed at your app catalog. You can change the   Do the steps mentioned below:

1. Go to your solution, Under Config move to package-solution.json file and change the id. You need to replace the guid and you can create new id  using online tools.

2  Now rebuild the solution and build the package again.

3  Upload the package to app catalog and it will work now.

Note : If you are provision list with the SPFx solution and you see this error in that case you also need to change the guid you provide for provisioning list.

Error 2 :

Some time you work with the SPFx solution and you deploy your solution at app catalog very frequently without updating the version and everything seems fine and suddenly, you see this issue at the page where you added the webpart. 

Something went wrong. If the problem persists, contact the site administrator and give them the information in Technical Details. And also contain Unable to load script https://teanant-name/sites/AppCatalog/ClientSideAssets/  in the error description.

Solution : 

1  Go to your solution, Under Config move to package-solution.json file.

2  Change the version of your solution.

3  Rebuild the solution and create new package.

4  Go to your appvcatalog site and delete the exsisiting package from app catalog and also from recycle bin.

5  Upload the latest package and it will work now.

Note: If you follow the steps mentioned above and issue still persist. In that case change the browser and follow same steps.

Error 3:  

When we deploy the sharepoint assets with SPFx solution, we create elements.xml and schema.xml and  if the the format of both the file is not correct we will get the error mentioned below:

Invalid SharePoint App package. Error: Unexpected XML declaration. The XML declaration must be the first node in the document, and no white space characters are allowed to appear before it. 


1 Go to the sharepoint folder in the solution and check the XML files you created.

2 Build the solution and create the package.

3 Deploy it again.

 You can check this blog : How to provision list with SPFx solution

Error 4: 

There were errors when validating the App manifest.: Xml Validation Exception: 'The 'Name' attribute is invalid - The value '-client-side-solution' is invalid according to its datatype


This error stated that the client side solution name is not correct. Client side solution name should not begin with the special character.

1  Go to your solution, Under Config move to package-solution.json file.

2  Change the name of client solution.

3  Rebuild and deploy tha package again.



Popular posts from this blog

How to create list from template in sharepoint

In this article, we are going to learn how to create a list from list template or using(.stp) file or we can say create list from existing list. Once you save the list as a template, It appears into List template option under the web designer gallery on site setting page. Steps to create list from list template: 1 Move to the site setting section where you have saved the list template. 2. When you click on the List templates, you will redirect to the List template gallery and from the list template gallery. 3. Now click on the File in ribbon and click on the upload document. 4. Browse the location where your list template is downloaded. I am uploading the template of an address list. 5.  After browsing the template, now you can give the name what you want to give to the list template and click on save. 6. Now the list template file appears into the list template gallery. Now click on the gear  icon and click on the Add an app. 7. On clicking add an app,

Content editor web part missing in SharePoint/Modern SharePoint.

Media and content editor web part missing in SharePoint online. At Some Point, you need to add content editor web part into the modern site but the content editor web part did not appear on the page, to appear content editor web part on page you need to follow the below steps. 1 Log in as the SharePoint Global Administrator or SharePoint Administrator. 2.  Log in and navigate to your site collection ("") and under the site settings activate the below features.   Site settings – site features – SharePoint Server Publishing .   Site Settings – Site Actions – Manage site features- SharePoint Server Publishing Infrastructure.                For this, you also need to enable Custom site scripts on your site collection(But In Modern SharePoint Its not recommended to enabling custom site scripting)  For this go to the  SharePoint Admin center – Settings -  Classic settings page (option mentioned on page)- Scroll the page you found an optio

Save site as template option in sharepoint online

In this article, we are going to learn about "save site as template option missing in sharepoint". When  you want  to replicate a site that you have already created and to do this you want to save site as template. To save site as template,  you go  on  Site setting   and then   move to  Site  action,   but you did not  find  the option “ Save site as template ” option.    In the modern sharepoint "save site as template" option is not enable by default. There are several option available to enable "save site as template".   Optione 1: Custom script is not allowed  on tenant  : On the new office 365 tenants or we say in Modern SharePoint experience by default the custom scripting is not allowed  on the tenant. If custom script is not allowed on your tenant some features will not work  o n your tenants. In common terms you may not able to  save site as template , options to create web part page will not appear on, some web parts  ( like media and