UNC path help

Hi,

I am trying to use delete a file using UNC path that is written perl script. This perl script gets a called by an external task of a workflow in the production server to delete a file in dev server using UNC path.

At the moment I am running the script on the dev server itself which does not require UNC path since it's running on dev server. However, when i change the path to file (e.g. "c:\\iw-home\\....\\file.txt" to "\\\\servername\\iw-home\\...\\file.txt") to UNC path which is technically the same thing since it's on the same server it does not work through workflow, but when I run the script manually through command line it works fine with the UNC path.

When it runs through external task from workflow it does not detect the file. I know this has something do with the system since it's running workflow as system user opposed to user such as me running it manually through command line. Any insights into this would be greatful Thank you.

Hopefully what I said is not confusing Smiley Happy

Find more posts tagged with

Comments

JMcNeil

I think the problem is that when you are logged in as your user running it from the command line, your user credentials are passed to the UNC path, and they have access to it.

However when it's called from a workflow and it's a different user running the script, that user does not have UNC access to that folder.

One option is to map a network drive with an external system 'net use' command, where you can supply a username and password of a user which would have access, or change the user which runs the TeamSite service to a user which has access to that UNC path.

paruntha

Thanks,

Ye the credentials things is probably why, but I'm confused as to why it will not work on the server itself.

What I mean is the external task is executing the perl script on the dev side itelf and it's using the dev the unc path (eventhough can be done just using local path)

I could understand whyt here has to be mapping to dev side if i was runnin from production because two differnet servers, but when i'm running the script on the dev side itself and using the dev server name for the unc path shouldn't it work? Or do I have to map the drive to itself?

I know for production like wht u said about net use i mite have to use it

Thanks

paruntha

also, i'm confused whether it is the SYSTEM that runs the workflow for teamSite 6.5 in Windows or is there a such thing as workflow user because I heard differnt things I'm kinda confused about that

Thanks,

PA

nipper

That depends on who owns the job and/or task being executed.

paruntha

That depends on who owns the job and/or task being executed.

Oh so who ever is the owner of the external task which calls the perl script, will use that owner's credentials when executing the perl script?

Thanks

paruntha

I have attached a fragment of iwevents.log file and as well as the workflow object file using the command iwgetwfobj for the job

to give me the owner of external task

but i'm trying to figure out is it using that owner's access permission to run the perl script?

Thanks in advance

paruntha

if someone can help me in this that will be greatly appreciated because I am trying to figure out whether the owner of external task is the one responsible for the perl script's access permissions in the external task or is it the workflow owner?

thanks

PA

Evani20

Hi everyone, I am totally new in this site....please forgive me if I make any mistake. Here PA, to go on your question, I would say owner of your script will be the same owner of that workflow, the external task is getting called by the workflow and to just make sure you can test it with different workflow owner.
Good Luck....