cancel
Showing results for 
Search instead for 
Did you mean: 

Scheduled Reports to MS Sharepoint are failing randomly

Former Member
0 Kudos

Hi All,

We have a set of scheduled WebI reports that are being sent to the Sharepoint folder.

But most of the reports randomly fail with the following error:

source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]

We have also searched through most of the related threads in SCN and did not come across any solution that helped in our scenario.

Any help/pointers will be greatly appreciated.

Thanks,

Jasmine.

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Got the same error and was able to achieve this by changing the share point location but reason of failure was unknown.

Former Member
0 Kudos

Hi Samatha,

We have actually scheduled the report to another network location, and it works perfectly file. It's just the sharepoint that acts up like so.

Let's hope we get a permanent fix for this.

-jas.

Former Member
0 Kudos

Make sure the service account has an access to Sharepoint directory.

And also check if the UNC path is set correctly. Check below KB.

1373496  - How to schedule reports to Sharepoint's Directory using UNC path?

Former Member
0 Kudos

Hi Jawahar,

The service account that we are using has the access, that's how some of the reports are succeeding and some are failing.

The UNC path is also correct since the reports that have successful instances are getting dropped into the Sharepoint location.

Thanks,
Jasmine.

Former Member
0 Kudos

what version of BO you are on? 3.1 or 4.0 and SP.

former_member191664
Active Contributor
0 Kudos

This "source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]" happens randomly, and I suspect that this is a network hiccup.

You can configure the number of retries from the report's default configuration in CMC to, e.g. 3, so that the scheduled job will reattempt to run it for up to 3 tries if there is a hiccup on the 1st or 2nd run.  You'd need to reschedule that recurring job for this number of retries to take effect.

Hope this helps,

Jin-Chong

Former Member
0 Kudos

Hi JinChong,

This was our first guess that it might be a network hiccup, but you never know.

Lets hope it works with the 'retries' method, will give it a shot today and get back.

Thanks a bunch

-jas