Resolve Microsoft SQL Server Password Error 18456

Microsoft SQL Server is one of the most widely used database system that allows users to handle multiple databases. It provides an authentication feature to let the authorized user access the database. So, a user needs to provide login credentials to access specific database. However, it has been observed that when an attempt is made to login to server, it displays SQL Server error 18456, which restricts them to access the database account. In this section, we are going to discuss various types of error 18456 in SQL server and simple steps to resolve them.

What is SQL Server Login Error 18456

SQL Server allows the login to database by using certain credentials: Server name, login, password. However, in certain cases when a user attempts to login to the database, it generates error code 18456 indicating wrong login credentials. As a result, the users become unable to access database and corresponding components.


Microsoft SQL Server Login Error Code 18456 States

The error 18456 may arise with different error states, which may be due to different reasons. Thus, depending upon the situation, major error states generated by SQL Server include:

1) State 2 & State 5 : Invalid UserId

SQL Server generates error 18456 with state 2 and 5, if you are trying to login to server with invalid userid. This may arise due to following reasons:

  • The server has not yet granted access to the user Id. Due to restricted access, SQL Server does not allow to login to the specified server.
  • There may be spelling or typing mistake in the server name entered by the user.

Error: 18456, Severity: 14, State: 5.
Login failed for user ‘chepsi’. Reason: Could not find a login matching the name provided. [CLIENT: ]


1) Firstly, make sure that the server name entered is absolutely correct and accurate.

2) If the server name is accurate but the login problem still persists, then go for authenticate mode settings. Follow the below mentioned steps to enable the authentication for specific server:

  • Using SQL Server Management Studio, navigate Object Explorer >> Connect.
  • Right click on the server name.
  • Choose Properties option from the list.
  • blog-img-2

  • Under Server Properties, Go to Security option.
  • blog-img-3

  • Select SQL Server and Windows Authentication mode for allowing server access.
  • blog-img-4

This procedure enables SQL Server authentication mode so that user id can be easily associated from the server at the time of login.

2) State 7: login disabled and password mismatch

SQL Server generates this error state in case the login account for the specified user has been disabled and user is trying to login with wrong password.

Error: 18456, Severity: 14, State: 7.
Login failed for user ‘chepsi’. Reason: An error occurred while evaluating the password. [CLIENT: ]


Firstly, the disabled account needs to be enabled from admin end. This can be done by the following steps:

  • Using SQL Server Management studio, login to system account using valid credentials.
  • Browse Object Explorer >> Security >> Logins.
  • blog-img-5

  • Now, right click on the specific user name and select Properties option.
  • Under status tab, mark Enabled for login option.
  • blog-img-6

  • Click on Ok to save the changes made.

3) State 8: Password Mismatch

One of the most commonly generated error state is due to incorrect password entered by the user. It means that the password entered by the user at the time of login does not match with the actual password. As a result, SQL Server displays password mismatch error and restricts login.

Error: 18456, Severity: 14, State: 8.
Login failed for user ‘chepsi’. Reason: Password did not match that for the login provided. [CLIENT:]


The user can reset the password for a particular account with the help of admin. The following steps need to be performed to reset or change the password:

  • Login to System account using the valid credentials.
  • Navigate Object Explorer >> Security >> logins.
  • Select the user name whose password needs to be changed.
  • Right click on user name and click on Properties option.
  • Under General settings window, type new password.

Once the login password is changed, the user can login with new password and access the database easily.

4) State 11 & 12: Valid login but server access failure

This error indicates that the login credentials provided by the user are correct but Windows Authentication has failed. The most possible reasons leading to this error state include:

1. The login for the particular account is denied from permission class.

2. The CONNECT permission might be granted for the Group users; instead of individual login.

Error: 18456, Severity: 14, State: 11.
Login failed for user ‘chepsi’. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT:]

In case of SQL related denial error, SQL Server provides error state 12:

Error: 18456, Severity: 14, State: 12.
Login failed for user ‘chepsi’. Reason: Login-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT:]


For error state 11, perform the following measure:

  • Delete the current login account and recreate with new credentials
  • Run SQL Server as admin and then, try to login again.
  • Another way may be to disable the UAC mode.

However, the error state 12 can be resolved by:

Using admin access, make sure that the access is allowed for the specified user. If not, enable the login access.

5) State 13: SQL Server service paused

In case, the user tries to login to SQL server at the moment when SQL service has stopped, the server generates an error state 13. It indicates that the server cannot establish any connection at the moment.

Error: 18456, Severity: 14, State: 13.
Login failed for user ‘chepsi’. Reason: SQL Server service has been paused. No new connection can be accepted at this time. [CLIENT:]


