Error when migrating from obiee 11.1.1.3 to 11.1.1.5

Hi
We have developed scorecards in Obiee 11.1.1.3.
Now we have a requirement to upgrade from 11.1.1.3 to 11.1.1.5...For that we are palnning to install 11.1.1.5 on other machine and move the rpd
and catalog from 11.1.1.3 to the new system..Will it work fine or do we need to do any changes...
I implemented it in windows machine where KPIs are working fine but scorecards are throwing Odbc error...
Could you please help me..

For upgrading you should consider
http://www.rittmanmead.com/2011/05/in-place-upgrading-of-obiee-11-1-1-3-to-11-1-1-5/

Similar Messages

  • Run DDL error when migration from sqlserver 2000 to Oracle

    Hello:
    DDL was generated from Oracle SQL developer. However, it always has some errors when running the script.
    Error starting at line 6 in command:
    CREATE OR REPLACE PACKAGE sqlserver_utilities AS
    FUNCTION convert(dataType VARCHAR2,num NUMBER) RETURN NUMBER;
    FUNCTION convert(dataType VARCHAR2,date DATE, num NUMBER ) RETURN VARCHAR2;
    END sqlserver_utilities;
    Error report:
    Incorrect syntax near the keyword 'OR'.
    Error starting at line 34 in command:
    CREATE SEQUENCE tableName_id_SEQ
    MINVALUE 1 MAXVALUE 999999999999999999999999 INCREMENT BY 1 NOCYCLE
    Error at Command Line:34 Column:0
    Error report:
    SQL Error: Line 1: Incorrect syntax near 'SEQUENCE'
    Thanks

    Hello, Dermot.
    Thanks for the help. I have MD_Packages, MD_Sequences, other MD tables and some MIGR tables created in the target oracle database. How could I know if it was created successful? Except those tables, no other tables(SQL server tables) were created in the target oracle database. The others errors in DDL scripts are:
    Error starting at line 370 in command:
    CREATE TABLE table_name1(
    ID NUMBER(10,0),
    Part_Activity VARCHAR2(20)
    Error at Command Line:370 Column:0
    Error report:
    SQL Error: Column or parameter #1: Cannot find data type NUMBER.
    Error starting at line 376 in command:
    ALTER TABLE table_name1
    ADD CONSTRAINT PK_table_name1 PRIMARY KEY
    ID
    ENABLE
    Error report:
    SQL Error: Line 6: Incorrect syntax near 'ENABLE'.
    Error starting at line 413 in command:
    CREATE TABLE table_name2 (
    ID VARCHAR2(6) NOT NULL,
    COMPETITION NUMBER(10,0)
    Error at Command Line:413 Column:0
    Error report:
    SQL Error: Column or parameter #1: Cannot find data type VARCHAR2.
    Error starting at line 2,800 in command:
    CREATE TABLE table_name3 (
    Prefix NVARCHAR2(510),
    Type NVARCHAR2(510),
    ProductGroup NVARCHAR2(510)
    Error at Command Line:2,800 Column:0
    Error report:
    SQL Error: Column or parameter #1: Cannot find data type NVARCHAR2.
    Error starting at line 2,808 in command:
    CREATE TABLE table_name4 (
    id NUMBER(10,0),
    bldg VARCHAR2(50),
    queue VARCHAR2(50),
    location VARCHAR2(50),
    type VARCHAR2(50),
    maxsize VARCHAR2(50),
    color VARCHAR2(50),
    empid VARCHAR2(50),
    serial VARCHAR2(50),
    duplex VARCHAR2(50),
    server VARCHAR2(15) DEFAULT 'Server'
    Error at Command Line:2,808 Column:0
    Error report:
    SQL Error: Column or parameter #1: Cannot find data type NUMBER.
    Thank you very much for the helo.
    Halfmoon

  • WebI report throwing error when migrated from XIR2 to XI3.1

    I have some webi reports built in BO XIR2 on OLAP universes (SAP BW3.5 based). Recently I have migrated the reports from old XIR2 environment to a new XI3.1 environment.
    The specification of new system is as below:
    BO XI3.1
    SAP BW 3.5
    No SP and FP is installed. (Actually when I tried to install the SP2, it failed)
    After the migration, some of my reports are running for 5 minutes and then throwing an error like below:
    A database error occured. The database error text is: Error in MDDataSetBW.GetCellData. See RFC trace file or SAP system log for more details. (WIS 10901).
    The same report is working fine in old system.
    Has anyone faced this problem yet?
    Regards

    Hi Jacques,
    The transports are already imported.
    What I can see is if there is a query with only dimension objects and no measure, then that is throwing error in XI3.1. But the same query is running fine in XIR2.
    Any Idea?
    Thanks and Regards

  • ODBC Error when migrating from SQL Server 2008 to SQL Anywhere 12

    Hello community,
    i have the following requirement:
    I need to migrate a Database with some Demo data into a SQL Anywhere 12 Database. The SQL Anywhere 12 Database is part of the SAP BusinessObjects Enterprise XI 3.1 SP7 installation and came with the same as OEM Product.
    The Environment looks like the following:
    DB1 is a MS SQL Server 2008 R2 64 Bit running on Windows Server 2008 R2 64 Bit.
    DB2 is the SAP BusinessObjects Enterprise XI 3.1 SP7 installation with the shipped SQL Anywhere 12 (12.0.1.3873) Database running on SLES 11.3 64 Bit
    CL1 is my Windows 7 64 Bit Client where Sybase Central is installed in 64 Bit. On CL1 i have a 64 Bit System ODBC Connection connecting to DB1 successfully.
    Basically i followed the following (pretty straight forward) tutorial:
    Migrating a SQL Server Database to SQL Anywhere White Paper-Technical: Mobile Enterprise, Database Management iAnywhere …
    When i want to test the connection from inside Sybase Central (During the migration process) i receive the following error:
    From inside Sybase Central my connection looks as follows:
    And from the ODBC Manager the connection looks as follows:
    Personally i found is strange that the Sybase ODBC Driver Manager drops the error. I would expect that the MS SQL ODBC Driver Manager pops the error it its related to the ODBC DSN to DB1.
    Any ideas?
    Thanks and Regards
    -Seb.

    Hi Sebastian,
    The data from the SQL Server database must be migrated to an existing SQL Anywhere database.  Could you please tell me where this SQL Anywhere database resides and how are you connecting to it?
    The error message is saying that the connection to the SQL Anywhere remote database server is failing, as opposed to the connection to the SQL Server database.

  • I got this error when migrate from Jdev11gTp4 into JDev 11g (Build 5188)

    Hello,
    when i migrated my application from Jdev11gTp4 into JDeveloper 11g (Build 5188) , i got this error but it's not understandable for me and I am new in jdeveloper and adf application
    C:\JDeveloper\mywork\Application14\FOO\ViewController\public_html\myFolder\myPage .jspx
    Error(7,4): The public type __myPage_32__jspx must be defined in its own file
    Thanks
    GreenApple
    Edited by: greenApple on Jan 15, 2009 9:18 AM

    Hello,
    when i migrated my application from Jdev11gTp4 into JDeveloper 11g (Build 5188) , i got this error but it's not understandable for me and I am new in jdeveloper and adf application
    C:\JDeveloper\mywork\Application14\FOO\ViewController\public_html\myFolder\myPage .jspx
    Error(7,4): The public type __myPage_32__jspx must be defined in its own file
    Thanks
    GreenApple
    Edited by: greenApple on Jan 15, 2009 9:18 AM

  • Permissions error when migrating from Access 2000

    Hi
    I have an Access 2000 database that is pretty small - only has 8 tables, total DB size is < 24MB. I've gone through all the steps of creating the Oracle model etc and all went without a hitch. However, when I come to migrate table data I get the following error:
    Unable to migrate data from source table "tbl Case" to destination table CDSS.tbl_Case : CDSS.tbl_Case; [Microsoft][ODBC Microsoft Access Driver] You do not have the necessary permissions to use the "C:\Customers\Vancouver\CDSS\Database\CDSS.mdb" object. Have your system administrator or the person who created this object establish the appropriate permissions for you.
    There is no security on the Access database so I'm a little unsure as to what is causing this error to occur; does anyone have any ideas?
    Thanks very much

    There is an option in the users guide for switching off any security in Access. This should solve the problem with permissions

  • Xerces.jar error when migrating from weblogic 8.1SP6 to Oracle Weblogic 10.

    Hi all,
    I am migrating the J2ee (1.4) application from 8.1sp6 to Oracle Weblogic server 10.3
    I have set the environment in build.xml to point to Oracle weblogic server and the java to the one that comes with Oracleweblogic.
    Rite now I am seeing the following error.
    [javac] C:\Zdev10.3\sep09_Build\src\source\com\myapp\sample\ejb\external\pmt\ServicesBean.java:51: package org.apache.xerces.validators.datatype does not exist
    [javac] import org.apache.xerces.validators.datatype.XMLException;
    [javac] ^
    [javac] C:\Zdev10.3\sep09_Build\src\source\com\myapp\sample\ejb\external\pmt\ServicesBean.java:109: cannot find symbol
    [javac] symbol : class XMLException
    [javac] location: class com.myapp.sample.ejb.external.pmt.ServicesBean
    [javac] public static String validateXML(String xmlRequest) throws XMLException {
    [javac] ^
    [javac] C:\Zdev10.3\sep09_Build\src\source\com\myapp\sample\dao\tm\CommonTMDao.java:281: warning: non-varargs call of varargs method with inexact argument type for last parameter;
    [javac] cast to java.lang.Object for a varargs call
    [javac] cast to java.lang.Object[] for a non-varargs call and to suppress this warning
    According to Oracle Weblogic , xerces is been not supported .
    Also we need to go with the xerces.jar for some time.
    Any ideas /inputs/work arounds on this will be appreciated.
    thanks,
    Jyothsna
    Edited by: user10751474 on Oct 9, 2009 9:56 AM

    You have to make sure the LogMessage class (weblogic/i18n/logging/LogMessage) is in the classpath
    Using WebLogic Internationalization utilities: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13704/utilities.htm#i1011073
    and an example: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13704/textformatterclasses.htm#g1016464
    and: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13704/loggerclasses.htm#g1020871

  • Link error when migrating from SUNWspro_6.2 to SunStudio 11

    I'm trying to "migrate" an application to be compiled with SunStudio 11 while now is successfully building with SUNWspro_6.2 in both release and debug mode.
    Using SunStudio 11 the application can be successfully built in release more (without -g option), however if I'm trying to use the -g option I get the following linkage error:
    Linking /nms/base/bin/_solaris/allmenudb ...
    /opt/SUNWspro/bin/CC -mt -R/usr/lnms/jre/lib/sparc/hotspot:/usr/lnms/jre/lib/sparc:/usr/lnms/jre/lib/sparc/server:/usr/lnms/jre/lib/sparc/client:/usr/lnms/lib:/usr/lnms/lib/plugin:/usr/dt/lib:/usr/openwin/lib:/opt/lnmsoracle/lib:/usr/OV/lib:/opt/OV/lib:/usr/ucblib solaris/main.o solaris/cMenuDB.o -L/nms/base/lib/_solaris -loplogdebug -loplog -lopjser -lwebcomm -ltopo -lmgmt_mibdb -lmibdbsql -lnotf_ng -loputil -loplockfile -lmonLevelAPI -lgetCommunity -lcrypto -lconfapi -L/nms/base/lib/_solaris -larl -lsnmpv3 -lmibtree -lengine -ldevkit -lmibtree -larl -L/usr/openwin/lib -lXt -lX11 -ltoposql -lorasql -L/nms/sys/solaris/SourcePro5e/lib -ltls7712d -lpthread -lnsl -lthread2312d -lthrexcept2312d -lnetwork1712d -linternet2212d -lpointer2312d -lsync2312d -ltrace2312d -lfunctor2312d -lfactory1312d -litc2312d -lfunctor_list2312d -lsecsock1215d -lftp2212d -lhttp2212d -lstreams1312d -ltypes1312d -lpop32212d -lmime1112d -lfunctor_map2312d -L/unixlnms5/ux_sys/solaris/OV6.4.1/lib -lc -lovsnmp -lov -lnsl -L/opt/corp/projects/onms/tools/oracle/solaris/product/9.2/lib -L/opt/corp/projects/onms/tools/oracle/solaris/product/9.2/rdbms/lib -lclntsh `cat /opt/corp/projects/onms/tools/oracle/solaris/product/9.2/lib/sysliblist` -R/opt/corp/projects/onms/tools/oracle/solaris/product/9.2/lib -laio -lposix4 -lkstat -lm -lthread -lintl -lw -lpthread -lposix4 -ldl -lgen -lnsl -lsocket -ll -lm -lc -ly -L/usr/ucblib -lucb -o /nms/base/bin/_solaris/allmenudb
    Undefined first referenced
    symbol in file
    __rwstd::moneypunct_impl<wchar_t,0>::ivals_ _solaris/main.o
    [Hint: static member __rwstd::moneypunct_impl<wchar_t,0>::ivals_ must be defined in the program]
    __rwstd::moneypunct_impl<wchar_t,1>::ivals_ _solaris/main.o
    [Hint: static member __rwstd::moneypunct_impl<wchar_t,1>::ivals_ must be defined in the program]
    __rwstd::moneypunct_impl<char,0>::ivals_ _solaris/main.o
    [Hint: static member __rwstd::moneypunct_impl<char,0>::ivals_ must be defined in the program]
    __rwstd::moneypunct_impl<char,1>::ivals_ _solaris/main.o
    [Hint: static member __rwstd::moneypunct_impl<char,1>::ivals_ must be defined in the program]
    ld: fatal: Symbol referencing errors. No output written to /nms/base/bin/_solaris/allmenudb
    *** Error code 1
    clearmake: Error: Build script failed for "/nms/base/bin/_solaris/allmenudb"
    clearmake[1]: Leaving directory `/nms/base/apps/appdbgen/allmenudb'
    make failed building all in /nms/base/apps/appdbgen/allmenudb
    *** Error code 1
    clearmake: Error: Build script failed for "all"
    build script failed ...
    The application uses the roguewave libraries 5.5 and I suspect there is something wrong when linking with this libraries but not sure.
    Is there a new version of roguewave needed for this new SunStudio 11?
    Is there some compatibility switches needed?
    Did anybody had a similar issue? Please Help!

    The recommended patches are all installed (please see the below showrevs commands), and the libCstd.so has the size and the date below (Is this the correct one ??? ). With all this the error is still there.
    13:23 nms1(daniel) ~/patchSolaris> ls -ail /usr/lib/libCstd.so*
    292129 lrwxrwxrwx 1 root other 12 Apr 14 14:59 /usr/lib/libCstd.so -> libCstd.so.1
    292349 -rwxr-xr-x 1 root bin 1890588 Nov 19 01:19 /usr/lib/libCstd.so.1
    13:18 nms1(daniel) ~/patchSolaris> showrev -p | grep 117557
    Patch: 117557-03 Obsoletes: Requires: Incompatibles: Packages: SUNWlibms, SUNWlmsx, SUNWlibm
    13:19 nms1(daniel) ~/patchSolaris> showrev -p | grep 108434
    Patch: 108434-13 Obsoletes: Requires: 109147-07 Incompatibles: Packages: SUNWlibC
    Patch: 108434-18 Obsoletes: Requires: 109147-07 Incompatibles: Packages: SUNWlibC
    Patch: 108434-21 Obsoletes: Requires: 109147-07 Incompatibles: Packages: SUNWlibC
    Patch: 108435-13 Obsoletes: Requires: 108434-13 Incompatibles: Packages: SUNWlibCx
    Patch: 108435-18 Obsoletes: Requires: 108434-17 Incompatibles: Packages: SUNWlibCx
    Patch: 108435-21 Obsoletes: Requires: 108434-21 Incompatibles: Packages: SUNWlibCx
    13:19 nms1(daniel) ~/patchSolaris> showrev -p | grep 108435
    Patch: 108435-13 Obsoletes: Requires: 108434-13 Incompatibles: Packages: SUNWlibCx
    Patch: 108435-18 Obsoletes: Requires: 108434-17 Incompatibles: Packages: SUNWlibCx
    Patch: 108435-21 Obsoletes: Requires: 108434-21 Incompatibles: Packages: SUNWlibCx
    13:21 nms1(daniel) ~/patchSolaris> showrev -p | grep 111721
    Patch: 111721-04 Obsoletes: Requires: Incompatibles: Packages: SUNWlibms, SUNWlmsx, SUNWlibm
    13:21 nms1(daniel) ~/patchSolaris> showrev -p | grep 109147
    Patch: 109147-26 Obsoletes: 110791-01 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcslx, SUNWcsl, SUNWcsxu, SUNWtoo, SUNWtoox, SUNWhea, SUNWbtool, SUNWarc, SUNWbtoox, SUNWosdem
    Patch: 109147-37 Obsoletes: 110791-01 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcslx, SUNWcsl, SUNWcsxu, SUNWtoo, SUNWtoox, SUNWhea, SUNWbtool, SUNWarc, SUNWbtoox, SUNWmdb, SUNWmdbx, SUNWosdem
    Patch: 109147-40 Obsoletes: 110791-01 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWcslx, SUNWcsl, SUNWcsxu, SUNWtoo, SUNWtoox, SUNWhea, SUNWbtool, SUNWarc, SUNWbtoox, SUNWmdb, SUNWmdbx, SUNWosdem
    Patch: 108434-13 Obsoletes: Requires: 109147-07 Incompatibles: Packages: SUNWlibC
    Patch: 108434-18 Obsoletes: Requires: 109147-07 Incompatibles: Packages: SUNWlibC
    Patch: 108434-21 Obsoletes: Requires: 109147-07 Incompatibles: Packages: SUNWlibC
    13:21 nms1(daniel) ~/patchSolaris> showrev -p | grep 111697
    Patch: 111697-04 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot, SUNWsprox, SUNWxcu4t
    13:21 nms1(daniel) ~/patchSolaris> showrev -p | grep 114802
    Patch: 114802-01 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot
    Patch: 114802-02 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot
    13:21 nms1(daniel) ~/patchSolaris> showrev -p | grep 108652
    Patch: 108652-74 Obsoletes: 110499-03 Requires: Incompatibles: Packages: SUNWxwfnt, SUNWxwice, SUNWxwplt, SUNWxwicx, SUNWxwplx, SUNWxwacx, SUNWxwman, SUNWxwfa, SUNWxwpmn, SUNWxwdxm, SUNWxwinc, SUNWxwslb
    Patch: 108652-83 Obsoletes: 110499-03 Requires: Incompatibles: Packages: SUNWxwfnt, SUNWxwice, SUNWxwplt, SUNWxwicx, SUNWxwplx, SUNWxwacx, SUNWxwman, SUNWxwfa, SUNWxwpmn, SUNWxwdxm, SUNWxwinc, SUNWxwslb
    Patch: 112663-01 Obsoletes: Requires: 108652-44 Incompatibles: Packages: SUNWxwplt
    Patch: 108940-57 Obsoletes: Requires: 108652-49 Incompatibles: Packages: SUNWmfrun, SUNWdtbax
    Patch: 108919-20 Obsoletes: Requires: 108652-19 Incompatibles: Packages: SUNWdtbas, SUNWdtdte
    Patch: 109354-19 Obsoletes: Requires: 108652-19 Incompatibles: Packages: SUNWdtdte, SUNWdtwm, SUNWdtma
    Patch: 108921-17 Obsoletes: Requires: 108652-19 Incompatibles: Packages: SUNWdtwm
    13:22 nms1(daniel) ~/patchSolaris> showrev -p | grep 120760
    Patch: 120760-04 Obsoletes: Requires: Incompatibles: Packages: SPROlang, SPROlangx
    13:22 nms1(daniel) ~/patchSolaris> showrev -p | grep 121017
    Patch: 121017-01 Obsoletes: Requires: Incompatibles: Packages: SPROcpl, SPROcplx, SPROtlbn7, SPROtll7, SPROtl7x, SPROtll7x, SPROscl, SPROsclx, SPROstl4h, SPROstl4a, SPROstl4o, SPROstl4x, SPROstl4y, SPROgc, SPROlgc, SPROgcx, SPROlgcx
    13:22 nms1(daniel) ~/patchSolaris> showrev -p | grep 121015
    Patch: 121015-02 Obsoletes: Requires: Incompatibles: Packages: SPROcc
    13:23 nms1(daniel) ~/patchSolaris> uname -a
    SunOS nms1 5.8 Generic_108528-29 sun4u sparc SUNW,Sun-Blade-2500
    Thank you for all the help,
    Daniel

  • Lightroom encountered and error when reading from it preview cache and needs to quit

    A power outage caused my Lightroom 5.2 to shut down without closing.  When I powered back up and opened lightroom it gives me an error "Lightroom encountered and error when reading from it preview cache and needs to quit" and then it says it will try to fix it the next time it opens. I have opened it 20 times and it is not fixing it. I removed the program completely and upgraded to 5.5 AND it is still giving me the same error.  Is my catalog corrupt or something? I had it set to automatically load the most currently used catalog, so it is not allowing me to open or start a new catalog either. HELP!!!

    Search the forum, this has been answered many times.

  • I'm unable to open up Lightroom 5, I get this message in a pop up box: "Lightroom encountered an error when reading from it's preview cache and needs to quit" Underneath  that is "Lightroom will attempt to fix this problem the next time when it launches."

    I'm unable to open up Lightroom 5, I get this message in a pop up box: "Lightroom encountered an error when reading from it's preview cache and needs to quit" Underneath  that is "Lightroom will attempt to fix this problem the next time when it launches."  It hasn't, what should I do? Thanks Shawn (Irish Se7en) .

    Can you try to rename (not delete!) the folder named "YOUR_CATALOG_NAME Previews.lrdata" and restart Lightroom?

  • "Lightroom encountered and error when reading from its preview cache and needs to quit"

    I keep receiving this error every time I open LR, "Lightroom encountered and error when reading from its preview cache and needs to quit" and the app won't open. It said LR would try and fix this error next time I opened it but the error remains. I tried uninstalled and installing the app and the error remains.
    Any Ideas here? Is there another app that may be telling it where to look for the cache and it no longer there? I was using a ramdisk for a bit but ditched it. Not sure if that has something to do with it but it seems suspect.
    Your thoughts?
    --Kenny Brandon Wilson

    Talked to Adobe support this morning, this is their response in case anyone else is looking for help. I'm running a Windows 7 box, LR 5.6.
      Gokul: Click on start and type %appdata%, then open roaming folder.
      Edward: ok
      Gokul: Open Adobe folder.
      Gokul: Open Lightroom folder.
      Gokul: Open Lightroom folder> Preferences.
      Edward: ok
      Gokul: Rename Lightroom 5 Preferences.agprefs file as Lightroom 5 Preferences.agprefsOLD.
      Edward: OK
      Gokul: Please check if you can launch Lightroom without any error.
      Edward: it shows me a welcome screen and is asking me to select my country
      Edward: aka, register the software
      Gokul: You can skip and launch it.
      Edward: LR catalog not found
      Gokul: Please select the catalog.
      Edward: my original catalog?
      Gokul: Yes.
      Edward: testing integrity of catalog
      Edward: loaded just fine
      Gokul: Okay.
      Gokul: Please check if you can re-launch it again.
      Edward: yes, it worked!
      Gokul: Excellent!
      Gokul: Since your preferences were corrupted you were facing issue so we renamed the preferences file to reset it.
      Edward: aha....ok
    All of my import/export presets were intact along with develop user presets. I'm happy as a clam for my $10/month!

  • LR encountered an error when reading from its preview cache and needs to quit.

    I have the 30 day trial version of Lightroom.  I was able to use it for one week, but the past 1.5-2 weeks, it has been locked up and giving this error message.  How do I resolve the problem?  And how do I reset the 30 day free trial?  I would like to have time using the product, before deciding on the annual contract.
    "LR encountered an error when reading from its preview cache and needs to quit.  Lightroom will attempt to fix this problem the next time it launches."
    Thank you.

    Delete the preview cache from the Lightroom folder in your Pictures folder if you used the default placement. It has the extension .lrdata.
    You cannot reset the trial period.

  • I keep receiving this error every time I open LR, "Lightroom encountered and error when reading from its preview cache and needs to quit" and the app won't open. It said LR would try and fix this error next time I opened it but the error remains. I tried

    I keep receiving this error every time I open LR, "Lightroom encountered and error when reading from its preview cache and needs to quit" and the app won't open. It said LR would try and fix this error next time I opened it but the error remains. I tried uninstalled and installing the app and the error remains. I have windows 8. Can anyone please help???

    Use Windows Explorer to open the folder containing your catalog. The normal location is Pictures\Lightroom. Locate a folder with the extension .lrdata and delete that folder. Then you should be able to start Lightroom again, and Lightroom will begin building and new previews folder. Do not delete anything else.

  • It says Lightroom encountered an error when reading from a previous cache and needs to quit. Light room will attempt to to fix the problem the next time it launches.

    how do i fix this. It says Lightroom encountered an error when reading from a previous cache and needs to quit. Light room will attempt to to fix the problem the next time it launches.

    Have a look at this thread.
    Lightroom encountered an error when reading from its preview cache and needs to quit.  Lightroom will attempt to fix this problem the next time it launches"."

  • Error Launching LR 5: "Lightroom encountered an error when reading from its preview cache and..."

    Error Launching LR 5: "Lightroom encountered an error when reading from its preview cache and needs to quit.  Lightroom will attempt to fix this problem the next time it launches."
    I've tried renaming my catalog.lrcat file.  I've copied over my most recent backup of the catalog.lrcat and that didn't work either.

    On Mac:
    PS - to open the previews "folder" (a "package" is just a "special" folder) on Mac, ctrl-click and choose "Show package contents.." - same way you open any other special folder, like .app or .lrplugin..
    Rob

Maybe you are looking for