I am having weird issue in BO 4.3.
Scheduled a report to network shared drive as the pdf and it works fine.
Scheduled a report to network shared drive as excel but it fails with error:
source file error. [Invalid argument]: [CrystalEnterprise.DiskUnmanaged]
We would need more information to be able to comment on this. Can you post the configuration of the schedule that you configured?
is it the same destination ?
did you enter the path to the „Destination_AllowList.txt“ ?
So, we did more test. The issue is sporadic. We were able to write to the shared drive both pdf and xls about 2 out of 10 times.
There are other users who can schedule to the shared drive without any issue but their shared might be different. User has access to the shared folder and can write to it.
What is „Destination_AllowList.txt“ and does it matter in our case if the issue is sporadic
When Business Objects writes files out to a LAN location, it uses the account that is running the Server Intelligence Agent to write the files, not the account of the user. Sounds like this probably isn’t the issue though if you are getting some successful writes.
Yes… but we are writing to the shared network drive that user has access to and can write to it. It does need username/password because one time we didn’t put any login info and the error was ‘Login failed’. Once we enter the username and password, it worked a couple of times and then failed.
Oh yeah, you can specify the credentials to be used to write the file in the destination properties when the report is scheduled. I forget about that because we don’t use it.
If you leave this blank, it will use the account that is running the Server Intelligence Agent. This is how we handle our scheduling.
Did you check your log files for the report run to see if you could get more information?
As of 4.2 SP09 Patch 1100+, 4.3 SP02 Patch 800+ and 4.3 SP03 and higher versions, due to the security vulnerability (CVE-2022-41267), an additional configuration should be made (Destination_AllowList.txt) to allow sending the file to an unmanaged disk to use (destination - file system) and sending without this additional configuration no longer works.
It is now mandatory to explicitly allow the locations you wish to schedule to
Not that I think the AllowList is the problem in this issue, since files can be written to the directory some times, here is the reference documentation for setting up AllowList for the upgrades listed since the AllowList became mandatory with those releases.
SAP KBA 2477817 - Error “CrystalEnterprise.DiskUnmanaged” when scheduling a report to file system after upgrade to 4.2 SP09 Patch 1100, 4.3 SP02 Patch 800, 4.3 SP03 
The KBA also includes the options for configuring this in early versions of Business Objects to also address the CVE.
This is very good information. Thank you so much. I will check and update you guys.
I was able to access the article as well. I will follow the steps provided.
One question that is still bothering me. There are many users who could write to the network drive.
Only 2 people can’t write and one of them is also sporadic.
The only common thing between the 2 users is that their windows password expired, and they had to reset it.
Since then, they can no longer write to the network drive.