Restarting the SQL Server services may eradicate this error and allow smooth login for the specified account. So, try to restart the server by following steps:

  • Click on Object Browser from SQL Server Management Studio.
  • Now, connect to the instance of database service using Connect option.
  • Click on Restart to initiate the server services again.

Automated way to Resolve SQL Error Code 18456

The users can also go for third party SQL password recovery tool to overcome various states error related to error code 18456. It allows to recover the password and access the account without encountering any kind of login error.


SQL Server authentication issues may create haphazard for the users and hamper their regular tasks. One such error is Microsoft SQL Server error 18456, which is basically a login error that restricts the users from accessing the account. Various error states associated with the error and their resolutions have been discussed. Moreover, an automated SQL password recovery tool has also been discussed to let the users overcome error fastly and efficiently.

3 Ways To Fix Oversized .EDB Files

Do you often encounter EDB files that are too large to handle? If so, then you could also be in danger of your Exchange server running short of storage space.

When excessive amounts of data pile up in an exchange database it can reach the file size limit and cause server crashes, outlook application collapses or even a sudden halt of the entire communication medium. Trying to remove data chunks may not help in this scenario since the compression of the EDB file will not take place in the correct way.

In this blog, we’ll discuss three different ways you can repair oversized EDB files without losing data.

Possible Solutions

  1. One way to handle oversized EDB files is to migrate data from the old mailboxes to new mailboxes after building a new mailbox database. However, mailbox migrations can be both time-consuming and complicated when you consider the excessive number of logs generated from the large volume of information.
  2. Another solution is known as the defragmentation technique. This is performed by running the “Eseutil” command in offline mode to track the size of the exchange database file and allow its compression. To defragment the EDB mailboxes using the Exchange management shell, you must dismount the database before starting the defragmentation process. However, users must have enough storage space available on their disk drives to execute the defragmentation.

    It is important to note that no user, inside or outside the organisation, will be able to access these mailboxes while the process is ongoing. When the defragmentation is complete, new EDB files are created from scratch (despite continuing to remain on the systems of users).

  3. The third solution is to alter the location of the mailbox database by executing the following procedure. This procedure will increase the data storage capacity of the exchange database file:

    Step 1 – In register editor, look for the following path
    “HKEY_LOCAL_MACHINE\SYSTEM\CurentControlSet\Services\MSExchangeIS\<Server Name>\Private-<databaseGUID>”

    Step 2 – Firstly, change the storage limit to GB and then increase it by specifying a higher amount of available GB under the last field of the above path i.e. in the field “Private-<databaseGUID>”

    Step 3 – Finally, restart the Exchange Information store and check the event viewer for Event ID 1216 to figure out the current size of the database.

The Final Verdict

The three methods discussed in this blog should help you to repair oversized .EDB files in a working Exchange database. Unfortunately, none of the methods will be successful if your exchange database turns out to be corrupt. However, many third party solutions, such as Lepide Exchange Recovery Manager, allow users to extract information; including mailbox folders, individual mailboxes, embedded attachments and email properties from even the most severely corrupted or damaged exchange databases without leaving any impact on data hierarchy.

Overview of SQL Server 2016 Temporal Table

SQL Server has been providing a reliable and efficient database management service to the users for a long time. With every release of new version, the users are offered new features, which attracts them to use SQL Server for every data storage purpose. The latest version, SQL Server 2016 has emerged out with many new functional features, out of which temporal tables are the most discussed among they experts and users. In this section, we will learn about SQL Server temporal table and their usage in the database.

What is Temporal Table in SQL Server?

A temporal table is a kind of user table, which attempts to maintain the history of all the data changes done with the database. It is also known as system-versioned temporal table as the system itself is responsible to manage the validity period of each row. Each temporal table is associated with the following columns which belong to datetime2 data type. They hold the values for the validity of data for which the row has been modified. These columns are also known as period columns as they represent the time related parameters in datetime2 data type.

The temporal table in SQL Server holds a link to another table known as History Table, which carries all the previous versions of the data. So, the history table allows the user to retrieve the older values of any column using the temporal table.

Consider an example where, in a database the value of x=20 and the user has just updated the new value of x to 125. If there were no temporal table, the user will always get x=125 while retrieving from the main database. However, in many cases it becomes necessary for the user to get an idea of the previous records which have either been updated or deleted. So, the SQL Server temporal tables can make it easy for the user to easily access the previous versions of columns as it maintains the record in history table.

So, if the temporal table is used in above discussed example, then the temporal table can be easily used to retrieve older value of column i.e., x=20.

