Remote Desktop Licensing service to fail to start

Remote Desktop Licensing service to fail to start, with error code %%-1073672191.

The Terminal Services Licensing service cannot start. The following error occurred: Can’t initialize Cryptographic – error code 5.

Sometime happens a problem with Remote Desktop Licensing services not starting.
The Terminal Licensing MachineKeys have permissions for Administrators and/or TermServLicensing  but the service starts using the “Network Service” account… Why??????

You can fix the problem adding Network Service account (read only privileges it’s ok), on follow directory (you can force ownership propagation for reapply the correct privilege tree):

C:\Documents and Settings\all users\Application Data\Microsoft\Crypto\RSA\MachineKeys

Then the service start, correctly.


For further information you can take a look at microsoft KB:

Default permissions for the MachineKeys folders:

Cisco – service config

Randomly, during bootup of Cisco hardware (IOS), error messages similar to these are displayed:

%Error opening tftp:// (Socket error)

%Error opening tftp:// (Socket error)

%Error opening tftp:// (Socket error)

%Error opening tftp:// (Socket error)

These error messages are related to the default service configuration option built into Cisco IOS software, which attempts to access the service configuration files from a network Trivial File Transfer Protocol (TFTP) server.

In order to disable this feature, issue the no service config global command.

Router#config terminal
Enter configuration commands, one per line.

Router(config)#no service config


Router#copy running-config startup-config

Debian – Service startup

Under Debian Linux startup files are stored in /etc/init.d/ directory and symbolic linked between /etc/rcX.d/ directory exists. Debian Linux uses System V initialization scripts to start services at boot time from /etc/rcX.d/ directory. Debian Linux comes with different utilities to remove unwanted startup file

Using rcconf:

This tool configures system services in connection with system runlevels. It turns on/off services using the scripts in /etc/init.d/. Rcconf works with System-V style runlevel configuration. It is a TUI(Text User Interface) frontend to the update-rc.d command.

Install rcconf in Debian:

#apt-get install rcconf

To start rconf, login as root user and type rcconf

# rcconf

Select the service you would like to enable or disable.

Using sysv-rc-conf:

sysv-rc-conf provides a terminal GUI for managing “/etc/rc{runlevel}.d/” symlinks. The interface comes in two different flavors, one that simply allows turning services on or off and another that allows for more fine tuned management of the symlinks. Unlike most runlevel config programs, you can edit startup scripts for any runlevel, not just your current one.

Install sysv-rc-conf in debian:

#apt-get install sysv-rc-conf

This will install sysv-rc-conf.Now you need to run the following command

# sysv-rc-conf

Select the service you would like to enable or disable.

Both sysv-rc-conf and rcconf are best tools to use on Remote Debian Linux or when GUI is not available

You can also use update-rc.d script as follows (update-rc.d removes any links in the /etc/rcX.d directories to the script /etc/init.d/service):

# update-rc.d -f {SERVICE-NAME} remove

For example to stop xinetd service you can type command as follows:

# update-rc.d -f xinetd remove