Error refreshing Planning

Hi , I got this error when refreshing :
com.hyperion.planning.olap.EssbaseException: Account (1060000)
I search in essbase error documentation , over internet , in oracle support but I never find a way to solve this problem ....
can anyone help giving a suggestion or a solution ?
Thanks
Edited by: 911660 on Oct 1, 2012 8:40 AM

When I look at the app logs when I try to refresh I got this messages :
[Mon Oct  1 17:05:11 2012]Local/ACASECNA///Info(1013210)
User [admin] set active on database [Bud]
[Mon Oct  1 17:05:11 2012]Local/ACASECNA/Bud/admin/Info(1013091)
Received Command [Create location alias] from user [admin]
[Mon Oct  1 17:05:11 2012]Local/ACASECNA/Bud/admin/Error(1023069)
Location alias PnlCube already exists
[Mon Oct  1 17:05:11 2012]Local/ACASECNA/Bud/admin/Warning(1080014)
Transaction [ 0x10009( 0x5069cd47.0x965e1 ) ] aborted due to status [1023069].
[Mon Oct  1 17:05:11 2012]Local/ACASECNA/Bud/admin/Info(1013091)
Received Command [Create location alias] from user [admin]
[Mon Oct  1 17:05:11 2012]Local/ACASECNA/Bud/admin/Error(1023069)
Location alias BsCube already exists
[Mon Oct  1 17:05:11 2012]Local/ACASECNA/Bud/admin/Warning(1080014)
Transaction [ 0x1000a( 0x5069cd47.0x967b7 ) ] aborted due to status [1023069].
[Mon Oct  1 17:05:13 2012]Local/ACASECNA///Info(1013214)
Clear Active on User [admin] Instance [1]