Role of Temporal Table in SQL Server 2016

Temporal table plays a very important role in maintaining the database records in a consistent way. An efficient use of the temporal table in SQL Server can help the user in the below mentioned ways:

  1. Data Forensics- Temporal tables provides an easy way to audit the data and understand how the values of a column has changed over the time. It can be used in data forensics to view all the changes made from history table.
  2. Data Reconstruction- One can easily view the nature of data change over the time using temporal table and reconstruct the data when needed.
  3. Data Recovery- In case of data corruption or server failure, the SQL Server temporal tables can be used to retrieve the older version of data and insert them back into the main table. So, it also acts like a backup.
  4. Research Purpose- The temporal tables can be used to study the change in values of the data for a time interval. It can help decision taking bodies to research and analyze the trends in data changes.

How to Create SQL Server Temporal Table

The temporal tables can be created for any database using a simple script. There are a few points which need to be taken care of while creating any temporal table:

  • The primary key should be defined for the table
  • Two columns must be created with datetime2 data type to hold the start and end date for records
  • The temporal tables cannot have INSTEAD OF triggers
  • The user can adopt AFTER trigger only on the current table

Consider the following script for creating a temporal table dbo.MyTemp, where two columns with datetime2 type are used to store the time records:

        (PID int primary key
        ,X int
        ,Y int
        ,Z AS X * Y
        ,SysStartTime datetime2 GENERATED ALWAYS AS ROW START NOT NULL
        ,SysEndTime datetime2 GENERATED ALWAYS AS ROW END NOT NULL


Temporal tables serve as a significant role in SQL Server as they help to maintain a record track of all the changes done on the values of columns. The users are advised to make a judicious use of these tables. We hope that with this article, the major concept of SQL Server temporal table is made clear to the users.

A quick overview of migrating from Exchange 2007 to Exchange 2016

Migrating from Exchange 2007 to Exchange 2016 is a laborious and time consuming process because it cannot be done correctly. It involves upgrading from Exchange 2007 to 2010/2013, and then to Exchange 2016. Doing the migration natively requires a large amount of technical knowledge and can be costly as it involves setting up an intermediate Exchange environment.

One other method is to deploy an Exchange migration solution like LepideMigrator for Exchange. This solution makes it possible to upgrade directly from Exchange 2007 to 2016, without the need for double hopping.

Upgrading from Exchange 2007 to Exchange 2016 using Exchange 2013

Upgrading from Exchange 2007 to Exchange 2016 through 2013 involves two major stages:

I. Upgrading from Exchange 2007 to Exchange 2013
For detailed steps, please refer to:

II. Upgrading from Exchange 2013 to Exchange 2016
For detailed steps, please refer to:

Upgrade from Exchange 2007 to Exchange 2016 using Exchange 2010

Upgrading from Exchange 2007 to Exchange 2016 through 2010 involves two major stages:

I. Upgrading from Exchange 2007 to Exchange 2010
It’s is easy to upgrade from Exchange 2007 to Exchange 2010 as they are immediate versions of Exchange. The steps are given here briefly:

  1. Ensure that you have the system requirements
    For smooth installation of Exchange 2010, and upgradation from 2007, ensure that you have the minimum system requirements:

    For Exchange 2010
    Processor- 64 bit supported (computer with x64 bit architecture)
    Disk space – 1.2 GB (for installation) + 200 MB free space
    OS –  Windows Server 2008 (SP2)/2008 R2 – Standard/Enterprise editions (64bit)
    For management tools –  Windows 7/Vista (64bit)
    Additional – NTFS (for disk partitions), .NET Framework 3.5 SP1, IIS,
    Windows PowerShell V2.0, Windows Remote Management V2.0

    In Exchange 2007
    Exchange 2007 Service Pack 3 (for each server)

  2. Configure disjoint namespace
    If you want to run a disjoint namespace in Exchange 2010, do the following:

    a) Configure the DNS suffix search list using GPMC
    In this step, set a DNS suffix search list using a GPO.

    b) Create a list of allowed DNS suffixes.
    For this, modify the relevant attribute (msDS-AllowedDNSSuffixes) value of the domain object container (using ADSI edit).Also, verify these settings (by pinging from other servers).

  3. Install the Client Access Role

    Client Access Role is the first server role to be installed on a server. This role facilitates the functioning of Exchange email clients.

    You can install this role from Exchange 2010 DVD by running the setup exe (if not installed previously, initiate .NET Framework 3.5 SP1 and Windows PowerShell v2 installation from here). For Exchange 2010 installation, accept the license agreement, and follow the instructions on the dialogue box. Here is a what you will do while going through different pages of the installation wizard:

    • Enable error reporting feature if required
    • Opt for ‘Custom Exchange Server installation’
    • Change Exchange installation path if necessary
    • Select Client Access Role on the Server Role Selection page

      Figure 1: Installation of Client Access Role


    • Configure an external FQDN (for connection with email clients)
    • Fix errors, if any are reported by the wizardFinally install Exchange and verity it using Get-ExchangeServer cmdlets (in Exchange Management Shell). After the installation, add digital certificates, and configure Outlook Anywhere and virtual directories.

      NOTE: It is possible to have separate servers for each role; but you can deploy multiple roles on servers as per the requirement.

  4. Install the Hub Transport Role

    Hub Transport Role facilitates internal mail flow in the organization. It can be installed on a separate server, or on the same server on which the CAS role was installed.

    To install the Hub Transport Role (on a separate server), follow the same steps as those for the installation of the CAS role. But on the Server Role Selection page, select Hub Transport Role. And verify the installation using Get-ExchangeServer cmdlets (in Exchange Management Shell).


    Figure 2: Installation of Hub Transport Role

    To ensure co-existence between the Exchange 2007 and Exchange 2010 environments, configure a legacy DNS and associate it with Exchange 2007 Server (while the current one will be associated with Exchange 2010 CAS). The steps are not given here as they may vary according to the firewall configuration and internet provider.

  5. Install the Unified Messaging Role

    The Unified Message Role facilitates voice mail and fax in Exchange mailboxes. For installation and verification of this role on a dedicated server, follow the steps for the earlier roles, but select Unified Messaging Role on the Server Role Selection page.

    The next step after the installation of UM role is to configure and enable unified messaging. If you already have UM in Exchange 2007, transition it to Exchange 2010 using Exchange Management Console or Exchange Management Shell. If you do not have one in Exchange 2007, create and configure a dial plan, gateways, and mailbox policies for UM, and then add the UM server to a dial plan. Finally, enable users for UM so that they can start using the UM features.

  6. Install the Mailbox Role

    Mailbox Role is important as it hosts databases—both the mailbox database and public folder database. Its installation and verification procedure—except for the selection of Mailbox Role on the Server Role Selection page— are the same as for described earlier.

    As the next step, you can move the offline address book generation to Exchange 2010. Use the Move Offline Address Book wizard (of Exchange Management Console) to do this.

    NOTE: How to install a server role along with an already installed one?
    After the installation of the Client Access Role, it is possible to install Hub Transport, Unified Messaging, and
    Mailbox Roles on the same server. However, the procedure for this is slightly different from that for installing
    them on a separate server. Here is how you can do this:
    1. Select Microsoft Exchange Server 2010 from the list in Control Panel > Programs and Features, and select Change.
    2. Click Next in the setup wizard.
    3. Select the required role on the Server Role Selection page.
    4. Proceed as with the installation procedure and complete the process.
    5. Restart the computer.

  7. Install the Edge Transport Role

    The Edge Transport Role is different from the all other server roles—it cannot exist with any other server role as the other roles do. Its responsibility being antivirus and anti-spam filtering, it is deployed outside the AD forest (in the perimeter network) for security reasons. On the installation and verification side, the procedure is similar, but it is mandatory to deploy this role on a dedicated server.

    At this stage, you can subscribe the Edge Transport server—either subscribe to the new Exchange 2010 Edge server or transition the Edge subscription from Exchange 2007 to Exchange 2010. These actions can be done using the Exchange Management Shell (on Exchange 2010 Edge Transport server). And the subscription can be verified using Get-EdgeSubscription cmdlets.

  8. Migrate mailboxes/public folders to exchange 2010.

    Finally, move mailboxes and public folder data from Exchange 2007 to Exchange 2010.

    To migrate mailboxes from Exchange 2007 to Exchange 2010 by create local move requests in Exchange Management Console (Recipient Configuration > Mailbox). While creating a move request, you can select mailboxes for migration and can browse for the database to which they are to be migrated. After successful completion of the move, use Get-Mailbox cmdlets to the mailboxes on the Exchange 2010 database to get the list of mailboxes over there.

    To migrate public folders from Exchange 2007 to Exchange 2010 by replicate them using the Exchange Management Console (Toolbox > Public Folder Management Console). The public folder migration can be verified by using Get-PublicFolder cmdlets in the Exchange Management Shell.

  9. Perform the final tasks
    Again use Get-ExchangeServer cmdlets to verify the Exchange installation. You can license the product now. And finally, proceed to configure accepted domains, internal mail flow, Outlook Anywhere, internal SMTP server list, and safe list aggregation.

