delar

TerminalServices-RemoteConnectionManager Event ID: 1057: The relevant status code was Object already exists.

12 posts in this topic

The computer is Windows 7 Professional 64-bit edition version 6.1 Build 7601 service pack 1. The computer is not in a domain environment. I believe this may be a security issue however I completed an in-place windows 7 upgrade to try and fix the problem but after all of the windows updates, etc the error remains and appears every time the computer is rebooted...

I could use some help with the following error:

Log Name: System

Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager

Event ID: 1057

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Description:

The Terminal Server has failed to create a new self signed certificate to be used for Terminal Server authentication on SSL connections. The relevant status code was Object already exists.

Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager"

Guid="{C76BAA63-AE81-421C-B425-340B4B24157F}"

EventSourceName="TermService"

I found {C76BAA63-AE81-421C-B425-340B4B24157F} in my registry in the:

HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin -> OwningPublisher

HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Analytic -> OwningPublisher

HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Debug -> OwningPublisher

HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> CurrentVersion -> WINEVT -> Channels -> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational -> OwningPublisher

Microsoft-Windows-TerminalServices-RemoteConnectionManager

%SystemRoot%\system32\termsrv.dll

When I open as administrator a command prompt window and enter the follow: regsvr32 termsrv.dll

I get the following message:

RegSvr32

The module termsrv.dll was loaded but the entry-point DllRegisterServer was not found.

Make sure that termsrv.dll is a valid DLL or OCX file and then try again.

Not sure if this is a problem or if this behavior is expected...

I ran sfc /scannow and check disk on the hard drive with both reporting no errors.

I updated the security profile for:

[Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security]

In the right pane, double click "Require use of specific security layer for remote (RDP) connections", in the security layer list, select RDP.

I modified the policy and there was no change in computer behavior. The error still appears each time the computer is reboot.

===

I found a semi-related webpage that at least lists the same Microsoft-Windows-TerminalServices-RemoteConnectionManager and 1057. However I'm running Windows 7 64-bit edition and I seriously doubt I have a lack of available memory issue.

Event ID 1057 — Terminal Services Authentication and Encryption

http://technet.microsoft.com/en-us/library/cc775192%28v=ws.10%29.aspx

Physical Memory (MB)

Total 24567

Cached 6337

Avaiable 21821

Free 15709

The relevant status code says that the "Object already exists" which I think is far more relevant then some memory issue. Do I have to delete some file or registry entry? Or is it a security issue?

Google search have come up with nothing. Any suggestions would be very helpful!

Share this post


Link to post
Share on other sites

Do you know what triggers the error? Are you trying to RDP to another computer when this even gets thrown?

Share this post


Link to post
Share on other sites

Any time the computer is reboot the error appears in the event log. Must be something windows is launching during startup.

Share this post


Link to post
Share on other sites

I rebooted the computer with a clean windows boot:

msconfig

In the System Configuration Utility dialog box, click Selective Startup on the General tab.

  1. Click to clear the Load Startup Items check box.
    Note The Use Original Boot.ini check box is unavailable.
  2. Click the Services tab.
  3. Click to select the Hide All Microsoft Services check box.
  4. Click Disable All, and then click OK.
  5. When you are prompted, click Restart.

Still have the error on computer reboots.

Share this post


Link to post
Share on other sites

delar:

Are you actually experiencing a problem or are you just irked by an Event Log entry ?

Share this post


Link to post
Share on other sites

I see that you've created a new topic on Technet

I'm assuming this is the article you mention that you found

Event ID 1057 — Terminal Services Authentication and Encryption

The article does recommend that if that fix does not work to contact Microsoft Support

A bit more searching though this user {Jonathan Bond} seems to have been able to fix it by removing and recreating the certificate

This was a followup post from experts-exchange for removing a certificate

How to Deleting a SSL Certificate using MMC

This article applies to Server 2008 but most components of Windows 7 are very similar.

Share this post


Link to post
Share on other sites

delar:

Are you actually experiencing a problem or are you just irked by an Event Log entry ?

I'm irked by an event log entry mostly. I did a in-place windows upgrade, etc and still can't seem to get this from not appearing in the event log on each computer reboot.

Share this post


Link to post
Share on other sites

If you are not experiencing a problem then it really is a non-issue. The fact that Terminal Services can't create a self signed certificate is nothing but a notification.

Registering termsrv.dll won't help. You are dealing with a SSL Certificate issue. Ron showed how you can access System based Certificates via the MMC Snap-In. Either you will have to manually create a Self Signed certificate and install it or obtain one from a Certificate Authority (CA). However if you are just using Win7 as just a desktop OS then it is not an issue to sweat over.

Share this post


Link to post
Share on other sites

I see that you've created a new topic on Technet

I'm assuming this is the article you mention that you found

Event ID 1057 — Terminal Services Authentication and Encryption

The article does recommend that if that fix does not work to contact Microsoft Support

A bit more searching though this user {Jonathan Bond} seems to have been able to fix it by removing and recreating the certificate

This was a followup post from experts-exchange for removing a certificate

How to Deleting a SSL Certificate using MMC

This article applies to Server 2008 but most components of Windows 7 are very similar.

I tried contacting Microsoft for support but they wanted to charge me $99 to fix the issue. I saw that post from Jonathan Bond but The relevant status code was "Key not valid for use in specified state." My The relevant status code was "Object already exists". I wasn't sure if I could cause more harm then good messing around without knowing what I was doing...

Which certificate do you suggest I delete using the MMC certificate tool?

Share this post


Link to post
Share on other sites

If you are not experiencing a problem then it really is a non-issue. The fact that Terminal Services can't create a self signed certificate is nothing but a notification.

Registering termsrv.dll won't help. You are dealing with a SSL Certificate issue. Ron showed how you can access System based Certificates via the MMC Snap-In. Either you will have to manually create a Self Signed certificate and install it or obtain one from a Certificate Authority (CA). However if you are just using Win7 as just a desktop OS then it is not an issue to sweat over.

Well Remote Desktop seems to be working properly which is what I was mostly worried about. If you suggest I ignore it then I will until something doesn't work.

Share this post


Link to post
Share on other sites

There 'ya go.

If RDP works and that's all you are doing in Win7 then you're OK.

Share this post


Link to post
Share on other sites

Thanks for the help all. If I run into any more issues with this I'll post to this thread or if I find a way to keep them from appearing in the event log.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.