TerminalServices-RemoteConnectionManager ID 1057: Object already exists

Hello

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

I could use some help with the following error

Log Name: Syste
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManage
Event ID: 105
Task Category: Non
Level: Erro
Keywords: Classi
User: N/
Description
The Terminal Server has failed to create a new self signed certificate to b
used for Terminal Server authentication on SSL connections. The relevant statu
code was Object already exists

Provide
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 -
OwningPublishe

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

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

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

Microsoft-Windows-TerminalServices-RemoteConnectionManage
%SystemRoot%system32termsrv.dl

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

I get the following message

RegSvr3

The module termsrv.dll was loaded but the entry-point DllRegisterServer was no
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 n
errors

I updated the security profile for

[Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Deskto
ServicesRemote Desktop Session HostSecurity

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

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

==

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

Event ID 1057 - Terminal Services Authentication and Encryptio
http://technet.microsoft.com/en-us/l...v=ws.10%29.asp

Physical Memory (MB
Total 2456
Cached 633
Available 2182
Free 1570

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

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

"delar" <> wrote in message news...
> Hello,
>
> 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%system32termsrv.dll
>

It may just be a typo on your part when you posted but there is an error in this path:

Microsoft-Windows-TerminalServices-RemoteConnectionManager
%SystemRoot%system32termsrv.dll

The back-slash is missing, it should be:
%SystemRoot%system32\termsrv.dll
If it's in the registry as you posted then I think that may cause problems.

Dave-UK wrote on 04/26/2012 06:01 ET
> "delar" wrote in messag
> news
>> Hello
>>
>> The computer is Windows 7 Professional 64-bit edition version 6.1 Build 760
>> service pack 1. The computer is not in a domain environment. I believe thi
>> ma
>> be a security issue however I completed an in-place windows 7 upgrade to tr
>> an
>> fix the problem but after all of the windows updates, etc the error remain
>> an
>> appears every time the computer is rebooted..
>>
>> I could use some help with the following error
>>
>> Log Name: Syste
>> Source: Microsoft-Windows-TerminalServices-RemoteConnectionManage
>> Event ID: 105
>> Task Category: Non
>> Level: Erro
>> Keywords: Classi
>> User: N/
>> Description
>> The Terminal Server has failed to create a new self signed certificate to b
>> used for Terminal Server authentication on SSL connections. The relevan
>> statu
>> code was Object already exists
>>
>> Provide
>> 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 -
>> OwningPublishe
>>
>> HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -
>> CurrentVersion -> WINEVT -> Channels -
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Analytic -
>> OwningPublishe
>>
>> HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -
>> CurrentVersion -> WINEVT -> Channels -
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Debug -
>> OwningPublishe
>>
>> HKey_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -
>> CurrentVersion -> WINEVT -> Channels -
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational -
>> OwningPublishe
>>
>> Microsoft-Windows-TerminalServices-RemoteConnectionManage
>> %SystemRoot%system32termsrv.dl
>>
>>
>>
>>
> It may just be a typo on your part when you posted but there is an error i
> this path
>
> Microsoft-Windows-TerminalServices-RemoteConnectionManage
> %SystemRoot%system32termsrv.dl
>
> The back-slash is missing, it should be
> %SystemRoot%system32termsrv.dl
> If it's in the registry as you posted then I think that may cause problems
>
Sorry may have mis-typed, the registry entry is

%SystemRoot%system32termsrv.dll

On 4/26/2012, delar posted:
> Dave-UK wrote on 04/26/2012 06:01 ET :
>> "delar" wrote in message
>> news:
>>> Hello,
>>>
>>> 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%system32termsrv.dll
>>>
>>>
>>>
>>>
>> It may just be a typo on your part when you posted but there is an error in
>> this path:
>>
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager
>> %SystemRoot%system32termsrv.dll
>>
>> The back-slash is missing, it should be:
>> %SystemRoot%system32termsrv.dll
>> If it's in the registry as you posted then I think that may cause problems.
>>
> Sorry may have mis-typed, the registry entry is:

> %SystemRoot%system32termsrv.dll

Which also looks bad.

You might need to type a pair of backslashes for your newsreader to
transmit the data correctly. It looks to me like the newsreader is
using a backslash as an escape character...

--
Gene E. Bloch (Stumbling Bloch)

"delar" <> wrote in message news:...
> Dave-UK wrote on 04/26/2012 06:01 ET :
>> "delar" wrote in message
>> news:
>>> Hello,
>>>
>>> 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%system32termsrv.dll
>>>
>>>
>>>
>>>
>> It may just be a typo on your part when you posted but there is an error in
>> this path:
>>
>> Microsoft-Windows-TerminalServices-RemoteConnectionManager
>> %SystemRoot%system32termsrv.dll
>>
>> The back-slash is missing, it should be:
>> %SystemRoot%system32termsrv.dll
>> If it's in the registry as you posted then I think that may cause problems.
>>
> Sorry may have mis-typed, the registry entry is:
>
> %SystemRoot%system32termsrv.dll

That still looks wrong to me.
I don't know what newsreader you are using but the registry entry
should have a backslash separating the word 'system32' and the word ' termsrv.dll'.