Exchange 2010 to Exchange 2016 migration
The second part of the migration involves upgrading from Exchange 2010 to Exchange 2016. For Exchange 2010 to Exchange 2016 migration, refer to our article “A quick guide for upgrading from Exchange 2010 to 2016”.

Another informative article to move mailboxes from Exchange 2010 to Exchange 2016 using Exchange Admin Center:

Exchange 2007 to 2016 migration using LepideMigrator for Exchange
LepideMigrator for Exchange helps you migrate directly from Exchange 2007 to Exchange 2016 (supports cross-forest migration only). The solution allows you to perform pre-migration analysis, synchronize Global Address List, migrate mailboxes and public folders, migrate limits and permissions, migrate Outlook rules & permissions and update Outlook profiles.

Pre-migration analysis
Before starting the migration, you can create and run a pre-migration analysis (for mailboxes and public folders) to get an idea of the approximate time required. To do this you have to provide the login credentials, network speed, no.  of agents used and the list of mailboxes/public folders to be migrated. After the analysis, the software displays the expected migration time.

Exchange 2007 to Exchange 2016 migration using LepideMigrator for Exchange
Exchange 2007 to Exchange 2016 migration project in the solution includes five simple migration jobs. Exchange administrators need to create and run the following jobs:

1.Mailbox configuration
2.GAL synchronization
3.Mailbox / Public folder migration
4.Outlook rule / folder permission migration
5.Profile manager

