Writing output to networkdrive using fileset-local

[Michael Vork]

Hello everybody,

I am experiencing a problem writing the output from the fileset-local protocol to a networkdrive. A forward slash is added to the file location, resulting in an error.

Example:

Drivemap is X:

Filename is Btype.12.xml

Location of the file should be X:Btype.12.xml

Attemped location is X:/Btype.12.xml

Error message: Error Msg: Cannot open X:/Btype.12.xml: No such file or directory^J

Cloverleaf is running on Windows.

Has anybody been confronted with this problem in the past?

If so, where you able to fix it?

If so, are you willing to share your knowlegde?

Thanks in advance for your repsonse.

Greetings,

Micha

Topic

[Frank Grube]

Hello,

try please UNC-Path:

//server/share/…/Btype.12.xml

[Levy Lazarre]

Michael,

Frank’s suggestion is great.

However, I am wondering if you are not experiencing permissions issues with the mapped drive.

In Tcl on Windows, both X:/Btype.12.xml and X:\Btype.12.xml are valid paths and should work, so you could be dealing with privileges issues.

Can you verify the X: drive is available and writable?

At a Tcl prompt, try the following command:

Code:

% file volume

This should return the X:/ drive in the list, if it is accessible.

Then check that it is writable from Cloverleaf:

Code:

% file writable X:

If writable, then try to manually create a dummy output file there:

Code:

% set fh [open X:/Btype.12.xml w]

% puts $fh “This is a test.”

% close $fh

This should tell you if you have issues with writing privileges to the share.

As a last resort, if you cannot get the fileset-protocol to work, you can change the thread to a UPOC protocol thread instead. Under UPoC Protocol Properties / UPoC Options/ Write TPS, you just have to provide a simple Tcl script that will write the file for you. With the Tcl script, you have complete control on how/where the output file is written. This is quite easy and has worked very well for me.

I hope this helps.

[Michael Vork]

Levy and Frank,

I tried both your suggestions. The full network path, as suggested by Frank, does not help.

I tried the suggestions of Levy and have to conclude that there is not an autorization problem.  

The strange thing that is actually happening is that, on saving the netconfig, there is not a error displayed.

However, once the engine is started in which the thread is defined, the processlog indicates the following:

[nci :nci :ERR /0:    FIN_1_cmd:12/29/2011 09:57:37] Check NetConfig error – error list:

FACT_VILA_IN Protocol Fileset/local-tps: OB directory ‘X:’ is not a directory.

Apparently the check on validity of the netconfig, upon saving, is different from the check which is performed upon starting the engine.

I’ll give it a try by using a UPOC.

Thanks for thinking with me.

Grtz,

Micha

[Levy Lazarre]

Michael,

How do you specify the directory in your NetConfig?

You should try X:/ or X:\  as expected by Tcl.

It appears that the directory validation occurs when the process is started, not when the NetConfig is saved.

X: is not a valid directory in Tcl since the is an escape character.

[Michael Vork]

Levy,

I tried them all, including the UPOC alternative you suggested.

It is simply is not going to happen.

Thanx for your support.

Greetings,

Micha

[Mike Kim]

I’m experiencing the same issue and the folder is writeable from Tcl.

Thanks!

[Donna Bailey]

Does your tcl testing tool work, but not when you try to run through the engine?  I had to make sure the Network user was the one who started the Windows service…once I fixed that, I could use the UNC path.

Donna

Donna Bailey
Tele: 315-729-3805
dbailey@microstar.health
Micro Star Inc.

[Max Drown (Infor)]

Cloverleaf on Windows is run by the “hciuser” user. This is a local user to the server. This is the user that must have permissions to mapped drives, shared folders, UNC paths, etc.

-- Max Drown (Infor)

[Author]

Replies