Service Fails on Start

[Jasonkimberson]

Currently I am having a problem creating a windows service that
monitors a mapped drive for events (using the FileSystemEvent Handler).
The service complies but fails to start:

"The XMLWatcher service on Local Computer started and then stopped.
Some services stop automatically if they have no work to do, for
example, the Preformance Logs and Alerts service."

The Service has no problem starting if i point the folder to be
monitored to my local C drive, and it had no problem monitoring the
mapped network drive as a console app or windows app.

Any Help would be greatly appreciated.

Installer:

private void InitializeCompo nent()
{
this.servicePro cessInstaller1 = new
System.ServiceP rocess.ServiceP rocessInstaller ();
this.serviceIns taller1 = new
System.ServiceP rocess.ServiceI nstaller();
//
// serviceProcessI nstaller1
//
System.ServiceP rocess.ServiceC ontrollerPermis sionAccess
this.servicePro cessInstaller1. Account =
System.ServiceP rocess.ServiceA ccount.User;
this.servicePro cessInstaller1. Password = "XXXXXXXX";
this.servicePro cessInstaller1. Username = "MyUserName ";
//
// serviceInstalle r1
//
this.serviceIns taller1.Service Name = "XMLWatcher ";
//
// ProjectInstalle r
//
this.Installers .AddRange(new
System.Configur ation.Install.I nstaller[] {
this.servicePro cessInstaller1,
this.serviceIns taller1});

}
Main Intializer
private void IntializeFileSy stemWatcher()
{
//Create File System Watcher for XML files
fsWatcher=new System.IO.FileS ystemWatcher("Y :\\","*.xml");
// Add event handlers for new XML files and change of existing XML
files.
fsWatcher.Chang ed += new FileSystemEvent Handler(OnXMLFi leChanged);
fsWatcher.Creat ed += new FileSystemEvent Handler(OnXMLFi leCreated);

// Begin watching.
fsWatcher.Enabl eRaisingEvents = true;
fsWatcher1.Enab leRaisingEvents = true;
}

[Brian Pelton]

My experience has been that services that start and stop are throwing
exceptions. Check the event log to see if there are any events with errors from
your service.

Also, it is usually easier / better to write the service in a library (dll) and
then test that using console or other applications, and then just make calls
into the dll from the service. This doesn't eliminate the chance of errors in
the service, but it reduces them and it makes development much easier.

--Brian

Jasonkimberson wrote:

Currently I am having a problem creating a windows service that
monitors a mapped drive for events (using the FileSystemEvent Handler).
The service complies but fails to start:

"The XMLWatcher service on Local Computer started and then stopped.
Some services stop automatically if they have no work to do, for
example, the Preformance Logs and Alerts service."

The Service has no problem starting if i point the folder to be
monitored to my local C drive, and it had no problem monitoring the
mapped network drive as a console app or windows app.

Any Help would be greatly appreciated.

Installer:

private void InitializeCompo nent()
{
this.servicePro cessInstaller1 = new
System.ServiceP rocess.ServiceP rocessInstaller ();
this.serviceIns taller1 = new
System.ServiceP rocess.ServiceI nstaller();
//
// serviceProcessI nstaller1
//
System.ServiceP rocess.ServiceC ontrollerPermis sionAccess
this.servicePro cessInstaller1. Account =
System.ServiceP rocess.ServiceA ccount.User;
this.servicePro cessInstaller1. Password = "XXXXXXXX";
this.servicePro cessInstaller1. Username = "MyUserName ";
//
// serviceInstalle r1
//
this.serviceIns taller1.Service Name = "XMLWatcher ";
//
// ProjectInstalle r
//
this.Installers .AddRange(new
System.Configur ation.Install.I nstaller[] {
this.servicePro cessInstaller1,
this.serviceIns taller1});

}
Main Intializer
private void IntializeFileSy stemWatcher()
{
//Create File System Watcher for XML files
fsWatcher=new System.IO.FileS ystemWatcher("Y :\\","*.xml");
// Add event handlers for new XML files and change of existing XML
files.
fsWatcher.Chang ed += new FileSystemEvent Handler(OnXMLFi leChanged);
fsWatcher.Creat ed += new FileSystemEvent Handler(OnXMLFi leCreated);

// Begin watching.
fsWatcher.Enabl eRaisingEvents = true;
fsWatcher1.Enab leRaisingEvents = true;
}

