A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

TerminalServices-RemoteConnectionManager ID 1057: Object already exists



 
 
Thread Tools Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
  #1  
Old April 26th 12, 10:09 AM posted to alt.windows7.general
delar
external usenet poster
 
Posts: 2
Default TerminalServices-RemoteConnectionManager ID 1057: Object already exists

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

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 ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop
ServicesRemote Desktop Session HostSecurity]

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/l...=ws.10%29.aspx

Physical Memory (MB)
Total 24567
Cached 6337
Available 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!
Ads
  #2  
Old April 26th 12, 11:01 AM posted to alt.windows7.general
Dave-UK
external usenet poster
 
Posts: 596
Default TerminalServices-RemoteConnectionManager ID 1057: Object already exists


"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.


  #3  
Old April 26th 12, 06:19 PM posted to alt.windows7.general
delar
external usenet poster
 
Posts: 2
Default TerminalServices-RemoteConnectionManager ID 1057: Object already exists

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
  #4  
Old April 26th 12, 06:35 PM posted to alt.windows7.general
Gene E. Bloch[_5_]
external usenet poster
 
Posts: 1,720
Default TerminalServices-RemoteConnectionManager ID 1057: Object already exists

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)


  #5  
Old April 26th 12, 07:28 PM posted to alt.windows7.general
Dave-UK
external usenet poster
 
Posts: 596
Default TerminalServices-RemoteConnectionManager ID 1057: Object already exists


"delar" wrote in message ...
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'.




 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 10:21 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.