Monday, October 29, 2012

Only 1 user Calendar (free/busy) information is not correct. [ Exchange Online ]

Issue:
========
There is a Recurring Calendar Event which keeps sending Reminders to Users Outlook Client and OWA as well. Even if we "Dismiss all" reminders, it keeps poping up. Even if you Remove the User from the "Attendees" list, the free/busy information does not sync up and it not updated either in OWA or Outlook Client.

Resolution
===========
Follow article http://support.microsoft.com/kb/2522226. Usually the '/cleanfreebusy' switch with Outlook client does not solve the issue. We need to follow the 2nd step, as per the Outlook client version of that problematic User.

"Proof of domain ownership has failed" Exchange Hybrid Configuration Wizard Failure

Issue:-
=========
While running the Exchange 2010 SP2 Hybrid Configuration Wizard, it fails with below error.

Proof of domain ownership has failed. Make sure that the TXT record for the specified domain is available in DNS. The format of the TXT
record should be "example.com IN TXT hash-value" where "example.com" is the domain you want to configure for Federation and "hash-value"
is the proof value generated with "Get-FederatedDomainProof -DomainName example.com". at
Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, Dictionary`2 parameters, Boolean ignoreNotFoundErrors).


Steps to Check and Rsolve.
===========================
1. Make sure your External DNS server has the proper TXT records for the "Proof" and you can query it successfully. [ Get-FederatedDomainProof -DomainName example.com ] Will give you the proof.

2. Open Exchange Console Management (On PREM) -> "Organization Configuration" -> Select "Federation Trust"
You should find an existing 'Microsoft Federation Gateway' Trust created by the wizard. Manually Try to run it and check if it fails. Alternatively you can run PS cmd as below in verbose mode to get the error as well.

Set-FederatedOrganizationIdentifier -DelegationFederationTrust 'Microsoft Federation Gateway' -AccountNamespace 'yourdomain.com' -Enabled $True -verbose

3. If it is pointing to FYDIBOHF25SPDLT.yourdomain.com, That GUID is Default, so dont worry. This means that still your TXT record is not fetched from External DNS to verify the 'Proof' record.

4. If you Manaully Delete the Federeation Trust and Create a new one, you will get a new Proof as well for the domain. "Get-FederatedDomainProof -DomainName example.com", will give you the new Proof, which you will need to again change in the External DNS, but mostly likely this will be the issue, if there is a stale entry in AD which can be checked through ADSIEDIT.msc

5. Main thing to check is from Command Prompt, basic 'nslookup' query. below are the commands.
>nslookup
>set q=ns
>yourdomain.com [ Here you will get multiple NS records if there are more than 1, precendence will take place during query. You need to individually Query the NS servers starting from the 1st one, usually if the first server fails to process the query, Hybrid Configuration Wizard will fail with same error. ]
>ns1.yourdomain.com < IP Address >
ns2.yourdomain.com < IP Address >

>nslookup-querytype=txt yourdomain.com ns1.yourdomain.com [ Here if the 1server fails, then that server is the issue, you need to change he precedence of the servers to the one which is responding with your Domain TXT record for the Proof. ]

Note:- This error is purely due to the Proof TXT record query is not getting processed. Even if you check in any online DNS Query tools or sites, you will see the TXT record, but it can come from multiple tries to other DNS servers as well, if the primary server fails. So usually we miss that point to check


Wednesday, August 8, 2012

SharePoint Server 2013 and SharePoint Foundation 2013 Released

SharePoint Foundation 2013 Preview
http://www.microsoft.com/en-us/download/details.aspx?id=30345

Language Packs for SharePoint Foundation 2013 Preview – English, Japanese, and Spanish
SharePointFoundationLP_en-us_x64.exe
http://www.microsoft.com/en-us/download/details.aspx?id=30343

Download Microsoft SharePoint Server 2013 Preview
http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx?wt.mc_id=TEC_121_1_33

Language Packs for SharePoint Server 2013 Preview – English, Japanese, and Spanish
Serverlanguagepack_en-us_x64.exe
http://www.microsoft.com/en-us/download/details.aspx?id=30347

SharePoint Designer 2013
SharePointDesigner_en-us_x64.exe
SharePointDesigner_en-us_x86.exe
http://www.microsoft.com/en-us/download/details.aspx?id=30346

SharePoint 2013: presentation: IT pro training
http://www.microsoft.com/en-us/download/details.aspx?id=30361

Wednesday, July 4, 2012

Search Crawl Time Out or Proxy Issue.

Issue:-
SharePoint 2007 (MOSS) Search crawl is not working for any web application.

Error:-
This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might also want to crawl this repository during off-peak usage times.

Resolution:-

Apart from all the basic troubleshooting of checking if the site opens up using the search service account on the server or not and application pool settings and Shared Services settings, below was the resolution for me.

In Command prompt run "netsh winhttp show proxy". You should get no proxy server, something like below.


If you see there is a proxy server, which can be old or not working, we need to reset this setting.

Run the command "netsh winhttp reset proxy" to Reset the proxy and again do a Show command, you should get "No Proxy Server" screen as above.

In Order these are the steps.

1. netsh winhttp show proxy
2. netsh winhttp reset proxy
3. Net stop Osearch
4. Net start Osearch

You can also check if there are any Proxy Settings in IE Configuration.

Tuesday, June 19, 2012

Before you Upgrade to SQL 2012 where SharePoint databases reside.

Please make sure to go through these articles before you upgrade to SQL 2012 where SharePoint databases are hosted.

SQL server 2012 is supported and works with SharePoint 2010 only if the SharePoint environment is on SP1 or higher
http://msdn.microsoft.com/en-us/library/hh231665(v=sql.110).aspx


Upgrade to SQL Server 2012
http://msdn.microsoft.com/en-us/library/bb677622.aspx

Supported Version and Edition Upgrades
http://msdn.microsoft.com/en-us/library/ms143393.aspx

Upgrade PowerPivot for SharePoint
http://msdn.microsoft.com/en-us/library/ee210646(SQL.110).aspx

Upgrade and Migrate Reporting Services
http://msdn.microsoft.com/en-us/library/ms143747.aspx 

Upgrade Analysis Services
http://msdn.microsoft.com/en-us/library/ms143686.aspx

Site Slowness due to Certificate CRL Checking.

Issue:- You can have ADFS sites or Kerberos or basic configuration sites using hardware appliances for NLB e.g. F5 or Big IP or you can also be using SiteMinder. You may experience slowness while loading the site.

Troubleshooting:-

If you collect Fiddler trace you will see CRL checking to Microsoft site.
   

Resolution:-

1. Disabled Certification Revocation checking.

OR

1. netsh http show sslcert (* check if 'Verify Client Certificate Revocation : Enabled' *)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo\0.0.0.0:443 -> DefaultSslCertCheckMode = 1

2. reboot server
3. netsh http show sslcert (* check if 'Verify Client Certificate Revocation : Disabled' *)

Consideration to Improve Performance for SharePoint 2010 Servers.

Performance of SharePoint 2010 Servers.

Performance is always a big topic of Discussion in Any Organization. No matter how much CPU or RAM you add to the Servers, most of the time Users will complain that the sites are slow, or sudden fluctuations in CPU going consistently high, or Customization issues, SQL Deadlock errors etc... etc.. the list goes on.

Here are some of the very Important things to look at Configuration settings and Troubleshoot certain things, which you may face in various different SharePoint Environments.

Many of the known performance issues like UPA sync is slow from Active Directory or Search crawling has suddenly become slow can be caused due to some SQL or OS related configurations not done correctly or they are not in place at all.

Here are some of the STRONGLY recommended articles that should be followed.

SQL Maxdop setting should NOT be 0
========================================
http://technet.microsoft.com/en-us/library/hh292622.aspx
Set max degree of parallelism (MAXDOP) to 1 for SQL Server instances that host SharePoint Server 2010 databases to ensure that each request is served by a single SQL Server process

Anti-Virus check.
====================
Certain folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in SharePoint
http://support.microsoft.com/kb/952167

SQL TempDB configuration and Optimization.
===================================================
http://msdn.microsoft.com/en-us/library/ms175527.aspx
http://blogs.msdn.com/b/joaquint/archive/2011/02/08/sharepoint-and-the-importance-of-tempdb.aspx

Database maintenance for SharePoint 2010 Products
http://technet.microsoft.com/en-us/library/cc262731.aspx

Disable Certification Revocation checking.
http://support.microsoft.com/kb/2625048

SQL Deadlock errors. Event ID 10016 in logs.
We need to disable following settings on ALL the SharePoint Servers and also SQL Servers. If SQL Server is in Cluster, all the nodes in the cluster also needs to be changed. After making the Changes, Reboot of all the Servers including SQL servers is Mandatory.

1. TCP Chimney Offload http://support.microsoft.com/kb/951037. by Default in Wind 2008 Servers, this setting is "Automatic", we need to Disable it. "netsh int tcp set global chimney=disabled"

2. IP Task Offload. by Default in Wind 2008 Servers, this setting is "Enabled", we need to disable it. "netsh int ip set global taskoffload=disabled". This is also applicable for Fast for SharePoint Server issues. http://support.microsoft.com/kb/2570111

3. NIC settings should be Disabled.

IPv4 Checksum Offload”, “Large Send Offload” and “TCP Checksum offload” [ note: this may require a hard reboot of the servers ]

Why to Disable TCP Chimney on SQL Servers?
http://blogs.msdn.com/b/psssql/archive/2008/10/01/windows-scalable-networking-pack-possible-performance-and-concurrency-impacts-to-sql-server-workloads.aspx



Other Tool you are use to Troubleshoot.

Use Developer Dashboard.
==================================
http://blogs.technet.com/b/patrick_heyde/archive/2009/11/16/sharepoint-2010-enable-using-developer-dashboard.aspx
stsadm -o setproperty -pn developer-dashboard -pv ondemand

SharePoint 2010 Search Query component is not responding. Synchronizing state.

Issue:- Search Topology has multiple Query components and after some Server reboots or patch updates or network connectivity issues, we get below error in the Logs.

Error:-

The following conditions are currently affecting index propagation to this server for search service application 'Enterprise Search':   1. Query 3, catalog Main: failing to copy index files from crawl component 2 for 105737 minutes. The network path was not found.   0x80070035  2. Query 3 is not being automatically disabled because the minimum number of ready query components per partition is 2.
01-14-2012 12:00:12.48 OWSTIMER.EXE (0x0958) 0x09B8 SharePoint Server Search Administration f6ql Warning The following conditions are currently affecting index propagation to this server for search service application 'Partitioned Search':   1. Query 1, catalog Main: failing to copy index files from crawl component 1 for 105658 minutes. The network path was not found.   0x80070035  2. Query 1 is not being automatically disabled because the minimum number of ready query components per partition is 2. d39bcb4a-a193-427f-9fcc-f65cd6127a73

01-14-2012 12:10:02.04 OWSTIMER.EXE (0x0958) 0x09CC SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject SearchQueryAndSiteSettingsServiceInstance. Version: 1489237 Ensure: False, HashCode: 22838785, Id: 4bfc05dd-9ba0-40f0-be26-427f7e05a614, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()     at Microsoft.SharePoint.Administration.SPIisWebServiceInstance.Unprovision()     at Microsoft.SharePoint.Administration.SPServiceInstanceJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPAdministrationServiceJobDefinition.ExecuteAdminJob(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result) 3860aa69-0248-463f-879e-cc473cddfba1

Resolution:-
You will have to create new Query Components and delete the Old ones following below article.

Search query critical error - Event 60 (SharePoint Server 2010)
http://technet.microsoft.com/en-us/library/ee513123.aspx

Timer Service keeps Crashing / causes UPA Sync to stop working.

Issue:- UPA Sync Service will stop functioning intermitently. During troubleshooting, you may not find any errors or Event's logged for this. You may also notice that the Timer Service is crashing every 2-3 mins if you keep an eye on the Services console.

Troubleshooting:- You can use Microsoft Procmon Tool to check if any Service is causing it crash or what might be interrupting the UPA and Timer Services to function properly.

Resolution:- Anti-Virus software is the main cause for such issues. Once you exclude SharePoint folders following the below article you need to restart/re-provision UPA and UPA Sync Service from Central Administration page.

Certain folders may have to be excluded from antivirus scanning when you use a file-level antivirus program in SharePoint
http://support.microsoft.com/kb/952167 

New AD Users not getting resolved in People Picker

Issue:- Any New User or Group created in Active Directory is not getting resolved in a specific SharePoint Site collection People Picker. It works fine for other Web Applications and if you create a new Site Collection in the same Web app, People Picker is resolving new Users and Groups there.

For the problematic Site Collection, the old Existing User accounts and Groups are resolving fine, only the New ones are not getting resolved in People Picker.

Resolution:-

Get-SPSite "http://SharePoint/sites/collection" | fl > C:\props.txt 

If you open the Props.txt file, you will see the properties for this site collection. Look for "UserAccountDirectoryPath" property. By Default it should be blank, if it is not, that is causing new Users in AD not to be resolved in People Picker.

To Change the Property value to Blank, follow as below.

$Site = Get-SPSite "http://SharePoint/sites/collection"
$Val=""
$Site.UserAccountDirectoryPath = $val

Note:- You can also first troubleshoot by creating a new Site collection in Same Web app and check if the issue is similar as per this blog.

SP 2010 User Profile Sync Service Won't start

Issue: SharePoint 2010 User Profile Sync Service won't start. As many are already pulling their hair over the UPA Sync service issues, one of the errors and resolution is as below.

Error:-
02/22/2012 11:49:18.87 OWSTIMER.EXE (0x1A10) 0x0AE8 SharePoint Portal Server User Profiles g4wt High UpdateILMMA: Failed to update password. Exception: {1}.. Available parameters: Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Access to the requested resource(s) is denied at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.GetResource(UniqueIdentifier identifier, String[] attributeNames, Nullable`1 resourceTime) at Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(UniqueIdentifier resourceIdentifier, String typeName, String[] attributeNames, CultureInfo locale, Boolean includePermissionHints, TimeZoneInfo localTimeZone) at Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(UniqueIdentifier resourceIdentifier, String typeName, String[] attributeNames, CultureInfo locale, Boolean includePermissionHints) at Microsoft.Office.Server.UserProfiles.Synchronization.MAConfiguration..ctor(Guid resourceIdentifier) at Microsoft.Office.Server.UserProfiles.Synchronization.ILMMAConfiguration..ctor(Guid resourceIdentifier) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.UpdateILMMA(String databaseServerIlm, String databaseInstanceIlm, String databaseName, String domain, String userName, SecureString password) . a4398ace-cf1f-4a23-a976-830806ce4c67

