Derivation Rule Problem After A Client Copy

Hello,
Has anyone ever encountered a problem with derivation rules after a client copy is performed? After a client copy, we have "some" FM and GM derivation rules (not all of them) that have to be manually copied from the source to the target client (line by line by line by line). I'm thinking that there has to be a way to prevent this since some rules are fine after the clent copy. Your input would be greatly appreciated.
Will

I believe that we have resoved our issue. For the derivation rule values that would never copy, we re-created these again starting in DEV and transported the derivation rules throughout the entire landscape (QAS and PRD). Evidently some derivation rules (and the related values stored in the tables) were created directly in Production. During a client copy the values in the tables for the derivation rules that were created directly in our Production environment would not copy to our QAS environment. Those rules were stored in a table named FMFMOAPRD1000122. Note that PRD is in the table name. After re-creating the rule and transporting it through the landscape, the table was named FMFMOADEV1000152 (for example).

Similar Messages

  • FM derivation rule - ??? client copy

    Hi Expert,
    I have encountered a strange problem on FM derviation rule (TCODE FMDERIVE). I tried to client copy a "gold copy" client to a seperate client using using SAP_ALL but found that all the details derviation rule were missing.... I tried in my different server and found the same problem. It seems that derviation rule would not be copied by "client copy"
    I tried to recopy the configure. I search the orginal request but found that it was a Workbench request. By my knowledge, workbench request should be cross client...
    Any other have the same situation? how can i fixed the probelm? Should i use scc1 to transport the request?

    Hi
    I do not know which version of EA-PS you are using .
    when we were trying for funds managment we came to know that If the version is EA-PS 2.00 or higher you will find 9 rules in FMRULS and for balance you will find finction module for which you have to go to FMDERIVE - Create and from Create step select function module it will show the function modules availables which will derive the target fields based on default source fields.
    If the answer is helpful kindly assign points.
    Thanks & Regards
    Mahesh

  • Inconsistant transport requests after local client copy

    Dear experts,
    our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
    How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
    Thanks for your appreciated help
    Andreas

    Hello,
    Transports are NEVER part of a client copy.
    In fact all the data of your transports is stored in tables that are client independent (E07* tables).
    This means that you can view (not edit) always all transports from all clients in a specific system.
    When you want to edit or release a transport the source client is important (in which client was the transport originally created).
    This is stored in table E070C for all transports and can not be overruled.
    So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
    Success.
    Wim

  • Derivation rules: problems w/ time-dependence

    Community!
    I have an issue with the derivation rules after an organizational restructuring which occured <u>during</u> the fiscal year.
    Let's say we have the following derivation rules:
    Derivation Rule 1 (before organizational change from 01.01.2006):
    a -> b -> c
    Derivation Rule 2 (after organizational change - from 01.07.2006):
    a -> c
    Now (in regards to a restatement for the year 2006) I want to switch off the derivation rule 1 for the second half of the year. Therefore I can only limit the valid-to date of the entries, but not of the derivation rule 1 itself!
    When I try to book something after the 01.07.2006, an error exception is coming up, telling that derivation rule 1 is missing the correct entry. But I actually don't want this rule to be valid after 01.07.2006!!!!! I only want Rule 2 to be valid for this time-period!
    Is there a possibility to limit the complete derivation rule so that SAP will not jump inside and look for a valid entry? Or, do you have any other ideas on how to solve this problem?
    Thanks for your help in advance,
    Bjoern

    Hi,
    Good evening and greetings,
    Please go through the following link
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/57/749fe2d51811d189f30000e829fbbd/frameset.htm
    Also go through the following SAP OSS Note
    Note 458951 - Derivation rules with validity date
    Please reward points if found useful
    Thanking you
    With kindest regards
    Ramesh Padmanabhan

  • Logical system on QAS after remote client copy from PRD to QAS

    I wander after remote client copy from PRD to QAS do I have to change Logical system on QAS. Do I have to run some postprocessing program?
    Thank you in advance

    Hi Branko,
    After the system copy, go to transaction SALE -> Sending and receiving Systems -> Logical systems -> Define Logical System , click New Entries and create a new logical system for your QAS; then go to SALE -> Sending and receiving Systems -> Logical systems -> Assign Client to Logical System, click on the client, click change and assign the new Logical system.
    Other activities, check Jobs, RFC's, etc...
    Regards
    Juan
    Please reward with points if helpful

  • Compile after local client copy

    Hi guys,
    We noticed that SAP ECC 6 will compile some stuff again after a local client copy. e.g. when we launch MM01 in the newly created client (by copy) it compiles again. The transaction has been run in the source client.
    Is this normal? Can we limit these compiling actions by a specific sgen task? Which one? Regenerate after an SAP System Upgrade?
    Thanks in advance!

    Hello Juan,
    So far I have not even once done SGEN after a client copy. SGEN is needed only after a fresh installation, SAP upgrade and support package import. This is when we are doing SGEN. SGEN is needed only when either the object is new or has got modified. Infact regeneration of programs also happens after transport imports which carry program changes.
    Though nothing wrong in doing SGEN after client copy. Can be done if you wish.
    In this case it might be that the system we are talkign about may be a totally new system where SGEN has not been run even once.
    Hello R. Van der Veen  ,
    Please confirm  that you were using the system in past without this MM01 delay issue.
    Also SGEn is system specific. Nothing to do with client.
    Regards.
    Ruchit.

  • Is there any step necessary to be takan after remote client copy

    Helllo
    I wander generally is there any step necessary to be takan after remote client copy
    Thank you in advance

    Hi Sunny,
    What about changing "Logical System Names", is it not necessary after a remote client copy.
    Thanks
    Ahamed

  • Transport Request number missing after Remote client copy

    Hi,
       I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
    Thanks
    Jyothish

    >    I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
    If you did client specific customzing in those they are of course not found.
    Markus

  • Derivation Rule Problem - Sales Order -CHALLENGE TO ALL SD CONSULTANTS

    Hi Friends
    I am stuck on i very critical issue, i am not able to solve it, I am SD consultant, i wrote this issue on FI forum also, but i did not get complete solution, they write me back it is SD issue.
    When i create a new sales order and click enter, a small screen open and message displayed on it "Error occurred in Derivation Rule, See long text"
    And when try to save sales order in display incompletion log. When i press on edit to complete it message display " Item 10 ... Missing data- Profitability Segment No.
    When i press on complete data - Account Assignment screen open (Business Area 9900)
    Would you please send me solution with complete path to fix this problem
    If you can give your email address, i will send you screen shot of the problem.
    I have tried KEDR transaction issue also but nothing happened.
    This is BIG challenge to all SD consultants now. Send me step by step solution
    If you send my your email id, i will send actual error saved in word format.
    Thanks
    Rajesh
    Email: [email protected]

    Good luck!
    to get a solution you need to provide the members of this forum with details regarding your PA set-up.
    PA is normally very customer driven, so not standard.
    Without information regarding your structure there you will not get any solution.
    GL
    Hein

  • Derivation Rule Problem - Sales Order

    Hi Friends
    I am SD consultant, i wrote this issue on SD forum also, but it is related to FICO.
    Please send me solution with complete path.
    When i create a new sals order and click enter, a small screen open and message displayed on it "Error occured in Derivation Rule, Seee long text"
    And when try to save sales order in display incompletion log. When i press on edit to complete it message diaplay " Item 10 ... Missing data- Profitability Segment No.
    When i press on complete data - Account Assignment screen open (Business Area 9900)
    Would you please send me solution to fix this problem
    If you can give your email address, i will send you screen shot of the problem.
    Thanks
    Rajesh
    Email: [email protected]

    Hi Waman
    I ckeck the transaction code /nKEDR there which entry i should select and in type of prfatibity Which one i should select Costing based or Accounting based.
    I tried on selecting IDEA and Accounting based and eleased but still i getting same error.
    My problem is still pending, please send next step to solve this issue
    Thanks
    Raj
    Email: [email protected]

  • Payroll infotypes disappearing after a client copy

    Hi everyone,
    Our project team has done a client copy to two new clients (configuration and master data), and then decommissioned the source client. However, for some reason a number of infotypes do not appear against employee records in PA30. The infotype audit log has no record of their deletions (only their creations), and the client copy logs indicate that the expected number of records for the infotype tables was copied to the destination clients.
    Has anyone else come across this situation before? I am wondering whether the "missing" infotypes are in the client system and require something further to make them appear, given that the client copy logs indicated nothing out of the ordinary.
    Any help or advice would be greatly appreciated.
    Cheers
    Nuwan

    Hi,
    The wage type configuration still exist, but the infotypes themselves are "missing"/hidden.
    Cheers
    Nuwan

  • Document archived on PRD visible on QAS after a client copy to QAS system

    We performed archiving on productive system. We plan to make a client copy to QAS system(sap_all profile)
    The system is version 4.7x2(oracle/unix)
    We wander if we adjust the archiving paths on QAS system will the archives be visible?
    This is also question of archiving infostructures for which I do not know wheter they are client dependent.
    Beside only on 4.7 system I noticed a remote client copy profile sap_all with cross client customizing (is this better procedure)

    Hi Tina,
    What we do for accessing archive files in our QA system that had been archived in production is to do a "Retrieve file" in prod for a sampling of files and then FTP the files to the QA archiving file system.  Then, go into the Archive Adminstration information and change the File name to "RETREIVED_xxxx" and the Logical path to your designated path name such as ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK
    Once the QA system can see the archive file, the archive information structures will be able to access the data.  You would not need to change anything there.
    We do it this way so that we can archive new data in the QA system without being concerned about QA archive files being sent to the production archive server.
    Hope this is helpful.
    Regards,
    Karin Tillotson

  • Is there away to activate all Transfer Rules after a client copy at once?

    Our Basis team recently created 2 new clients from copying our existing dev & qa systems they then changed the partner profiles and source systems to point to our new ecc clients but we now cant get anything to run without activating transfer rules trying to do this one at a time twice is going to take a long time is there anyway of doing this en masse?

    Hi
    you may have to use following FM too
    RS_COMSTRU_ACTIVATE_ALL      Activate all inactive Communication Structures
    RSAU_UPDR_REACTIVATE_ALL      Activate Update Rules
    and then
    RS_TRANSTRU_ACTIVATE_ALL      Activate Transfer Structure
    Regards
    Sudeep

  • BW error after ERP client copy

    Hi Experts,
    I am facing an issue trying to transfer data from QAS to BW.
    I checked note 886102 - System Landscape Copy for SAP NetWeaver BW .
    Everything seems to be ok but tx BD87 IDOCs got stuck.
    After I run report RSEOUT00 in tx SE38 IDOCs works fine and status is green.
    RFCs are fine and also authorization check.
    Any clue?

    Hi Jorge,
    Logical system name can be an issue as PRD and QAS will have different logical system names within table entries as well.
    GUIDs also create problems in data transfer post copy. So when you copy ECC client BW client should also be copied to avoid issue with GUID
    Regards,
    Deepak Kori

  • Problems after new Client IR10

    Hello Guys,
    I just installed the new IR10 and after that I could NOT start msi-installation from servervolume anymore.
    e.g. adobe professional / groupwise 2012 setups.
    got MSI-Error.
    I tried this with Windows 8.1 and 7 on 3 different Machines
    after rollback to IR9 it was functional again
    Greets
    Uwe

    groupwise install log
    maybe Problem with too long filenames ?
    in german I read "DOWNLOADS" is not a valid short filename
    === Verbose logging started: 03.12.2014 14:41:04 Build type: SHIP UNICODE 5.00.9600.00 Calling process: C:\Windows\SysWOW64\MSIEXEC.EXE ===
    MSI (c) (74:7C) [14:41:04:194]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
    MSI (c) (74:7C) [14:41:04:194]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
    MSI (c) (74:08) [14:41:04:194]: Resetting cached policy values
    MSI (c) (74:08) [14:41:04:194]: Machine policy value 'Debug' is 7
    MSI (c) (74:08) [14:41:04:194]: ******* RunEngine:
    ******* Product: \\VUX-HRZ-PORTAL3\DATEN\DOWNLOADS\nopublic\groupwise\gw12.0. 3_client_win_multi\client\win32\groupwise.msi
    ******* Action:
    ******* CommandLine: TRANSFORMS="1031.MST" SETUPEXEDIR="\\VUX-HRZ-PORTAL3\DATEN\DOWNLOADS\nopublic\groupwise\gw12.0. 3_client_win_multi\client\win32"
    MSI (c) (74:08) [14:41:04:225]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (c) (74:08) [14:41:04:241]: Machine policy value 'DisableUserInstalls' is 0
    MSI (c) (74:08) [14:41:04:288]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (c) (74:08) [14:41:04:335]: Cloaking enabled.
    MSI (c) (74:08) [14:41:04:335]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (74:08) [14:41:04:335]: End dialog not enabled
    MSI (c) (74:08) [14:41:04:335]: Original package ==> \\VUX-HRZ-PORTAL3\DATEN\DOWNLOADS\nopublic\groupwise\gw12.0. 3_client_win_multi\client\win32\groupwise.msi
    MSI (c) (74:08) [14:41:04:335]: Package we're running from ==> C:\Windows\Installer\5b45b.msi
    MSI (c) (74:08) [14:41:04:335]: APPCOMPAT: Uninstall Flags override found.
    MSI (c) (74:08) [14:41:04:335]: APPCOMPAT: Uninstall VersionNT override found.
    MSI (c) (74:08) [14:41:04:335]: APPCOMPAT: Uninstall ServicePackLevel override found.
    MSI (c) (74:08) [14:41:04:335]: APPCOMPAT: looking for appcompat database entry with ProductCode '{00335E50-4DC1-4E01-A60C-91C5746D489E}'.
    MSI (c) (74:08) [14:41:04:335]: APPCOMPAT: no matching ProductCode found in database.
    MSI (c) (74:08) [14:41:04:335]: MSCOREE not loaded loading copy from system32
    MSI (c) (74:08) [14:41:04:350]: Machine policy value 'DisablePatch' is 0
    MSI (c) (74:08) [14:41:04:350]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (c) (74:08) [14:41:04:350]: Machine policy value 'DisableLUAPatching' is 0
    MSI (c) (74:08) [14:41:04:350]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (c) (74:08) [14:41:04:350]: Looking for file transform: C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST
    MSI (c) (74:08) [14:41:04:350]: Original transform ==> C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST
    MSI (c) (74:08) [14:41:04:350]: Transform we're running from ==> C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST
    MSI (c) (74:08) [14:41:04:350]: SOFTWARE RESTRICTION POLICY: Verifying transform --> 'C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST' against software restriction policy
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: SOFTWARE RESTRICTION POLICY: C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST is not digitally signed
    MSI (c) (74:08) [14:41:04:350]: SOFTWARE RESTRICTION POLICY: C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST is permitted to run at the 'unrestricted' authorization level.
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Patch 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2205 2: 3: PatchPackage
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: _Tables 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: _Columns 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Media 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: File 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
    MSI (c) (74:08) [14:41:04:350]: TRANSFORM: Applying regular transform to database.
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: _Tables 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: _Columns 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Binary 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: File 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: CheckBox 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Component 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Icon 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ComboBox 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Directory 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ControlCondition 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ControlEvent 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: CreateFolder 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: CustomAction 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: EventMapping 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ListBox 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ListView 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: LockPermissions 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Media 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Patch 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Registry 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: RemoveFile 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ReserveCost 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: TextStyle 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: Upgrade 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: _Validation 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ISComponentExtended 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ISCustomActionReference 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: ISDFLInfo 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: #_BaselineCost 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: #_BaselineFile 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: #_BaselineData 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: Note: 1: 2262 2: #_PatchCache 3: -2147287038
    MSI (c) (74:08) [14:41:04:350]: APPCOMPAT: looking for appcompat database entry with ProductCode '{00335E50-4DC1-4E01-A60C-91C5746D489E}'.
    MSI (c) (74:08) [14:41:04:350]: APPCOMPAT: no matching ProductCode found in database.
    MSI (c) (74:08) [14:41:04:350]: Transforms are not secure.
    MSI (c) (74:08) [14:41:04:350]: Transforming table Property.
    MSI (c) (74:08) [14:41:04:350]: Transforming table Control.
    MSI (c) (74:08) [14:41:04:350]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\upilz\AppData\Local\Temp\MSI6f5c2.LOG'.
    MSI (c) (74:08) [14:41:04:350]: Command Line: TRANSFORMS=1031.MST SETUPEXEDIR=\\VUX-HRZ-PORTAL3\DATEN\DOWNLOADS\nopublic\groupwise\gw12.0. 3_client_win_multi\client\win32 CURRENTDIRECTORY=\\VUX-HRZ-PORTAL3\DATEN\DOWNLOADS\nopublic\groupwise\gw12.0. 3_client_win_multi\client\win32 CLIENTUILEVEL=0 CLIENTPROCESSID=5492
    MSI (c) (74:08) [14:41:04:350]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{04FA1456-97FD-4F90-9BF5-78FF644CEF8A}'.
    MSI (c) (74:08) [14:41:04:350]: PROPERTY CHANGE: Adding TRANSFORMS property. Its value is 'C:\Windows\Installer\{00335E50-4DC1-4E01-A60C-91C5746D489E}\1031.MST'.
    MSI (c) (74:08) [14:41:04:350]: Product Code passed to Engine.Initialize: '{00335E50-4DC1-4E01-A60C-91C5746D489E}'
    MSI (c) (74:08) [14:41:04:350]: Product Code from property table before transforms: '{00335E50-4DC1-4E01-A60C-91C5746D489E}'
    MSI (c) (74:08) [14:41:04:350]: Product Code from property table after transforms: '{00335E50-4DC1-4E01-A60C-91C5746D489E}'
    MSI (c) (74:08) [14:41:04:350]: Product registered: entering maintenance mode
    MSI (c) (74:08) [14:41:04:350]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
    MSI (c) (74:08) [14:41:04:350]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
    MSI (c) (74:08) [14:41:04:350]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
    MSI (c) (74:08) [14:41:04:366]: Note: 1: 2303 2: 144 3: \\VUX-HRZ-PORTAL3\DATEN\
    MSI (c) (74:08) [14:41:04:366]: Note: 1: 1325 2: DOWNLOADS
    MSI (c) (74:08) [14:41:04:366]: Note: 1: 2303 2: 144 3: \\VUX-HRZ-PORTAL3\DATEN\
    MSI (c) (74:08) [14:41:04:366]: Note: 1: 1325 2: DOWNLOADS
    DOWNLOADS ist kein gltiger kurzer Dateiname.
    Dieses Installationspaket konnte nicht geffnet werden. Stellen Sie sicher, dass das Paket vorhanden ist und Sie darauf zugreifen knnen, oder wenden Sie sich an den Hersteller der Anwendung, um sicherzustellen, dass es sich um ein gltiges Windows-Installationspaket handelt.
    \\VUX-HRZ-PORTAL3\DATEN\DOWNLOADS\nopublic\groupwise\gw12.0. 3_client_win_multi\client\win32\groupwise.msi
    MSI (c) (74:08) [14:41:04:366]: Note: 1: 1729
    MSI (c) (74:08) [14:41:04:366]: Produkt: GroupWise -- Die Konfiguration ist fehlgeschlagen.
    MSI (c) (74:08) [14:41:04:366]: Das Produkt wurde durch Windows Installer neu konfiguriert. Produktname: GroupWise. Produktversion: 12.0.3. Produktsprache: 1031. Hersteller: Novell. Erfolg- bzw. Fehlerstatus der neuen Konfiguration: 1619.
    MSI (c) (74:08) [14:41:04:366]: MainEngineThread is returning 1619
    === Verbose logging stopped: 03.12.2014 14:41:04 ===

Maybe you are looking for

  • BPM design -help

    Hi all, i need you your help in enhancing one existing BPM. the initial state was file sys-> BPM -> sap R3 (system A) and also sap R3 (system B) where the BPM is   --> recv > sync send(A)->send(B) file sys send ONE vendor_key in xml format to BPM. no

  • How can I transfer from ipod to computer?

    How can I transfer from ipod to computer?

  • Network speed issue

    Dear Experts, We have a 10MB Data-link between our company and an external DATA-CENTER where our mail-server is hosted aswell,  this 10MB link has been provided for us through an ISP.   so our issue is while we open outlook it takes 1 to 2 minutes to

  • Problems with usa Apple Tv in europe due to PAL/NTSC

    Im thinking about buying one in NY to take it to Spain, is it possible??

  • Typing Chinese characters on iPad keyboard

    How can I type Chinese using the iPad keyboard and how to switch between English and Chinese?