Error connecting to the workflow manager: Nintex Workflow designer for O365

Cause

Workflow Service Store feature is not activated by default.

Resolution

To resolve this issue,we need the activate the feature  using the url   _layouts/15/WorkflowServiceHealth.aspx. 

SharePoint - User Information List

The people picker gets/picks information from multiple locations:

– The User Information List

– Active Directory

The User Profile Service Application syncs information from the AD and updates the User Information List.This Sync

 does not delete the user from the list.

User Information List is hidden List.

It can be viewed via the browser by navigating to below urls

1.<Site URL>/_catalogs/users/simple.aspx

2. <Site URL>/_catalogs/users/detail.aspx 

3.To delete the same open the below URL's

<Site URL>/_layouts/people.aspx?MembershipGroupId=0

or

<Site URL>/_layouts/15/people.aspx?MembershipGroupId=0

and click on “Actions –> Delete Users from Site Collection

4.To view Specific User

<Site URL>_layouts/userdisp.aspx?Force=True&ID=idofUserInUserInfoList

5.Orphande users will cause problem

JSON Error Fix - People Picker InfoPath form

The JSON issue in people picker is bug and fix is given in this patch update. Please find the workarounds mentioned below.

Resolution :

 

The workaround is to add the following to the “pickerdialog.master”:

 

< !DOCTYPE html>

Replace the meta tag where it has
< meta http-equiv=”X-UA-Compatible” content=”IE=10″ />
with the following:
<meta http-equiv=”X-UA-Compatible” content=”IE=edge;chrome=1″ />

 

Incoming Email Settings- Good Link

http://anyrest.wordpress.com/2010/11/05/configuring-sharepoint-2010-to-accept-incoming-emails/

SharePoint 2010: error "The administration service is running sl all administration jobs will be run in the timer service"

SharePoint 2010: error "The administration service is running sl all administration jobs will be run in the timer service"

Symptom:
I had a solution that was stuck in the deploying state. When I looked at it, it had only deployed successfully on one the the front ends. To solve the problem, I ran stsadm execadmjobs. I have done this multiple times in 2010, but this time I got this message:
The administration service is running so all administration jobs will be run in the timer service.
Problem:
The timer service is set to take care of all admin tasks, so it is telling you that the jobs will run when the timer service is good and ready to kick them off, but until then, just sit on your hands and wait.
Solution:
Stop the admin service, then run the command to execute the admin jobs, then turn back on the admin service. These are the three powershell commands to do this:

• net stop SPAdminV4
• Start-SPAdminJob
• net start SPAdminV4

The first command shuts off the admin service. The second command is the powershell equivalent to stsadm execadmjobs and the third one turns back on the admin service. 

Page Title disappears after Ajax Post back

Page Title disappears after Ajax Post back

The Problem:
SharePoint page titles disappears when Ajax postback, title turn to square icons or empty space instead of page title.

We are having custom form and are using ajax to save the postback but when page postback asysnc the page title turns to square.

We have update panel as well in the webpart

Solution :

This was the line in master page after master page design:

<title id=”onetidTitle”>
<asp:ContentPlaceHolder id=”PlaceHolderPageTitle” runat=”server”/>
</title>


After figuring out i found that if i removed the space between the html tag then problem get resolved and title appears as it required.

The correct line of code is as follows :

<title id=”onetidTitle”><asp:ContentPlaceHolder id=”PlaceHolderPageTitle” runat=”server”/></title>

Sharepoint 2010 : CreateSubSiteGroup

Sharepoint 2010 : CreateSubSiteGroup       


         /// <summary>
        /// Create group
        /// </summary>
        public void CreateSubSiteGroup(SPWeb web, string groupName, string PermissionLevel, string groupDescription, SPFieldUserValueCollection fieldUserNames)
        {
            SPUserCollection users = web.AllUsers;
            SPUser owner = web.SiteAdministrators[0];
            SPMember member = web.SiteAdministrators[0];
            SPGroupCollection groups = web.SiteGroups;
            web.BreakRoleInheritance(true);
            groups.Add(groupName, member, owner, groupDescription);
            SPGroup newSPGroup = groups[groupName];
            SPRoleDefinition role = web.RoleDefinitions[PermissionLevel];
            SPRoleAssignment roleAssignment = new SPRoleAssignment(newSPGroup);
            roleAssignment.RoleDefinitionBindings.Add(role);
            web.RoleAssignments.Add(roleAssignment);
            AddUsersToSpecifiedGroup(fieldUserNames, web, newSPGroup);
            web.Update();
        }