[Brian Pelton]

Rereading the post I'm thinking it is a security / rights issue. If it works
against C:\ but not against a network drive, that would point to security.

I haven't used it myself but you might look into impersonating another user when
your service runs. I see that you're trying to set a username and password but
I'm not sure that that is what the service is running under.

Try looking into the System.Security .Principal.Wind owsIdentity class'
Impersonate method.

--Brian
Brian Pelton wrote:

My experience has been that services that start and stop are throwing
exceptions. Check the event log to see if there are any events with
errors from your service.

Also, it is usually easier / better to write the service in a library
(dll) and then test that using console or other applications, and then
just make calls into the dll from the service. This doesn't eliminate
the chance of errors in the service, but it reduces them and it makes
development much easier.

--Brian

Jasonkimberson wrote:

Currently I am having a problem creating a windows service that
monitors a mapped drive for events (using the FileSystemEvent Handler).
The service complies but fails to start:

"The XMLWatcher service on Local Computer started and then stopped.
Some services stop automatically if they have no work to do, for
example, the Preformance Logs and Alerts service."

The Service has no problem starting if i point the folder to be
monitored to my local C drive, and it had no problem monitoring the
mapped network drive as a console app or windows app.

Any Help would be greatly appreciated.

Installer:

private void InitializeCompo nent()
{
this.servicePro cessInstaller1 = new
System.ServiceP rocess.ServiceP rocessInstaller ();
this.serviceIns taller1 = new
System.ServiceP rocess.ServiceI nstaller();
//
// serviceProcessI nstaller1
//
System.ServiceP rocess.ServiceC ontrollerPermis sionAccess
this.servicePro cessInstaller1. Account =
System.ServiceP rocess.ServiceA ccount.User;
this.servicePro cessInstaller1. Password = "XXXXXXXX";
this.servicePro cessInstaller1. Username = "MyUserName ";
//
// serviceInstalle r1
//
this.serviceIns taller1.Service Name = "XMLWatcher ";
//
// ProjectInstalle r
//
this.Installers .AddRange(new
System.Configur ation.Install.I nstaller[] {
this.servicePro cessInstaller1,
this.serviceIns taller1});

}
Main Intializer
private void IntializeFileSy stemWatcher()
{
//Create File System Watcher for XML files
fsWatcher=new System.IO.FileS ystemWatcher("Y :\\","*.xml");
// Add event handlers for new XML files and change of
existing XML
files.
fsWatcher.Chang ed += new
FileSystemEvent Handler(OnXMLFi leChanged);
fsWatcher.Creat ed += new
FileSystemEvent Handler(OnXMLFi leCreated);

// Begin watching.
fsWatcher.Enabl eRaisingEvents = true;
fsWatcher1.Enab leRaisingEvents = true;
}

[Jasonkimberson]

Any idea why the mapped drive is invalid?

System Events Log:
The following information is part of the event: Service cannot be
started. System.Argument Exception: The directory name Y:\ is invalid.
at System.IO.FileS ystemWatcher..c tor(String path, String filter)
at XMLFileWatcher. XMLWatcher.Inti alizeFileSystem Watcher() in
c:\documents and settings\deskto p\service\xmlfi lewatcher.cs:li ne 147
at XMLFileWatcher. XMLWatcher.OnSt art(String[] args) in c:\documents
and settings\deskto p\service\xmlfi lewatcher.cs:li ne 610
at System.ServiceP rocess.ServiceB ase.ServiceQueu edMainCallback

[Willy Denoyette [MVP]]

"Jasonkimberson " <ja************ @gmail.com> wrote in message
news:11******** **************@ f14g2000cwb.goo glegroups.com.. .

Any idea why the mapped drive is invalid?

