The remote session was disconnected because there are no Terminal Server client access licenses available for this computer

 

If the error “The remote session was disconnected because there are no Terminal Server client access licenses available for this computer” shows up when you are trying to connect to your terminal server it is caused by one of  two problems.

The first is that you have run out of licenses on your Terminal Server user CALS. These CALS specify how many users can be logged into the terminal server at one time. So if you have 5 Terminal Server user CALS then there can only be 5 sessions logged into the terminal server at one time.

If you are receiving the error because of exceeding user count the only way to fix the issue is to buy more Terminal Server user CALS.

 

The second problem exists on the computer that is trying to log into the problem. This error is resolved by deleting some registry keys on the host machine.

Step 1: Open the registry editor (Start menu – Run – Then type in “regedit” with out the quotes)

Step 2: Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSLICENSING

Delete these keys
Delete these keys

Step 3: Delete all the keys in MSLICENSING

Step 4: Test the remote connection

Once the keys are deleted the remote desktop connection should work again. It will automatically remake the keys upon starting remote desktop.

Read More →
Replies: 1 / Share:

Outlook 2013 and Exchange 2003

Warning; Buying Office 2013

So you may have upgraded to Microsoft office 2013 and gone to connect your email to an exchange account and then you will see two error boxes come up, the first one says:

The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance.

The second window says:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The file (then the file path) is not an Outlook data file (.ost).

It seems that Microsoft Exchange 2003 is not supported by Outlook 2013. At the moment I do not know of any work around, if you do please leave a comment in the section below.

Snippet from the Office 2013 known issues page:

Error when connecting to Exchange 2003

When you configure Outlook 2013 for an Exchange 2003 account, you can get the following error message:

The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance.

Workaround    Outlook 2013 isn’t supported on Exchange 2003 and connectivity is blocked. Please connect Outlook 2013 to Exchange 2007, 2010, or 2013.

This is one of the things you need to be aware of if you are still running exchange 2003.
You can

through that link.

Read More →
Replies: 0 / Share:

IIS is the Web Server component of Windows. It is included in your normal Windows installation but it is a stripped down version. We will be using the Windows Server version of this software which is much more rich in features.

 

Read More →
Replies: 0 / Share:

So yesterday I logged into yahoo and the browser (internet explorer) just reloaded that quickly that I couldn’t even press the stop button. I was quite baffled by this and started scanning for computer viruses. I found none on the system. So why was it reloading…

I restored all default settings and erased all of the cache. Nothing it still reloaded as soon as I logged in.

Then I noticed that there was a message that popped up on the screen (really quickly mind you I had to read it one word at a time) the message said

Your browser settings prevent you from automatically redirecting to a new URL

Then I started going through all of my advanced settings and found one that said allow meta refresh this was set to enable.

I proceeded to disable the setting and tried again and it worked. I was just starting to think that I was going to have to reinstall my system.

The steps to fixing this are here:

1. Open Internet explorer

2. Click on tools and then Internet options

3 . Click on Security tab.

4. Click on Internet and made it highlight.

5. You will see Custom Level Click on it.

6. Now you will Allow META REFRESH make this Enable.

7. If Allow META REFRESH option is also set in enable mode then try to disable

8. Click on OK and OK again.

Hope that helps with your problem 🙂

Read More →
Replies: 0 / Share:

This is how to get the print spooler to start and it gives you a message saying “Print Spooler Failed to Read Description – error code 1813”. If you look in the event logs you may find some events with the ID “Error 1053”

To get the spooler to start you will need to navigate to the actual print spooler excecutable file in the “C:\Windows\System32\” folder. In this folder will be a file called spoolsv.exe this is the exe file for the spooler service.

You should also see a file called spoolsv.exe.org. It will be around 545kb in size and the spoolsv.exe file will be about 41kb. For some reason this has replaced the spooler service with a different file and created a copy of the original file.

So what we need to do is delete the actual file named spoolsv.exe

Then make a copy of the spoolsv.org.bak and rename it to spoolsv.exe. Now the exe file is the correct file go the services windows( press”ctrl + r” then type in “services.msc” then press enter). Now find the spooler service and run it.

Now your print spooler is running again and you can print. YAY!

 

NOTE:

This problem for me seemed to occur when installing a new WiFi HP printer on a dell laptop. I have not been able to get it to work print over WiFi yet but I have figured out that this problem occurs while installing the wireless driver. This is just how to get the print spooler to start.

Read More →
Replies: 0 / Share:

I will show you how to make a windows user profile associate with another users files. This can be very useful when joining non active directory computers that have been used in a non active directory environment to the active directory domain. So what will happen is that you point a the new active directory user to use the old non domain profile. This doesn’t always work on Windows 7 machines but it does on Windows XP computers.

  • You will need to log in as the new domain user
  • Then log out and log back in as local administrator
  • Open the registry editor. Do this by pressing “ctrl” + “r” and typing in regedit
  • Inside the registry editor navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\ProfileList
  • Look inside each key they will be named with a {GUID} you will need to find the one for the new domain user
  • In each key will be a string value called “ProfileImagePath”
  • Change this string value to the profile path of the old non-domain user
  • Now log off and log in as the new user

Now your user will load up that location for their user profile.

Read More →
Replies: 0 / Share:

This happened to me because I installed MMSQL Server and then I had to uninstall it and re-install because I had the collation wrong. But during one of the pre-installation checks that SQL Server runs it come up with:

“Reporting Services Catalog Database File Existence” failed
“Reporting Services Catalog Temporary Database File Existence” failed.

reporting_services_catalog_database_failed

To fix this problem we need to delete some files that the SQL Server uninstaller must miss for some reason.

Navigate to “C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA” then delete the following files:files_to_delete

ReportServer.mdf
 ReportServer_log.LDF
 ReportServerTempDB.mdf
ReportServerTempDB_log.LDF

Once you have deleted the files hit the re-run button on the pre-installation check and it will pass.

Now your problem should be resolved just continue on with your install.

Read More →
Replies: 38 / Share: