 |
 |
 |
Tuesday, December 18, 2012
Monday, December 3, 2012
Audiences not working as expected
In the following scenario you can experience unexpected behavior from Audiences Groups:
Assume that your environment includes the following servers:
- SharePoint 2010 (Single Deployment \ Multi Server Deployment):
- SpsLab1001 (include User Profile Synchronization Service)
- Active Directory Servers:
- ADLab1
- ADLab2
- ADLab3
- NetBIOS Domain Name: LABENV
- FQDN Domain Name: Lab.Env.com
The UPA service configured with Synchronization Connection to Lab.Env.com domain.
On the Manage User Profiles page you can find users with Account Name like this:
lab\userlab1
LABENV\userlab2
lab\userlab3
lab\userlab4
This strange behavior could happen when your NetBIOS Domain name different from your FQDN Domain name like in this scenario.
Because of this, the "Audiences Groups" compile the users who hit the rules with wrong domain name.
As a result of this we can see users who exist inside the audience group and can't see the WebPart that was setup with that audience group.
To fix that we need to enable: NetBIOSDomainNamesEnabled in the UPA with PowerShell.
Please refer to this post: Click Here
Assume that your environment includes the following servers:
- SharePoint 2010 (Single Deployment \ Multi Server Deployment):
- SpsLab1001 (include User Profile Synchronization Service)
- Active Directory Servers:
- ADLab1
- ADLab2
- ADLab3
- NetBIOS Domain Name: LABENV
- FQDN Domain Name: Lab.Env.com
The UPA service configured with Synchronization Connection to Lab.Env.com domain.
On the Manage User Profiles page you can find users with Account Name like this:
lab\userlab1
LABENV\userlab2
lab\userlab3
lab\userlab4
This strange behavior could happen when your NetBIOS Domain name different from your FQDN Domain name like in this scenario.
Because of this, the "Audiences Groups" compile the users who hit the rules with wrong domain name.
As a result of this we can see users who exist inside the audience group and can't see the WebPart that was setup with that audience group.
To fix that we need to enable: NetBIOSDomainNamesEnabled in the UPA with PowerShell.
Please refer to this post: Click Here
Tuesday, November 27, 2012
Error message: "A script on this page is causing Internet Explorer to run slowly"
Assume you created an InfoPath form with some SharePoint list data connections and Rules, you run this form from SharePoint with
IE browser and you get:
This because how the IE Praser works, please refer to: Error message: "A script on this page is causing Internet Explorer to run slowly"
Also you can download hotfix for SharePoint 2010, InfoPath 2010: SharePoint Server 2010 hotfix package (Ifswfe-x-none.msp): August 28, 2012
* This hotfix exist in August 2012 CU: SharePoint Server 2010 cumulative update package (SharePoint server-package): August 28, 2012
Also you can download hotfix for SharePoint 2010, InfoPath 2010: SharePoint Server 2010 hotfix package (Ifswfe-x-none.msp): August 28, 2012
* This hotfix exist in August 2012 CU: SharePoint Server 2010 cumulative update package (SharePoint server-package): August 28, 2012
Sunday, November 18, 2012
Sunday, June 24, 2012
WUS Warning: SharePoint 2010 Administration Service not started - KB2677070
Symptoms:
SharePoint 2010 Administration Service not started.
Claims To Windows Token service not started.
Cause:
KB2677070 was installed on a server without internet connection.
Resolution:
Uninstall KB2677070 and restart.
*You can see also: TechNet post
** Their are more reasons why SharePoint 2010 Administration service won't start.
SharePoint 2010 Administration Service not started.
Claims To Windows Token service not started.
Cause:
KB2677070 was installed on a server without internet connection.
Resolution:
Uninstall KB2677070 and restart.
*You can see also: TechNet post
** Their are more reasons why SharePoint 2010 Administration service won't start.
Subscribe to:
Posts (Atom)