Universe overload migration failure

Hi All,
Iu2019d like to ask your help concerning an issue that Iu2019m charge of resolving. It's concerning the migration of universe overload from a source to a destination. Two unviverse restrictions are applied on two groups in the source: Rest1->Group1, Rest2->Group2.
These are the steps:
1- In srource CMC create 2 groups: Group1 and Group2
2- In Designer apply two row restrictions Rest1 applied on Group1 and Rest2 applied on Group2 (I used eFashion universe)
3- Export the groups and eFashion universe to destination CMS using Import Wizard (keep the universe overload)
4- In the destination CMS, Create a new user User1 and add it to the newly imported Group1 AND Group2
5- In the destination system, Log in InfoView using User1
6- Create a new Webi doc using eFashion universe
7- You get this error :
User rigths not found: See your BusinessObjects administrator (Error WIS 00502).
does anyone knwo why the user rights cannot be found?
Thanks in advance,
Mohamed Ali

Grace's Babe wrote:
Trying to use Migration Assistant to transfer files from my G4 Mirror Door to a G5. Both are running updated Leopard.
Firewire's connected, everything seems to work fine, until the process is nearly done about an hour and half later. Then I get the message "The Mac you are transferring from is not responding. Check your network connections."
I don't get this. Why would the process fail at the end when all is working fine?
who knows. how are computers connected? via ethernet or airport? can you boot G4 in target mode and connect it to the G5 directly? try transferring that way.