Creating a job is very easy. The screenshot below shows the first step towards creating a mailbox migration job (this step is similar for all other jobs).


When creating a job, you can opt to run them immediately or at any desired time. The screenshot below shows the options (under Run Job at) for running a mailbox migration job (the same options are available for all the jobs).


Mailbox configuration job
By creating and running a mailbox configuration job, you can migrate the limits and permissions of mailboxes/public folders from Exchange 2007 to Exchange 2016.


While migrating you can merge, reassign, replace or skip the permissions on the target Exchange with the permissions on the source Exchange. With Limits, you have the options to Replace and Skip.

GAL Synchronization Job
The GAL synchronization job lets you synchronize the Global Address List between the source and target Exchange Servers.


This job provides four options depending on how you want to create a GAL in the target.

  • Full Global Address List –  all addresses from the source
  • Partial Global Address List – selected addresses from the source
  • Full Container – all addresses from the selected source Container(s)
  • Partial Container – selected addresses from the selected source Container(s)

Mailbox / Public folder migration job
Mailbox / Public folder migration job migrates all or selected mailboxes/public folders from Exchange 2007 to Exchange 2016. Once you start creating the job, the wizard will lead you to various steps that can be performed by reading the instructions on the screen. Some important steps of the mailbox/public folder creation job are:

  1. Selection of the mailboxes/Public folders
    You can select mailboxes and public folders as per the requirement.
  2. Filtering
    You can filter the mailboxes and public folders for the required items. It helps to migrate only the selected items.
    You can filter mailboxes/public folders by the criteria message classes and date range. The items from a particular date range can be included or excluded. And for mailboxes, an option to include or exclude folders also is available.
  3. Synchronization
    LepideMigrator for Exchange allows you synchronize mailboxes and public folders so that any change on end will be reflected in the other end depending on the selection you have made).
  4. Notifications
    Configuring notifications helps you get notified at different stages of the migration.
    Note: For this, you need to configure Notification Setting (see the Tools > Notification Settings in the Tool bar) in the beginning.
  5. Setting migration time
    You can set the time period during which migration is to be done. This option helps to pause the migration in office working hours.
  6. Outlook rules/folder permission migration jobs
    LepideMigrator for Exchange helps you migrate Outlook rules and folder permissions from Exchange 2007 to Exchange 2016.
  7. Profile Manager job
    After the completion of all other jobs, you can use the Profile Manager to update the Outlook profiles of the migrated mailboxes.

Why LepideMigrator for Exchange is the better option for migrating from Exchange 2007 to 2016
LepideMigrator for Exchange allows you to migrate directly from Exchange 2007 to Exchange 2016. You do not need to use Exchange 2010/2013 as a go-between. The solution allows anyone, regardless of technical ability, to accomplish this migration easily as no in-depth knowledge of Exchange Server architecture is required. The solution’s load sharing feature enables migrations with low server resources. Its Report Console also provides complete details of the migration.

