Sap Business One Invalid Report File Path

[Riitta Palazzo]

The error show, not getting the path of crystal report file. Generally good coding is you set all your crystal report in one folder in your working directory and just create an entry in web.config to access path like

The problem is that the Crystal Reports runtime continues to look for the report files on the C: drive, even though that drive does not exist, and it reports in the log files that it is looking for the reports on the correct drive letter.

If you don't know your computer's machine name, right click on the My Computer icon and go to Properties, then to the Computer Name tab. On the Full computer name: line, we need everything up to the . For example, if it says jason.wasp.com, we just need to know "jason". Also for this example, we will use I: as the existing drive.

To map the drive, open your My Computer icon, then on the Tools menu select Map Network Drive. For Drive, select C:. If you don't see C: as an available choice, that letter may have been assigned to a removeable drive in the Disk Management component of Computer Management. Change that drive to another letter; then C: will be available for mapping.

My customer using SAP 10 FP 2111. We are using Document Printing wizard to print bulk document from AR Invoice screen. We are taking more than 50 prints at same time with this wizard. System is printing 40 to 45 layouts without any issues but after that system troughing error is "Invalid report path file", "The report file name was empty", Cannot load the rpt file" because of this after that not printing.

In the same customer we have developed the add-on and there we enabled the print layout as well. It was working before, Suddenly its not working and same error "Invalid report file path error". can we have any solution for it. Please suggest me on this.

I am trying to schedule a report and save the report is a particular file location. So I scheduled the report and in Destination\File Location i gave the path where to store, but when I do this my report fails and the error it gives is 'source file error. CrystalEnterprise.DiskUnmanaged: Invalid argument '.

I am having the same error. I have enabled the unmanaged disk and I have used a username and password that is a Domain Admin account. Using the account I can access the share I want tot copy the PDF output to with no problem. If I schedule the output to a local drive (on the XI server), it creates and saves the PDF properly. The arguments do not change when I run the report. Any ideas?

And our existing weekly and some daily Webi reports failed for the last 2 days due to this error. And these are not new reports, they are all existing reports that has been generating for the last 1 year or so.

We solved this issue in our environment. It has something to do with the server name. In our case, the UNC path to the Unmanaged Disk had the servername:
\ServerName\folder1\subfolder1\subsubfolder1a\subsubfolder1b.

Both servers execute under the service account that has admin privileges on the BOXI servers. We control access to the file server directories through AD Access Groups, and the service account has rw privileges through the Access Group to the destination directories. As a result, I leave the destination username and password blank.

After investigation, I noticed that on the server 1 CrystalReportsJobServer Metrics page, Unmanaged Disk Destination Default Settings Valid was true, whereas on server 2 it was false. Since I could see no way to change it to true, I went to the Destination page on server 2 and Removed the File System entry. After saving and closing the change, I came back in and Added it again.

I have had similar problems with scheduling reports via the CMC to save to a file location on another server.
Like other people who have posted replies to the post I also experienced the source file error. CrystalEnterprise.DiskUnmanaged: Invalid error. To fix this I had to get the service account that runs the scheduled reports to have admin rights to the file location that the scheduler was attempting to write the reports to.

I know this is an old topic, but I was facing the same problems. It took me alot of reading, trial and error. Nothing worked. It was driving me crazy. Yesterday it came to me. For the destination path I was using the follwing:

Hi guys, I've been migrating .rdl reports from AX2012 R3 to D365. While trying to deploy one of these reports in visual studio, I get the following error and no further explanation: "Path: [AxReport/.../Designs/PrecisionDesign1/Expression]:PrecisionDesign1: Field expression is invalid since there is no context dataset."

What I've been doing to migrate the reports is convert the .rdl file into an .rdlc, and replace the .rdlc file on the designer of the report. The report designer is ok with this since it doesn't throw any other error when trying to compile. I have already defined a dataset on the report (a data provider class with its correspondent tmp table), and the fields on the report correspond with the ones on the dataset. I have also looked at the metadata file of the report and the definition of the dataset are all set to the dataset I defined on the report.

Yes, I figured it out... you have to check that every tablix element in the report design has a dataset associated to it. When you finished assigning the datasets, save the design and re-deploy the report. I tried it on multiple reports and it worked everytime.

We've recently had the computer which holds our Sage data crash. We thought we'd successfully moved the Company file to a new location, but although everything else is working, we can no longer print customer invoices. The error message we get is "Specificed report path is invalid". The command works fine in the Demo Data, and all other reports work within the Company. It seems to be only when trying to Print an invoice that we get the error.

When running trying to run the Company tax report option I am getting the following error message "The specified path for the output file doesn't exist" as it is year end its timing is impeccable :-(. I am hoping someone has had this error before and could point me towards where to fix it. We were also at the time trying to create a new blank company for the future but don't believe this should have impacted on the current live company. Any help and advice would be greatly accepted.

I have had this same issue. i am trying to print to screen and i am receiving the error message you stated. The file option is not checked though there is a file name greyed out in there. I took out the file name which is for another user and was able to print to screen. i would not think having it unchecked with a saved file name in there would cause an issue though. Any suggestions?

The error occurs primarily because of improper path to a specific local or network drive. Before printing the report, point to "Destination" button under which there are three options (Screen, Printing and File). For the file option, there is a specified path, which appears to be incorrect

Verify that the output path in FRx is a valid path: On the Company menu, click Information. The Company Information dialog box. Select the FRx System Information tab; verify thatthe Import/Export path is valid.
Verify that the File Name path is valid in the Catalog of Reports in FRx: Click the Output tab. Click the Output Options tab. Under File Name verify that the path is valid.
Verify how much disk space is available for the file: Open Windows Explorer.Select the Local Disk (drive letter: ) that the report is stored on.Right-click on the Local Disk (drive letter: ) and click on Properties. The Properties window opens. Verify the available free space on that local disk.
Verify the user has permissions to the IO_Data folder: Open Windows Explorer. Right-click the FRx main folder for FRxReporter andselect Properties. Click the Security tab.Verify that the user has full permissions for that folder and all sub-folders. If you are not able to verify permissions please contact your Administrator.

I'm at a bit of a crossroads with some API design for a client (JS in a browser) to talk to a server. We use HTTP 409 Conflict to represent the failing of an action because of a safety lock in effect. The satefy lock prevents devs from accidentally making changes in our customers' production systems. I've been tasked with handling 409s a bit more gracefully on the client to indicate why a particular API call failed.

My solution was to wrap the failure handlers of any of our AJAX calls which will display a notification on the client when something fails due to 409 - this is all fine and works well alongside other 4XX and 5XX errors which use the same mechanism.

A problem has arisen where one of our route handlers responds with 409s when encountering a business logic error - my AJAX wrapper reports that the safety lock is on, whilst the client's existing failure handler reports what (it thinks) the problem is based on the body of the response. A simple solution would be to change either the handler's response or the status code we use to represent the safety lock.

Which brings me to my crossroad: should HTTP status codes even be used to represent business logic errors? This question addresses the same issue I am facing but it did not gain much traction. As suggested in the linked answer, I'm leaning towards using HTTP 200 OK with an appropriate body to represent failure within the business logic.

The 409 (Conflict) status code indicates that the request could notbe completed due to a conflict with the current state of the targetresource. This code is used in situations where the user might beable to resolve the conflict and resubmit the request. The serverSHOULD generate a payload that includes enough information for a userto recognize the source of the conflict.

c80f0f1006