Server 2008 R2

How to Fix RIP Address Out Of Range Error When Installing Server 2008 R2

I have primarily seen this error on HP Proliant Gen 9 Servers when installing an operating system pre-Server 2012, such as Server 2008 R2. The error may display several messages that may not mean a lot to you, such as:

X64 Exception Type 0D - General Protection Exception

RIP Address Out Of Range

CALL ImageBase ImageName+OFFset

How to Fix RIP Address Out Of Range Error When Installing Server 2008 R2

How to Fix RIP Address Out Of Range Error When Installing Server 2008 R2 - 2

The most likely time you will see this error is when booting to a Server 2008 R2 installation disc.

To resolve this error, in the bios, disable the following setting:

UEFI Optimized Boot

How to Fix rdesktop disconnect: Internal licensing error on When connecting to Windows Server 2008 - Ubuntu Linux

If you use rdesktop to gain access to a Windows Server 2008 Terminal Server from Linux, you may experience the following error:

rdesktop my.terminalserver.com

Autoselected keyboard map en-us

disconnect: Internal licensing error.

This happens when your terminal server is Windows Server 2008 or 2008 R2, the licensing mode is set to "per device", and you are using rdesktop 1.7.0 or less. There are two ways to resolve this error. You can either set the licensing mode to "per user", or you install rdesktop 1.7.1. rdesktop 1.7.1 includes a patch for the problem connecting to 2008 terminal servers with "per device" licensing.

To fix error on Ubuntu Linux, install rdesktop 1.7.1:

sudo apt-get install libx11-dev libssl-dev

wget http://iweb.dl.sourceforge.net/project/rdesktop/rdesktop/1.7.1/rdesktop-1.7.1.tar.gz
tar -zxvf rdesktop-1.7.1.tar.gz
cd rdesktop-1.7.1
./configure
make
sudo make install

​You may have to close and open a new terminal window before you run rdesktop again, but you won't receive the error any more.

***Note***

There are a couple of workarounds for this problem that have surfaced, but they are all outdated as of rdesktop 1.7.1. Do not use these workarounds, as 1.7.1 fixes the issue. Here are two of the work arounds:

Fix for Can't RDP into 2008 R2 or Windows 7 after Update 2667402 and SP1 - Remote Desktop Services Stops

If you arrived at this page, it is likely because you can't use Remote Desktop Protocol to remote into a Wndows 7 or Server 2008 R2 system. The Remote Desktop Services is stopped, and everytime you enable it, it crashes. You also receive an error message like this in the Application event log:

2667402rdp2008r2-2"Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1

Faulting module name: rdpcorekmts.dll, version: 6.1.7600.16952, time stamp: 0x4f1f9e66
Exception code: 0xc0000005
Fault offset: 0x000000000000a793
Faulting process id: 0xabc
Faulting application start time: 0x01cd4a68213a1459
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: C:\Windows\system32\rdpcorekmts.dll

This is a known issue and will occur if you are running Windows 7 or Server 2008 R2, apply update 2667402, and then install Service Pack 1. After you install security update 2667402, and then you install SP1, the binary version of Rdpcorekmts.dll is 6.1.7600.16952 and not 6.1.7601.17767. This issue occurs because the SP1 binary version of Rdpcorekmts.dll was not originally deployed when security update 2667402 was originally installed.

Fix error 0x000006D9 on Windows 7 and Server 2008 R2 - Sharing Printer

If you are trying to share a printer on Windows 7 or Server 2008 R2, you may experience this error:

0x000006D9

This issue occurs because the Spooler services uses the Firewallapi.dll file to make an API call to check the availability of the Windows Firewall service. If you experience this error, you must have the firewall enabled in order to share out the printer. This only seems to affect network printers, not locally attached printers.

To enable the firewall:

Start > Run > firewall.cpl > Turn Windows Firewall on or off > Turn on Firewall for the type of network location you use

As far as I can tell, you can turn the firewall back off after you share the printer and it will not mess up the printer sharing.

http://support.microsoft.com/kb/2123653

Subscribe to Server 2008 R2