Problems installing service

[Claire]

Hi,
I know this isn't strictly C# language related, but my service IS written in
c# and I checked out the list of microsoft newsgroups for win2000 and
couldn't really see one that applies.
I'm trying to test my service on a remote win2000 server machine, accessing
the machine as user "administrator" on remote desktop. Im just at the
install stage and using the installutil.exe to register the service on the
server.
The install appears to succeed but when I look through the "services" list
my application isn't appearing. (Ive installed it previously on my local xp
pro pc and it appeared in the services list immediately)
The installutil log file reads as follows and there's nothing in the event
log. I'm not too au fait with Windows 2000, so I've no idea if this is a
problem with me doing things over remote desktop or there's something else.

"Installing assembly 'c:\program files\mcas service
test\debug\jfmmcasmonitorservice.exe'.
Affected parameters are:
assemblypath = c:\program files\mcas service
test\debug\jfmmcasmonitorservice.exe
logfile = c:\program files\mcas service
test\debug\jfmmcasmonitorservice.InstallLog
Installing service jfmMCASService...
Creating EventLog source jfmMCASService in log Application...
Committing assembly 'c:\program files\mcas service
test\debug\jfmmcasmonitorservice.exe'.
Affected parameters are:
assemblypath = c:\program files\mcas service
test\debug\jfmmcasmonitorservice.exe
logfile = c:\program files\mcas service
test\debug\jfmmcasmonitorservice.InstallLog"

 

[Ollie Riches]

have you refreshed the services window in the MMC?


--
HTH

Ollie Riches
http://www.phoneanalyser.net

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a programmer
helping programmers.

 

[Claire]

Yes, several times.

 

[Claire]

And I've rebooted and the service remains unlisted.

 

[Guest]

I'm trying to test my service on a remote win2000 server machine,
accessing the machine as user "administrator" on remote desktop.

We've had similar problems installing services when logged on with
remote desktop (and with terminal services).
Have you tried installing actually "physically" logged onto the server
normally?