The SharePoint Health Analyzer detected an error. One or more services have started or stopped unexpectedly

Problem Description:

The SharePoint Health Analyzer detected an error. One or more services have started or stopped unexpectedly.

Error Message:

The following services are managed by SharePoint, but their running state does not match what SharePoint expects: SPAdminV4. This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface. If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.

SharePoint was unable to automatically repair this error.

To stop or start a service managed by SharePoint, use the SharePoint service management interface in the SharePoint Central Administration Site. If a service has crashed, restart the service manually on the affected servers by running "net start [service name]" from a command prompt. For more information about this rule, see http://go.microsoft.com/fwlink/?LinkID=142683.

Checkpoints:

- All services are running fine.

- All SharePoint sites as well as web applications are running without any issues.

Reason:

Basically it’s a clear cut indication that the one of the required service is un-reachable.

Resolutions you can try as there are multiple things by which we can resolve this issue:

- Check the administration service is running or not in services console. if its stopped/disable then please restart it.

- try to reboot the server and check the results again.

- try restarting the services by using command prompt

- after the above things and if you are still facing the problem then please check the SP logs and surely you will find the  exact error which will tell you the root cause behind it.

If you have any issues/queries regarding the above mentioned information then please let me know, Thank you

Product applies to:

- SP2010

- SP2013

- SharePoint Foundation 2010

List tools tab was missing after Migration from 2007 to 2010

Hi some after Migration issues discussed . 

Issue : List tools tab was missing after Migration from 2007 to 2010

We found today that one of the User had a site collection with 5 lists . When he clicks on the first list the List tools tab at the top is available . 

However for one of the Lists we don't see the Tab . Thought the list has gone corrupt and was about to create a new list with the Template and move the contents .

But then while troubleshooting we found that if we click on one Item we see the List tools tab . Ahhhh But that is not a resolution . why is it working for others ?. 

It also looked like the permissions were gone but that was wrong. Permissions were correctly set and the user was logged on as an site collection admin.

Then some how we found the solution . 

Resolution : The user had added edited the page when they were on 2007 and added a Content Editor web part without any text on the top of the list as a web part 

Deleted the web part and there you go got the List tools back

SharePoint 2013 Build Numbers

This will come very handy while installing and troubleshooting 2013

Build Number	Build Name	Component	Information Link	Download Link	Notes
15.0.4128.1014	Beta	SharePoint Foundation 2013		Download	Bugs, Notes, & Regressions
15.0.4128.1014	Beta	SharePoint Server 2013		Download
15.0.4128.1014	Beta	Project Server 2013		Download
​	​	​	​	​	​
​15.0.4420.1017	​RTM	​​SharePoint Foundation 2013	​	​Download	​ Bugs, Notes, & Regressions
​​15.0.4420.1017	​RTM	​SharePoint Server 2013	​	​Download	​
​​15.0.4420.1017	​RTM	​Project Server 2013	​	​Download	​
​	​	​	​	​	​
​15.0.4433.1506	​December 2012 Hotfix	​SharePoint Server 2013	​KB2752058	​Download	​ Bugs, Notes, & Regressions
​15.0.4433.1506	​December 2012 Hotfix	​SharePoint Server 2013 (coreserver)	​KB2752001	​Download	​

Courtesy - http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=346

You can’t delete a site that has subsites

Cannot Delete Subsite

Error deleting a website “/Teamsite/SP2010”. You can’t delete a site that has subsites

If you are facing this error message then there are multiple ways to delete it. Let’s look at those details and let me know in case of any queries/doubts based on the same.

-Subsite console

-Site collection console

-SPD 2010

-STSADM utility

-PowerShell utility

-Content and structure

Imp Note:

-You need to make sure that which subsite you are trying to delete and

-How many nested subsites are present underneath?

-Logged in account that you are using to delete that subsite

-Make sure you don't have any meeting workspaces on your site

Let’s look into each category by exploring thoroughly:

Subsite Console:

-Login to SharePoint site with administrator account.

-Click "Team Site" on the top of the "Admin" Page.

-Navigate to the subsite you prefer to delete.

-Click "Site Actions", and then click "Site Settings".

-Click “Delete this site” under "Site Actions".

-Click "Delete" Button, and then click "OK" to confirm.

Site Collection Console:

-Login to the SharePoint site collection with admin account

-Site actions

-Site settings

-Site administration

-Sites and workspaces

-You will see a list of subsites which are present underneath the site collection

-In the right hand side, you will find the option of delete

-Click on delete and it will ask you to confirm the details

-Click OK

-That’s it and you are done.

SharePoint Designer 2010 Console:

-Click start

-All programs

-Microsoft Office SharePoint Designer 2010

-File

-Open site

-Enter the site collection URL

-Once the site will be open then you will see the complete hierarchy

-You will see a separate section named as “Subsites”

-Click on it and you will see the number of subsites in the right hand side

-Right click on the subsite that you want to delete

-Click OK and you are done.

Content and structure:

-Site Actions -> Site Settings

-Site Administration: Content and Structure

-In the left column, move to the parent of the main site to be deleted

