4.1 SP6 Instance Name String Length Limit Bug?

We’ve found that creating schedules with instance names longer than 70 characters are causing the schedules to fail with the following error message:

Could not open the file C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\FileStore\Output\a_021\026\000\6677\012345678901234567890123456789012345678901234567890123456789012345678901_30_9126521297334807839-guid[afd91171-3616-4e8e-a942-f51e55b107fb1].xlsx.

When we shorten the instance names to less than 70 characters the schedules process successfully. Schedule instance names over 70 characters are currently processing successfully in 3.1 SP7.

DBRICHARD (BOB member since 2007-02-01)

The full path name is over 255 characters, that’s probably what’s causing it to fail. I’m not sure why it would have worked before, however.

As a workaround, try moving the whole FRS to the root (i.e., c:\frs).


joepeters :us: (BOB member since 2002-08-29)

Thank you for your reply, but this sounds like a major limitation as compared to 3.1.

In our current 3.1 SP7 environment (we’ll be upgrading to 4.1 SP6 very soon) we have a schedule with a 192 character instance name that runs successfully. With a difference of over 120 characters (192 vs 70) this must be an issue beyond the install path.

We will contact support in hopes this limitation can be remedied.

DBRICHARD (BOB member since 2007-02-01)

We are on BI4.1sp5 and it appears that the have added the quid to the instance name but I haven’t seen an instance name as long as the one that you have listed here. I really don’t understand why they have to make the file name so long. I would think if anything, just the QUID would be sufficient for how it is stored in the filestore. I’ll be interested to hear what support has to say about this.

We had to change our Temp directory and the FileStore directory in our installations and we started out on BI4.1sp2.

JohnBClark :us: (BOB member since 2007-03-27)

I am using 4.2 SP6 and keep getting the scheduler error on LONG report names as well.

When I rename the reports to shorter length, the scheduler is successful.

Any solutions that I might not know of?


eelza (BOB member since 2017-07-03)

Only what I posted above… Move the frs so it has a short path.

joepeters :us: (BOB member since 2002-08-29)