cancel
Showing results for 
Search instead for 
Did you mean: 

Connection error in Write File operator

0 Kudos

Hi

I am doing the "Store Sensor Data in Cloud Storage in SAP Data Hub, Trial Edition 2.5" tutorial here: https://developers.sap.com/tutorials/datahub-trial-v2-pipelines-part02.html

This is the pipeline:

When I run the pipeline I always get this error:

The connection of the Write File operator with WASB is configured via the Configuration Manager:

The connection itself works if I check it in the connection manager:

When I use the manual Configuration Type like this:

I get this error:

When using the Data Transform operator in this tutorial: https://developers.sap.com/tutorials/datahub-trial-v2-workflow-part01.html the connection with WASB does work.

Any idea on how to fix this?

Thanks!

Accepted Solutions (0)

Answers (4)

Answers (4)

schneidertho
Advisor
Advisor
0 Kudos

Hi Bart,

last update from my side: whe have a bug (in the trial edition). I hope to fix this with the planned update of SAP Data Hub, trial edition to version 2.6.

For now I have documented the bug here: https://blogs.sap.com/2018/04/26/faqs-for-sap-data-hub-trial-edition/

Best regards
Thorsten

schneidertho
Advisor
Advisor
0 Kudos

Hi Bart,

sorry for the late reply. I tested different scenarios and I am still not 100% sure why this happens. The connection (in the trial which I have created myself) does not look like it should.I got an error as well, but never the error about authentication.

I suggest (as workaround) you:

- edit the connection in Connection Management and maintain the endpoint suffix. Please set to: core.windows.net

- you (continue to) use the connection maintained in Connection Management when you create the graph

Let me know if that helps. In parallel I will check why we don't maintain the endpoint suffix (re. why we don't use the default).

Cheers
Thorsten

schneidertho
Advisor
Advisor
0 Kudos

Hi Bart,

I tested myself with manually maintained credentials in several systems (including a trial environment) and did not face a problem. But the configuration of my operators might be different from yours.

Does this issue happen in a trial or a "productive" system?
If trial => why don't you use the connection from connection management in the operator? Does it also give the same error when you do?
If "produtive" system => in that case, best would be to open a support ticket

Cheers
Thorsten

0 Kudos

Hi Thorsten

Thanks for your reply!

This is on the trial. I did use the the connection from connection management first like this:

But then I always get this error:

The connection itself when checking the status in Connection Management does work btw.

Hope this helps!

BJarkowski
Active Contributor
0 Kudos

Hi,

I also had some problems with the Write File operator. Not sure if that's fixed in the latest release of Data Hub, but I ended up using Flowagent File Producer.