The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.


If you are facing this error message when trying to RDP to a Domain-joined Server :

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.


1st to check is as told by the message; DNS configuration. Client-side and Server-side.

If that’s fine, the problem is elsewhere.

You should be able to connect using the IP address


using the Hostname but login with a Local Account instead of a Domain Account.


If I’m correct, your Server CLOCK is not Synchronized with your Domain. Simply Sync it using w32tm or modify it manually and try to connect.


Hope this helps.


The operation could not be completed, because the server that you specified requires a restart


When trying to install a Role which require to install WID (Windows Internal Database), you could face an issue where it won’t install and throw this error message:

The operation could not be completed, because the server that you specified requires a restart

If we look at the Event viewer, we can find the following error:



The solution is to add “NT SERVICE\MSSQL$MICROSOFT##WID” the permission to  “log on as a service”.

It can be done by editing the “Default Domain Controller” GPO:

Computer Configuration –> Policies –> Windows Settings –> Security Settings –> Local Policies –> User Rights Assignment branch and then double click the ‘Log on as a service’ setting.

Finally, run a “gpupdate /force”, restart and the Role installation should now work!

Note: In my case when the Role installation failed, it created the WID user. I was then able to add it my GPO. But after a restart, it has been removed and therefor showing as an missing SID. But anyway, it solved the problem too. Maybe the SID is kept as it is.


Hope this help!


Remotely SQLPlus as sysdba – ORA-01031: insufficient privileges


SQLPlus as SYSDBA remotely can throw the following error due to security reason :

>sqlplus sys/syspass@servername/instance as sysdba

SQL*Plus: Release Production on Mer. Ao¹t 30 14:25:48 2017

Copyright (c) 1982, 2011, Oracle. All rights reserved.

ORA-01031: insufficient privileges


To allow to connection, connect locally using SQLPlus and make sure the parameter “remote_login_passwordfile” is set to ‘”EXCLUSIVE” :

SQL> show parameter remote_login_passwordfile

------------------------------------ ----------- ------------------------------
remote_login_passwordfile string EXCLUSIVE


Then check a password file exist for your instance :

SQL> select * from v$pwfile_users;

no selected row.


It appears it does not exist and needs to be created to allow remote connection. We will create on a Windows Server and I will refer to Oracle doc

D:\oracle\11.2.0\db\BIN>orapwd.exe file=D:\oracle\11.2.0\db\database\PWDINSTANCENAME.ora

Enter password for SYS:


You can now log on remotely.

Oracle Veeam Backup | VSS_FAILED_AT_FREEZE | ORA-00257: archiver error from remote SQLPlus | ORA-16038 ORA-19809 ORA-00312 found in Eventvwr | Fast Recovery Area is Full

Today, I was facing an issue where my Veeam Backup job failed on one Oracle Server hosting many Instances.

Only one of them was failing and Veeam reported the following error :