System Events Log:
The following information is part of the event: Service cannot be
started. System.Argument Exception: The directory name Y:\ is invalid.
at System.IO.FileS ystemWatcher..c tor(String path, String filter)
at XMLFileWatcher. XMLWatcher.Inti alizeFileSystem Watcher() in
c:\documents and settings\deskto p\service\xmlfi lewatcher.cs:li ne 147
at XMLFileWatcher. XMLWatcher.OnSt art(String[] args) in c:\documents
and settings\deskto p\service\xmlfi lewatcher.cs:li ne 610
at System.ServiceP rocess.ServiceB ase.ServiceQueu edMainCallback

You cannot access a mapped drive that is mapped into another login session.
The drive Y: is mapped in an interactive users logon session, right?
All you can do to solve this is to map the drive in the logon session of the
service, the easiest wa to do is by executing (using
System.Diagnost ics.Process.Sta rt) a "net use..." command from your service
OnStart metod.

Willy.

[Brian Pelton]

I was thinking it had to do with the permissions the service was running, but if
it is a drive mapping issue, could a UNC path be used instead?

--Brian
Willy Denoyette [MVP] wrote:

"Jasonkimberson " <ja************ @gmail.com> wrote in message
news:11******** **************@ f14g2000cwb.goo glegroups.com.. .

Any idea why the mapped drive is invalid?

System Events Log:
The following information is part of the event: Service cannot be
started. System.Argument Exception: The directory name Y:\ is invalid.
at System.IO.FileS ystemWatcher..c tor(String path, String filter)
at XMLFileWatcher. XMLWatcher.Inti alizeFileSystem Watcher() in
c:\document s and settings\deskto p\service\xmlfi lewatcher.cs:li ne 147
at XMLFileWatcher. XMLWatcher.OnSt art(String[] args) in c:\documents
and settings\deskto p\service\xmlfi lewatcher.cs:li ne 610
at System.ServiceP rocess.ServiceB ase.ServiceQueu edMainCallback

You cannot access a mapped drive that is mapped into another login session.
The drive Y: is mapped in an interactive users logon session, right?
All you can do to solve this is to map the drive in the logon session of the
service, the easiest wa to do is by executing (using
System.Diagnost ics.Process.Sta rt) a "net use..." command from your service
OnStart metod.

Willy.

[Jasonkimberson]

Hi Willy,

Do you have any code samples of this?

thanks a lot for all the help!

[Willy Denoyette [MVP]]

"Brian Pelton" <[e-mail] > wrote in message
news:et******** ******@TK2MSFTN GP14.phx.gbl...

I was thinking it had to do with the permissions the service was running,
but if it is a drive mapping issue, could a UNC path be used instead?

--Brian

Sure, UNC paths are a valid option, but this has it's own issues, services
in general don't have network access privileges (and they better don't have
them), so the service user must have access privileges to the UNC anyway, or
you need to impersonate.

Willy.

[Willy Denoyette [MVP]]

"Jasonkimberson " <ja************ @gmail.com> wrote in message
news:11******** **************@ g44g2000cwa.goo glegroups.com.. .

Hi Willy,

Do you have any code samples of this?

thanks a lot for all the help!

In OnStart() ...

// user credentials with access privs. to remote resource, don't
hardcode if you care about security ;-)
string user = "user account";
string passwd= "user pwd";
System.Diagnost ics.ProcessStar tInfo psi = new
System.Diagnost ics.ProcessStar tInfo();
psi.FileName = @"C:\WINDOWS\sy stem32\cmd.exe" ;
// The command Arguments, get servername and sharename from a config
file or hardcode...
psi.Arguments =String.Format( "/c net use \\\\servername\ \sharename
/USER:\"{0} {1}\" user, passwd);
psi.WindowStyle =System.Diagnos tics.ProcessWin dowStyle.Hidden ; //Hide
the cmd window
System.Diagnost ics.Process p = System.Diagnost ics.Process.Sta rt(psi);
//Run
p.WaitForExit() ;
if(p.ExitCode != 0)
// throw an exception to exit OnStart and signal failure to
start to the SCM
throw...
else
// Go on and start your service thread

Willy.

[Jasonkimberson]

What is the proper syntax for this:

/c net use \\\\servername\ \sharename /USER:\"{0} {1}\" user, passwd

if i typed it into a cmd prompt? =

net use Y: \\server\folder \ /USER:domain/username password
is that correct?