Article Summary
To upgrade from Exchange 2007 to Exchange 2016 is a two staged process—first you need to upgrade from Exchange 2007 to Exchange 2010/2013 and then from Exchange 2010/2013 to Exchange 2016. LepideMigrator for Exchange, however, simplifies the migration of mailboxes and public folders – by allowing you to directly move mailboxes and public folders from Exchange 2007 to Exchange 2016.

Product Review – Stellar Phoenix SQL Database Repair

Microsoft has marketed several versions of SQL Server, which is its proprietary relational database management system (RDBMS) until now. All the available versions are aimed at satisfying audiences from different backgrounds and with different workloads that can range from a small single-machine to large Internet-based applications, with a lot of concurrent users.

Although built with enhanced internal underlying technology with its each new version coming into being, they do get corrupt making the objects in the database inaccessible. This brings in the requirement of not just any, but an MS SQL Repair software that has the capability to restore the SQL Server database saved as MDF and NDF format.

A tried and tested software for repairing the corrupt database files of MS SQL Server and making the stored objects accessible once again is Stellar Phoenix SQL Database Repair. The SQL Database Repair utility by Stellar, a leading Data Recovery company, can resolve all corruption issues of SQL Server database by fixing the errors that one encounters while working with it. Following that, it can retrieve all data objects from the primary MDF and secondary NDF files that became inaccessible due to the damage caused.

The software is devised with multiple features so as to repair the server’s database files. They have been found to be powerful enough to recover data objects without data loss while maintaining the database integrity. Additionally, it promises MS SQL repair irrespective of the severity of corruption, and in maximum cases has been found to achieve what it assures. However, one needs to configure and run the software to experience what it offers. Listed below are some of its significant features:

  • It can repair all the MDF and NDF files of your damaged SQL Server database.
  • It has a fast scan feature so that the issues can be identified and fixed quickly, leading to the recovery of the stored objects.
  • It can retrieve the database components: tables, triggers, views, keys, rules, indexes, and defaults
    • Keys – Primary Keys, Foreign Keys, Unique Keys, and Identity.
    • Indexes – Clustered and Non-clustered indexes
  • It can recover even the ROW and PAGE compressed data
  • It allows you to preview the recoverable objects post scanning
  • It permits you to search for MDF files on the PC as well as specific objects and recovers them.
  • It reconnects to the server automatically when disrupted so as to complete the repair process

Here a review of Stellar Phoenix SQL Database Repair 6.0 is presented which is its latest released version. It was released for use in October last i.e., 2015. Devised to repair corrupt Microsoft SQL Server database MDF and NDF files, its latest version of the software provides enhanced features which have increased its capabilities to the next level. In addition to the above-stated benefits, this particular version offers several new and advanced features which is listed below:

  • It provides support for the 2016 release of MS SQL Server which is the latest available version in addition to SQL Server 2014, 2012, 2008, and all other lower versions.
  • It offers to recover deleted records with the help of an extraordinary feature embedded in the software.
  • It provides the option to move and save database files to Live SQL database post repair.
  • It gives you the option to save the fixed database files in XLS, CSV, and HTML formats in addition to MS SQL.

However, to be able to achieve what the software is devised for, you need to fulfill certain system requirements which are as follows:

  • The system must run on only a Pentium Class processor.
  • The Operating System can be any of the following: Windows Server 2008 or 2003, and Windows 10, 8, 8.1, 7, Vista, and XP.
  • The memory should be at least 1 GB; however, the recommended is 2 GB.
  • Lastly, the hard disk in the system must contain at least 50 MB of free space so as to have the software installed.

Note – The system requirements are easy to achieve and are present in almost all Windows systems.

Steps to Repair Damaged MS SQL Server MDF & NDF File

This SQL database repair software has three simple steps to repair the damaged SQL Server database files and recover its data items. They are Select, Repair, and Save.

  • Select – You can select the corrupt database with the ‘Select Database’ tab present in the interface, provided you know the location. But if the location is unknown, you should look for ‘Find Database’ section and click on the tab ‘Search in folder’ followed by a click on the tab ‘Find.’ If you want the software to find the database file in sub-folders as well, you should check the option ‘Search in sub-folders.’ Also, place a check mark in the checkbox ‘Include deleted record’ to scan for and recover the deleted records.

Main Interface

  • Repair – Once the MDF file is selected, click on the ‘Repair’ tab to begin the scanning process. With this, over some time a preview of the database objects that can be recovered is prompted on the screen. After that, a message will appear on the screen of your system that the selected MS SQL database has been successfully repaired, and then click on ‘OK’ to save the file in a new database. The screenshot below showcases the repair and preview step.


  • Save – To save, you have to complete the software registration process by entering the serial number sent through email. Then, you can save the recovered items in MS SQL, CSV, HTML, and XLS formats. You get the option of saving in the new database and live database that can be selected as per want. Finally, the repaired file and the retrieved objects are saved. The screen shots below display the ‘saving’ step.

