Office can't be activated because it doesn't meet the requirements for running on remote

 Error :

When user tries to open office applications and gets the error,

 

Office can't be activated because it doesn't meet the requirements for running on remote

 

in Terminal/RDS server the following error may occur:

This copy of Microsoft Office 2016 cannot be used on a computer running Terminal Services. To use Office 2016 on a computer running Terminal Services, you must use a Volume License of Office.

 

Troubleshoot:

Please confirm whether the office product installed as Office 365 ProPlus on a remote desktop server through ODT deployment.

 

Fix/Solution:

If it is not installed by ODT then try to install using ODT installation method.

 

If yes,

Open the registry editor (Win+R > regedit) and go to this path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

Add the SharedComputerLicensing (Reg_SZ) key and set its value to 1.

(or)

Press Win+R and run gpedit.msc to open the local group policy editor.

Edit the policy or create this policy if it doesn’t exist:

Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Licensing Settings

Enable the 'Use shared computer activation'.

Error: bad allocation Failed to upload disk in Veeam backup

 

Issue:

When I try to backup Hyper-V environment got the below error, 

Error: bad allocation Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: Reconnectable protocol device was closed. Unable to retrieve next block transmission command. Number of already processed blocks: [825]. Failed to download disk 'FIleName.vhdx'.  

Cause:

Bad Allocation - This issue due to high usage of either CPU or memory.

Fix:

Checked the Hyper-V and found that the VM is using too many resources (both CPU and memory), try to reduce the resource usage or reboot the server to make server normal usage.

---

Once server became normal backup started work normally.

Unable to create azure subscriptions : check the user has administrative privilages on the specific Azure account

Issue: 

I'm trying to restore whole VM in from Hyper-V backup job in to MS Azure. When I add account in to Veeam server getting below error,

"Unable to create azure subscriptions : check the user has administrative privilages on the specific Azure account "

We are not sure why Veeam is trying to create a new subscription while adding credential. Could you check and help us to check this case.

We found only below log in our log files

[19.10.2021 14:40:46] Info Connecting to Azure by Power Shell
[19.10.2021 14:40:46] Info Login to Azure Account
[19.10.2021 14:40:46] Info [PS] 'Add-AzureRmAccount'. Arguments: EnvironmentName='AzureCloud'.
[19.10.2021 14:41:04] Info [PS] 'Get-AzureRmContext'. Arguments: .
[19.10.2021 14:41:04] Info [PS] 'Get-AzureRmADApplication'. Arguments: IdentifierUri='https://VeeamAzureApp';ErrorAction='SilentlyContinue'.
[19.10.2021 14:41:05] Info [PS] 'Get-Module'. Arguments: n/a.
[19.10.2021 14:41:07] Info Registering application in AD
[19.10.2021 14:41:07] Info [PS] 'New-AzureRmADApplication'.
[19.10.2021 14:41:07] Info Disposing splash form
[19.10.2021 14:41:07] Error [Veeam Backup and Replication] Unable to add Azure subscriptions: check that user has administrative priviliges on the specified Azure account

my Finding:

I have tried to add account under the version 10.0.1.4854 and got this error, however after I upgraded to veeam 11 it works fine.

Note : I believe this is Veeam version issue and raised the issue to Veeam Team but they refused it. Someone has same issues on Veeam 10 and fixed it?

Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

Issue/Error: When we try to backup the VM in veeam backup server, we gets  exception like below,

Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

Root Cause:

When backup jobs starts and proxy will assign automatically, but assigned proxy doesn't have access for the disk, so unable to access the disk and got failed.

Fig 1 : Backup proxies for HD1 and 2 don't have access permission.

Fig 1 : Backup proxy for HD 2 doesn't have access permission.

Solution:

1. Assign the proxies which has right permission.(Change the proxies to manual in backup job settings and and assign it)

2. Check the proxies that has same IP range as you Hyper-V/Vcenter node, so access using proxies will not get any issues.

Find PID for VEEAM backup job

Kill veeam backup job using Process ID

Issue: Sometimes veeam backup job won't complete (hung) in particular time and it does not backup any data, so when we try to stop the job and it won't help us and will remain in stopping state. So killing the backup job is only option using PID.

So we can find the corresponding backup job's PID using their log file.


Solution: The default log path C:\ProgramData\Veeam\Backup and you can find .LOG file with the below format.

JOB.<JOB_NAME>.backup.log  Filter those files with modified date and pick the latest date log file and Search PID: Kill the job using taskkill option. Note: When backup job starts meanwhile in background there are a lot of MSSQL transaction will  start for the backup job, If you kill the backup job using PID it may lead to corrupt backup job, try using your own risk. So mostly this is not a recommended way to stop the running backup jobs.

This item cannot be deleted because it is still referenced by other pages in SharePoint 2013

I got the error This item cannot be deleted because it is still referenced by other pages, when I delete a Test.master and Test.html files from SharePoint 2013.

I have checked more suggestions and solutions from Google, but no one suggestions and solutions helps me.