Similar Messages

  • Document Universe Overloads/Access Restrictions

    Is there a good way to document universe overloads/access restrictions? I can't seem to find anything. We have a ton of universe objects which are restricted for certain users/groups, and we need to re-work this list. Ideally, I'd love to have these listed out by restriction name - restricted object, or restriction name - row-level restriction.
    Any help is much appreciated!

    Hi Kunal,
    Yep, that's exactly what I did.  The query I used was:
    Select SI_NAME, SI_OBJECTS
                      from CI_APPOBJECTS
    where  SI_KIND like '%OVERLOAD%' and SI_PARENT_CUID = '<universe ID>'
    This worked fairly well, but it would be great if SAP would give us an ability to output these queries to Excel to make them more manageable.
    Thanks!
    Bill

  • Hyper-V guest SQL 2012 cluster live migration failure

    I have two IBM HX5 nodes connected to IBM DS5300. Hyper-V 2012 cluster was built on blades. In HV cluster was made six virtual machines, connected to DS5300 via HV Virtual SAN. These VMs was formed a guest SQL Cluster. Databases' files are placed on
    DS5300 storage and available through VM FibreChannel Adapters. IBM MPIO Module is installed on all hosts and VMs.
    SQL Server instances work without problem. But! When I try to live migrate SQL VM to another HV node an SQL Instance fails. In SQL error log I see:
    2013-06-19 10:39:44.07 spid1s      Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.07 spid1s      SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.
    2013-06-19 10:39:44.07 spid1s      Write error during log flush.
    2013-06-19 10:39:44.07 spid55      Error: 9001, Severity: 21, State: 4.
    2013-06-19 10:39:44.07 spid55      The log for database 'Admin' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
    2013-06-19 10:39:44.07 spid55      Database Admin was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
    2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.31 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.31 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.32 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.32 spid36s     fcb::close-flush: Operating system error (null) encountered.
    2013-06-19 10:39:44.33 spid36s     Starting up database 'Admin'.
    2013-06-19 10:39:44.58 spid36s     349 transactions rolled forward in database 'Admin' (6:0). This is an informational message only. No user action is required.
    2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail (failure): alignBuf 0x000000001A75D000, writeSize 0x400, filePos 0x156adc00
    2013-06-19 10:39:44.58 spid36s     blankSize 0x3c0000, blkOffset 0x1056e, fileSeqNo 1313, totBytesWritten 0x0
    2013-06-19 10:39:44.58 spid36s     fcb status 0x42, handle 0x0000000000000BC0, size 262144 pages
    2013-06-19 10:39:44.58 spid36s     Error: 17053, Severity: 16, State: 1.
    2013-06-19 10:39:44.58 spid36s     SQLServerLogMgr::FixupLogTail: Operating system error 170(The requested resource is in use.) encountered.
    2013-06-19 10:39:44.58 spid36s     Error: 5159, Severity: 24, State: 13.
    2013-06-19 10:39:44.58 spid36s     Operating system error 170(The requested resource is in use.) on file "v:\MSSQL\log\Admin\Log.ldf" during FixupLogTail.
    2013-06-19 10:39:44.58 spid36s     Error: 3414, Severity: 21, State: 1.
    2013-06-19 10:39:44.58 spid36s     An error occurred during recovery, preventing the database 'Admin' (6:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected,
    contact Technical Support.
    In windows system log I see a lot of warnings like this:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider
    Name="Microsoft-Windows-Ntfs" Guid="{3FF37A1C-A68D-4D6E-8C9B-F79E8B16C482}" />
      <EventID>140</EventID>
      <Version>0</Version>
      <Level>3</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8000000000000008</Keywords>
      <TimeCreated
    SystemTime="2013-06-19T06:39:44.314400200Z" />
      <EventRecordID>25239</EventRecordID>
      <Correlation
    />
      <Execution
    ProcessID="4620" ThreadID="4284" />
      <Channel>System</Channel>
      <Computer>sql-node-5.local.net</Computer>
      <Security
    UserID="S-1-5-21-796845957-515967899-725345543-17066" />
      </System>
    - <EventData>
      <Data Name="VolumeId">\\?\Volume{752f0849-6201-48e9-8821-7db897a10305}</Data>
      <Data Name="DeviceName">\Device\HarddiskVolume70</Data>
      <Data Name="Error">0x80000011</Data>
      </EventData>
     </Event>
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{752f0849-6201-48e9-8821-7db897a10305}, DeviceName: \Device\HarddiskVolume70.
    ({Device Busy}
    The device is currently busy.)
    There aren't any error or warning in HV hosts.

    Hello,
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
    Thank you for your understanding and support.
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click 
    here.
    Fanny Liu
    TechNet Community Support

  • Data Miner Extension in SQL Developer 4.0 EA3 Release: EA3 Repository Migration Failure

    The Data Miner extension in the SQL Developer 4.0 EA3 release fails when attempting to migrate the repository to EA3. This posting contains instructions on how to recover from this failure as well as to successful migrate the repository from EA2 to EA3. There are no problems when just installing a fresh Data Miner repository.
    Sorry about the difficulty if this has caused you any problems.
    Mark
    Failure message displayed in log when migrating to EA3:
    Error report -
    ORA-06550: line 96, column 40:
    PLS-00382: expression is of wrong type
    ORA-06550: line 96, column 7:
    PL/SQL: Statement ignored
    06550. 00000 -  "line %s, column %s:\n%s"
    *Cause:    Usually a PL/SQL compilation error.
    *Action:
    Instructions on how to recover from failure and continue using original version of SQL Developer:
    1) Execute the following sql as SYS in order to allow the Data Miner repository to be open for use again:
    UPDATE ODMRSYS.ODMR$REPOSITORY_PROPERTIES
    SET PROPERTY_STR_VALUE = 'LOADED'
    WHERE PROPERTY_NAME = 'REPOSITORY_STATUS';
    COMMIT;
    2) During attempted migrationto EA3 failed, access priviliges to the Data Miner repository are revoked from users. In order to use Data Miner again, these grants must be reapplied. You can either use the UI guided process to accomplish this, which requires the SYS password, or you can run the usergrants.sql script, again as the SYS user. For instructions on how to run the usergrants.sql script, or any adminstrative script, review the instructions contained in the install_scripts_readme.html file. You can find this file in the SQL Developer directories created when you unzipped SQL Developer. It is located in the following relative directory: \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts.
    Instructions on how to successfully migrate to EA3.
    If you have already attempted to migrate to EA3 and failed, then you need to perform the recovery instructions noted above, after which you can continue with the instructions below.
    If you have not yet attempted to migrate to EA3, then just following the instructions below.
    1) Replace all contents the script file createxmlworkflowsbackup.sql with specification contained at the end of this posting. The file to edit can be found in the \<SQL Developer Install Directory>\sqldeveloper\dataminer\scripts directory.
    2) After completing the edit to createxmlworkflowsbackup.sql,  you can proceed with the UI guided migration or perform the migration using the appropriate migration script. Review the install_scripts_readme.html file in the /dataminer/scripts directory for instructions on how to perform the migration using the script. For the UI migration, simply open any user connection in your Data Miner navigator, and you will be prompted to perform the migration.
    WHENEVER SQLERROR EXIT SQL.SQLCODE;
    DEFINE MAX_VERSIONS = 30
    EXECUTE dbms_output.put_line('Start Backup Data Miner Workflows ' || systimestamp);
    DECLARE
      table_cnt NUMBER;
    BEGIN
      SELECT count(*) INTO table_cnt FROM all_tables WHERE owner='ODMRSYS' AND table_name='ODMR$WORKFLOWS_BACKUP';
      IF (table_cnt = 0) THEN
        EXECUTE IMMEDIATE '
          CREATE TABLE ODMRSYS.ODMR$WORKFLOWS_BACKUP
            USER_NAME VARCHAR2(30 CHAR) NOT NULL
          , PROJECT_ID NUMBER NOT NULL
          , PROJECT_NAME VARCHAR2(30 CHAR) NOT NULL
          , PJ_CREATION_TIME TIMESTAMP(6) NOT NULL
          , PJ_LAST_UPDATED_TIME TIMESTAMP(6)
          , PJ_COMMENTS VARCHAR2(4000 CHAR)
          , WORKFLOW_ID NUMBER NOT NULL
          , WORKFLOW_NAME VARCHAR2(30 CHAR) NOT NULL
          , WORKFLOW_DATA SYS.XMLTYPE
          , CHAIN_NAME VARCHAR2(30 CHAR)
          , RUN_MODE VARCHAR2(30 CHAR)
          , STATUS VARCHAR2(30 CHAR) NOT NULL
          , WF_CREATION_TIME TIMESTAMP(6) NOT NULL
          , WF_LAST_UPDATED_TIME TIMESTAMP(6)
          , BACKUP_TIME TIMESTAMP(6) NOT NULL
          , VERSION NUMBER NOT NULL
          , WF_COMMENTS VARCHAR2(4000 CHAR)
          , CONSTRAINT ODMR$WORKFLOWS_BACKUP_PK PRIMARY KEY
              PROJECT_ID
            , WORKFLOW_ID
            , VERSION
            ENABLE
          LOGGING
          PCTFREE 10
          INITRANS 1
          XMLTYPE COLUMN "WORKFLOW_DATA" STORE AS BASICFILE CLOB';
      END IF;
    END;
    DECLARE
      schema_old_ver VARCHAR2(30);
      schema_ver   VARCHAR2(30);
      patch        VARCHAR2(30);
      db_ver       VARCHAR2(30);
      v_storage    VARCHAR2(30);
      schema_data  CLOB;
      v_db_11_2_0_2 NUMBER; -- db is <= 11.2.0.2?
      row_cnt      NUMBER;
      ver_num      NUMBER := 1;
      maintaindom  NUMBER;
      workflow_rec ODMRSYS.ODMR$WORKFLOWS_BACKUP%ROWTYPE;
    BEGIN
      SELECT STORAGE_TYPE INTO v_storage FROM ALL_XML_TAB_COLS WHERE OWNER='ODMRSYS' AND TABLE_NAME='ODMR$WORKFLOWS' AND COLUMN_NAME='WORKFLOW_DATA';
      if (db is >= 11.2.0.3 AND SQL Dev > 3.0) OR (db is <= 11.2.0.2 AND MAINTAIN_DOM_PATCH_INSTALLED)
        back up all workflows
      end if  
      IF (v_storage != 'BINARY') THEN
        -- determine xml schema version
        SELECT XMLSerialize(CONTENT SCHEMA AS CLOB) INTO schema_data
        FROM DBA_XML_SCHEMAS WHERE schema_url = 'http://xmlns.oracle.com/odmr11/odmr.xsd' AND owner = 'ODMRSYS';
        maintaindom := INSTR(schema_data, 'xdb:maintainDOM="false"', 1, 1);
        -- determine database version
        SELECT version INTO db_ver FROM product_component_version WHERE product LIKE 'Oracle Database%';
        --- Check schema compatibility
        schema_old_ver := '11.2.0.1.9'; -- default value
        BEGIN
          SELECT property_str_value INTO schema_ver
          FROM "ODMRSYS"."ODMR$REPOSITORY_PROPERTIES" WHERE property_name = 'WF_VERSION';
          IF schema_old_ver = schema_ver  THEN
            IF NOT (db_ver = '11.2.0.1' OR db_ver = '11.2.0.2') THEN
              dbms_output.put_line('WARNING: The backup process can not be done, The workflows need to be migrated first');
            RETURN;
            END IF;
          END IF;
        EXCEPTION WHEN NO_DATA_FOUND THEN
          schema_ver  := schema_old_ver;
          dbms_output.put_line('No WF_VERSION found. Defaults to: '  || schema_old_ver);
        END;
        -- determine if MAINTAIN_DOM_PATCH_INSTALLED
        IF (INSTR(db_ver, '11.2.0.2') > 0 OR INSTR(db_ver, '11.2.0.1') > 0 OR INSTR(db_ver, '11.2.0.0') > 0) THEN
          v_db_11_2_0_2 := 1;
          BEGIN
            SELECT PROPERTY_STR_VALUE INTO patch FROM ODMRSYS.ODMR$REPOSITORY_PROPERTIES WHERE PROPERTY_NAME = 'MAINTAIN_DOM_PATCH_INSTALLED';
            patch := UPPER(patch);
          EXCEPTION WHEN NO_DATA_FOUND THEN
            patch := 'FALSE';
          END;
        ELSE
          v_db_11_2_0_2 := 0;
        END IF;
      END IF;
      IF (   v_storage = 'BINARY'
          OR (v_db_11_2_0_2 = 0) -- db is >= 11.2.0.3
          OR ((v_db_11_2_0_2 > 0) AND ((patch = 'TRUE') OR (maintaindom = 0))) ) THEN -- db is <= 11.2.0.2 AND (MAINTAIN_DOM_PATCH_INSTALLED OR maintaindom="true")
        SELECT count(*) INTO row_cnt FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
        IF (row_cnt > 0) THEN
          SELECT NVL(MAX(VERSION)+1,1) INTO ver_num FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP;
        END IF;
        FOR wf IN (
          SELECT
            p.USER_NAME "USER_NAME",
            p.PROJECT_ID "PROJECT_ID",
            p.PROJECT_NAME "PROJECT_NAME",
            p.CREATION_TIME "PJ_CREATION_TIME",
            p.LAST_UPDATED_TIME "PJ_LAST_UPDATED_TIME",
            p.COMMENTS "PJ_COMMENTS",
            x.WORKFLOW_ID "WORKFLOW_ID",
            x.WORKFLOW_NAME "WORKFLOW_NAME",
            xmlserialize(DOCUMENT x.WORKFLOW_DATA as CLOB indent size = 2) "WORKFLOW_DATA",
            x.CHAIN_NAME "CHAIN_NAME",
            x.RUN_MODE "RUN_MODE",
            x.STATUS "STATUS",
            x.CREATION_TIME "WF_CREATION_TIME",
            x.LAST_UPDATED_TIME "WF_LAST_UPDATED_TIME",
            x.COMMENTS "WF_COMMENTS"
          FROM ODMRSYS.ODMR$PROJECTS p, ODMRSYS.ODMR$WORKFLOWS x
          WHERE p.PROJECT_ID = x.PROJECT_ID
        LOOP
          workflow_rec.USER_NAME := wf.USER_NAME;
          workflow_rec.PROJECT_ID := wf.PROJECT_ID;
          workflow_rec.PROJECT_NAME := wf.PROJECT_NAME;
          workflow_rec.PJ_CREATION_TIME := wf.PJ_CREATION_TIME;
          workflow_rec.PJ_LAST_UPDATED_TIME := wf.PJ_LAST_UPDATED_TIME;
          workflow_rec.PJ_COMMENTS := wf.PJ_COMMENTS;
          workflow_rec.WORKFLOW_ID := wf.WORKFLOW_ID;
          workflow_rec.WORKFLOW_NAME := wf.WORKFLOW_NAME;
          workflow_rec.WORKFLOW_DATA := SYS.XMLTYPE(wf.WORKFLOW_DATA);
          workflow_rec.CHAIN_NAME := wf.CHAIN_NAME;
          workflow_rec.RUN_MODE := wf.RUN_MODE;
          workflow_rec.STATUS := wf.STATUS;
          workflow_rec.WF_CREATION_TIME := wf.WF_CREATION_TIME;
          workflow_rec.WF_LAST_UPDATED_TIME := wf.WF_LAST_UPDATED_TIME;
          workflow_rec.BACKUP_TIME := SYSTIMESTAMP;
          workflow_rec.VERSION := ver_num;
          workflow_rec.WF_COMMENTS := wf.WF_COMMENTS;
          BEGIN
            -- Output the ids (proj name, workflow name, proj id, workflow id)
            dbms_output.put_line('Backup workflow: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
            INSERT INTO ODMRSYS.ODMR$WORKFLOWS_BACKUP VALUES workflow_rec;
            COMMIT;
          EXCEPTION WHEN OTHERS THEN
            dbms_output.put_line('Backup workflow failed: ('||wf.PROJECT_NAME||', '||wf.WORKFLOW_NAME||', '||wf.PROJECT_ID||', '||wf.WORKFLOW_ID||')');
          END;
        END LOOP;
      END IF;
      -- keep the latest 30 versions
      EXECUTE IMMEDIATE 'DELETE FROM ODMRSYS.ODMR$WORKFLOWS_BACKUP WHERE VERSION <= :1' USING (ver_num - &MAX_VERSIONS);
      COMMIT;
    EXCEPTION WHEN OTHERS THEN
      ROLLBACK;
      RAISE_APPLICATION_ERROR(-20000, 'Workflow backup failed. Review install log.');
    END;
    EXECUTE dbms_output.put_line('End Backup Data Miner Workflows. ' || systimestamp);

    823006 wrote:
    5.a. XLS export of big number columns looses precision, for example a number(38) column with all digits used.
    I believe excel only holds 15 digits of precision.
    Edited by: 823006 on Jan 18, 2011 8:14 AMThen it would be nice if you can define the "excel type" of each column. So you can make this number a "string" in the XLS.
    Edited by: user9361780 on Jan 18, 2011 9:12 AM

  • Mailbox Migration Failure for Exchange 2010 to 2010 latest SP and Rollup

    I'm getting the following error for the last mailbox to migrate. This is Exchange 2010 to 2010 DB and no idea how to get pass this so far. It failed with 465 errors at 76%.
    Any ideas?   I've check AD account to make sure permissions was okay.   I was able to open the mailbox and look at the message and the size was 56k.   Target mailbox database didn't have restrictions.  
    10/12/2014 11:36:32 PM [CAS1] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.
    <baditem errorType="MapiExceptionInvalidParameter" errorCode="0x80070057" flags="0x00000000" id="000000004BA135250C952443B11655B7F71ABAC6070007BFF2DC839F1443BD2C542D104D64790000003036DA000007BFF2DC839F1443BD2C542D104D647900004361F8040000">
      <folder id="000000004BA135250C952443B11655B7F71ABAC6010007BFF2DC839F1443BD2C542D104D64790000003036DA0000">Inbox</folder>
      <sender>Microsoft Outlook</sender>
      <recipient>Joe</recipient>
      <subject>ICON 2.5%   46.125-46.875 vs 2.99</subject>
      <messageClass>IPM.Note</messageClass>
      <size>1609</size>
      <dateSent>06/24/2014 12:38:04</dateSent>
      <dateReceived>06/24/2014 12:38:04</dateReceived>
      <errorMessage>MapiExceptionInvalidParameter: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80070057, ec=-2147024809)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=8259]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=677][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropFXDstCopyConfig [83]
        Lid: 27962   ROP: ropTellVersion [134]
        Lid: 27962   ROP: ropFXDstPutBufferEx [157]
        Lid: 17082   ROP Error: 0x80070057
        Lid: 31329 
        Lid: 21921   StoreEc: 0x80070057
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 1238    Remote Context Overflow
        Lid: 27676   dwParam: 0x1A8000
        Lid: 36537   dwParam: 0x1A8000
        Lid: 5587    StoreEc: 0x8004010F PropTag: 0x1A8000 
        Lid: 33375   StoreEc: 0x8004010F
        Lid: 17146   StoreEc: 0x8004010F
        Lid: 27676   dwParam: 0x1A8000
        Lid: 36537   dwParam: 0x1A8000
        Lid: 5587    StoreEc: 0x8004010F PropTag: 0x1A8000 
        Lid: 33375   StoreEc: 0x8004010F
        Lid: 17146   StoreEc: 0x8004010F
        Lid: 50223 
        Lid: 14012   StoreEc: 0x80070057
        Lid: 39487 
        Lid: 33551   StoreEc: 0x80070057
        Lid: 49935 
        Lid: 55871   StoreEc: 0x80070057
        Lid: 48163 
        Lid: 64547   StoreEc: 0x80070057
        Lid: 36807 
        Lid: 53645   StoreEc: 0x80070057
        Lid: 36097   StoreEc: 0x80070057
        Lid: 6993    StoreEc: 0x80070057
        Lid: 4921    StoreEc: 0x80070057
        Lid: 17200   StoreEc: 0x80070057
        Lid: 41725 
        Lid: 2761    StoreEc: 0x80070057
        Lid: 28570   StoreEc: 0x80070057
        Lid: 29738 
        Lid: 3401    StoreEc: 0x80070057
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849 
        Lid: 21817   ROP Failure: 0x80070057
        Lid: 22630  </errorMessage>
      <errorContext>--------
    Operation: IMapiFxProxy.ProcessRequest
    OpCode: TransferBuffer
    DataLength: 16347
    Operation: IMapiFxProxy.ProcessRequest
    OperationSide: Target
    Primary (d40cec8b-1128-4f50-923b-0822538abe36)
    OpCode: TransferBuffer
    DataLength: 16347</errorContext>
    </baditem>

    Hi,
    Please try to use Outlook switches with /cleanfinders, /cleanreminders and /resettodobar to check this issue. Usually the corrupted items were default mailbox folders, especially search folders.
    Refer to the similar thread.
    https://social.technet.microsoft.com/Forums/en-US/89902f00-4b84-4f10-b909-121a81241c85/can-not-move-exchange-2003-mailboxes-to-exchange-2010?forum=exchangesvrdeploylegacy
    Best Regards.

  • Universe Connections migration

    Hi ,
    we are using SAP BW Query as the sourse for the Creation of Universe with connections to DEV system.
    please let me know how should we migrate the universe connections from DEV to QA?
    or how is that we can point the universe connection from DEV to QA ?
    Regards

    Hey Jaya,
    the only thing i don't understand is how a universe can have more than connection.
    >> It is not possible But this feature is avail in BO XI 4.0
    I told Connection mat be same but we are in diff systems (Dev/QA/Prod)
    the connection to the universe is changed in the parameters if i'm not wrong.
    >> Yep
    Can let me know the steps where the connection can be changed and pointed to all the systems at the same time.
    >> At same time not possible.
    Possible if you open all 3 systems(D-Q-P) then change connections in each system.
    Hope you understood.
    Gracias...!!

  • Reg: Universe Designing (Migration Project)

    Hi Gurus,
    I need Informtion related to the migration project.
    Migrating BO 5.1.7 to BO XI R 3.1.
    the old universe with old database is structured as.
    Eg: PTKEN as table name and objects as PTKEN.WASId
    the new ( migrated universe ) has the database structure as
    Eg: KEM_LKP_PTKEN as table anem and objects as WASId
    What the process has to be done to change all the tables in the universe with the new database...
    Regards
    L K Vepuri
    Edited by: L K Vepuri on Feb 28, 2011 3:56 PM

    Hi Mr. Vepuri,
    If the table name is changed at the universe level then follow the below steps.
    1. Open the universe in the designer
    2. Right click on the table which has been modified and rename it with the changed name.
    3. Click on the View>> Refresh Structure.
    4. and check whether it throws any error message or not.
    For Object  PTKEN.WASId--- what does it mean?
    Is it column name or object name at universe level.
    Object definition of each object is visible as Table_Name.Column_Name.
    If you want to change the object name then you can rename it.
    In order to propagate the changes made at a database level to universe level always click on the View >>refresh structure
    Hope it helps.
    Thanks,
    Sands

  • Migration failure

    Hello,
    I've been trying for the past three days to migrate a Sybase 11 database to Oracle, using the latest migration workbench and the sybase 11 plugin. I'm doing the migration to the built-in catalogue, not to an external Oracle database. The process for loading the source model runs for about 16 hours and then aborts with an error message that says:
    Failed to load Source Model. [INTERSOLV][ODBC SQL server driver][SQL Server]Invalid column name 'fill_factor'.
    Does anyone have any idea what this means?
    Any help will be appreciated.
    Gabriel.

    16 hours seems like a very long time. Is it a massive database?
    The error you are getting is related to the version of Sybase11 you are migrating. It works with 11.9.2 but should work for 11.5 and 11.0.3 but
    there is an issue with the later two versions in the 202 release which should be fixed in the upcomming 92010 release.
    Contact Oracle Migration Workbench ([email protected])support for a possible resolution to your problem.

  • IPlanet migration failure for Sun One Web server 6.1SP6

    Recently we downloaded the Sun One Web server 6.1SP6 and we are having problem trying to upgrade our current version. We have been able to install the package and get the admin console running but we can not migrate the current instances across to the new version. We can successfully choose an instance to migrate however once we click the migrate button, absolutely nothing happens in the browser and nothing can be seen in any error logs and truss indicates a read of a pipe going nowhere, after which the cgi stub terminates.
    We are migrating from
    iPlanet-WebServer-Enterprise/6.0SP5 B10/31/2002 16:22
    to
    CORE1116: Sun ONE Web Server 6.1SP6 B05/07/2006 12:33

    well, it is good that you have considered to upgrade considering 6.0 Sp5 has been EOL'ed for some time now.
    here is the url that describes migrating to 6.1 from 6.0
    http://docs.sfbay/app/docs/doc/819-6514/6n8h9dr61?a=view
    now, if you are still having issues with migration using GUI, you can provide us the admin server error logs or call Sun tech support (if you have support contract) to help you with this.

  • Access Migration Failure: Error 3021 Method 'Run' of object

    I am doing a proof-of-concept to migrate and convert some Access applications.
    I downloaded the migration tool and then tried the Northwind mdb to verify it worked and all went as planned with a SQL output file.
    When I run it against a working copy of the production mdb it gives this error and produces no output.
    Error #3021 – XMLExporter – Method ‘Run’ of object ‘_Application failed *access.mdb” Database Schema Export did not complete successfully.
    I conjecture it is trying to 'Run' the object and not finding it. How can I work around this or fix the error. I am not an Access expert so any ideas are appreciated.
    slavanaway
    Message was edited by:
    slavanaway

    Hi Ian,
    Thanks for the detailed posting, it's very helpful.
    If you are receiving error #2501, it would appear that there's an issue in opening a report in your MS Access database.
    When you open the MS Access database to be exported, can you successfully view your report(s) or do you receive the #2501 error even then? If you receive this error when accessing the reports, I believe it's relating to the printer setup on the machine. The default printer on the machine you are using may be "imcompatible" with the format of your MS Access report. Try to select another printer on your network as the default, or even try re-installing the default printer. If this does not resolve your issue, please let me know.
    I hope this helps.
    Regards,
    Hilary

  • Migration failure to new MacBook Pro

    have tried using Migration Assistant to transfer content from old MacBook pro to a new 13 inch i5. Seems to go smoothly via Firewire cable and get completion message with all transferred successfully etc. But I get no content for iPhoto, iCal, Address book, Photo booth? What is wrong??? have tried three times with same result. Have tried importing files for those applications without success.

    Robbherbal wrote:
    Thanks...But the manual says clearly if you don't want to use set up assistant when first opening the new machine, no probs, just use Migration Assistant, later when you like........Is that really duff advice from Apple??
    Yup. 
    They're right, you can use Migration Assistant, but there are downsides you don't get with Setup Assistant.
    With Migration Assistant, you end up with an extra user account.  The one you created when setting-up the new Mac plus the one(s) you transferred.  Look in System Prefs > Accounts; most likely, the missing data is in one of them.

  • GW801 Primary Domain Netware to OES migration failure

    I have started migrating my GroupWise from NetWare to OES. I have migrated a small post office to a server with no problems. I have created a new domain and webaccess on another OES server. My problem came when trying to migrate my primary domain from NetWare to OES. I used the migration utility from the same NetWare server and to the same OES server the small post office I migrated earlier. The migration utility ran without errors. I manually changed the IP's in the Domain and Link configuration, and also I have a startup MTP in our main post office to the primary domain which I changed (I needed this when running on the NetWare Cluster). I ran a database recover DB before and after the migration. All links were green but no traffic from post office to migrated domain or gwia domain to primary domain, queues were filling up. I was running out of time so had to revert back to the NetWare server. I changed the IP's in the Domain object and Links, and MTP on PO, ran DB recover again. Now it wouldn't work on the NetWare server. Luckily I ran a DBCOPY to another source before migrating. I copied over top the domain directory and that saved me.
    Any ideas???
    I'm running OES with NSS and long name support because I didn't want to deal with administration compatibility issues. I didn't have any problems using my workstation ConsoleOne for the small post office and new webaccess domain. But should I have been using ConsoleOne on the OES server?
    On the NetWare server I had in the startup files "Remote Connections" user and password. These are NLM settings and error out when using them on OES. Do I still need a "Remote Connections" user for OES?
    If I'm using long name space on the NSS volume do I have to worry about case sensitivity? I'll just copy the files over manually.
    Unrelated
    The default agent file and log locations are in /opt and /var. I would prefer to have these on my NSS volume. Is this good practice for OES?

    kjhurni, thanks for your response. I hope this reply looks correct. I'm reply via my GroupWise Client. For some reason I have a problem with replying via the browser.
    I figured the agents would have to stay put if I didn't want to deal with update issues in the future. I think I'll move my logs.
    I used the GroupWise Migration utility. Actually I tried again last night with no luck again. The link configuration changes I know that the PO is trying to connect. Here is part of the log file.
    06:32:36 094 MTP: GW HCH: Unable to open connection [8925]. Address = 10.0.59.210, Port = 7100
    The Primary Domain thinks all is well when looking at the screen. Because it shows all PO's and Domains open. The Secondary Domain shows Primary is down.
    I have been using the Migration utility because of the case issues. Which when I tried Dbcopy it didn't seem to change the files to lower case. I think I figured this out and that I need to have Unix name space running and not long. Otherwise it won't make it lowercase.
    I just have a Training PO on this server, no MTA.
    Do you think I should add secondary IP addresses for POA and MTA agents on the same server?
    I do use odd ports for my secondary MTA's because they still run on a NetWare cluster.
    Yes, I'm using OES/NSS and ConsoleOne on Windows. I have many administrators that I didn't want to educate, that's why I didn't go SLES.
    This is my plan for my third try.
    Change the volume name space to unix on destination server.
    Make normal dbcopy on original server (This is what saved me the last two times).
    Change ConsoleOne Domain and MTA paths.
    Stop MTA
    Use DBCOPY -m (it will probably work now that I'm using unix name space).
    Delete mslocal, wpcsin and wpcsout folders.
    Start MTA
    Check Links and change If needed.
    If I cannot get it to work. Perform a top down rebuild.
    What do you think?
    >>> On 3/31/2010 at 1:56 PM, kjhurni<[email protected]> wrote:
    kwhite;1953211 Wrote:
    > I have started migrating my GroupWise from NetWare to OES. I have
    > migrated a small post office to a server with no problems. I have
    > created a new domain and webaccess on another OES server. My problem
    > came when trying to migrate my primary domain from NetWare to OES. I
    > used the migration utility from the same NetWare server and to the same
    > OES server the small post office I migrated earlier. The migration
    > utility ran without errors. I manually changed the IP's in the Domain
    > and Link configuration, and also I have a startup MTP in our main post
    > office to the primary domain which I changed (I needed this when running
    > on the NetWare Cluster). I ran a database recover DB before and after
    > the migration. All links were green but no traffic from post office to
    > migrated domain or gwia domain to primary domain, queues were filling
    > up. I was running out of time so had to revert back to the NetWare
    > server. I changed the IP's in the Domain object and Links, and MTP on
    > PO, ran DB recover again. Now it wouldn't work on the NetWare server.
    > Luckily I ran a DBCOPY to another source before migrating. I copied
    > over top the domain directory and that saved me.
    >
    > Any ideas???
    > I'm running OES with NSS and long name support because I didn't want to
    > deal with administration compatibility issues. I didn't have any
    > problems using my workstation ConsoleOne for the small post office and
    > new webaccess domain. But should I have been using ConsoleOne on the
    > OES server?
    > On the NetWare server I had in the startup files "Remote Connections"
    > user and password. These are NLM settings and error out when using them
    > on OES. Do I still need a "Remote Connections" user for OES?
    > If I'm using long name space on the NSS volume do I have to worry about
    > case sensitivity? I'll just copy the files over manually.
    >
    > Unrelated
    > The default agent file and log locations are in /opt and /var. I would
    > prefer to have these on my NSS volume. Is this good practice for OES?
    NSS is fine, but you can't really change the location of the agent
    files. Log files, yes, but the agents and startup files are going to be
    in the /opt/novell/groupwise/agents/bin and /share directories
    Anyway, back to your question
    You used which migration utility? the OES Miggui or the groupwise
    migration utility?
    I personally just do a dbcopy if it's an MTA as it'll do everything I
    Need it to do.
    On the destination OES2 server, you mentioned you had a PO on it. Did
    you also have another MTA on that as well?
    The only time I've seen issues is when you have multiple agents on
    OES2. At that point you'll need to use dedicated IP's (there's a
    problem it seems where Groupwise doesn't pay attention to the "bind to
    specific" IP if it's running on Linux/OES2).
    Also, I've had an issue where the stupid MTA had a "bad" configuration
    (odd port # leftover from WAY back when) and no amount of rebuilding
    would fix it. I ended up having to manually edit the startup file to
    force it to use the configured IP and Port.
    Then I stopped/started the MTA and it stayed loaded. Then I
    stopped/started the POA and it loaded.
    Then a few minutes it got communication to each other and seemed to
    behave properly from that point on.
    I am assuming that you are using NSS on your OES2 server and using
    ConsoleOne on a Windows machine (as opposed to running on the actual
    OES2 server itself).
    kjhurni
    kjhurni's Profile: http://forums.novell.com/member.php?userid=734
    View this thread: http://forums.novell.com/showthread.php?t=405860

  • Migration failures

    Hi,
    We are migrating form Exchange 2007 to Exchange 2013.  Migration has been a pain as we are constantly hitting the bad item limit.  With the test mailboxes we have been using we have had to export almost every email to a pst file to successfully
    migrate them.  We have mailboxes with tens of thousands of items and it looks like we will have to archive every email, migrate the mailbox then reimport them.
    The so-called bad items are all able to be read using Outlook 2007, and cannot be deleted due to legal requirements.
    Several mailboxes I was moving had about a dozen or so items in total (emails, calendar items etc).  However no matter what bad item limit I set the migration always fails saying there are too many bad items; even when I set the bad item limit to 1000!
    Has anyone else had this trouble?
    cheers
    Justin

    I have seen this before with certain mail archiving solutions where the stubs left in the mailbox were causing this. Do the "bad items" all have the same IPM.Note type? Have you run an ISINTEG against the source mailbox? What happens if you create
    a new mailbox store in 2007 and move the mailbox there first before going to 2013?

  • Ds 5.2 - ds 6.2 migration failure

    Several things, the kernel and ds5.2 application are both 64 bit.
    I am migrating the instance to the same host just in a different directory.
    Im trying to migrate from ds 5.2 -> ds 6.2 and having issues migrating the schema using the dsmig command.
    Here is the output of the command:
    ./dsmig migrate-schema -v /jes/slapd-ds3 /jes/6.2/slapd-ldap
    Backing up file (/jes/6.2/slapd-ldap/migration/migration_status) ..... DONE.
    Launching Schema Migration of server instance /jes/slapd-ds3 .....
    Stopping server instance /jes/6.2/slapd-ldap ..... Server stopped
    Parsing file (/jes/slapd-ds3/config/schema/05rfc2247.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/05rfc2927.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/11rfc2307.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/20subscriber.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/25java-object.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/28pilot.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/30ns-common.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50iplanet-servicemgt.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-admin.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-calendar.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-certificate.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-compass.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-delegated-admin.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-directory.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-legacy.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-mail.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-media.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-mcd-browser.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-mcd-config.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-mcd-li.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-mcd-mail.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-mlm.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-msg.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-netshare.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-news.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-proxy.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-value.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-wcal.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-web.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/99user.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/99iaaa-radius.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/99migrated_custom.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/50ns-iabs.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/55ims-ical.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/56ims-schema.ldif) ..... DONE.
    Parsing file (/jes/slapd-ds3/config/schema/60iplanet-calendar.ldif) ....
    After all of these parsing statements, the dsmig command just exists with return code 125.
    I checked the new config/schema directory and some of the schema ldifs are not even copied over.
    Thanks for your help in advance.

    Figured out the problem.
    Seems like when there is an ldif file that dsmig doesnt like, the process just exists.
    Manually moved that one particular file and restarted slapd seemed to work.

  • SBS Migration Failure

    Ok migrating sbs 2008 to sbs 2011 all went well until exchange uninstall.
    IT have used Adsi edit to remove all referneces to Exchange and now I have no logon server and no exchange server.
    The exchange iinstallation software on the new sbs 2011 server states all roles are installed yet I cannot add the existing forest as the exchnge container has been deleted. Also there are no logon servers either now.
    So sbs 2008 was migrated till the point of uninstalling exchange where an issues occurred leadind some one to use ADSI edit to remove anything to do with exchnage. Cannot demote source server because AD is broken.
    Need to get exchange up and running on sbsb 2011 and remove the old server permantely  
    any help would be gratefully received
    H

    My advice is to call Microsoft support.  Without actually looking at the condition of your AD/what is left in Exchange, there's no way this can be done in a forum.
    1-800-microsoft
    Unfortunately TechNet isn't coming back, sorry folks :-(

Maybe you are looking for