TDMS 3.0 Installation

Hi Folks,
I'm new to TDMS. We are going to install it in our systems. Till now what i bag the info regarding TDMS is like
Eg:   Central/Control system  = TDMS
        Sender System             =  ECC 6.0
        Receiver                        = Solution Manager ( I'm Not sure of the version )
OS is Windows 2008 R2 :   DB is MS Sql 2008
I refered so many guides regarding TDMS Installation in SMP . Its bit confusing for me.
Can any TDMS Gurus please eloborate the process how to start from first to last. Or else is there any step by step
TDMS 3.0 Installation
Thanks & Regards
Raghu

Hi Raghu,
Please find the answers below:
1. What is the impact on both the servers ?
-> There's no impact as such. TDMS will transfer the data from the sender to the receiver system using RFC connections.
There will be jobs scheduled on both these servers.
2. Will it create the RFC Connections automatically ?? Or do we need to be done in manually ?
-> For TDMS execution, you need to create and sepcify the RFC destination using activity "define RFC settings" in "Technical Settings" phase of TDMS process tree.
3. Insted of doing shell creation we take an export from sender , can we import it into reciver system ??
-> The main pre-requisite of TDMS is to have same repository on sender and receiver side.
We recommend to use TDMS shell creation or System copy to bring the repository in synch.
If you can do so by import and export method, it should be ok.
Thanks and Regards,
Rupam

Similar Messages

  • "TDMS Open.vi" won't open file if not administrator

    I have an app that I install and run from a subFolder of the program files folder, and there's a TDMS file that installs alongside it (it's a set of pattern match data that the app needs).  When the app calls "TDMS Open.vi" everything works fine if I'm logged on as an administrator, but I get an error 8 (file permission error).if I'm not.
    When I'm not an admin, I can run the exe that's in the same folder - why can't that exe then load the TDMS file?  What am I missing here?
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

    Ben wrote:
    crelf wrote:
    Why do I feel like I'm having an ACME Do-It-Yourself conversation?
    That's because you are used to LAVA.  We have trouble spelling TDMS or LVOOP on this forum.
    At least someone's watching   Thanks Ben!
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

  • Pre-requisites before doing TDMS installation

    Hi,
    Can any one give me pre-requisites before doing TDMS installation
    Regards
    Kiran,

    Hi,
    Please check the documents in the First Post of the Forum i.e.
    Links, Documents, Support Pack Schedule
    This would give you all the details that are required.
    Regards,
    Suman

  • Trouble during TDMS installation

    Hi there,
    I hope this is the correct forum for this issue. If otherwise please point me out to the best place to ask this question.
    I started installing TDMS using saint into a fresh NetWeaver. At first all worked as supposed. But there was a network breakdown during the installation and the process was cancelled. Never mind, i thought, restarted saint and hit the continue button. But the installation does not finish. Also the import can not be cancelled, because it is already in the 'import proper'-Phase. The transport-log shows no actions or errors after the restart of the queue (except the skipping of the tasks already finished). The according Workprocess in the MMC is in the state 'STOP' with the reason 'RFC'. I can find no detail-messages for this.
    Can someone give me a hint where to look or what to do next. If you need more information just ask.
    Thank you in advance.
    Magnus

    Thank you for your offer. Yes, it is a Windows System. Sorry for not mentioning it.
    I suppose you talk about the File 'SAPKK-617I0INDMIS.SM2' (where SM2 is the System-ID), not the one starting with SAPKK...The whole file is over 500KB large, since we restarted the import several times. I'll post everything in the last block. Sorry, but i fail to format this 'readable', for the 'code'-tag doesn't work. Here it is:
    4 ETW000 date&time: 14.04.2009 - 09:46:18
    4 ETW675 end import of "R3TRCLASCL_DMC_CONST".
    4 ETW000 E071-LOCKFLAGs 000066 - 000066 updated ('2', 1 entries).
    4 ETW000 report CL_DMC_CONST==================CCMAC      (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CCIMP      (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CCDEF      (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CP         (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CU         (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CT         (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CO         (L) synchronized.
    4 ETW000 report CL_DMC_CONST==================CI         (L) synchronized.
    4 ETW690 COMMIT "620524" "76143126"
    3 ETW674Xstart import of "R3TRCLASCL_DMC_CONTAINER_TYPE" ...
    4 ETW000   1 entry for TADIR updated  (R3TRCLASCL_DMC_CONTAINER_TYPE                   ).
    4 ETW000   0 entries of SMODILOG updated (CLASCL_DMC_CONTAINER_TYPE                   *)
    4 ETW000 successfully set a temporary lock on table REPOSRC
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CI         A replaced.
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CO         A replaced.
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CT         A replaced.
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CU         A replaced.
    4 ETW000   0 d /  36 i /   1 u /  81 =  68% ucf SEOCOMPO
    4 ETW000 118 entries for SEOCOMPO imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   0 d /  35 i /  80 u /   0 =   0% ucf SEOCOMPODF
    4 ETW000 115 entries for SEOCOMPODF imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000 successfully set a temporary lock on table SEOCOMPOTX
    4 ETW000   0 d /  59 i /   2 u / 161 =  72% ucf SEOCOMPOTX
    4 ETW000 222 entries for SEOCOMPOTX imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   0 d /   7 i /   0 u /  19 =  73% ucf SEOIMPLREL
    4 ETW000  26 entries for SEOIMPLREL imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   0 d /   3 i /   2 u /   0 =   0% ucf SEOMETAREL
    4 ETW000   5 entries for SEOMETAREL imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   2 d /  32 i /   0 u /  95 =  73% ucf SEOSUBCO
    4 ETW000 127 entries for SEOSUBCO imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   2 d /  32 i /  17 u /  78 =  60% ucf SEOSUBCODF
    4 ETW000 127 entries for SEOSUBCODF imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000 successfully set a temporary lock on table SEOSUBCOTX
    4 ETW000   4 d /  53 i /   5 u / 176 =  73% ucf SEOSUBCOTX
    4 ETW000 234 entries for SEOSUBCOTX imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000 DOCUT E CO CL_DMC_CONTAINER_TYPE         IF_DMC_VALIDATE~CHECK (typ = E) inserted
    4 ETW000 DOCUT E CO CL_DMC_CONTAINER_TYPE         SET_DEFAULT_READING_TYPE (typ = E) inserted
    4 ETW000 successfully set a temporary lock on table REPOSRC
    4 ETW000   4 d /   0 i /   0 u /  32 =  88% ucf SEOREDEF
    4 ETW000  32 entries for SEOREDEF imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   0 entries from SOTR_USE (LIMUCPUBCL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SOTR_USE (LIMUCPUBCL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SOTR_USEU (LIMUCPUBCL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SOTR_USEU (LIMUCPUBCL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CP         A replaced.
    4 ETW000   0 d /   0 i /   0 u /   1 = 100% ucf SEOCLASS
    4 ETW000   1 entry for SEOCLASS imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   0 d /   0 i /   1 u /   0 =   0% ucf SEOCLASSDF
    4 ETW000   1 entry for SEOCLASSDF imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000 successfully set a temporary lock on table SEOCLASSTX
    4 ETW000   0 d /   0 i /   0 u /   1 = 100% ucf SEOCLASSTX
    4 ETW000   1 entry for SEOCLASSTX imported (CL_DMC_CONTAINER_TYPE         E*).
    4 ETW000   0 d /   0 i /   0 u /   1 = 100% ucf SEOCLASSTX
    4 ETW000   1 entry for SEOCLASSTX imported (CL_DMC_CONTAINER_TYPE         D*).
    4 ETW000   0 entries from SEOFRIENDS (CL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SEOFRIENDS (CL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   1 entry for DDTYPES updated  (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000   0 entries from SEOMAPATT (CL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SEOMAPATT (CL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SEOMAPCLS (CL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 entries from SEOMAPCLS (CL_DMC_CONTAINER_TYPE         %) deleted.
    4 ETW000   0 d /   0 i /   0 u /   1 = 100% ucf SEOTYPEPLS
    4 ETW000   1 entry for SEOTYPEPLS imported (CL_DMC_CONTAINER_TYPE         *).
    4 ETW000 successfully set a temporary lock on table REPOSRC
    4 ETW000 method ADD_STREE                                                     include CL_DMC_CONTAINER_TYPE=========CM001      will be imported as CL_DMC_CONTAINER_TYPE=========CM001    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM001      A replaced.
    4 ETW000 method ADJUST_SEQNUM                                                 include CL_DMC_CONTAINER_TYPE=========CM002      will be imported as CL_DMC_CONTAINER_TYPE=========CM002    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM002      A replaced.
    4 ETW000 method CONSTRUCTOR                                                   include CL_DMC_CONTAINER_TYPE=========CM003      will be imported as CL_DMC_CONTAINER_TYPE=========CM003    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM003      A replaced.
    4 ETW000 method CREATE_STRUCT_TREE                                            include CL_DMC_CONTAINER_TYPE=========CM004      will be imported as CL_DMC_CONTAINER_TYPE=========CM004    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM004      A replaced.
    4 ETW000 method DELETE_LINE_IN_S_FIELDS                                       include CL_DMC_CONTAINER_TYPE=========CM005      will be imported as CL_DMC_CONTAINER_TYPE=========CM005    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM005      A replaced.
    4 ETW000 method DEL_ACT_STRUCTURE                                             include CL_DMC_CONTAINER_TYPE=========CM006      will be imported as CL_DMC_CONTAINER_TYPE=========CM006    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM006      A replaced.
    4 ETW000 method FROM_REL                                                      include CL_DMC_CONTAINER_TYPE=========CM007      will be imported as CL_DMC_CONTAINER_TYPE=========CM007    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM007      A replaced.
    4 ETW000 method GET_ACTUAL_STRUCT                                             include CL_DMC_CONTAINER_TYPE=========CM008      will be imported as CL_DMC_CONTAINER_TYPE=========CM008    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM008      A replaced.
    4 ETW000 method GET_ACTUAL_STRUCT_NAME                                        include CL_DMC_CONTAINER_TYPE=========CM009      will be imported as CL_DMC_CONTAINER_TYPE=========CM009    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM009      A replaced.
    4 ETW000 method GET_CUSTOM_CONTROL                                            include CL_DMC_CONTAINER_TYPE=========CM00A      will be imported as CL_DMC_CONTAINER_TYPE=========CM00A    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM00A      A replaced.
    4 ETW000 method GET_DRAG_DROP_HANDLE                                          include CL_DMC_CONTAINER_TYPE=========CM00B      will be imported as CL_DMC_CONTAINER_TYPE=========CM00B    
    4 ETW000 REPOS CL_DMC_CONTAINER_TYPE=========CM00B      A replaced.
    4 ETW000 method GET_NODES                                                     include CL_DMC_CONTAINER_TYPE=========CM00C      will be imported as CL_DMC_CONTAINER_TYPE=========CM00C    
    Edited by: Magnus Gertkemper on Apr 14, 2009 1:24 PM
    Sorry, but somehow i fail to format this readable
    Edited by: Magnus Gertkemper on Apr 14, 2009 1:30 PM
    Edited by: Magnus Gertkemper on Apr 14, 2009 1:31 PM

  • TDM Excel Add-In for Microsoft Excel will not install: Installation Summary No software will be installed or removed.

    Hello,
    My7 computer is running Windows 7, I have the Base installation of LabVIEW, and have Microsoft Office 2007 installed.
    I have downloaded the Add-In for Microsoft Excel from:
    http://zone.ni.com/devzone/cda/epd/p/id/2944
    unzipped it successfully (66 files created)
    searched for messages and updates  (No notifications.)
    and I get a screen reading:
    Start Installation
       Review the following summary before continuing.
    Installation Summary
       No software will be installed or removed.
    The "Next" button is grayed out, leaving "Save File" "<<Back" and "Cancel"
    Does anyone have a suggestion why I am unable to go any further?
    Thank you,
    Solved!
    Go to Solution.

    Are you sure it hasn't been installed before? Under Control Panel...Programs and Features...National Instruments Software...do a "Change/Remove" and look down the list for "NI TDM Excel Add-In verX.XX". If found, uninstall and re-run the installer for the newest version.
    This might help as well.
    “A child of five could understand this. Send someone to fetch a child of five.”
    ― Groucho Marx

  • TDMS installation components

    Hi Guys,
    I've already installed my TDMS server and applied every SP for each component (DMIS,DMIS_CNT and DMIS_EXT), now I have a doubt. For receiver and sender environment, It is necessary to install the same component (Midia installation + SP) as I've installed in the Server system? or the components to be installed in the receiver and sender is only the Midia installation?
    I mean, in the whole procedure that I've seen, is requiring to install the components in the all landscape, but I m not sure if i need to apply the same components that I applied in the TDMS server, I mean Installation Midia + SP.
    Could  you provide for me a answer?
    Thanks in advance

    There are many system specific objects (means they get used in one system and not in other) but they are all packaged in a single add-on.
    So it is required that the add-on and the SPs are installed in all the systems in the landscape.

  • TDMS Installation

    We are preparing to install TDMS and use across our multiple systems which are currently ECC 6.0, BI 7.0/CRM 7.0 and HR 620.  We desire to have a single server(control and central server) that would support data migrations for all 3 different SAP system environments. The documentation does not provide guidance as to the minimum SAP platform to use prior to the TDMS add-ons.  What is the mimnium SAP base install we need for central server? Does it depend on the sending/receiving clients SAP WAS or ABA?  Netweaver 7.0?
    In regards to the Sending/Receiving clients we will install the add-ons for DMIS,  DMIS_CNT, and  DMIS_EXT.  For BW/CRM we will install DMIS_BSC.  Will it also need DMIS_HR even though these sending/receving clients will not use, just to be consistent with the central server?
    Likewise for HR, for the Sending/Receiving clients we will install the add-ons for DMIS,  DMIS_CNT, and  DMIS_EXT.  For HR we will install DMIS_HR.  Will it also need DMIS_BSC even though these sending/receving clients will not use, just to be consistent with the central server?

    Hi,
    > We are preparing to install TDMS and use across our multiple systems which are currently ECC 6.0, BI 7.0/CRM 7.0 and HR >620.  We desire to have a single server(control and central server) that would support data migrations for all 3 different SAP >system environments. The documentation does not provide guidance as to the minimum SAP platform to use prior to the TDMS >add-ons.  What is the mimnium SAP base install we need for central server? Does it depend on the sending/receiving clients >SAP WAS or ABA?  Netweaver 7.0?
    >
    These are the supported release for TDMS:
    System Recommendation
    - SAP WebAS 6.20, 6.40 or 7.00
    - Minimum 4000 SAPS (20 GB hard drive)
    Supported Releases*
    ERP: 4.6C, 4.7, ERP 5.0, ERP 6.0
    BI: 3.5, 7.0
    CRM: 4.0, 5.0, 6.0
    HCM: 4.7
    > In regards to the Sending/Receiving clients we will install the add-ons for DMIS,  DMIS_CNT, and  DMIS_EXT.  For BW/CRM >we will install DMIS_BSC.  Will it also need DMIS_HR even though these sending/receving clients will not use, just to be >consistent with the central server?
    >
    If you want to use TDMS for HR/HCM then you will need DMIS_HR component.
    > Likewise for HR, for the Sending/Receiving clients we will install the add-ons for DMIS,  DMIS_CNT, and  DMIS_EXT.  For >HR we will install DMIS_HR.  Will it also need DMIS_BSC even though these sending/receving clients will not use, just to be >consistent with the central server?
    DMIS_BSC is required only when you will use Business Process library scenario.
    Thanks
    Sunny

  • 8.6.1 installer build

    I have a problem with the installer build in 8.6.1.  The short story - I build an executable and then an installer.  In the installer I have the 8.6.1 Runtime checked on the Additional Installers page.  Every thing is OK (except it prompts me for my disk for something in the 8.6.1 distribution, but that works OK and the build continues).  I can modify the application, rebuild the exe, and then rebuild the installer - all OK so far.  Now, I exit LabVIEW and install the application on my development machine - I do this to try and see if I have any obvious problems with the application or installer (like missing VIs for dynamic calls or config files) before I take it to the lab.  This also works OK.  Now, I see something that needs modification.  I open LabVIEW, modify the VI that needs it, save, rebuild the application, and then try to rebuild the installer.  Only now, the installer opens the Locate Distribution dialog and insists that "LabVIEW needs to copy a component installed or updated by the distribution" and it's pointing to the distribution (my installer) that I am trying to build. This circular dependency can't be resolved and the build fails.  Here's some excerpts from the build log
    Getting distribution information for NI LabVIEW Run-Time Engine 8.6.1
         This product is cached. Skipping.
    Getting distribution information for NI MetaUninstaller
         This product is cached. Skipping.
    Getting distribution information for MDF Support
         This product is cached. Skipping.
    Getting distribution information for NI Service Locator
         This product is cached. Skipping.
    Getting distribution information for Math Kernel Libraries
         This product is cached. Skipping.
    Getting distribution information for NI_Logos_5.0
         Product is in volume 1 of distribution with id '{CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}'
         Product is in volume 1 of distribution with id '{FA21606E-6B91-43A2-83DE-199D5045AE5F}'
         Adding distribution 'LabVIEW 8.6.1'
         Path: D:\Distributions\LabVIEW\LabVIEW861\
    Loading distribution information from path: D:\Distributions\LabVIEW\LabVIEW861\
         Product is in volume 1 of distribution with id '{FDAAAF1C-1FFC-4C29-A472-27A929FC8489}'
    Getting distribution information for NI TDM Streaming 1.2
         This product is cached. Skipping.
    Complete list of distributions and products to copy:
         (0) LabVIEW 8.6.1, Disk 1
              Id: {FA21606E-6B91-43A2-83DE-199D5045AE5F}  Volume: 1
              Path: D:\Distributions\LabVIEW\LabVIEW861\
              Products:
              (0) NI_Logos_5.0
                   Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936}  Flavor: 'Full'
                   Path: Products\NI_Logos\
         (1) MA231 Tester
              Id: {CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}  Volume: 1
              Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
              Products:
              (0) NI_Logos_5.0
                   Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936}  Flavor: 'Full'
                   Path: bin\p9\
         (2) MA231 Tester
              Id: {FDAAAF1C-1FFC-4C29-A472-27A929FC8489}  Volume: 1
              Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
              Products:
              (0) NI_Logos_5.0
                   Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936}  Flavor: 'Full'
                   Path: bin\p9\
    And then,
    > The source directory for "MA231 Tester" is invalid because it is at the same location as the deployment destination directory (source = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\", destination = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\").
    <<<MDFDistCopyList_GetItemInfo>>> Returning info for distribution 1
         Last known path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
         Distribution title: MA231 Tester
    I can only fix this by uninstalling my application AND going into the registry and deleting the first entry with the GUID under the NI_Logos_5.0 (which refer to my application) - these entries are in the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\Distributions\" - where there are also registry entries for every app I've ever built and installed with LabVIEW - all 300 something.  Obviously, the uninstall doesn't do much in cleaning up these things.
    So, anybody have any good ideas what to do?  OR at least an explanation?  I'm leaving soon today and won't have access to email again until Tuesday, 30 June, so if you post and I don't respond immediately please understand that I'm not ignoring the thread.
    Thanks,
    Mark
    This has also been opened as Service Request 7249245

    I have a problem with the installer build in 8.6.1.  The short story - I build an executable and then an installer.  In the installer I have the 8.6.1 Runtime checked on the Additional Installers page.  Every thing is OK (except it prompts me for my disk for something in the 8.6.1 distribution, but that works OK and the build continues).  I can modify the application, rebuild the exe, and then rebuild the installer - all OK so far.  Now, I exit LabVIEW and install the application on my development machine - I do this to try and see if I have any obvious problems with the application or installer (like missing VIs for dynamic calls or config files) before I take it to the lab.  This also works OK.  Now, I see something that needs modification.  I open LabVIEW, modify the VI that needs it, save, rebuild the application, and then try to rebuild the installer.  Only now, the installer opens the Locate Distribution dialog and insists that "LabVIEW needs to copy a component installed or updated by the distribution" and it's pointing to the distribution (my installer) that I am trying to build. This circular dependency can't be resolved and the build fails.  Here's some excerpts from the build log
    Getting distribution information for NI LabVIEW Run-Time Engine 8.6.1
         This product is cached. Skipping.
    Getting distribution information for NI MetaUninstaller
         This product is cached. Skipping.
    Getting distribution information for MDF Support
         This product is cached. Skipping.
    Getting distribution information for NI Service Locator
         This product is cached. Skipping.
    Getting distribution information for Math Kernel Libraries
         This product is cached. Skipping.
    Getting distribution information for NI_Logos_5.0
         Product is in volume 1 of distribution with id '{CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}'
         Product is in volume 1 of distribution with id '{FA21606E-6B91-43A2-83DE-199D5045AE5F}'
         Adding distribution 'LabVIEW 8.6.1'
         Path: D:\Distributions\LabVIEW\LabVIEW861\
    Loading distribution information from path: D:\Distributions\LabVIEW\LabVIEW861\
         Product is in volume 1 of distribution with id '{FDAAAF1C-1FFC-4C29-A472-27A929FC8489}'
    Getting distribution information for NI TDM Streaming 1.2
         This product is cached. Skipping.
    Complete list of distributions and products to copy:
         (0) LabVIEW 8.6.1, Disk 1
              Id: {FA21606E-6B91-43A2-83DE-199D5045AE5F}  Volume: 1
              Path: D:\Distributions\LabVIEW\LabVIEW861\
              Products:
              (0) NI_Logos_5.0
                   Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936}  Flavor: 'Full'
                   Path: Products\NI_Logos\
         (1) MA231 Tester
              Id: {CB09ABD9-FCCC-43BC-B4E1-9DDA6EB98ADB}  Volume: 1
              Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
              Products:
              (0) NI_Logos_5.0
                   Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936}  Flavor: 'Full'
                   Path: bin\p9\
         (2) MA231 Tester
              Id: {FDAAAF1C-1FFC-4C29-A472-27A929FC8489}  Volume: 1
              Path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
              Products:
              (0) NI_Logos_5.0
                   Id: {ADAD3A9A-8E72-405F-BB2E-535AA7C8A936}  Flavor: 'Full'
                   Path: bin\p9\
    And then,
    > The source directory for "MA231 Tester" is invalid because it is at the same location as the deployment destination directory (source = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\", destination = "C:\MA231 Tester\Software\Builds\MA231 Tester Installer\").
    <<<MDFDistCopyList_GetItemInfo>>> Returning info for distribution 1
         Last known path: C:\MA231 Tester\Software\Builds\MA231 Tester Installer\Volume\
         Distribution title: MA231 Tester
    I can only fix this by uninstalling my application AND going into the registry and deleting the first entry with the GUID under the NI_Logos_5.0 (which refer to my application) - these entries are in the registry under "HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\Common\Installer\Distributions\" - where there are also registry entries for every app I've ever built and installed with LabVIEW - all 300 something.  Obviously, the uninstall doesn't do much in cleaning up these things.
    So, anybody have any good ideas what to do?  OR at least an explanation?  I'm leaving soon today and won't have access to email again until Tuesday, 30 June, so if you post and I don't respond immediately please understand that I'm not ignoring the thread.
    Thanks,
    Mark
    This has also been opened as Service Request 7249245

  • G4 OS 9.2 Installation Problems

    I just bought a used G4 with an updated CPU processor. The specs are:
    Power Mac g4 (AGP Graphics)
    Model Powermac 3,1
    CPU Power PC g4 (3.2)
    1 CPU
    CPU speed 1.2 ghz
    Memory 1 gb
    boot rom version 4.2.8f1
    3 Digidesign TDM audio cards
    I am trying to run this machine from OS 9.2 because i have some music software that won't run on OSX. The machine boots up fine with OSX, but freezes up in 9.2 when the extensions icons start to appear. I reformatted one drive to make sure the OS9 drivers were installed. Now i can't even install os 9.2 at all. Starting up from the OS disc freezes up the computer every time. I tried several different OS9 Cds and they are all the same.
    Now it seems that this installation process has corrupted the OSX folder as well and that won't start either. I don't care so much about that but now all my repair strategies will have to be in the 9.2 domain.
    Thanks for reading
    GT

    Hi, Geoff -
    The only OS 9 Install CDs that a G4 (AGP) model can use are -
    • An original Software Install CD that came with the machine; this may be for OS 8.6 (on the first (AGP) models) or for OS 9.0.4 (on later AGP models)
    • A retail OS 9.0.4 Install CD
    • A retail OS 9.1 Install CD
    • A retail OS 9.2.1 Install CD
    Now i can't even install os 9.2 at all. Starting up from the OS disc freezes up the computer every time. I tried several different OS9 Cds and they are all the same.
    Several folk with similar machines which have had processor upgrades have discovered that the machine will not boot to an OS 9 Install CD with the processor upgrade installed. The solution appears to be to put the old processor back in, install OS 9, then re-install the processor upgrade.
    The machine boots up fine with OSX, but freezes up in 9.2 when the extensions icons start to appear.
    Have you tried booting with Extensions Off? To do that, hold down the Shift key from the beginning of booting (from when the startup chimes sound), keep it held down until the desktop has loaded.
    If this works, it would indicate that you have an extensions conflict of some kind.

  • TDMS 3.0 for ERP 6.0:  step by step procedure for  TDSH6 Shell creation

    Dear All,
    I need to perform shell creation. I have never done this and need help with step by step instructions.
    I need to refresh my my development system with a TDMS shell creation from production client in production system.
    I am familiar with TDTIM and performed many TDTIM copies. I have gone throught the master and operational guides for TDMS also.
    I would try to list down my understanding so far after reading the guides.
    Please correct me if I am wrong ang also suggest correct steps.
    1. All my three systems (central, sender and receiver) are ready from installation point of with with authorizations and latest SPs.
    2. I log into Central/Control system and start a new package  "ERP Shell creation package for AP Release higher 4.6 "
    3. AS I have never executed this option I do not know what are the stps inside it.
       But I assume I should be asked for the source client details from which shell needs to be creates. (000 or pruduction client)
       What type of shell  : slave or master?
    4. During the shell creation from sender system client, is there a downtime for sender system.
    5. Once the shell creation is done an export dump will created.
    6. I perform all the preprocessing steps of a homogenous system copy on the receiver systems.
    7. Stop receiver system, start sapinst  database instance installation with homogenous system copy with R3load option.
    8. Provide the export dump location to sapinst.
    9. After database instance is installed, perform system copy specific post processing steps.
    10. Afte the system is ready it has only one client 000 now available in development system and  i need to create a new cleint from 000 which will act as my new development cleint.
    I request all you experts to please provide your comments at the earliest as activity would be starting from 5th of this month.
    Regards,
    Prateek.

    Hi,
    Let me answer your questions.
    Some queries
    1. Is there a downtime for Production system (sender system).
       SAP recommends that nothing much should be going on during the export of the Sender(PRoduction) system, but so far i have never encountered an issue doing the export in online mode.
    2. Shell creation works on both Production and 000 client or only Production client,
       Be carefull!!! - A Shellcreation is a normal Homogenous Systemcopy using R3load. You will create a 'new' system with the DDIC and clientindependent customization of the Sender system. ALL former data of the target system will be deleted.
    You mention that you will refresh a development system that way. Please be aware of the implications that a development refresh contains. That said. After the refresh you will have the 000 client and parts (users ... authorizations of sonder) of the other clients on the new system.
    3. when I import the the dump using sapinst, how many clients are available in receiver systems.
    See above. All client configuration will be available, but nearly no data will be in these clients except 000. A manual part of the Shellcreation is to clean up the target system (delete the clients that are not needed) This is a fast process.
    4. Soem where in the guide it is mentioned that downtime depends on the type of shell I create.
    Kindly suggest should I create a master shell or slave.
    Hm. The master shell is just a concept that you create a complete new system and put that system into your transport landscape without filling it with data. You can then use that system as the source for a normal (database dependent) systemcopy without impacting your prod system. The result is a very small copy that can be repeated very often without an impact to prod/QA...
    Downtime is as described in point1 not required
    5. Once I execute this activity of shell creation for lets say receiver system A, then can I use the same export dump for second receiver system B.
    Yes
    6. Lastly please suggest the activity execution time as customer has provided us 2 days to execute this activity.
    This depends on your knowledge of homogenuous systemcopies and the preparation + some items like size of stxl  and other tables that will be exported/imported.  If you are very familiar with the systemcopy process using R3Load 2 days are feasable.
    I have seen shellcreations done within 1-2 days but also much longer ones!
    As a prerequisite i would always recommedn to have the latest R3* + migmon exe available on sender + target.
    I hope i have clarified some of your items.
    Best Regards
    Joerg

  • TDM vi's work in Admin account, but not Limited user

    I have an app that I wrote using the TDM VIs that works perfectly in the development environment and as an executable in an Admin account in WindowsXP. I am trying to deploy the app for use in a limited user account, and I am getting an error about an unrecognized file type. Is there a way to enable this functionality?
    The VI is used to create a file map of a custom TDM file that was created using the TDM header writer VIs. I've included the VI and the executable in the archive, as well as a sample file to read (select the .tdm, not the .bin in the path control when running the program).
    The actual error text is:
    Error -2564 occurred at Open Storage
    Possible reason(s):
    LabVIEW: The software installed on this computer does not support the file format you requested. The Storage VIs access files through plug-in libraries LabVIEW and DIAdem install. Visit ni.com to download the library you need.
    Thanks,
    Chris
    Attachments:
    cTDM Map Test.zip ‏868 KB

    The TDMS VIs probably are better, but I started this project before they were available, and I spent a considerable amount of time with the TDM Header Writer VIs to create my file format. I don't use the TDM VIs to write the files; I do that all with my own binary format that is fast and efficient. I also stripped out all the extraneous gunk that the TDM files like to put in, and customized the files with my own properties. Unfortunately, I am disappointed with the time necessary to read and write properties, but it's too late now to replace the whole system with a database backend.
    Anyway, I'm hopeful that there is a solution to this problem. I doublechecked all the options in the installer and app build specifications, and I didn't see the checkbox for Storage VI Support. I have a fuzzy memory of this; is it possible that it existed in a previous version of the builder?
    Chris

  • How to clear macbook pro without installation disc

    Recently purchased new Macbook.  I now need to delete all content on old Macbook Pro, before selling for parts.  I cannot find the original installation disc.  How do I reset to manufacturers settings and delete all personal content?
    OS X 10.6.8

    You could connect the old MBP to the new one in target disk mode. That will mount the old drive on the desktop of the new computer. You can then erase the drive using Disk Utility. Applications / Utilities / Disk Utility.
    TDM requires the computers to be connected. So you will need an appropriate cable and even an adapter. Which ones will depend on the ports on the computers. The following web page gives the basic info. You can google for other pages for more instructions.
    OS X Mavericks: Transfer files between two computers using target disk mode
    I must point out that you can buy a copy of OS 10.6 DVD for $20. Which might be less than the cost of the cables, and who ever buys your Mac would appreciate the OS dvd.
    http://store.apple.com/us/product/MC573Z/A/mac-os-x-106-snow-leopard

  • TDMS central/control system, should I have to install it in a solution manager? Is it a prerequisite?

    Hello,
    I have a doubt about the installation of the central/control system of TDMS, the documentation say that TDMS should be installed in a Netweaver 7.0 and it also say that the solution manager can be used for the central/control system, but I also have read in a lot of documents relating TDMS with solution manager, so I am a little confused with this prerequisite.
    Is the Solution manager a prerequisite for the installation of the central/control system? If so, where can I find it in the documentation?
    or
    Can we use a simple Netweaver 7.0 ERP to be the central/control system? Without any solution manager?
    Please, advice
    Thanks in advance,
    Walde Requena

    Hello Billy,
    This is quite interesting.  TDMS is fully supported with a Solman system as well and is being used
    extensively by several customers. We have not heard of any Solman Service getting impacted because of using that system as a TDMS Control system. Can you precisely describe what kind of
    conflicts where encountered , when you had tried using your solman as a TDMS control system.
    May be you have followed some incorrect step here.
    Note : The idea of using a Solman system was to avoid redundant systems in your landscape .
    Hope this helps.
    Thanks,
    Rajesh

  • How to create a central system on TDMS control system

    Seems the central system on the TDMS control system is an alias.
    Which transaction to create it?
    Thanks!

    Hi
    Central system is not required to be created explicitly. Once you install the TDMS Add-on components the system can be used as a control as well as central. Only condition being that to use a system as a central system the server should be with basis release higher than 6.2.
    Refer to TDMS installation guide for details.
    Regards
    Pankaj

  • TDM Excel Add-In truncate

    We're experiencing a wierd issue with the TDM Excel Add-In where data is truncating depending on from where the file is read.
    We haveTDMS (binary encoded data) files on a lab PC and copies of these files in a server folder.
    When we run the TDM Excel Add-In to import these files the behavior is different when it comes from a "local" drive versus when the same data file (binary compare confirms they are the same) comes from a server folder.
    We normally get ~8900 rows and when it is read from the server we get ~1400 rows per control.
    A test of a different server was also performed with the same baffling results.
    This previously worked as expected from both locations.
    Is anyone else seeing this issue?  Do you have a fix??

    Hi Perkin,
     Just to clarify, when you import from a local file, you are able to load the entire file (approx 8900 rows). However, when you load the same file from the server, you are only able to load a portion of the file (approx 1400 rows). 
    Does this happen every time you load the file?
    You mentioned that this used to work, do you know of any changes that you have made since that time? (Consider software installation, removal, firewall or network changes).
    If you try to load a smaller file (such as one with fewer than 1400 rows) does the entire file get loaded? 
     Also, please do let us know about your software versions, share types, etc. as AndreasK mentioned.
    Thanks, and have a great afternoon!
    National Instruments
    Applications Engineer

Maybe you are looking for