-In the right column, choose the site to be deleted (Your Site in our example)

-Menu: Actions -> Delete

-Note: Deleting the selected sites will permanently delete all content and user information. All subsites in this site will also be permanently lost. Do you want to continue? Click OK.

STSADM Utility:

stsadm -o deleteweb

   -url <URL name>

For deleting a site within an orphaned site collection or an orphaned site within a site collection:

   -force

   -webid <Web ID>

   -databasename <database name>

   -databaseserver <database server name>

POWERSHELL Utility:

Remove-SPWeb "http://ursite/" -Confirm:$false

Reference:

http://technet.microsoft.com/en-us/library/cc262877(v=office.12).aspx

http://technet.microsoft.com/en-us/library/cc288016(office.12).aspx

 

If you have any queries/questions regarding the above mentioned information then please let me know. 

I would be more than happy to help you as well as resolves your issues…

Thank you.

Workflows are not available after we upgrade from 2007 to 2010 using database attach method

This is a very critical issue that most of the users have faced after the migration from SharePoint 2007 to 2010

After upgrading the SharePoint 2007 Database via database attach method to SharePoint 2010, You might find that the 2007 Approval workflows are no longer available for users to create new workflows.

In SharePoint 2010 the 2007 workflows are there to allow any running workflows to complete, but by default creating new instances of the workflows is disabled as the expectations are that you will want to move forward to the SharePoint 2010 workflows.

Resolution

The following steps must be taken to enable 2007 workflows after upgrading to SharePoint 2010:

·         Go to Site Actions ->Site Settings->Site Collection Administration->Site collection features

·         Activate SharePoint 2007 Workflows 

·         Remove ‘none’ from none

·         14-templatefeaturesReviewWorkflowsReviewapproval.xml

·        
14-templatefeaturesReviewWorkflowsReviewFeedback.xml

·        
 14-templatefeaturesSignatureWorkflowSignatures.xml

·        
 Associate Workflow

·         Go to Shared Documents, Library Settings, Add a Workflow

·        
 Select legacy Workflow.

Note: Please take a back up of Reviewapproval.xml,ReviewFeedback.xml,Signatures.xml before doing the modification, the above solution is not verfied after we install any new update. chances are there that these files might get replaced in future update. please have a backup of working files as well.

Reference -

http://blogs.technet.com/b/vinitt/archive/2011/02/23/moss-2007-workflows-no-longer-available-visible-when-we-upgrade-from-2007-to-2010-database-attach-method.aspx

Code Blocks are not allowed in this file error in sharepoint 2010

Hello Everybody,

Today I worked on one critical issue which belongs to our development environment. We have migrated one web application from production environment to development for testing purpose. Migration has been successful but we were facing an exception while browsing the web application.

Error Message:

An error occurred during the processing.

Code blocks are not allowed

Troubleshoot issues with Microsoft SharePoint Foundation.

Server Configuration:

·         2 SharePoint Servers

·         SQL server 2008 R 2

·         Windows Server 2008 R2

·         SharePoint Version: SP2010

Troubleshooting done:

1.    Tried accessing the system pages i.e. settings.aspx, viewlsts.aspx etc. every system was opening fine without any issues. So the issue is with the home page only…

2.    Tried accessing the web part maintenance page, it opened without any issues. We closed the webparts which are present on the home page-just to make sure that there is no problem with the existing webparts. Checked the home page again but same issue.

3.    Tried changing the master page as were able to open the system pages (by appending _layouts/changesitemasterpage.aspx). We changed to different one as we are using custom master page. Checked the results again but same problem.

4.    Opened the site in SharePoint Designer 2010 and checked the status of master page as well as the home page. It was fine and without customization too.

Note: if you see any of these pages in customizable state then I would suggest you to take the backup and try ‘reset to site definition” option.

Obviously, next question will arise- what exactly it will do? Yes, it will reset your page to default state. It means you will lose your customizations. But issue will be resolved and you can customize the page again as per your requirements.

5.    Checked the windows application as well as SP logs (Location: \14\Logs). I would suggest you to analyze these logs before continuing your troubleshooting.

What is my observation\Understanding?

·         Code blocks are only processed for custom pages deployed in the root virtual directory of a site if the code it considered safe.

·         This code is considered safe only if the page is served directly from the file system. As soon as it becomes unghosted for any reason, the code is no longer considered safe and the error shown in the symptom occurs.

Resolution:

As our production web application was working without any issues so I compared the web.config of both the applications. Analyze the code line by line with the production web.config and that’s it. I found the one which was missing in the web.config that belongs to my development web application.

Note: I would suggest you to take a proper backup before making any changes in the web.config file.

What I did? What kind of entries I added in the web.config file?

Here we go:-

In you web.config, you need to search the tag name as “<PageParserPaths>”

Once you find that then make the following  entry:

<PageParserPaths>

    <PageParserPath VirtualPath="/apps/*" CompilationMode="Always"

              AllowServerSideScript="true" IncludeSubFolders="true" />

</PageParserPaths>

After adding this entry then IISRESET is mandatory.

Tried accessing the site and the issue has been resolved.

Happy SharePoint once again…

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.