Page 1 of 1

ASCIIOUTPUT From one server to another

Posted: Wed Apr 15, 2020 3:22 am
by MT1
Hi
We have two tm1 instances, Instance 1 running in Server A and Instance 2 running in Server B.
I am trying to asciioutput some cube data from Instance 1 ( which is running in server A) to a folder location in server B.

Here is what I am doing
sCube='Sales Reporting';
sFileName='InterserverDataOutput.csv';
sFilePath= '\\servername\D:\Inbound';


ExecuteProcess('Bedrock.Cube.Data.Export'
, 'pCube', sCube
, 'pView', ''
, 'pFilter', ''
, 'pDimensionDelim', '&'
, 'pElementStartDelim', ':'
, 'pElementDelim', '+'
, 'pSkipRules', 1
, 'pSkipCons', 1
, 'pZeroSource', 0
, 'pDestroyTempObj', 1
, 'pFilePath', sFilePath
, 'pFileName', sFileName
, 'pDebug', 1
);

This is the error message I am getting
Invalid export directory: \\servername\D:\Inbound

Also note
Inbound Folder is a shared folder
The service account used in running the TI has full control for Inbound folder.
Any pointers as to what I am missing.

Re: ASCIIOUTPUT From one server to another

Posted: Wed Apr 15, 2020 4:10 am
by gtonkin
The UNC specified in "sFilePath= '\\servername\D:\Inbound';" is not valid.
If you paste this into Explorer it probably will not work.

Depending on how you have set up your share, it may be:
sFilePath= '\\servername\D\Inbound';
or
sFilePath= '\\servername\D$\Inbound';
(D$ is used when you have not specifically shared but are accessing as an administrator i.e. an administrative share).

You may also need to confirm if Bedrock expects a trailing slash on the folder e.g.
sFilePath= '\\servername\D\Inbound\';

Re: ASCIIOUTPUT From one server to another

Posted: Wed Apr 15, 2020 11:16 am
by tomok
MT1 wrote: Wed Apr 15, 2020 3:22 am sFilePath= '\\servername\D:\Inbound';
This is not a valid path. When you use a UNC path like this, it is in the form of:

\\ServerName\ShareName\Path

I highly doubt that you have a share named "D:". That is a mapped drive letter not a share name.