Processing SERVER_NAME Error: Unfreeze error: [Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
A VSS critical writer has failed. Writer name: [Oracle VSS Writer - INSTANCE_NAME]. Class ID: [{26d02976-b909-43ad-af7e-62a4f625e372}]. Instance ID: [{bf669252-5552-433d-a0b5-cab28e14a19b}]. Writer's state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f4].]


Checking the Server Eventlogs reported Event 46, Oracle.VSSWriter.INSTANCE_NAME

General Tab :

VSS-00046: failure to switch the current database redo logs

Cause : OCI call failed.

Action : Check the accompanying error message.

Additional info :
Oracle Database 11g Enterprise Edition Release - 64bit Production
Oracle VSS writer version Production
Error at line : 4856
Failure on Freeze event

Details Tab reported (example copied from Internet) :

ORA-16038: log 1 sequence# 49 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:


Also, trying to connect remotely using SQLPlus trowed the following :

ORA-00257: archiver error. Connect internal only, until freed.


With all these information, I suspected the Fast_Recovery_Area to be full and it has been confirmed by running the following SQL statement (locally to avoid SQLPlus connection issue explained above) :


----------- ---------- ----------------- ---------------
 4322230272 3,4490E+10 759962624 809

Indeed, it is more than full.


Finally, I tried to delete expired Archivelogs using RMAN but it did not find any files to delete. It’s why I suggest to 1st run a Crosscheck and then delete expired items :

  • Start RMAN in a Command Prompt
  • Connect to your Instance
rman > connect target SYS/oracle@trgt
  • Run a Crosscheck
rman > crosscheck archivelog all;
  • Delete expired Archivelogs
rman > delete expired archivelog all;


In my case,  after deleting expired Archivelogs, the FRA was still Full so I decided to simply delete all of them and just keep the last 10 days by running :

rman>delete archivelog until time ‘SYSDATE-10’;


Veeam Backup & Oracle VSS is now working, Remote SQLPlus connection too. Solved. Hope this helps.

BGInfo – Display Windows information on Background and deploy using GPO


I have just set up BGInfo on my Servers and I will share with you the steps I followed to get it customized and deployed through GPO.


At the time I write this, the version is 4.22.


  • Extract it and copy Bginfo.exe to \\domain.local\NETLOGON\BGInfo\

BGInfo folder has to be created. If you face permission problem, logon to your DC and create it in its local location : C:\Windows\SYSVOL\domain\scripts\BGInfo


  • Run Bginfo.exe and customize it to suit your needs.

I will not explain how it works as it’s pretty simple. Once configured, save it (File – Save As) in the same folder. You can name it what you want. for this example I used “Bginfo.bgi”.


  • Create a new Batch file in the same folder, in this example named “Bg_script.bat” which will contain the following and will be executed by your GPO in the next steps :
@echo off
\\domain.local\NETLOGON\BGInfo\Bginfo.exe /nolicprompt /timer:0 \\domain.local\NETLOGON\BGInfo\Bginfo.bgi

The argument “/nolicprompt” remove the licence agreement and “/timer:0” apply it without delay. For more information on arguments, check the download link given above.


  • Create a new GPO and link it to your Servers Organization Unit. The settings I used are :


As you can see, the script is executed at Logon on User’s context (yeah I know, I said to apply the GPO on your Servers Organization unit). This is why the GPO Loopback Processing mode is enabled. For more information, consult Microsoft documentation here :


  • Ok, at next logon, you should have your new BGInfo applied.

In my case, it’s mostly instant on Windows Server 2008 (R2) but takes a few seconds/minutes on Windows Server 2012 (R2).

Hope this helps!



The trust relationship between this workstation and the primary domain failed

Hello everyone,

Here is an easy fix to solve the broken relationship between your workstation and the Domain Controller.

Error message at logon : The trust relationship between this workstation and the primary domain failed


  • Logon locally with the Administrator account : “.\Administrator
  • Run Powershell as Administrator
  • Run the following to prompt you to enter your Domain Admin user account credential
$credential = Get-Credential
  • Finally, run the following to reset your AD Computer Password
Reset-ComputerMachinePassword -Server <DomainControllerName> -Credential $credential


You should now be able to log you in as a Domain User.

Clone and Sysprep VM without vCenter Server

When running vCenter Server, you can clone the VM and it will prompt you for new customization settings.

Without it… You will need to manually copy the VM files (or only the VMDK if you attach it to a newly created VM). Then run Sysprep to configure it and avoid duplicate SID.

  • Shutdown your VM and copy its files or VMDK to a new folder on the current or new Datastore. If you want to rename the VMDK file, copy it using “vmkfstools”.

Example :

vmkfstools -i /vmfs/volumes/server/server1.vmdk /vmfs/volumes/datastore1/cloned-server/server2.vmdk -d thin
  • Create a new VM and attach the cloned VMDK. If all files have been copied, just register the VMX file to the Inventory.
  • Boot up the VM and run Sysprep :
sysprep /oobe /generalize /reboot
Tips : You can use the switch /shutdown to turn it off after customization and then convert it to a VM Template if needed.
  • VM will reboot and ask you for customization settings.
Another and easier way to accomplish this task is to use VMWare vCenter Converter Standalone during the “Convert Machine” GUI. Or if you forgot it, you can do it through the “Configure Machine” GUI.