[p4] Problems running trigger scripts on a network drive
sjamison at ciena.com
Tue Feb 19 08:31:07 PST 2008
For non 2003 windows servers what you described below does work.
I've tried logging to the server with the same user the network resource
is mapped with and the service is setup to run as.
>From my experience so far services on windows 2003 enterprise server can
only touch files on local drives.
From: Dave Birkhead [mailto:daveb at data-pipes.com]
Sent: Tuesday, February 19, 2008 10:40 AM
To: Jamison, Shawn; perforce-user at perforce.com
Subject: Re: [p4] Problems running trigger scripts on a network drive
Yes, The problem is that a service is not run as you. It is run as a
user with very limited access.
You can change this by:
- going into the services menu in windows and choosing the perforce
- hit properties
- choose the log on tab
- Choose This account and add your account details.
- restart the service.
That should have you working correctly.
---- Jamison, Shawn <sjamison at ciena.com> wrote:
> Has anyone had problems with the Perforce service not being able to
> run trigger scripts located on a network mounted drive?
> We are using windows server 2003 and my trigger scripts are located on
> the z drive mounted to a Network appliance. The triggers fail but the
> errors don't tell you much and so far I have not found anything in the
> p4 logs that is helpful.
> Has anyone else run into this?
> How did you solve it?
> -Shawn Jamison>
> Ciena Corp Perforce Admin.
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user