Tuesday, January 13, 2015

Sunday, January 11, 2015

Outlook continuously prompting for password while connecting to Office 365? Solution is here.

Issue: Outlook continuously prompting for password while connecting to Office 365 Find out the solution.

When attempting to create an Outlook profile or connecting to an Office 365 mailbox, you are sometimes continuously prompted for credentials. The client displays the message "trying to connect...”." If you cancel the credentials prompt, you receive the following error:

Error: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.


Change the Logon network security setting to Anonymous Authentication.

Mandatory Checks:

If you can’t find “Anonymous Authentication” under Logon network security drop down, you will have to download Service Pack 2 , which is mandatory for Outlook 2010. Open attached PDF to download the Service Pack 2.

Launch Control Panel.

In Windows 8 and Windows 8.1

Swipe in from the right to open the charms, tap or click Search , and then type control panel in the search box. Or, type control panel at the Start screen.

In Windows 7
Click Start, type Control Panel in the Start Search box, and then press Enter.

3.    In Control Panel, locate and double-click Mail.

4.    Click Show Profiles, select your Outlook profile, and click Properties.

5.    Click E-mail Accounts, select Account Settings and on the E-mail tab, click Change.

6.    In the Change Account dialog, click More Settings.

7.    In the Microsoft Exchange dialog, select the Security tab.

8.    From the Login network security dropdown, select Anonymous Authentication and click OK.

9.    Click Next and click Finish, and then click Close on the Account Settings dialog.

10. Click Close on the Mail Setup dialog, and click OK to close the Mail control panel.

  Why does it happen?

This issue can occur if Logon network security under More Settings on the Microsoft Exchange Security tab is set to a value other than Anonymous Authentication.

 Applies to: Outlook 2013, Office 365.

Friday, January 9, 2015

NoILMUsed UserProfileApplication class property should not use: SharePoint 2013

While reading some articles on internet, I bumped in very interesting article shared by MS back in 2013.

A property name NoIMLUsed was elaborated an MS suggest this property should not be altered else can damage you are working User Profile service.

They have given a PowerShell Snippet below to be used to correct this.

$upa = Get-SPServiceApplication | ? {$_.typename -like 'User Profile *'}
if ($upa -eq $null)
    Write-Host "No User Profile service application is found."

if ($upa.noILMUsed -eq $true)
    Write-Host "Reverting back the NoILMUsed flag to false..."
    $upa.noILMUsed = $false    
        Write-Host "Failed updating UPA once. Try it again..."
        $upa = Get-SPServiceApplication | ? {$_.typename -like 'User Profile *'}
        $upa.noILMUsed = $false 

    # check the flag after update
    $upa = Get-SPServiceApplication | ? {$_.typename -like 'User Profile *'}
    if ($upa.noILMUsed -eq $false)
        Write-Host "Successfully reverted back the NoILMUsed flag to false."
        Write-Host "Failed to revert back the flag. Please try running the script again."
    Write-Host "The NOILMUsed flag is already set to false. "

# check sync service status
$syncServices = @(Get-SPServiceinstance | ? {$_.typename -like 'User Profile Synchronization *'})
$flag = $false
foreach ($service in $syncServices)
    if ($service.status -eq 'Online')
        $flag = $true

if ($flag -eq $false)
    Write-Host "The User Profile Synchronization service is not started in this farm. Please proceed with restarting the profile sync service when in need." 
    Write-Host "All appears to be good."

Reference KB can be found here:

I hope this information is useful for you.

Applies to: SharePoint Server 2013.

Thursday, January 8, 2015

Version comment is blank in a document library: SharePoint 2013.

Issue: When you check-in back a document and enter comment in the version history you see you comments are not saved.

Error: There is no error message, it’s just version comments are missing.

Background: on some of the site when version is enabled and require check-out before you edit a document is enabled you see that when you write comments in version and reading versions history versions are there but their associated comments are not there.


We check-out on other document libraries and this problem was across.

We disabled version on a particular library and saw not difference.

We disabled require document to be checkout and saw no difference.

Set-up another document library with same features enabled and problem was there.

I noticed this is wider problem them expected.


Found a hotfix published by MS on October, 2013 has listed about the issue.

This hotfix also does talks about many other related issue.

Alternatively installing cumulative update this 
could also resolve the problem.

Prerequisites for the above KB is

Applies to: SharePoint Server 2013.  


snow flakes

blogger widgets Blogspot Tutorial


Related Posts Plugin for WordPress, Blogger...