Oltism.Com Nerdaliciousness + Informative solutions underway!

12Jul/100

How To:Fix “The System Could Not Access The Credential Manager Server” in Windows Vista

Credential manager is a single sign-on feature that allows users to input user names and passwords for multiple network resources and applications.Credential Manager is a central store for all of your usernames, passwords, and X.509 certificates.

In Windows Vista, Credential Manager can roam stored user names and passwords between multiple computers in an Active Directory domain. For example, if a user logs on to a computer and connects to a password protected web server and selects “Remember My Password” checkbox. This information will be saved within the Credential Manager. When the user logs on to a different computer and connects to the same server, Internet Explorer will provide the password. So, the user is not supposed to type it again. Earlier versions of Windows cannot access the stored credentials.

Those who use HP / Compaq line of desktops and laptops, you can find all of a sudden that can no longer access the system by displaying the following message: “The system could not access the Credential Manager Server“. The problem is not for the Windows Vista operating system, but certainly one of the software pre-installed by the manufacturer that for most will never be used and that encumbers the eroding precious memory.

“The system could not access the Credential Manager Server” error occurs due to a software “HP ProtectTools Security Manager”,which can be configured to prevent unauthorized access using Smart Cards, TPM Embedded security chips, USB sticks.

There are two ways to solve the problem:

First solution:

Reboot the PC. While it is being restarted by pressing the F8 function key. On the screen will display a different kind of start (If we do not even get the pc reboot and press the F8 function key faster;)
Select “Start in Safe mode”
When you are prompted to log in using the local administrator account
Go to services and DISABLE everything that starts with HP
Reboot the system. Hit f10 while it’s starting and disable the security settings (the second colum halfway down). You’ll have to configure a password to do it for some reason.
When you are prompted to log in using the local administrator account
Go to Start / all program / HP ProtectTool Security Manager FOR ADMINISTRATORS
Click on Credential Manager and then click Settings
Deselect the checkbox in the General tab “Use credential manager to log on to Windows”
You need to logoff
Select “Logon as a different user” and use a standard domain account.
Second Solution:

At the Windows Vista login screen, do the following:

Choose “log in as different user”
Click “log on with Wizard”.This will bring up a new login window where you can specify you username, Domain, and password.
In the bottom left corner of this window is a button labeled “More” Click it, and check the box labeled “Do not logon to Credential Manager”
Write your username, password and domain in the respective places and log on.
After successful logon, UNINSTALL CREDENTIAL MANAGER!
If you don’t, you will have to repeat the procedure next time you start up your PC again!

Sometimes this solution will works fine:

Start in safe mode and log on as a local admin
Start device manager and look under ‘Security Devices’ for ‘TrustedbPlatform Module’ – Right click and select uninstall
Reboot and allow the module to auto-reinstall itself
You should now be able to logon to Windows Vista without receiving a credential manager error. Depending on the versions of Windows Vista and TPM you are running you might have to re-register any finger scans you had stored. The problem is the driver becomes corrupted.

8Apr/100

Problem activating a Terminal Services license server, Windows Server 2003

Symptoms:

When you try to activate a Terminal Services license server on a computer that is running Microsoft Windows 2000 Server or Microsoft Windows Server 2003, the Terminal Services Licensing service starts, but the license server is not activated.

When you view the System log in Event Viewer, you see an event that is similar to the following:

Type: Error
Date: Date
Time: Time
Event ID: 38
Source: TermServLicensing
User: N/A
Computer:
Details: Can't generate a license for client because of error "Can't add certificate to store, error c0010020".

You may also recieve this internal error: Internal Error: 0xc0110011

Resolution:

NOTE: Have your licensing information ready to go, as you will need to call your nearest Microsoft Clearinghouse for re-activation of the licenses.


To resolve this problem, remove the Terminal Services Licensing program, and then reinstall it. To do this, follow these steps:

  1. Click Start, point to Programs, point to Administrative Tools, and then clickServices. In the right pane, right-click Terminal Services Licensing, and then clickStop. After the Terminal Services Licensing service stops, close Services.
  2. Click Start, click Run, type cmd, and then click OK.
  3. At the command prompt, type the following commands. Press ENTER after each command.
    cd %systemroot%system32
    ren LServer LServerOLD
  4. Type exit to close the commmand prompt window.
  5. Click Start, point to Settings, and then click Control Panel.
  6. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
  7. In the Components list, click to clear the Terminal Services Licensing check box, and then click Next.
  8. On the Terminal Services Setup page, click Next, and then click Finish.
  9. Restart your computer.
  10. Click Start, point to Settings, and then click Control Panel.
  11. Double-click Add/Remove Programs, and then click Add/Remove Windows Components.
  12. In the Components list, click to select the Terminal Services Licensing check box, and then click Next.
  13. On the Terminal Services Setup page, click Application server mode, and then click Next.
  14. On the Terminal Services Licensing Setup page, click the option you want to use, type the path of your license server database in the Install license server database at this location box, and then click Next.
  15. Click Finish, close Add/Remove Programs, and then close Control Panel.
  16. Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.
  17. In the System log, verify the existence of two events that are similar to the following:

    Event Type: Information 
    Event Source: TermServLicensing 
    Event Category: None 
    Event ID: 5 
    Date: Date
    Time: Time
    User: N/A 
    Computer: Computer_Name
    Description: Policy Module %SystemRoot%system32File_Name.dll for companyCompany_Name has been loaded.

    Event Type: Information 
    Event Source: TermServLicensing 
    Event Category: None 
    Event ID: 0 
    Date: Date
    Time: Time
    User: N/A 
    Computer: Computer_Name
    Description: Terminal Services Licensing was started.

  18. Start Windows Explorer.
  19. Expand the %systemroot%System32 folder, and verify that the LServer folder has been created.
  20. Click Start, point to Programs, point to Administrative Tools, and then clickTerminal Services Licensing.
  21. Right-click the name of your license server, and then click Activate.
  22. Follow the steps in the Licensing Wizard to activate your license server.