DComTalk.com

James W. Long · Guest

Hi all,

I am running Windows 2000 sevice pack 4 and IE 6.0

I can run netmeeting but I can't install remote desktop sharing.
That option is grayed out, so I cant get to the wizard.

If I try to start the netmeeting remote desktop sharing service manually,
I get this message:

"Could not start the NetMeeting Remote Desktop Sharing service on local
Computer.
The service did not return an error. This could be an internal Windows
error or an internal service error.
If the problem persists, contact your system administrator."

During a regedit session, I am sure that I deleted some netmeeting/remote
desktop sharing
registry entries from my registry by mistake. This had to do with removing
the remote desktop
client for terminal services, which has about the same exact name. That's
when Remote Desktop Sharing
from netmeeting stopped working, My Bad.

How can I re-install neetmeeting/rdp, or get it to work again it work again?

Thank you in advance,

James W. Long

Brian Sullivan MVP · Guest

James W. Long wrote:

James W. Long · Guest

Dear Brian:

Thank you for the help!

I performed the uninstall and reinstall as described but it did not fix
the problem.

The remote desktop sharing is still grayed out and I cant select it.

System log shows that the files were replaced to thier original versions
by windows file protection!!
Do I need to turn that off?

The remote desktop service will not start automatically
the application log shows this:

Event Type: Error
Event Source: mnmsrvc
Event Category: None
Event ID: 1
Date: 11/6/2004
Time: 3:59:07 AM
User: N/A
Computer: HAL9000
Description:
Service Error in StartServiceCtrlDispatcher failed.

When I try to start remote desktop sharing service manually I still get:

"Could not start the NetMeeting Remote Desktop Sharing service on
local Computer.
The service did not return an error. This could be an internal Windows
error or an internal service error.
If the problem persists, contact your system administrator."

on my other systems, that service always starts, which I suspect is the
difference,
but I dont know WHY it wouldn't start on this system, do you?
could it be a security, rights, policy, priveledges, issue?

Thank you in advance,

James W. Long

"Brian Sullivan MVP" <brians@WORMTIREDmeetingbywire.com> wrote in message
news:O8NkuCBxEHA.2732@TK2MSFTNGP12.phx.gbl...

Brian Sullivan MVP · Guest

James W. Long wrote:

James W. Long · Guest

Dear Brian
you wrote:
Are you running on an account that has full adminstrator privileges?

yes.

you wrote:
It is also possible to turn RDS off via policies -- what does gpedit.msc (
the policy editor) say?

gpedit.msc shows nothing. everything is in default state
domain policy does not prohibit rds either, its runs fine on all my other
clients.
where else do I look, because SOMETHING is preventing the service from
starting.
its only on this machine
thanks
James

"Brian Sullivan MVP" <brians@WORMTIREDmeetingbywire.com> wrote in message
news:e2gBFmRxEHA.4076@TK2MSFTNGP10.phx.gbl...

Brian Sullivan MVP · Guest

James W. Long wrote:

LuckyRon · Guest

Was wondering if anyone was able to find a fix for the above because I am
experiencing exactly the same issue on 2 of my servers. Others work fine.
All were built using the same image and a server re-name was performd on
each. Again though, only 2 have this problem. Thanks.

Brian Sullivan MVP · Guest

On Wed, 15 Dec 2004 17:32:10 -0500, LuckyRon wrote:

LuckyRon · Guest

Yes I applied all the suggestions posted thus far. I even removed the
NetMeeting Remote Desktop Sharing "service" manually via the "SC" Resource
Kit Utility and then rebooted..Still no luck... Yes NetMeeting runs in
normal "client" mode and I'm able to make and receive secure calls as
well.

Just happen to notice however that Protected Storage appears to be
preventing me from deleting the existing/old files that should have been
removed via the uninstall. Perhaps this is where the main issue
lies...corrupted DLLs or EXEs??? One major problem though, at this point,
is that I can't completely remove the Protected Storage affect since I'm
troubleshooting this issue remotely via Terminal Services. Unfortunately,
Protected Storage is completely dependent on RPC Calls which is
significantly hampering my ability to really test my theory, i.e. can't
disable RPC Service and remotely connect to the Server...Any suggestions?
What's your experience with the Resource Kit Utility "In Use" to delete
files that may be locked???

Thanks.

Brian Sullivan MVP · Guest

On Thu, 16 Dec 2004 18:21:27 -0500, LuckyRon wrote:

Brian Sullivan MVP · Guest

On Thu, 16 Dec 2004 18:59:32 -0500, Brian Sullivan MVP wrote:

Guest

In response to immediately above, no the MS Article does not apply here.

Insofar as the remaining part of this problem is concerned, turns out
though that Protected Storage was indeed the source of my problems. As
luck would have it, I managed to obtain local assistance at the remote
location in order to successfully removed the hooks Protected Storage had
on the NetMeeting Program files. This was required because the NetMeeting
re-install suggested by Microsoft does not overwrite files if they are
System Protected (obviously by design). I do suspect that one or more
NetMeeting DLLs on our server was corrupted. Unfortunately, since
Protected Storage is dependent upon RPC Services, this Service also needed
to be stopped. Not an easy task to say the least. Discovered the only way
to do so was to disable the RPC Services and then reboot. Disabling RPC
and rebooting is ugly since many services depend on this to successfully
run but re-running the Netmeeting re-install did work which finally
corrected my problem. Afterwards however, getting RPC back up and running
could only be achieved by manually changing the "Startup" parameters in
the Registry for this Service. Once this was done and the server
restarted, all was back to normal for Desktop Sharing.

LuckyRon · Guest

In response to immediately above, no the MS Article does not apply here.

Insofar as the remaining part of this problem is concerned, turns out
though that Protected Storage was indeed the source of my problems. As
luck would have it, I managed to obtain local assistance at the remote
location in order to successfully removed the hooks Protected Storage had
on the NetMeeting Program files. This was required because the NetMeeting
re-install suggested by Microsoft does not overwrite files if they are
System Protected (obviously by design). I do suspect that one or more
NetMeeting DLLs on our server was corrupted. Unfortunately, since
Protected Storage is dependent upon RPC Services, this Service also needed
to be stopped. Not an easy task to say the least. Discovered the only way
to do so was to disable the RPC Services and then reboot. Disabling RPC
and rebooting is ugly since many services depend on this to successfully
run but re-running the Netmeeting re-install did work which finally
corrected my problem. Afterwards however, getting RPC back up and running
could only be achieved by manually changing the "Startup" parameters in
the Registry for this Service. Once this was done and the server
restarted, all was back to normal for Desktop Sharing.

	DComTalk.com Forum Index -> Netmeeting	All times are GMT
Page 1 of 1