Author: iulian

Occasionally, and for no particular reason, my computer will no longer establish Remote Desktop connections to any computer. When trying to connect, I get the error message “The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.” The issue seems to stem from a corrupt registry key, so the best way to resolve the problem is by removing that key from the registry and allowing Remote Desktop to recreate it. The fix is basically the same for Windows XP through Windows 7, though Vista/7 may require one more step.

 

1. Log in as an Administrator.

2. start regedit

3. delete key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing 

4. Reboot your computer.

5. Start ( “Run as Administrator” ) Remote Desktop.

To boot past Windows 8’s Start screen and go directly to Windows 8 desktop, you need to make a simple registry tweak. Do the following:
While in Windows 8 (desktop or Start screen, it doesn’t matter), open regedit. If you don’t know how to run regedit, read dotTech’s How to run Register Editor in Windows 8 guide.
When you have regedit open, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon:

At the Winlogon registry folder, look for the registry entry named Shell, right-click it, and hit modify:

Once you right-click Shell and hit modify, a dialog box will pop open. In that box, there will be a Value data field which will say explorer.exe. Change explorer.exe to “explorer.exe /select,explorer.exe” (without the quotes) and hit OK:

Close Registry Editor.
Done! Restart your computer (click here to learn how to restart Windows 8, if you don’t know how) and upon boot you should see Start screen appear for a split second after which you are taken to Windows 8 desktop automatically:

 

 

 

 

v1:

If you are using win xp pro and outlook 2003 and can’t open Tif files in outlook.

Here is what you can do:

This problem known by Microsoft

In safe mode go to:
C:\Documents and Settings\username\Local Settings\Temporary internet Files\olk xxx

then delete this library contents.

if you cant see this library – open the hidden files and folder in the folder option

Now restart the computer to normal mode, open the outlook
and open the tif files

 

v2:

When opening an attachment directly from within Outlook you could get an error message saying that it can’t create the file and to that you need check the permissions on the folder you want to save it in. In most cases the permissions on the folder isn’t the issue but the fact that the folder is “full”. When you open an attachment directly from within Outlook it will first save a copy to a subfolder of the Temporary Internet Files folder. Cleaning out the folder will solve the issue.
Outlook Secure Temp folder

Unfortunately this is easier said than done. The subfolder name Outlook creates (on installation of Outlook) in the Temporary Internet Files folder is quite random. In Outlook 2003 and previous, the name starts with OLK and is followed by up to 4 random numbers or letters. In Outlook 2007 and Outlook 2010, this folder is called Content.Outlook and then has a subfolder which is named with with 8 random numbers and letters. In addition, by default, you cannot simply browse to the folder to clean it out. Getting to the Temporary Outlook Folder can still be accomplished in 2 easy steps though.

Step 1: Locate the folder
The folder location is stored in the registry in the following key;Outlook 97 HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Outlook\Security
Outlook 98 HKEY_CURRENT_USER\Software\Microsoft\Office\8.5\Outlook\Security
Outlook 2000 HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Security
Outlook 2002/XP HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security
Outlook 2003 HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security
Outlook 2007 HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security
Outlook 2010 HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security

Step 2: Get to the folder
Open the OutlookSecureTempFolder registry key from the location provided in Step 1.
Copy the path from the key.
Open Explorer
Paste the address in the Address Bar and press Enter

 

 

If you have found this page, it is likely that you encountered the following error when you tried to restore a differential backup using Microsoft SQL Server 2005. Restore failed for Server ”. (Microsoft.SqlServer.Smo) Additional Information: System.Data.SqlClient.SqlError: The log or differential backup cannot be restored because no files are ready to rollforward. (Microsoft.SqlServer.Smo) What this error is telling you is that there is no database that was left in non-operational mode, and thus has not been cleaned up such that uncommitted transactions have not been rolled back. The easy way to reproduce this error is to backup your database using full recover model, and do full and differential backups. Once you have your full and differential backup files you, if you want to restore your database all you have to do is restore the full backup first, and then one of the differential files (differential backups have all the changes since the last full backup) that brings you up to the point you want to restore to. You will get the above error when you try to restore the differential backup (after you just restored the full backup). Unfortunately, you forgot one critical detail (just like I did at first). You MUST restore all but the last (in this case the full backup) with NORECOVERY option. In the Microsoft SQL Server Management Studio there are three options on the Option “page” when you restore a database. Option 1 (the default): Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored.(RESTORE WITH RECOVERY) Option 2: Leave the database non-operational, and do not roll back uncommitted transactions. Additional transaction logs can be restored.(RESTORE WITH NORECOVERY) To properly restore a database that is backup up using full recovery mode with full and differential backups, here are the steps you need to follow to not get the above error. Restore Full backup

1. Open the Restore Database window in Microsoft SQL Server Management Studio
2. Ensure the To database field is filled in with the name you want.
3. Choose From device as the Source for restore.
4. Choose the full backup file you want to restore. In most cases this is the most recent full backup file.
5. Click the Options page on the left navigation.
6. Choose Leave the database non-operational, and do not roll back uncommitted transactions. Additional transaction logs can be restored.(RESTORE WITH NORECOVERY). This is the most important step!!!

Restore Differential backup

1. Open the Restore Database window in Microsoft SQL Server Management Studio
2. Ensure the To database field is filled in with the name you want. The same that you specified in step 2 for the Restore Full backup
3. Choose From device as the Source for restore.
4. Choose the differential backup file you want to restore. In most cases this is the most recent differential backup file.
5. Click the Options page on the left navigation.
6. Choose the default: Leave the database ready to use by rolling back uncommitted transactions. Additional transaction logs cannot be restored.(RESTORE WITH RECOVERY) Make sure to choose this if you want to use your database after the restore.

That is it, no more error. If you are lucky 🙂