Friday, June 27, 2014

Microsoft SQL Server Version List

 Microsoft SQL Server Version List


Below is the detailed list of SQL versions



RTM (no SP)SP1SP2SP3SP4
 SQL Server 2014

12.00.2000.8
 SQL Server 2012
    
11.00.2100.60 11.00.3000.0 11.00.5058.0
 SQL Server 2008 R2
  
10.50.1600.110.50.2500.0
or 10.51.2500.0
10.50.4000.0
or 10.52.4000.0
 SQL Server 2008
   
10.00.1600.2210.00.2531.0 10.00.4000.010.00.5500.0
 SQL Server 2005
  
9.00.1399.069.00.20479.00.30429.00.40359.00.5000
 SQL Server 2000
  
8.00.1948.00.3848.00.5328.00.7608.00.2039
 SQL Server 7.0
  
7.00.6237.00.6997.00.8427.00.9617.00.1063

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SQL Server 2012 Service Pack 2



SQL Server 2012 Service Pack 2

In the below article I am providing the details of Service packs for SQL. Download the Latest packs by below URLS.

Microsoft® SQL Server® 2012 Service Pack 2 (SP2)
Microsoft® SQL Server® 2012 SP2 Report Builder
Microsoft® SQL Server® 2012 SP2 Reporting Services Add-in for Microsoft® SharePoint®
Microsoft® SQL Server® 2012 SP2 Power Pivot® for Microsoft SharePoint 2013®
Microsoft® SQL Server® 2012 Service Pack 2 (SP2) Master Data Services Add-in For Microsoft® Excel®
Microsoft® SQL Server® 2012 SP2 Power Pivot for Microsoft Excel® 2010
Microsoft® SQL Server® 2012 SP2 Semantic Language Statistics
  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Thursday, June 26, 2014

SharePoint Designer Workflow Stopped



SharePoint Designer Workflow Stopped

Issue: SharePoint Designer Workflow Stopped. This will show the workflow status as Stopped.

Cause: Send Email action has SharePoint group/ workflow lookups in the To / Cc line.

Workaround :Ensure to follow the below steps to get rid of the error.

Make sure each SharePoint group has at least Read permissions for the site. 

Additionally, that in the Group Settings area of the Group Page, under Who can view the membership of the group, Everyone is selected.

1.    On SharePoint site, click Site Actions -> Site Settings -> Modify All Site Settings.
2.     Under Users and Permissions heading, click People and groups.
3.     Select appropriate group(s), click Settings -> Group Settings.
4.     Under Group Settings area, select Everyone for Who can view the membership of the group, click OK.

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Access Denied while creating a workflow in SharePoint designer



Access Denied while creating a workflow in SharePoint designer

Issue: Access Denied while creating a workflow in SharePoint designer
Sometimes while creating a workflow using a SharePoint Designer we may see the error Access Denied even if the user is having Full Control on the site.

Solution: please find the below steps to get resolve the issue.

Ensure whether having permissions on the list to which you are attaching the workflow.
If you still see the problem even after doing that, ensure you do the below steps.
  1. Open the site in the browser.
  2. Right click on the Workflows folder and select Properties.
  3. In the Security tab, select “Manage Permissions using the browser“.
  4. In the workflows list’s permissions window, provide permission for the user you are facing the issue.
 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, June 23, 2014

People Picker takes too long to resolve names



People Picker takes too long to resolve names 

 http://i.technet.microsoft.com/dynimg/IC468765.jpg

This is a most common issue that we see in People search that picker takes more time to resolve the names. Microsoft has provided a fix for this. There is not impact and no downtime.

Issue: People Picker takes too long to resolve names

Cause: The problem is that we will always go to Active Directory first by default to do the lookup via the Translate To ids  function.  This isn’t desirable in this specific case because it’s a SharePoint security group that’s being passed.  The second part of the problem is with the format of the name specified on the people picker field.  The fact that there is no \ in the name causes Active Directory to submit the lookup against every domain in the forest.  In a large Forest, this can become a taxing operation.  Finally, the lookup is resolved within SharePoint.

Solution: Please run the following to resolve the issue.

1.    [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
2.    $webapp=[Microsoft.SharePoint.Administration.SPWebApplication]::Lookup("WEB App URL")
3.    $webapp.PeoplePickerSettings.ActiveDirectoryRestrictIsolatedNameLevel=$true;
4.    $webapp.Update();
 

Related KB’s:


 This property is set on the Web Application level and is false by default. In order to work around the problem, set this property to true.  

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Related Posts Plugin for WordPress, Blogger...

ShareThis

X