Similar Messages

  • Error refreshing Planning Database

    Hi Friends,
    I am not able to refresh the database in Planning.
    I am getting following error at step2(Setting Locaiton Aliases) "java.lang.UnsatisfiedLinkError: no HspEssbaseOutlineAPI in java.library.path"
    Anyone please guide me.

    It worked well before.
    But after we copied the schema from Prod to dev . Then I tried to login dev environment and refresh. From that time onwards I am facing the isssue.
    Thanks,
    Vishnu.L

  • Database Refresh errors in Planning 9.3.1

    Hi,
    While refreshing the database in planning 9.3.1, i am getting the below errors
    com.hyperion.planning.olap.HspVerifyOutlineException: Verify Outline failed with the following errors:
    **     Error [1042006] detected in member formula for member "Education Allowance".**
    **     Error [1042006] detected in member formula for member "Telephone Allowance".**
    **     Error [1042006] detected in member formula for member "Leave_Allowance".**
    **     Error [1042006] detected in member formula for member "Overtime".**
    **     Error [1042006] detected in member formula for member "Bonus".**
    **     Error [1042006] detected in member formula for member "Turnover Adjustment".**
    **     Error [1042006] detected in member formula for member "Social Security Tax".**
    **     Error [1042006] detected in member formula for member "Medicare".**
    **     Error [1042006] detected in member formula for member "112000".**
    **     Error [1042006] detected in member formula for member "112001".**
    **     Error [1042006] detected in member formula for member "112002".**
    Regards,
    PC

    Hi John,
    Thanks for the prompt reply..
    I checked the error code *1042006* in esb_err_msgs PDF, it showing the errors as "*Network Error message: Unable To*
    *Connect To serverName. The client*
    *timed out waiting to connect to the*
    *Essbase Agent using TCP/IP. Check*
    *your network connections.*"
    But, i am getting different errors in planning. As you suggested, i checked all the member formula. Its validating fine.
    I confused here, which i have to follow John...
    Thanks,
    PC

  • Error creating planning locations from eas console

    Hi,
    I am getting the following error when trying to create new location that point to planning apps from EAS. I was able to see the servers listed under planning. But when clicking on that it displays the following error.
    "Error connecting to planning server" I looked in the EAS logs and saw the error
    " error connecting planning server 11333"
    I tested telnet connection from EAS server to planning server and it worked fine.
    I checked the HBRServer properties file location on planning server and looks good.
    Is there anything else I need to look.
    Thanks
    Srinivas

    Hi John,
    Thanks for the reply. I forgot to mention.
    I followed the steps in the document.
    Logged into every app from planning web.
    Logged into EAS -> right click Administartion and refresh users.
    Then tried. But getting the same error.
    I also checked the planning logs and it clearly mentions "Planning connected to HBR repository successfully".
    Thanks
    Srini

  • Planning error : hyperion.planning.DuplicateUserException

    I am unable to log into planning app after we refreshed our test sqlserver with prod data. I get the followeing error
    hyperion.planning.DuplicateUserException: Another user with the name hypadmin already exists.
    com.hyperion.planning.HspRuntimeException: Failed to sync with user provisioning.
    any ideas ?
    I have tried updating the sid value in HSP_USERS table with the old values -- no luck.
    Please help.

    Sounds like you have not done the migration correctly.
    I take it hypadmin is the application owner and a native user.
    If so you should store the correct native sid on your test environment.
    Have a look at a working planning app on your test environment, go into the relational tables
    look at table HSP_USERS and store the sid for id 50001
    Update the other planning app in your test environment with the correct stored sid in the same table.
    Restart planning.
    Also run the updateusers utility in the planning bin/utiliites directory.
    Its much easier if you create planning applications with the default admin account as the sid stays the same across environments.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • "Error determining planning periods for calendar "  when running a program

    Hi,
    When i am running a program with date range say "01/05/2011" to "30/06/2011",the program is executing successfully without any error. When i am executing the same program with date range as a) "01/05/2009" to "30/06/2011" and b)"01/05/2008" to "30/06/2011" the program is failing with error as "Error determining planning periods for calendar". Can anyone suggest me what i should do to avoid the failure of the program with above date ranges also.
    Thanks in advance,

    Dear,
    Error message 61123:"Error determining planning periods for calendar &".The PPC planning calendar specified in the material master MRP 2 view for the material is  incorrectly.
    The planning calendar periods are insufficiently maintained for the planning calendar used.
    Check the period of planning calendar in MD26 and generate the correct period.You can avoid the problem in several ways:
    Maintain the planning calendar far enough in the future (at least until beyond  the end of the planning horizon).
    Also check any demand is lies beyond the validity period of planning calendar.
    Reduction of the planning horizon of MRP also can control such issue, as MRP planning horizon lies in an area in which the planning calendar is no longer maintained
    Regards,
    R.Brahmankar

  • Server 2009 R2 Stuck Installing Updates and Unexpected Error Refreshing Server Manager

    I have a 2008 R2 server that is running but has issues when restarting or trying to install IE 10. I ran the System Readiness Tool and it fixed a number of issues but there are 5 remaining errors in the Component store that will not repair automatically. 
    They are:
    Checking Component Store
    (f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b 
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_3ef665796f74e084  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_e2d7c9f5b7176f4e  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_13026217d8d91020  
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_6f20fd9b91368156  
    I tried to run a SFC but if failed because there is a repair operation that needs a reboot.  When rebooting, the server tries to install a number of updates but the update fail and the server backs them out and then comes up.  It goes through this
    loop every restart.  There is a pending.xml file that has much in it and I will copy at the end of this post.
    I moved the pending.xml out of the winsxs folder and tried to run the SFC again and now it fails with: "Windows Resource Protection could not perform the requested operation".
    Checking windows updates shows that the IE 10 upgrade for Server 2008 R2 failed a number of times.  I tried to manually install it and it fails.  I was going to go to the server manager and see if I could disable IE and then re-enable it (this
    has worked on W7 pcs in the past) but the Server manager aborts with "Unexpected Error refreshing Server Manager: Catastrophic failure (Exception from HResult: 0x8000FFFF (E_UNEXPECTED)).
    The details of the pending.xml is 32MB but here is an initial snipet:
    <?xml version='1.0' encoding='utf-8'?>
    <PendingTransaction Version="3.1" WcpVersion="6.1.7601.17592 (win7sp1_gdr.110408-1631)" Identifier="9afdc4c419d7ce01476300001c0cb817">
        <Transactions>
            <Transaction TransactionId="TI4.30332431_1303162608:4/Package_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="mdmnis2u.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-2_neutral_GDR" RefExtra="16"/>
                <Install Application="mdmnis1u.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-4_neutral_GDR" RefExtra="16"/>
                <Install Application="mdmgen.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-6_neutral_GDR" RefExtra="16"/>
                <Install Application="mdmcpq.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-8_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1357902608:4/Package_for_KB2853587~31bf3856ad364e35~amd64~~6.1.1.2">
                <Install Application="e30c96e70bb8831ddd580ec5531db3e7, Culture=neutral, Version=6.1.7601.18219, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2853587~31bf3856ad364e35~amd64~~6.1.1.2.2853587-4_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1359952608:4/Package_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0">
                <Install Application="838a6900433638745b282fd8a4ba817a, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-3_neutral_GDR" RefExtra="2"/>
                <Install Application="50fab9749cbc66134f38ae1dc56c98dd, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-6_neutral_GDR" RefExtra="2"/>
                <Install Application="ff3f54cca48812ca511cd304f4431436, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-8_neutral_GDR" RefExtra="2"/>
                <Install Application="6ea506ab96b6a14822c1c2ab6846fc8f, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-10_neutral_GDR" RefExtra="2"/>
                <Install Application="87e192610d63f582a53ceb1723d390ab, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-12_neutral_GDR" RefExtra="2"/>
                <Install Application="4a1985f0141fae9c7cae493197a6b878, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-14_neutral_GDR" RefExtra="2"/>
                <Install Application="016dd2fdac3816d0990ef71a86b49ca5, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-17_neutral_GDR" RefExtra="2"/>
                <Install Application="a37f333ec2c8fbbf96c5ecfffad21444, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-20_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1370242608:4/Package_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="8e09fc8e70ef526fe271bb58df1b359b, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_38_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-149_neutral_GDR" RefExtra="17"/>
                <Install Application="5e964ab696366f5925e35f48bce2e817, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_39_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-152_neutral_GDR" RefExtra="16"/>
                <Install Application="e7ec7425bc5783cd10ed371bbb5001dd, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_39_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-155_neutral_GDR" RefExtra="16"/>
                <Install Application="c4861d635189a7cabac3e380ad0cc01f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_59_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-272_neutral_GDR" RefExtra="17"/>
                <Install Application="36b758890f2cc03ad4c1f7b69ba4b785, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_75_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-364_neutral_GDR" RefExtra="3"/>
                <Install Application="2e15e374d2e2b02519eb2bc107d92452, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_75_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-367_neutral_GDR" RefExtra="3"/>
                <Install Application="79efe25214ed979d4739ffca9cef136f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_76_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-370_neutral_GDR" RefExtra="16"/>
                <Install Application="b8cda4a0fbf72009baf7a4d31ebb7e3f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_76_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-373_neutral_GDR" RefExtra="16"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1428402608:4/Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2">
                <Install Application="65d33ad308914579e80ef4e979752b4e, Culture=neutral, Version=6.1.7601.18177, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-5_neutral_GDR" RefExtra="2"/>
                <Install Application="449dd8313096e8ea0b2798f052e79452, Culture=neutral, Version=6.1.7601.18177, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-8_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1441832608:4/Package_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2">
                <Install Application="0f6c352b3b8ab87d68b593ef7f08823f, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-2_neutral_GDR" RefExtra="3"/>
                <Install Application="8a9b3736ee0dfd9a2d51fe6ecb8262b9, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-4_neutral_GDR" RefExtra="3"/>
                <Install Application="f03bb92dd4f91f6ca1fea9aa5f3d01f6, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-6_neutral_GDR" RefExtra="3"/>
                <Install Application="d985d750c9b4e2d9ac9a71db0b5caeca, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-8_neutral_GDR" RefExtra="3"/>
                <Install Application="4564761e21602085599bee5eebe25ff9, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-10_neutral_GDR" RefExtra="3"/>
                <Install Application="3b2d92a9b35c82a0178c4a63bc04bfd0, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-12_neutral_GDR" RefExtra="3"/>
                <Install Application="c41ad6a9882c5db61704dffad48784e4, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-14_neutral_GDR" RefExtra="3"/>
                <Install Application="b9b638b3db7627f18507dfafb2c78403, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-16_neutral_GDR" RefExtra="2"/>
                <Install Application="54ae1ba9684b6049e8d67dcdc4f58954, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-18_neutral_GDR" RefExtra="2"/>
                <Install Application="4f41d944af2db3f0120fc02c77158999, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-20_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1462782608:4/Package_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0">
                <Install Application="588b833b8de1c71547d6a889dbb75439, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-3_neutral_GDR" RefExtra="2"/>
                <Install Application="0c2bb2bb69a4efa72cf82d30ab59e369, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-6_neutral_GDR" RefExtra="2"/>
                <Install Application="206b27624daebef1bb13dfa8dd6da833, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-8_neutral_GDR" RefExtra="16"/>
                <Install Application="bf6e4fabe941322fa7c42cb2ce5ab035, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-11_neutral_GDR" RefExtra="2"/>
                <Install Application="772cf3ed88bc1b0fc9931ec07075f86d, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-13_neutral_GDR" RefExtra="16"/>
                <Install Application="119d2a1cf82292079aacac2e30f2c14c, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-16_neutral_GDR" RefExtra="2"/>
                <Install Application="8c3eb9ca2caa78fb873d66d3c41a68c5, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-19_neutral_GDR" RefExtra="2"/>
                <Install Application="303a1ce634b3a16c69749f5139be8471, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-22_neutral_GDR" RefExtra="2"/>
                <Install Application="2be7629126ed2b6468203097350f0dfe, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-26_neutral_GDR" RefExtra="16"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1488382608:4/Package_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="6f20d92a7648d71eb43ee35ded059bb1, Culture=neutral, Version=6.1.7601.18254, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-9_neutral_GDR" RefExtra="2"/>
                <Install Application="f0ed83bda0697abd97fd471015aed5c2, Culture=neutral, Version=6.1.7601.17939, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-12_neutral_GDR" RefExtra="16"/>
                <Install Application="febe4281e112cc22eaba92dbd2b4d55c, Culture=neutral, Version=6.1.7601.18254, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-15_neutral_GDR" RefExtra="2"/>
                <Install Application="2f9f4d4b3253a56c28a30f0cb9598076, Culture=neutral, Version=6.1.7601.18264, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-17_neutral_GDR" RefExtra="2"/>
                <Install Application="6cccd8f687e69c579827fb5568f5bd2a, Culture=neutral, Version=6.1.7601.17939, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-20_neutral_GDR" RefExtra="3"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1507982608:4/Package_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0">
                <Install Application="98968d78510963c63353649885f3ecf0, Culture=neutral, Version=6.1.7601.18219, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.2861191-2_neutral_GDR" RefExtra="17"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1608052608:4/Package_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="4eac8b2780d12dcb68dc93ac25ddea50, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-9_neutral_GDR" RefExtra="17"/>
                <Install Application="f3f2fab1a47c8f10dba321b4564b5da2, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-12_neutral_GDR" RefExtra="17"/>
                <Install Application="5683dbcbaaf84c80d448b8e4ff5c4102, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-15_neutral_GDR" RefExtra="2"/>
                <Install Application="6a6f4875757b66f16c6a4827a5d031c4, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-18_neutral_GDR" RefExtra="16"/>
                <Install Application="ed4721225b1075dc927cca1f55a4feb7, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_4_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-21_neutral_GDR" RefExtra="2"/>
                <Install Application="8be73aa5d92530e63a3fa2360881e888, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-24_neutral_GDR" RefExtra="17"/>
                <Install Application="5102c4e5b602cbe09557ed48ea490121, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-27_neutral_GDR" RefExtra="3"/>
                <Install Application="7db7cf609e29d6d392051d1175075ae5, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-30_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_2531772608:4/Package_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0">
                <Install Application="8a96329682d824abc0f8f934fb341ede, Culture=neutral, Version=7.1.7601.18142, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0.2834140-6_neutral_GDR" RefExtra=""/>
            </Transaction>
    andy

    Here is the contents of the CheckSur.log file:
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 26.0
    2015-02-08 22:46
    Checking Windows Servicing Packages
    Checking Package Manifests and Catalogs
    Checking Package Watchlist
    Checking Component Watchlist
    Checking Packages
    Checking Component Store
    (f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b 
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_3ef665796f74e084  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_e2d7c9f5b7176f4e  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_13026217d8d91020  
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_6f20fd9b91368156  
    Summary:
    Seconds executed: 825
     Found 5 errors
      CSI Missing Identity Total count: 1
      CSI Missing Winning Component Key Total count: 4
    andy

  • Error in Planning services

    Hi when i am trying to accesss the forecast data of campaign related one planning profile i am getting this error.
    Error in planning services
    Error messages - count 0001:
    RFC error: Call of a method or kernel Method that has not been implemented.
    Pleas help
    Regards,
    Ravi

    Hi Ravi
    hope you have sorted out this problem, i am getting the same error, could you please guide me or share some informaton. i need this as soon as possible
    thank you
    regards
    shankar

  • Error detailed planning has been reset

    PS Gurus,
    user is trying to copy planning through CJ9BS
    Gave project definition & versions & month & year
    In setting button user selected copy detailed planning for Cost elements
    User is getting error (detailed planning has been reset) Message no. KPT3017
    Thanks
    MM

    We would appreciate if you post the solution for this.
    Regards
    Madhusekhar Gupta

  • Error in planning services urgent plz

    Hi when i am trying to accesss the forecast data of campaign related one planning profile i am getting this error
    Error in planning services
    Error messages - count 0001:
    RFC error: Error when attempting to IMPORT object RSDRI
    plz tellme how to resolve this.points willbe rewarded
    regards
    madhuri

    Hi Madhuri,
    Please check the following in BW BPS Server:
    - Check whether the campaign related planning profile is activated from Client-000 of BW system and transport to client-800
    - After activating the planning profile in Client 000 and transporting it to Client-800. Goto transaction bps0 in BW system and select the planning profile tree. Right click on it and set the profile.
    Also check the following things in BW:
    - Maintain the master data for Business Partners in BW, if not maintained the load the master data for BP as well as products using the normal BW process:
    1.     Activate the data source in CRM system and replicate in BW system.
    2.     Assign the data source to info source and activate the transfer rules.
    3.     Create the Infopackage and load the data.
    I hope this helps
    regards
    Srikantan

  • Error determining planning periods for calendar

    Hello SAP Guru's
    We are receiving the above error when trying to go into MD04 for a particular material.  we have checked the forecast agains the planning calendar and the dates in the forecast and demand planning are approximately 2 years less than the end date in the planning calendar.
    Checking SAP it has said to extend the planing calendar past the planning horizon. It is already extended past the planning horizon.
    The only issue with this product is that the material will soon be superseded by another material, this has a different calendar assigned to it.  Could this be the problem?
    Any info gratefully received.
    Thanks
    Sue

    Hello Vicky,
    The error occurs when first going into MD04.  The exact error message is as follows:
    Error determining planning periods for calendar M14
    Message no. 61123
    Diagnosis
    The system could not determine sufficient planning periods by the planning calendar to group requirements by planning calendar periods for all the requirements planned in the future.
    System Response
    When a material is planned by using the periodical lot size by planning calendar, sufficient periods must be calculated to group requirements by the planning calendar for all requirements.
    Procedure
    Rework the planning calendar with which the material was planned, which means calculate new planning calendar periods.
    To do this, go to Customizing for MRP, under the activity Change PPC periods.

  • Error - Overview Planning (T.Code IMAPL) - Invest Management

    Dear All,
    As i am entering the Planned values on the appropriation request using the T. Code IMAPL, i found the bellow shown error.
    "Planning profile 000001 does not allow planning in controlling area currency"
    I couldn't even unable to view the Approriation Request that i have created at the above mentioned screen (IMAPL)
    Controlling Area Currency - USD
    Company Code Currency - MYR
    System has selected the MYR as default Currency in the Appropriation request that i has created.
    So I would like to request you to provide me the solution to over come the above error ASAP.
    Thanks in Advance
    Gopi

    Check you configuration node OIP1, the Planning currency and set default object currency check box.
    Regards
    Sreenivas

  • Error refresh transfering to PC Suite 6.81 rel 13

    Atenttion!
    Error refresh transfering to PC Suite 6.81 rel 13 for Nokia 6021. My phone turn off short. My phone is connection via Bluetooth.
    PC Suite 6.81 rel. 13 don't work correctly.
    PC Suite 6.80 rel. 22 is all rights. It work correctly.

    Hi,
    Files of around 3.5-4Mb play OK. The files that don't play are around 8-10Mb.
    Yes, it's Nokia Music Manager I'm using.
    Haven't tried moving it without converting - will try this.
    When I say it plays but no sounds, what I mean is the music player comes up with the track apparently playing (i.e. all of the controls are there and the progress bar and time move as if the track is playing) but there is no sound.

  • Error Reading Planning Area

    Hello Gurus,
    While executing a macro via an activity on a background job, the job is cancelled with an error message Error Reading Planning Area. Macro is calculating certain Key figure
    We then run Consistency Check for planning area but no inconsistency and errors were found. We also check the macro and it is on GREEN LIGHT status. We reexecute but it still fails.
    Kindly help on how to go abaout this error as we need this macro working.
    This job with the macro is working for quite a long time and it is the first time it fails and encountered the said error.
    Any help will be gladly appreciated.
    Thanks in advance,
    Raymond

    Check your planning area and see if it has been initialized to the right dates. Its possible your planning book and macros are reading a differenty date and the planning area is not initialized till that date
    Check your macros in the macro workbench (/sapapo/advm) to see what dates are on the macros. If you run the macro interactively you should be getting the same error
    reinitialize the planning area.. pl search the forum for some recent posts on the program involved
    Also check when your planning area was initialized last. you might have to set the initialization requently based on your planning books and other processes

  • Error when Refresh Planning after adding attribute V9.2.1

    Has anyone encountered this and what is the solution:
    Added new attribute dimension in planning web and added attribute members. When I try to do incremental or full refresh, receive error message:
    Errors detected (AssocAttrDimension, 1060057) Could not associate attribute with member (attribute,member) Decanatura, Career -2147218881
    Career is the dimension and Decanatura is the attribute added
    Using 9.2.1
    Thanks
    Jeff

    Hi Jeff,
    please find some findings from planning DBAG which may be useful to resolve your issue:
    You can assign attributes only to sparse dimensions.
    You cannot assign attributes to label-only members.
    After you create attributes and attribute values, you can assign attribute values to each member of the dimension.
    You must assign attribute values to dimension members at the same member level within a dimension.
    You can define attribute values for Entity, user-defined custom dimensions, and Account
    members if the Account dimension is designated as a sparse dimension in all plan types. You
    can then assign attribute values to members of a dimension.
    Attribute values for an attribute must be assigned to the same-level sparse dimension members.
    Assigning an attribute value to another level causes an error during the application refresh.
    hope this helps.
    www.dornakal.blogspot.com
    Edited by: Dornakal on May 28, 2009 5:55 AM

Maybe you are looking for

  • Accessing diff schema at a time in 9ifs

    Hi, Some of business data exits in ifs schema, other datas are exists in oracle db schema. i want to generate a report by using data exists in these two schema. Is that possible through reports server. I badly need solution to this problem. If any on

  • I want XSLT do not create any output file

    I have a xslt file.  <xsl:variable name="var:InValidReceiptCount"> .... In here. I want xslt do not create any output file, also an empty file </xsl:variable> Thanks for helping :)

  • FTP server was down when XI was sending messages

    Hi guys, I have the following problem: Yesterday the FTP server of a legacy system was down while some interfaces were running in XI and were producing some files that should be written in target ftp server. In communication channel monitoring I get

  • 8i EE 2.6.1 , des6i, dev6i

    hi everybody , i have redhat 6.1 / mandrake 7.0 i, i have two quest. : 1- which linux i choose for 8i ? 2- how install both designer 6i and developer 6i above the 8i ? thank u , mohamed

  • Why do embedded videos in mail not play?

    Since I installed OS 10.7, none of the videos being sent to me in mail can be viewed.  Even if I save them to the desktop, I can open them but no video is displayed.