Saving Options


Save Formats

Inference Drawn

Stellar Phoenix SQL Database Repair 6.0 is an ideal MS SQL 2016 Repair software. This is because it accomplishes almost all the guaranteed benefits without fail. Moreover, the interface is easy-to-use and can even be understood by a lay person as well. All you need to do is install it properly on your system to repair the damaged SQL database file. The software is available only in English for now; hence, only the English-speaking populace can leverage it meanwhile.


PowerShell script to download all Farm solutions

MSTechTalk PowerShell

Some time we got requirement to download farm solutions and it is specially required in migrations. Below I am sharing a simple PowerShell script which can download all solutions deployed on the SharePoint Farm. You need to execute  this script on SharePoint Farm with SPFarm account as this script need SharePoint Farm administrative access to execute.


function DownloadAllFarmSolutions()
#Get reference to SharePoint farm
$farm = [Microsoft.SharePoint.Administration.SPFarm]::get_Local()

#Path to save the solution files, Create the folder before executing script
$path = “C:\SPSolutions”

#Download all the farm solutions

foreach($spSolution in $farm.Solutions){

$spSolution = $farm.Solutions[$spSolution.Name]
$file = $solution.SolutionFile
$file.SaveAs($path + ‘\’ + $spSolution.Name)

Execute the script on PowerShell and then call the function DownloadAllFarmSolutions which will save Farm solutions on specified path.

This script has been tested on SharePoint 2010, SharePoint 2013 and SharePoint 2016.

Beta Exam for SharePoint 2016 is now available (Exam 70-339)

Microsoft has announced Beta exam 70-339 for SharePoint 2016 , there are 350 beta seats allocated for the exam.

You can register for exam through exam link page and use code  BETA339MCP, this code is only for exam dates till July 11, 2016.

You can check BorntoLean post for more details :

Exam Link:

Preperation Matrial:

You need to take below two instructor led training for exam preparation:

Restricted Countries:

The beta code will not work in few countries which include Turkey, Pakistan, India, China, Vietnam.

Migrating to Exchange 2016 using the Exchange Admin Center

MS Exchange Server 2016 comes with advanced facilities that enterprises can’t wait to benefit from. Architecture simplicity, reliability, improved email-client features and cloud readiness are the hallmarks of this version. But when it’s time to upgrade to this new Exchange version, the existing Exchange data needs to be moved to it. So let’s go through the options available for mailbox migration, especially from Exchange 2010.

Is direct migration to Exchange 2016 possible from all previous versions?

Exchange 2016 supports direct migration from Exchange 2010 and Exchange 2013 only. Direct migration is not possible from Exchange 2007 and previous versions unless you use third-party migration solutions.

Why migrate from Exchange 2010 to Exchange 2016 now?

Exchange 2016 will possibly be the last Exchange version to which Exchange 2010 mailboxes can be migrated directly using the built-in features of Exchange.

What are the requirements for successful Exchange 2010 to Exchange 2016 migration?

Apart from hardware, OS, and email client requirements, co-existence between Exchange 2010 and 2016 Exchange versions is required for the migration. For co-existence with Exchange 2016, you should have Exchange 2010 RU11 or later (in all servers). You can get updates from Microsoft sites to fulfill these minimum criteria.

How to move mailboxes from Exchange 2010 to Exchange 2016 using Exchange Admin Center

You can use the Exchange admin center (EAC) as well as Exchange Management Shell (EMS) to move mailboxes from the Exchange 2010 database to Exchange 2016 database. Here we will show you the migration steps using EAC:

  1. Open Exchange admin center and sign in.
  2. Go to recipients>migration and click; select Move to a different database.
Move to a different database

Move to a different database

  1. Select the option, Select the users that you want to move; click  and add users (you can add users in the Select Mailbox window).
New Migration Batch

New Migration Batch

Note: Users can be added using CSV file option too.

  1. Click Next when mailboxes are listed.
New Migration Batch

New Migration Batch

  1. Enter a name to the mailbox move. Under Archive, select the option Move the primary mailbox and the archive mailbox if one exists. Provide the target database name and bad item limit (ideally you can give bad item limit as 10). Click Next.
Migration Batch

Migration Batch

Note: The Browse button opens up the Select Mailbox Database window where you can select and add an Exchange 2016 server mailbox database.

  1. Enter the user to whom mailbox move reports are to be sent (the default entry can be modified using the Browse button); keep the option Automatically start the batch If you want to complete the migration automatically, keep the option Automatically complete the migration batch selected. Finally click New.
Migrating to Exchange 2016

Migrating to Exchange 2016

Note: To manually complete the mailbox move

In recipients>migration, select the mailbox migration batch that is to be moved; click Complete this migration batch in the details pane (available only when batch is ready for completion).

  1. Now in recipients>migration, you can check the mailbox migration status in the details pane by selecting the migration batch. Click View details to get more details.
Exchange 2016 Admin Center

Exchange 2016 Admin Center

Are there simpler ways to migrate Exchange 2010 to Exchange 2016?

Professional Exchange migration solutions make Exchange/Office 365 to Exchange/Office much simpler and easier. They support the latest as well as all popular versions of Exchange for migration. LepideMigrator for Exchange is a reliable and trusted solution used by many organizations across the world.

Blog Summary

After the successful deployment of Exchange 2016, organizations have to move their Exchange 2010 mailboxes to the new Exchange. You can use EAC or EMS to accomplish this migration. However, because of the complexities involved, most of the organizations rely on Exchange migration tools.

SharePoint Server 2016 Hardware and Software Requirements

SharePoint Server 2016 release candidate patch has been released few days back which need to be applied on SharePoint Server 2016 Beta 2. In this post I just summarized the hardware & software requirements and Installation prerequisites which are already listed on different sites, at the end of this article you can the listing of few important links which give you more details on below listed information and also helpful how you can apply Release Candidate patch on SharePoint Server Beta 2.

Operating System

  • Windows Server 2012 R2
  • Windows Server 2016 Technical Preview 4

Software Requirements:

  • Microsoft SQL Server 2014 Service Pack 1– (64-Bit)
  • SharePoint Server 2016 Beta 2
  • SharePoint Server 2016 Release Candidate Patch

Hardware Requirements:

Below table shows the standard hardware requirement for Single Server installation or Multi-server installation.

SharePoint Server 2016 Hardware Requirements

SharePoint Server 2016 Hardware Requirements

Deployment Type:

  1. Two computer farm with:
  •      One SharePoint server that uses the Single-Server role.
  •      One SQL Server
  1. Four or five computer farm with:
  •      One SQL Server
  •      One Front-end web server.
  •      One Application server.
  •      One Distributed Cache server.
  •      One Search server.

SharePoint Server 2016 installation Pprerequisites

  • Windows Identity Foundation
  • SQL Client
  • Microsoft Identity Extension
  • Microsoft Sync Framework 1.0 SP1
  • Windows Server App Fabric
  • AppFabric 1.1 Cummulative Update
  • Active Directory Rights Management Services Client 2.1
  • Windows Communications Framework Data Services 5.6.0
  • .NET Framework 4.6
  • Visual C++ 2013 Redistributable Package
  • Security Update for .NET 4.5.2

Some important links are listed below:

Disassociating InfoPath Forms from list in Office 365


We did migration of SharePoint 2010 from SharePoint online using a 3rd party migration tool. Content migrated successfully but with time we got some issues from the users regarding the behavior of the new environment and issues after migration


SharePoint list view is showing data in the list but view/edit forms got corrupted after migration.


We have gone through the requirement, there were InfoPath forms used with the SharePoint List which are migrated to SharePoint online but were not associated properly. There were no business rules in the InfoPath which means those were basic view and edit forms. So we decided to disassociate the InfoPath forms from list. The basic steps are:

Go to List settings and under General click on Form Settings (option only working in IE), where you can get the option to disassociate the InfoPath form. But things are not quite lucky for us here because we can’t see the option to dissociate InfoPath form. Check below screen for reference:

Form setting not showing Default Sharepoint form option

Form setting not showing Default Sharepoint form option

It is not showing the option “Use the default SharePoint form” which I can see in SharePoint 2010.

Now open the SharePoint online site in SharePoint Designer 2013 to disassociate it in Office 365. Go to your SharePoint List through List and Libraries, and click on Item under the Content Type section which will take you to the item content type detail page.

SharePoint Designer List and libraries

SharePoint Designer List and libraries

In Forms section in above picture, you can see the associated InfoPath forms with the item content type. Click on the form path and remove it, this is how you can disassociate InfoPath forms from list manually.

disassociate InfoPath forms from list manually

disassociate InfoPath forms from list manually

The other solution is that you from list ribbon, click on the InfoPath form settings and publish the InfoPath form, if there any were any rules which are not showing up then you have to create them again.