Somebody suggest me to do  Create a folder, move the master page into the folder, delete that folder through SPD. MS blogs suggests to Hide the File using this link http://support.microsoft.com/?kbid=926812 (This trick for MOSS 3.0 i.e SP 2007). Some people told me to use SCRIPT ( http://blogs.msdn.com/b/kvosters/archive/2011/10/12/this-item-cannot-be-deleted-because-it-is-still-referenced-by-other-pages.aspx ), and many more suggestions. I spent more than Two days for this issue, but no more improvement. That time my colleague give the below Solution. It works fine.

Please try this,

1) My Issues with Test.html and Test.master

2) Go to Root Site, Site Settings->Look and Feel Section: Design Manager. Here the Master Page Html file can          be modified what changes are we make in .master file.

3) But Site Settings->Look and Feel Section: Design Manager ->Edit Master Pages Test.html was missing.(By default Seattle and Oslo will be appear)

4) Open the site collection through SharePoint Designer, Right click on Seattle.html file -> Select "Edit File in Advanced Mode" from context menu.

5) Seattle.html opens in a new Tab. Select all and copy the code.

6) Then Go to Test.html (Right Click) -> "Edit File in Advanced Mode". Opens in a new tab.

7) Replace the existing code in the "Test.html" by pasting the code from Seattle.html

8) Save the file (This is done in "Check In" status)

9) In the Browser, Go To Root Site, Site Settings -> Look and Feel: Design Manager -> "Edit Master Pages" in the left side.

10) Now here the Test.html file will appear. Delete this file.

11) Check the "Delete" Folder. Here the files will be removed automatically. Delete the Delete folder.

Archieve/Backup Visual SourceSafe file using CMD

@ECHO OFF
@TITLE Backing up source safe databases
FOR /F "tokens=2-4 delims=/ " %%i IN ('date /t') DO SET DATE=%%k%%j%%i
FOR /F "TOKENS=1-2 DELIMS=: " %%I IN ('time /t') DO SET TIME=%%I%%J
FOR /F "TOKENS=2 DELIMS= " %%K IN ('time /t') DO SET AMPM=%%K
"C:\Program Files\Microsoft Visual SourceSafe\ssarc" -d- "E:\Today.ssa" $/ "-sE:\Vss-Projects" -yadmin,pass@word1
@ECHO Finished backups


Here - C:\Program Files\Microsoft Visual SourceSafe\ssarc is SourceSafe Archieve application (ssarc.exe) path
E:\Today.ssa - Backup File Location and Name
E:\Vss-Projects - Current Srcsafe stored Location.
admin and pass@word1 is credential for the VSS admin who has permission to backup and restore. 

Add a crawled property in SharePoint 2013 with sortable/Refinable using Powershell

Add a crawled property in SharePoint 2013 with sortable/Refinable using Powershell

For Sortable:

New-SPEnterpriseSearchMetadataCrawledProperty -Category SharePoint -IsNameEnum $false -Name "ows_MyCrawledProperty" -PropSet 00130329-0000-0130-c000-000000131346 -SearchApplication "Search Service Application" -VariantType 0
 
New-SPEnterpriseSearchMetadataManagedProperty -Name "MyCrawledProperty" -SearchApplication "Search Service Application" -Type 1 -Queryable $true -Retrievable $true
 
$cp = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication "Search Service Application" "ows_MyCrawledProperty"
 
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication "Search Service Application" -Identity "MyCrawledProperty"

$mp.sortable= $true

$mp.update
 
New-SPEnterpriseSearchMetadataMapping -SearchApplication "Search Service Application" -CrawledProperty $cp -ManagedProperty $mp


For Refinable:

New-SPEnterpriseSearchMetadataCrawledProperty -Category SharePoint -IsNameEnum $false -Name "ows_MyCrawledProperty" -PropSet 00130329-0000-0130-c000-000000131346 -SearchApplication "Search Service Application" -VariantType 0
 
New-SPEnterpriseSearchMetadataManagedProperty -Name "MyCrawledProperty" -SearchApplication "Search Service Application" -Type 1 -Queryable $true -Retrievable $true
 
$cp = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication "Search Service Application" "ows_MyCrawledProperty"
 
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication "Search Service Application" -Identity "MyCrawledProperty"

$mp.Refinable= $true

$mp.update
 
New-SPEnterpriseSearchMetadataMapping -SearchApplication "Search Service Application" -CrawledProperty $cp -ManagedProperty $mp

Error: cannot generate SSPI context

Issue: Got the error cannot generate SSPI context in 2008 sql, when I access 
(machine1) Destination machine’s SQL instance from (machine2)Source Machine SQL instance.

Solution: Checked the error machine<machine1> is remote accessible using machine name and got the below error.

Remote Desktop Connection fails - outdated entry in the DNS cache.

Took RDP using IP, Works fine and checked the time, the time was off by an hour. 

Run the below comments in cmd

· net stop w32time

· net start w32time

The both the problem has been solved.