Error preparing to read file - Local Object Library

[system]

Hi all,

My task is very simple, however it makes me crazy since 2 days :/.
I need to import data from xls file into staging tables. Very simple, but…

I decided to use Local Object Library → Excel Workbooks functionality. I connected to my file, everything is ok so far. Then I drag & drop this file onto data flow, query transform, target and done ;). In the data flow when I click on the excel source, I can see the data without any problems.

When I run a job, it gives me an error: "Error preparing to read …, Exception occurs when executing ‘begin’ method of the adapter operation with ID . No files were found in names like \10.177.177.117\etl/bart.xlsx.

I’ve read somewhere on the forum, that the path for the file should be threat like a path from a server, that’s why I use an IP address. This IP address in my local desktop address, where the client is located. I also tested it with c:\etl folder, but it was the same.

My DS Server is installed on linux , different address.
I’ve also tested scenario, where these files should be on the server, not local desktop. So I copied files to the server, error was the same.

Can anybody tell me, is this an architecture issue, or BO DS issue?

I use BO DS 4.1 SP2, client is installed on my desktop (10.177177.117), server is somewhere else.

I’d be grateful for any info.

Thanks
Bart

---

golicz (BOB member since 2014-02-13)

[system]

When you view the data via the looking glass the file is locally viewed.

Your job server cannot reach the location of the file, hence the error during execution.

---

Johannes Vink (BOB member since 2012-03-20)

[system]

Hi Johannnes,

Thanks for reply.
So you suggest, that in the location of the file I should use the path from job server location?

So I’ve tried this, putting my desktop IP and folder. Of course I shared this folder with “everybody”, and it didn’t help :/.

What I’ve tried also is that I put these files on server location, but I wasn’t sure where it should be (what folder, and what path is then ? )

Thanks
Bart

---

golicz (BOB member since 2014-02-13)

[system]

The file should be placed on a location where the job server can access the file. That is either locally on the physical server or on a shared location (that can be reached from the job server).

You shared your pc with everyone, but that is not a guarantee that the job server can reach it. Either a mapped share, authorisations or some unix/samba thing.

---

Johannes Vink (BOB member since 2012-03-20)

[system]

Ok,

I’ve tested scenario, where files are on job server. I used filezilla to copy these files.

And I still have an error :/. What’s more, I can’t import the schema now, cause my desktop doesn’t have an access to this server.

Please see below.

Thanks
Bart

P.S. bt/BO/SP4 etc is of course on the linux server

---

golicz (BOB member since 2014-02-13)

[system]

… maybe it has to be in a DS “bin” folder ?

---

golicz (BOB member since 2014-02-13)

[system]

I don’t know about your security setup, so I don’t know how much the BODS user can access certain folders.

Also about xls and unix: I do not know if BODS does support it out the box (I hope so).

You could test with a flat file if the location can be read by BODS.

Could you also try a simpler selection on Excel? Just all fields?

---

Johannes Vink (BOB member since 2012-03-20)

[system]

Johannes,

Thanks for your reply.

After your suggestion, a created a folder on job server, changed permission to all user and put a txt file there. I run a process and everything went ok !!!

Then I did the same with xlsx file. Unfortunately, it generated an error, the same one :/.

Hmmm, so what now ? Any ideas ?
Do I really need additional component to be installed ? Ehhh

Thanks
Bart

---

golicz (BOB member since 2014-02-13)

[system]

Not sure if you are in supported product platform…

There was this note "1296454 - Cannot find worksheet - Error preparing to read :<Exception occurs when executing ‘begin’ method of the adapter operation with ID[number]> " which dates long back to a 12.x version for something called POI or whatever it is.

Look into that.

---

ganeshxp (BOB member since 2008-07-17)

[system]

Ah that triggered me. There were some SAP Notes or even fixes.

1777068 - Error Could not find worksheet in file <unix\linux path> Error preparing to read : <Exception occurs when executing ‘begin’ method of the adapter operation with ID [number]

Cause

Unix, Linux is case sensitive and the sheet name is case sensitive as well. When the excel file is read from Unix or Linux , the sheet name should exactly match to whatever is defined in Access method: Worksheet “”, in the excel workbook format.

Resolution

Change the Worksheet name in format to exactly how it is specified in the Excel document’s worksheet.

1908954 - How to use Excel source on Linux/Unix - Data Services 4.x

Resolution

To use an Excel spreadsheet as a source on a Linux or Unix job server, the job server will need to have support for adapters enabled in Server Manager. An Excel Adapter associated with the appropriate job server will also need to be configured in the Data Services Management Console to be able to use an Excel file as a source.

1798810 - Is Microsoft Excel 2007 or 2010 Supported for Linux or Unix? - Data Services 4.0

Resolution

As noted in the Supported Platforms Matrix documentation, Microsoft Excel 2007 format (xlsx) is not supported for Data Services 4.x running on Unix or Linux

So summarized:

• Check case sensitivity
• Check that you did setup an Excel adapter
• Xlsx is not supported

---

Johannes Vink (BOB member since 2012-03-20)

[system]

HI Guys again.

So, I’ve checked 3 things below:

a) case sensitivity - ok
b)excel adapter - - it’s been set up and is up and running
c) changed file to be MS Excel 97-2003 (*.xls)

And guess … Unfortunately it’s not running, I have the same issue.

I will rise an OSS with SAP. Maybe they will tell me what is wrong.

Thanks anyway

Bart

---

golicz (BOB member since 2014-02-13)

[system]

Hi,

Just want you to know, that we’ve re-installed BODS again (4.0, SP3) and everything works fine.

No idea what was the issue

Thanks for your help.

Bart

---

golicz (BOB member since 2014-02-13)