02/22/2012 11:49:18.87 OWSTIMER.EXE (0x1A10) 0x0AE8 SharePoint Portal Server User Profiles 9q17 High UserProfileApplication.SynchronizeMIIS: Failed to configure ILM MA, will attempt during next rerun. Exception: Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Access to the requested resource(s) is denied at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.GetResource(UniqueIdentifier identifier, String[] attributeNames, Nullable`1 resourceTime) at Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(UniqueIdentifier resourceIdentifier, String typeName, String[] attributeNames, CultureInfo locale, Boolean includePermissionHints, TimeZoneInfo localTimeZone) at Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(UniqueIdentifier resourceIdentifier, String typeName, String[] attributeNames, CultureInfo locale, Boolean includePermissionHints) at Microsoft.Office.Server.UserProfiles.Synchronization.MAConfiguration..ctor(Guid resourceIdentifier) at Microsoft.Office.Server.UserProfiles.Synchronization.ILMMAConfiguration..ctor(Guid resourceIdentifier) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.UpdateILMMA(String databaseServerIlm, String databaseInstanceIlm, String databaseName, String domain, String userName, SecureString password) at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance). a4398ace-cf1f-4a23-a976-830806ce4c67

02/22/2012 11:49:18.87 OWSTIMER.EXE (0x1A10) 0x0AE8 SharePoint Portal Server User Profiles 9i1u Medium UserProfileApplication.SynchronizeMIIS: End setup for 'UserProfileServiceApplication'. a4398ace-cf1f-4a23-a976-830806ce4c67

Log Name: Application
Source: FIMSynchronizationService
Date: 2/22/2012 11:49:18 AM
Event ID: 6331
Task Category: MA Extension
Level: Error
Keywords: Classic
User: N/A
Computer: computer.domain.com
Description:

A update on the configuration of a MA or MV failed to replicate to a target connector directory that is capable of storing MA/MV configurations. As a result, the MA/MV configuration data in this connector directory is not up to date. Please correct the condition that causes the error, and triggers a resync by updating the password information of the target MA.

Additional information:
Error Code: 0x80231317
Error Message: (The management agent failed to validate against the application store with the specified credentials.)
Operation: Clean up MAs
Name of the MA to replicate:
Name of the target MA: ILMMA
Guid of the target MA: {F2CD610F-9L7E1-45S2-834J-D76734328DFCAC4}

(The management agent failed to validate against the application store with the specified credentials.)
Clean up MAs


Resolution:-
1. Make sure you are logged into the Server as the UPA Service account.
2. Run RSOP information for account specifically for 'Allow Logon Locally' and 'Deny Logon Locally' GPO.
3. If the User Account is part of any AD group and that Group is added to the "Deny Logon Locally" policy, the UPA Sync service will NOT start.
4. The Service account has to be specifically be part of the "Allow Logon Locally" GPO.

PDF iFilter - Error "The file Exists"

Issue:- While crawling .pdf documents, some documents are crawled successfully and some are not. This can happen for either Adobe PDF iFilter or FoxIt PDF iFilter.

Error:- "The file Exists. (Exception from HRESULT: 0x80070050)".

Resolution:-
In case you are using Adobe PDF iFilter, follow below steps.

1.  Change the Registry key for ‘Default’ under \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension to “{E8978DA6-047F-4E3D-9C78-CDBE46041603}”
a.  Perform net stop osearch14
b.  Net start osearch14
In case you are using FoxIt PDF iFilter, Follow below steps.

1. Change the Registry key for ‘Default’ under \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension to“{987f8d1a-26e6-4554-b007-6b20e2680632}”,
a. Perform net stop osearch14
b. Net start osearch14