"Save site as template" Missing in MOSS 2007

Issue:

Sometime "Save site as template" link may be missed in MOSS 2007. 

Solution:

Usually this link will be available in the "Site Actions" --> "Site Settings" area. This may be missed sometimes, if you upgrade your team site into "Publishing Site". (i.e. If you forced to convert as a publishing site through the STSADM command). Then, How can we save the site template?

Still there is an answer. Just type the below command in browser after the site name & port (without quotes).

"/_layouts/savetmpl.aspx"

For example:

http://172.16.10.10:5002/_layouts/savetmpl.aspx

Later, you can download this template from "Site Template Gallery" (under Site Actions --> Site Settings). 

For Example:

http://172.16.10.10:5002/_catalogs/wt/Forms/Common.aspx

Thats it...

Error: Some or all identity references could not be translated

Error:

Some or all identity references could not be translated.

Reason:

You will get this error, when you migrate your server domain from one to another. Coz, your farm administrator domain also will be changed.

Solution:

1. Go to command prompt.

2. Navigate to STSADM tool folder.

3. type the below command

stsadm.exe -o updatefarmcredentials -userlogin "NewDomain\Admin" -password "Password"

4. Reset the IIS.

Thats it...

Error: Content deployment job '<Job Name truncated>' failed.The remote upload Web request failed

Error: 

Content deployment job '<Job Name truncated>' failed.The remote upload Web request failed

Reason:

You will get this error, when you are trying to deploy the content from one sharepoint server to another. You will get this 

error, because the destination server name/IP may not be resolved by the deployment job.

Solution:

1. Go to your destination server desktop.

2. Right click on the "My Computer"

3. Click on "Properties"

4. Go to "Computer Name" tab.

5. Copy the Full Computer Name as shown below:

6. Open your host file from "c:\windows\system32\drivers\etc\hosts" in NotePad. (In Source Server)

7. Paste the Server name along with IP address at last as below: (Do not delete/move other texts)

8. Now run the content deployment.

Thats it.

SharePoint: Custom validator or InputFormCustomValidator, Which one is best?

In some scenarios, you are in a situation to use "CustomValidtors" in your SharePoint WebPart coding (object model). This is very common situation to handle/validate our webpart controls using default validation controls.  

But, in SharePoint object model, "CustomValidator" won't fire perfectly in most of the scenarios. Then what to do?

Microsoft Provides an another control called "InputFormCustomValidator". Just explore all the features by using this control. Some of the key points are:

1. For InputFormCustomValidator, we need not to assign the "ControlToValidate" property.

2. We can enforce the "Page.Validate();" method on button click method.

Error: The protocol handler cannot be found. Check that the handler has been installed.

Scenario:

You will get this error, when you are trying to "Crawl" the content in SharePoint SSP.

Solution

1. Go to Services in the SharePoint server (type "Services.msc" in command prompt and preses  'Enter')

2. Stop the "SharePoint SHarePoint server search", "Windows SharePoint Services Search" & "Windows SharePoint Services" Timer.

                   

3. Start all the 3 services again.

4. Reset the IIS

Thats it...

Error: The form submission cannot be processed because it exceeded the maximum length allowed by the Web.

Error:

The form submission cannot be processed because it exceeded the maximum length allowed by the Web.

Reason:

Whenever you are trying to upload a file into the SharePoint with more than 50MB, you will get this error. 

You can not fix this issues, even if you updated the tag in web.config file.

Solution:

1. Go to Central Admin

2. Open "Web Application Gegenal settings" link

3. There is an option to enter the maximum file size. type 100 MB in that text box. Don't forget to change the web application in the dropdown box.

4. Also, change the HttpRuntime in the web.config as follows:

 <httpruntime maxrequestlength="102400" executiontimeout="3600"></httpruntime>

 

Thats it...

Error: The application is unable to accept further updates because the last attempt to persist the state failed. See the event log for more details

Error:

The application is unable to accept further updates because the last attempt to persist the state failed. See the event log for more details

Solution:

Sometimes you will get this error, when you configure the search in sharepoint server. Do the below steps, one by one.

1.  Go to central admin 

2. Go to Operations Tab.

3. Click on "Services on Server" link and Stop the "Office Sharepoint Server Search"

4. Again, start the "Office Sharepoint Server Search".

5. Go to SSP & Search Settings.

6. Here you have to configure again the search settings. 

7. Then, It will take few minutes to complete teh operation. (based on the Timer execution).

Thats it...