'SetReportFile' was shown as "FAILED". I never really found out what this error was about. But the good news is - go ahead and process your MDP task. It works just fine! Almost 90% of my old MDP 6 processes had this error when I verified the .dpf. And they all worked just fine. I remember looking through the Help Menu on this before. When you are looking at the message under the Verify Tab hilight the error message and double click for the details of the error. The details for the Error Message were: "Failed".

No big deal though as I just trudged ahead and ran the prcoess. The process ran fine with no error messages by viewing the MDP Process Scheduler log files (view process events - no errors!)

Go ahead and run the process. Unless there are other messages in the verification, you will be just fine! Another glitch in MDP6...

You need to add some sort of file handling process for this to work. Click on the Workflow Tab. Pre-Processing field can be left blank. When you click on the Process Options tab you will get the error message; "Error opening report file".

Click "OK" to this message. Click on the Post-processing tab. This can be left blank too. Click on the File handling tab. This is where you need to tell MDP what to do with the file after being processed with Monarch.

The Report File Handling Options need to be set. I click the radio button to set the option:

"Move Report File To This Location". And I set a location for the report file to drop to using the browse function. Let me know if this has already been set or not...

Do you have a process set for this .dpf in the MDP Process Scheduler? If you do please advise of your settings and what happend when you drop a file in the correct location for processing. Let me know what your processing parameters and Execution Triggers are.

I have tried to re-create your error but cannot. Every time I run a sample file with the same parameters I get an output. The only other thing I can think of is that you change the location of your source .txt file to pick up from another location different from the model file.

Hi, the only thing I can think of, is that if this is a server version of Datapump, then the Datapump Service needs to run under an account which has the necessary rights to the folders where the reports reside (models as well)

Gareth

Originally posted by Darren:

Yes'B,

I have tried to re-create your error but cannot. Every time I run a sample file with the same parameters I get an output. The only other thing I can think of is that you change the location of your source .txt file to pick up from another location different from the model file.