Showing posts with label Errors. Show all posts
Showing posts with label Errors. Show all posts

Saturday, December 24, 2016

Your web part will not appear in the toolbox - Office 365

Your web part will not appear in the toolbox - Office 365

You get below error when you try to load the webpart in the Office 365 workbench (for the first time in the workbench.aspx) after you perform "gulp serve"

----------------------------------
Your web part will not appear in the toolbox. Please make sure "gulp serve" is running in a web part project. Please refresh the page once "gulp serve" is running.
--------------------------------

To resolve this error, you will be to first run the below command to install the certificate (note that the certification error in the local workbench also disappears after this)

gulp trust-dev-cert

After this, you can run gulp serve to again see the local workbench and then launch the office 365 tenant site to see if your locally developed webpart is available to be added on the workbench.aspx

Wednesday, July 24, 2013

Increasing the file upload maximum size

Increasing the file upload maximum size

I was not able upload a document of size more than 50 MB. It was giving document upload with status as failed.

This is because of the default configuration of 50MB for the corresponding web application in the SharePoint central administration website.

To increase the default file upload maximum size, follow the below steps.

1) Goto -> Central Administration
2) click on “Manage Web Applications”
3) Select (single click on the row) desired web application
4) Click on “General Settings” in the ribbon
5) Under "Maximum Upload Size", change the setting to the desired value (e.g. 100 MB in our example)
6) “OK”

If you are running IIS 7, follow the below KB article
http://support.microsoft.com/kb/944981/en-us


Service Unavailable

While browsing the SharePoint web application, I got the below error.

Service Unavailable

The possible reasons why this error occurs are 

1) Your application pool for the corresponding SharePoint web application is down  (is not in running state)
2) You might have changed your application pool identity password.

Cannot connect to configuration database

While opening the SharePoint web application I received the below error.

Cannot connect to configuration database

The possible reasons for this error are 
1) You might have changed the application pool identity password.
2) The SQL server instance fro SharePoint is not in "running" state.
3) There is some network issue connecting to the SQL server database.