|
From: Leif M. <le...@ta...> - 2007-04-24 03:01:08
|
Roland,
From what you said, it sounds like you have already tried everything
I know to suggest
but here is a checklist.
1) Windows is funny about the way mapped drives work. The user needs to
be logged on
as an active desktop at the time the service starts or the drive will
not be visible. This
always seemed like a Windows bug to me. Anyways. Always use UNC paths
when
running as a service.
2) The account that you are running the service as needs to have
permission to access the
network resources. Try logging on as that user and make sure the
Wrapper can be
run as a console app as that user.
3) Be aware that network drives will not be available when running as
the SYSTEM
account. It sounds like you are using an account correctly though.
4) When the service is running, verify that it is running as the correct
user using the task
manager. You might actually be using the SYSTEM account if you spelled the
wrapper.ntservice.account property incorrectly.
4) ?? Try posting back.
Cheers,
Leif
Roland Chan wrote:
> Hi All -
>
> I've scoured the forums, re-read the FAQ, and tried several
> suggestions, however, I still am encountering a problem with
> accessing network resources while running our Java app as a service.
>
> While running in console-mode, using an authorized user account, I
> have no problem accessing resources on the network via UNC or mapped
> drive.
>
> However, while running as a service, using the same user account, I
> consistently encounter the dreaded "No such directory" error when
> trying to access these resources either via UNC or mapped drive.
>
> The environment is JDK 1.5, Windows 2003 Server.
>
> I welcome any tips or advice.
>
> Cheers,
> Roll
>
|