Ls_Restore job failed every-time when executed through job throws error “Executed as user: Domain\UserAccount. The step failed.”

Disclaimer:Hey Guys, this post contains affiliate link to help our reader to buy best product\service for them. It helps us because we receive compensation for our time and expenses.

Note:  Best viewed in Internet Explorer 6 and above

Implementation: Configure Log shipping in SQL server 2016.

Scenario: Today I have faced very strange issue while configuring log shipping in SQL server 2016 standard edition.

The prerequisites for configuring log shipping were already been taken care.

  1. The backup log job (ls_backup) was happening as per its schedule.
  2. Copy job, copying TRN file to DR server with issue
  3. Here comes ls_restore job, this job was failing continuously when it was being from ls_restore job and throwing   “Executed as user: Domain\UserAccount. The step failed.” every time.
  4. I rechecked log shipping prerequisites ,verify logins and its rights everything but no luck

Infrastructure: Log shipping between SQL server 2016 standard edition.

Resolution:

1.SQL server 2016 requires .NET framework 4.2 as the prerequisites It was already there.Mostly people think that If you have .NET 4.2 that fine.

2. But here for log shipping it is require to have .NET 3.5 features enabled as well for the backward compatibility.

3.Install .NET framework 3.5 on DR server restart DR server and now let the ls_restore job run with its schedule time.

4.Now you will see that the log shipping will be running fine with no issue further.

This was really strange issue, since it is recommended to have .NET 3.5 enabled on server whether you already have 4.2 framework installed.

Hope this will help few DBAs who can come across with such issue “Executed as user: Domain\UserAccount. The step failed.”

Dear Visitors!
To get Best Deals and Discounts Buy Now from Amazon just by
Clicking This Image

Simply send snap of your product details after delivery at ad22092012@gmail.com for more surprises or additional discounts

 

 

 

 

 

 

How to Fail-over MSDTC and Quorum Resources in Windows server 2003/R2 cluster

Disclaimer:Hey Guys, this post contains affiliate link to help our reader to buy best product\service for them. It helps us because we receive compensation for our time and expenses.

Note:  Best viewed in Internet Explorer 6 and above

Implementation: How to Fail-over MSDTC and Quorum Resources in Windows server 2003 R2 cluster.

Scenario: Today I have been asked to fail-over the MSDTC and Quorum cluster resources to another active node where SQL server resource group was online and owned.

Consider two node NODE15 and NODE16 and active/passive cluster scenario.

  1. SQL Server resource was owned by Node15 (Assume)
  2. MSDCT and Quorum was owned by Node 16(Assume)

Since the MSDTC and Quorum was owned by NODE16 hence the its drives,network name and IP was also owned by NODE16.

So client wanted to move resources back to NODE15.

InfrastructureThis steps are for the Windows server 2003/R2 cluster only.

The Fail-over cluster is totally changed,manageable and handy from windows server 2008 onward.

For Windows server 2003/R2 it is bit confusing.

Here I am going to guide how to fail-over the MSDTC and Quorum resource to another node.

Step 1:

Go to Server NODE16–>All program–>fail-over cluster manager–>Expand the Windows fail-over cluster name–>expand the group–>Highlight the MSDTC group

Once you highlight the MSDTC group, on right pane you will see its resources list like Disk,IP and network name.

MSDTC Resource.png

Note: Here the MSDTC group resources are online ad owned at NODE16

Step 2:

Now right click on the MSDTC group and select the option move group as per image above.
The MSDTC group is separate group

Note: As soon as you click move group, Cluster manager start moving resources to NODE15 and you can see the change in status on right pane.

Step 3:

Move Quorum Disk:

Go to Server NODE16–>All program–>fail-over cluster manager–>Expand the Windows fail-over cluster name–>expand the group–>Highlight the cluster group

Once you highlight the cluster group, on right pane you will see its resources list like cluster name,IP and Quorum disk.Qourum disk.png

Note: As soon as you click move group, Cluster manager start moving resources to NODE15 and you can see the change in status on right pane.

This is how you can fail-over the MSDCT resources and Quorum disk in windows server 2003/R2.

Hope this will help out for those DBA who may receive same requirements from client.

Dear Visitors!
To get Best Deals and Discounts Buy Now from Amazon just by
Clicking This Image

Simply send snap of your product details after delivery at ad22092012@gmail.com for more surprises or additional discounts