8 Replies Latest reply: May 15, 2014 10:09 AM by akalyan _ RSS

    Project Conversion error

    akalyan _

      I am trying to convert a monarch version 6 .dpf file to a version 10.5 project file using Monarch version 10.5.0.2.

      I get the meesage:

      System.IO.FileLoadException: Could not load file or assembly 'Interop.DPSCHEDCONVERTLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

      File name: 'Interop.DPSCHEDCONVERTLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'

       

      What could be the reason?

        • Project Conversion error
          Olly Bond

          Hello akalyan

           

          I would expect that a v6 Monarch project file would be .prj, and a model file would be .mod. Both of these could be converted using the Monarch Utility provided with Monarch.

           

          I've never seen a dpf file and I'd be fascinated to know what it is. Do you think you could email it to me? Perhaps it's an early format for a DataPump process definition - in which case extracting the relevant projects and links to models should[/B] be feasible... 

           

          Best wishes,

           

          Olly

            • Project Conversion error
              elginreigner _

              Olly, best I could find is Vessel Drafting Program File, related to an addin for AutoCad.

               

              But as  programmer, I know that extensions mean nothing as I could write an app to replace the .prj if I wanted. It would be foolish to do so though.

                • Project Conversion error
                  elginreigner _

                  The internet rocks, found these too Olly:

                   

                  •DanProgrammer (Script) by DanSoft

                  •Dataplore Figure(analysis of signals and time series data)

                  •DeltaDOS Delta Patch File

                  •Dictaphone Walkabout Express

                  •Document Processor (FLOW Project File)

                  •Dynamic Process Format (Database) by BarcoPrinted

                  •F-Secure (Default Policy File) by F-Secure

                    • Project Conversion error
                      akalyan _

                      The file looks as below, the extension of the file is .dpf:

                       

                      ReportFile=D:\ABCD\PQ.txt

                      ModelFile=D:\ABCD\PQ.MOD

                      Type=2

                      Compress=0

                      IncludeModel=0

                      IncludeTree=0

                      UsePassword=0

                      Password=

                      PRFName=

                      FilePrefix=

                      NameType=0

                      DateType=0

                      IncludeDatabase=0

                      UserFormat=

                      Database=

                      Table=

                      ExportVersion=

                      ReportEngine=0

                      ReplaceRecords=0

                      FileExt=

                      FilePrefix=

                      NameType=0

                      DateType=0

                      UserFormat=

                      Database=UAT

                      Table=PQ

                      UID=ABC

                      Password=XYZ

                      ReplaceRecords=2

                      TransactionSize=1000

                      Database=

                      FileExt=xml

                      FilePrefix=

                      NameType=0

                      DateType=0

                      UserFormat=

                      Schema=

                      Style=

                      Total=19

                      Mapping0=ACCOUNT_ID+ACCOUNT_ID

                      Mapping1=B_DATE1+B_DATE1

                      Mapping2=B_DATE2+B_DATE2

                      Mapping3=B_DATE3+B_DATE3

                      Mapping4=CCY+CCY

                      Mapping5=CUR_BAL+CUR_BAL

                      Mapping6=F_CLASS+F_CLASS

                      Mapping7=GL_NUM+GL_NUM

                      Mapping8=L_BAL+L_BAL

                      Mapping9=M_C_BAL+M_C_BAL

                      Mapping10=M_L_BAL+M_L_BAL

                      Mapping11=M_P_BAL+M_P_BAL

                      Mapping12=P_BAL+P_BAL

                      Mapping13=PROC_CTR+PROC_CTR

                      Mapping14=REF+REF

                      Mapping15=RPT_DATE+RPT_DATE

                      Mapping16=SB+SB

                      Mapping17=TRAN+TRAN

                      Mapping18=TYPE+TYPE

                      Total=0

                      Total=0

                      MultipleReport=0

                      Filter=

                      ExportType=0

                      Total=0

                      ReportDestLocation=

                      ReportDestName=

                      ReportDestFormat=

                      ReportDestExt=

                      ReportDestType=0

                      ProfileName=

                      ProfilePassword=

                      MailAddress=

                      MessageTitle=

                      MessageText=

                      Route=0

                        • Project Conversion error
                          Olly Bond

                          Hello,

                           

                          That's definitely an old DataPump format. I don't have an XML export of a modern DataPump process to hand here - but PreProcessing and PostProcessing give it away. DataPump used to exist in a desktop "Personal" edition - we're talking ten years ago, so Monarch v6 would sound right - and with DataPump you have a "process" - a sequence of projects (each calling their associated input data and model). As well as the project files, it allows you to run scripts at different stages (pre & post processing) and manages distributions for you.

                           

                          It looks from this that the DPF format did away with Monarch Project files and let you just specify the input & model. To convert it, I think you're going to need to contact Datawatch support, or even the developers. You could convert the ModelFile=D:\ABCD\PQ.MOD into an XMOD easily using Monarch or Utility. You'd need to build a new project file to specify the input and export paths, and I'm guessing that the only project export here was:

                           

                          [DestODBC]

                          Database=UAT

                          Table=PQ

                          UID=ABC

                          Password=XYZ

                          ReplaceRecords=2

                          TransactionSize=1000[/CODE]

                           

                          ... so writing out to the PQ table in the UAT database with credentials ABC,XYZ, but whether ReplaceRecords=2 means "overwrite" or "append" I've no idea.

                           

                          Good luck!

                           

                          Best wishes,

                           

                          Olly

                            • Project Conversion error
                              Bill Watson

                              As olly says, DPFs are the datafile of choice for old versions of datapump - we still have an archive folder full of them from our old version 5 DP.

                               

                              I can't recall what we did exactly when we moved to DP8, but I am pretty sure we had to create projects and then add them into our new installation manually. It gave us the opportunity to cleanse a lot of the processes which had got convoluted over the years.

                               

                              Edit: I tell a lie - have a look at Program Files > Datawatch > Monarch Datapump >  Utilities > Conversion Tool

                               

                              This seems to allow you to take DP6 DPF files and create DP7 (in my version of the tool) Project files. You would then manually add each project to the new Datapump processes. The project files created with this tool are perfectly usable, however they do not use any functionality from later versions of monarch.