EnsLib.File.OutboundAdapter + fully qualified path names

[M. Kurz]

Hi,

am I getting something wrong here or is it impossible to configure a
fully qualified path name with EnsLib.Hl7.Operation.FileOperation
+EnsLib.File.OutboundAdapter?

As far as I see, it doesn't work.

best regards,

Michaela

[Dale du Preez]

Hi Michaela,

What is the exact problem or error that you are seeing?

If you are on a Windows network, you may be seeing some OS-related behaviour involving mapped/shared network drives and the user Ensemble runs as**, but I am not sure if this has any bearing on your problem.

Dale

** To outline that further, by default Ensemble runs as the local SYSTEM account on Windows, and this user's session may not have shared drives mapped to a letter drive. In other words, you may have problems accessing S:\Your_Folder\ if SYSTEM doesn't know that S:\Your_Folder\ points to \\shared\Your_Folder\. If you access the UNC path directly, say \\shared\Your_Folder\ you should be able to access the files. If that fails, then I suspect that we are seeing a different problem.

[M. Kurz]

Hi Dale,

thanks a lot for your answer. I'm not using any drive letters, just
UNC paths, so I don't have a clue what the problem might be.

I get the following error:

FEHLER #5005: Kann Datei '\\pc59102\Downloads\test\out.hl7' nicht
öffnen.
=
ERROR #5005: Cannot open file '\\pc59102\Downloads\test\out.hl7'.

If I write the file from a commandline, it works ok. Ensemble is
running as user ensemble, and I created an account with the same name
and password on my pc pc59102.

Is there a way I can get more detailed error information? I set
^Ens.Debug("TraceCat", "file") to 1, is there any more I can do?

best regards and thanks a lot for your answer,

Michaela

On 21 Apr., 13:35, Dale du Preez <dale.dupr...@intersystems.com>
wrote:

> > Michaela- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

[Dale du Preez]

Hi Michaela,

In this case, it sounds a lot more like a permissions issue for the Ensemble user. Because a number of Ensemble processes are started in the background, the user for Ensemble production processes is often different to the one you would use when opening a csession, as well as being different to the user that started Ensemble.

The next steps here are to identify which user the core Ensemble processes are running under, and working out whether that user has permissions to access the files in your UNC path. You can do this by starting your production (so we have some of these processes running) and then going to the Jobs page in the Ensemble Management Portal, where you should choose a particular PID, say 12345.

Next, at your Unix/Linux terminal, run a command like:
    ps -a | grep 12345
You may need to escalate your privileges in order to run the command, and/or may need to get an administrator to run the command for you.

That should list which user the process is running under, and from there you should be able to identify whether this particular user has access to the share and/or the files in the share.

If you are still having problems after going through those steps, then you should contact the WRC so that we can work out exactly what is happening.

Dale

Dale du Preez
Support Advisor
Dale.d...@intersystems.com
+1 (617) 621 0700
+44 1753 830 077
Please CC sup...@intersystems.com with regard to any active problems so that you can receive assistance should I be unavailable.

[M. Kurz]

Hi Dale,

unfortunately this Windows Server 2003 64 bit (German). The Ensemble
Controller service is running as Local System. Unfortunately, there is
no Windows resource kit for 64 bit, so I can't try a batch file with
srvany.

I haven't opened a support case before, I'll have to ask my SE.

thanks for your help,

Michaela

On 21 Apr., 15:16, Dale du Preez <dale.dupr...@intersystems.com>
wrote:
> Hi Michaela,
>

> In this case, it sounds a lot more like a permissions issue for the
> Ensemble user. Because a number of Ensemble processes are started in the
> background, the user for Ensemble production processes is often
> different to the one you would use when opening a csession, as well as
> being different to the user that started Ensemble.
>
> The next steps here are to identify which user the core Ensemble
> processes are running under, and working out whether that user has
> permissions to access the files in your UNC path. You can do this by
> starting your production (so we have some of these processes running)
> and then going to the Jobs page in the Ensemble Management Portal, where
> you should choose a particular PID, say 12345.
>
> Next, at your Unix/Linux terminal, run a command like:
>     ps -a | grep 12345
> You may need to escalate your privileges in order to run the command,
> and/or may need to get an administrator to run the command for you.
>
> That should list which user the process is running under, and from there
> you should be able to identify whether this particular user has access
> to the share and/or the files in the share.
>
> If you are still having problems after going through those steps, then
> you should contact the WRC so that we can work out exactly what is
> happening.
>
> Dale
>
> Dale du Preez
> Support Advisor

> Dale.duPr...@intersystems.com

> +1 (617) 621 0700
> +44 1753 830 077

> Please CC supp...@intersystems.com with regard to any active problems so that you can receive assistance should I be unavailable.

> >> - Zitierten Text anzeigen -- Zitierten Text ausblenden -