Relational connection to an Excel file shared by Azure

[former_member272418]

Hi guys

I can't create a relational connection to an Excel file shared from an Azure folder.

The BO I'm using is 4.2 SP05 patch 02 installed on Windows 2012 R2.

So far I have successfully created other relational connections to Excel files shared by file servers. To do this I have always used the Windows 32 bit ODBC driver for Excel (version 14.00.7248.5000) and then selecting "Excel 12.0" as the "database version" in the DSN configuration. Then, in the Information Design Tool, I use the network layer "ODBC" and the "database" MS Excel 2007 and everything is ok.

To configure this shared folder from Azure, I ran a power shell script (provided to me) that maps the share as drive Z. The script basically runs the following two commands:

cmd.exe /C "cmdkey /add:`"<BLAHBLAHBLAH>.windows.net`" /user:`"<USER>`" /pass:`"<PASSWORD>`""

New-PSDrive -Name Z -PSProvider FileSystem -Root "\\<BLAHBLAHBLAH>.windows.net\<SUBFOLDER>" -Persist

I can see the unit Z in the VM's resources and I can navigate through the folders. So I set the ODBC DSN to point to the file on the newly mounted drive but, when testing the relational connection I'm getting the following error:

I downloaded the excel file locally to the BO's machine and had the ODBC DSN point to him and, obviously, everything is ok.

I also tried copying this Excel file to a shared folder from another host on the same network and again, by pointing the DSN-ODBC to it, the relational connection works.

So I'm wondering, maybe there are compatibility issues for BO in accessing shared folders from Azure? Anyone have information?

Let me know, thank you very much.

[former_member446821]

Thank You PANCOTTA i have a similar issue on a normal Windows Machine!

[denis_konovalov]

what is the actual path you're using in DSN ?

[former_member272418]

Hi Denis

since the shared folder is mapped as unit Z the path of the file, in the ODBC DSN configuration, is:

Z:\CP-A004-Project Basic Info.xlsx

However, I also tried to not use the mounted unit Z and write the full path of the remote resource:

\\<BLAHBLAHBLAH>.windows.net\testfilesharetecm\CP-A004-Project Basic Info.xlsx

In this way I am getting a different error while testing the relational connection:

"Failure creating file"

[denis_konovalov]

soo, this test shows that Z:\ path is not working and UNC path does, but the tool can't create some temp file
I'm afraid you'll need to trace failing workflow and see what really happens.
KBA https://launchpad.support.sap.com/#/notes/2103024

[former_member272418]

Hi Denis, thank you again.

I tried to see the detailed log from IDT using the SAP Note 1934985... but it doesn't seem to be useful 😞

[former_member272418]

Hi everybody

thank you for your answers.

SAP support confirmed that the shared folder mapped as logical unit are not supported (look at SAP Note 1342998)

So I am working with the Azure management team to solve the access by UNC that, in my case is not working.

Most likely the problem is about the authentication on Azure resource.

I'll keep you posted.

Regards.

[denis_konovalov]

Just to clarify - I did not said anything about "not supported", I said the test showed that its not working. I was not aware of the KBA 1342998

[former_member272418]

Hi Denis I'm sorry if I wasn't precise.

I just corrected my incorrect quote.

My apologies