Catalog Conversion Problem

I have been trying to convert a photo catalog from Photoshop Album 2 to Photoshop Elements 9.  The PSA is on an XP system and the PSE 9 is on Windows 7.   The backup and restore both go fine.  The conversion begins and stops right at 27% every time.  I get an error telling me to repiar with original software.  I've tried just about everything I know and have seen on the blogs with no success.  I removed any photo creations from the catalog and that did not help.  The catalog contains a few thousand photos that are really well organized by my 80 year old mother and I'm petrified she will lose them. If anyone can help it would be greatly appreciated.  Neither product is supported any longer by Adobe.

The catalog conversion process is quite buggy, and PSE 6 and later have serious bugs in handling drives.  As a first step in troubleshooting, download and run the utility psedbtool:
http://www.johnrellis.com/psedbtool/#_Downloading,_Installing,_and
Copy and paste the output here -- come to the Web to post your reply, rather than using email, since the Adobe forum software will truncate your reply.

Similar Messages

  • Photoshop Elements 11 catalog conversion solution

    The Photoshop Elements 11 Organizer failed to convert my Photoshop Elements 6 catalog until I ran the PSE11 Organizer under the built-in Windows 7 Administrator account. I did not find this solution mentioned during my efforts to solve this installation problem. It was not a suggestion I found in Adobe's help files dealing with catalog conversion. So here is a summary for others with this problem.
    I installed Photoshop Elements 11 on my Dell XPS 9000 running Windows 7 Pro x64. I retained my PSE6 installation. I have nearly 20,000 cataloged images in my PSE6 catalog.
    Problems began when the PSE11 Organizer failed to convert my PSE6 catalog to the new PSE11 format. The process seemed to run to completion, but then an error message said the conversion had failed. The suggestion was to repair and optimize the PSE6 catalog using PSE6, then try converting again. Conversion to PSE11 still failed. I spent a few hours searching for suggestions and solutions and tried each of them without success.
    I then found one suggestion that the problem might involve permissions. The suggestion was to right click PhotoshopElementsOrganizer.exe in its installation folder (which on my computer is at at D:\Photo\Elements 11 Organizer) and run Organizer as an administrator. This also failed. However it did get me thinking about permissions.
    Even though my personal account on my computer is an administrator account, I logged off my personal account and logged on to my computer's built-in Administrator account that comes with Windows 7. I don't think I've used that account for any other purpose since I set up this computer 3 years ago.
    I then ran the PSE11 Elements Organizer using the Administrator account and the catalog conversion ran to completion and all seemed correct.
    However, when I went to the folder where I kept my PSE6 catalog (G:\0-PSElementsCatalog\FamilyPhotos-6), the new PSE11 catalog was not there. Instead, PSE11 had put the converted catalog in the (absolutely awful) default location at C:\ProgramData\Adobe\Elements Organizer\Catalogs\FamilyPhotos-6). Using the PSE11 Organizer, I renamed the catalog to G:\0-PSElementsCatalog\FamilyPhotos-11(ConvertedFrom6). I then used PSE11 Organizer to move the converted catalog to my preferred location on my G: drive.
    All is now well.
    Why did I have to use the built-in Administrator account to do the catalog conversion? What permissions does it have that my personal account (also an Administrator) does not have? Some years ago I encountered a similar problem that involved permissions on a registry key, not permissions on files or folders. Perhaps someone at Adobe can enlighten us.

    One thing puzzles me:
    RedClayFarmer wrote:
    I then found one suggestion that the problem might involve permissions. The suggestion was to right click PhotoshopElementsOrganizer.exe in its installation folder (which on my computer is at at D:\Photo\Elements 11 Organizer) and run Organizer as an administrator. This also failed.
    I don't understand why running the exe from the installation folder would have worked.
    I would have simply tried to run that exe from its real location :
    Sorry, I can't help you more about permissions...

  • LR 4.4 (and 5.0?) catalog: a problem and some questions

    Introductory Remark
    After several years of reluctance this March I changed to LR due to its retouching capabilities. Unfortunately – beyond enjoying some really nice features of LR – I keep struggling with several problems, many of which have been covered in this forum. In this thread I describe a problem with a particular LR 4.4 catalog and put some general questions.
    A few days ago I upgraded to 5.0. Unfortunately it turned out to produce even slower ’speed’ than 4.4 (discussed – among other places – here: http://forums.adobe.com/message/5454410#5454410), so I rather fell back to the latter, instead of testing the behavior of the 5.0 catalog. Anyway, as far as I understand this upgrade does not include significant new catalog functions, so my problem and questions below may be valid for 5.0, too. Nevertheless, the incompatibility of the new and previous catalogs suggests rewriting of the catalog-related parts of the code. I do not know the resulting potential improvements and/or new bugs in 5.0.
    For your information, my PC (running under Windows 7) has a 64-bit Intel Core i7-3770K processor, 16GB RAM, 240 GB SSD, as well as fast and large-capacity HDDs. My monitor has a resolution of 1920x1200.
    1. Problem with the catalog
    To tell you the truth, I do not understand the potential necessity for using the “File / Optimize Catalog” function. In my view LR should keep the catalog optimized without manual intervention.
    Nevertheless, when being faced with the ill-famed slowness of LR, I run this module. In addition, I always switch on the “Catalog Settings / General / Back up catalog” function. The actually set frequency of backing up depends on the circumstances – e.g. the number of RAW (in my case: NEF) files, the size of the catalog file (*.lrcat), and the space available on my SSD. In case of need I delete the oldest backup file to make space for the new one.
    Recently I processed 1500 photos, occupying 21 GB. The "Catalog Settings / Metadata / Automatically write changes into XMP" function was switched on. Unfortunately I had to fiddle with the images quite a lot, so after processing roughly half of them the catalog file reached the size of 24 GB. Until this stage there had been no sign of any failure – catalog optimizations had run smoothly and backups had been created regularly, as scheduled.
    Once, however, towards the end of generating the next backup, LR sent an error message saying that it had not been able to create the backup file, due to lack of enough space on the SSD. I myself found still 40 GB of empty space, so I re-launched the backup process. The result was the same, but this time I saw a mysterious new (journal?) file with a size of 40 GB… When my third attempt also failed, I had to decide what to do.
    Since I needed at least the XMP files with the results of my retouching operations, I simply wanted to save these side-cars into the directory of my original input NEF files on a HDD. Before making this step, I intended to check whether all modifications and adjustments had been stored in the XMP files.
    Unfortunately I was not aware of the realistic size of side-cars, associated with a certain volume of usage of the Spot Removal, Grad Filter, and Adjustment Brush functions. But as the time of the last modification of the XMP files (belonging to the recently retouched pictures) seemed perfect, I believed that all my actions had been saved. Although the "Automatically write changes into XMP" seemed to be working, in order to be on the safe side I selected all photos and ran the “Metadata / Save Metadata to File” function of the Library module. After this I copied the XMP files, deleted the corrupted catalog, created a new catalog, and imported the same NEF files together with the side-cars.
    When checking the photos, I was shocked: Only the first few hundred XMP files retained all my modifications. Roughly 3 weeks of work was completely lost… From that time on I regularly check the XMP files.
    Question 1: Have you collected any similar experience?
    2. The catalog-related part of my workflow
    Unless I miss an important piece of knowledge, LR catalogs store many data that I do not need in the long run. Having the history of recent retouching activities is useful for me only for a short while, so archiving every little step for a long time with a huge amount of accumulated data would be impossible (and useless) on my SSD. In terms of processing what count for me are the resulting XMP files, so in the long run I keep only them and get rid of the catalog.
    Out of the 240 GB of my SSD 110 GB is available for LR. Whenever I have new photos to retouch, I make the following steps:
    create a ‘temporary’ catalog on my SSD
    import the new pictures from my HDD into this temporary catalog
    select all imported pictures in the temporary catalog
    use the “File / Export as Catalog” function in order to copy the original NEF files onto the SSD and make them used by the ‘real’ (not temporary) new catalog
    use the “File / Open Catalog” function to re-launch LR with the new catalog
    switch on the "Automatically write changes into XMP" function of the new catalog
    delete the ‘temporary’ catalog to save space on the SSD
    retouch the pictures (while keeping and eye on due creation and development of the XMP files)
    generate the required output (TIF OR JPG) files
    copy the XMP and the output files into the original directory of the input NEF files on the HDD
    copy the whole catalog for interim archiving onto the HDD
    delete the catalog from the SSD
    upon making sure that the XMP files are all fine, delete the archived catalog from the HDD, too
    Question 2: If we put aside the issue of keeping the catalog for other purposes then saving each and every retouching steps (which I address below), is there any simpler workflow to produce only the XMP files and save space on the SSD? For example, is it possible to create a new catalog on the SSD with copying the input NEF files into its directory and re-launching LR ‘automatically’, in one step?
    Question 3: If this I not the case, is there any third-party application that would ease the execution of the relevant parts of this workflow before and/or after the actual retouching of the pictures?
    Question 4: Is it possible to set general parameters for new catalogs? In my experience most settings of the new catalogs (at least the ones that are important for me) are copied from the recently used catalog, except the use of the "Catalog Settings / Metadata / Automatically write changes into XMP" function. This means that I always have to go there to switch it on… Not even a question is raised by LR whether I want to change anything in comparison with the settings of the recently used catalog…
    3. Catalog functions missing from my workflow
    Unfortunately the above described abandoning of catalogs has at least two serious drawbacks:
    I miss the classification features (rating, keywords, collections, etc.) Anyway, these functions would be really meaningful for me only if covering all my existing photos that would require going back to 41k images to classify them. In addition, keeping all the pictures in one catalog would result in an extremely large catalog file, almost surely guaranteeing regular failures. Beyond, due to the speed problem tolerable conditions could be established only by keeping the original NEF files on the SSD, which is out of the question. Generating several ‘partial’ catalogs could somewhat circumvent this trap, but it would require presorting the photos (e.g. by capture time or subject) and by doing this I would lose the essence of having a single catalog, covering all my photos.
    Question 5: Is it the right assumption that storing only some parts (e.g. the classification-related data) of catalog files is impossible? My understanding is that either I keep the whole catalog file (with the outdated historical data of all my ‘ancient’ actions) or abandon it.
    Question 6: If such ‘cherry-picking’ is facilitated after all: Can you suggest any pragmatic description of the potential (competing) ways of categorizing images efficiently, comparing them along the pros and contras?
    I also lose the virtual copies. Anyway, I am confused regarding the actual storage of the retouching-related data of virtual copies. In some websites one can find relatively old posts, stating that the XMP file contains all information about modifying/adjusting both the original photo and its virtual copy/copies. However, when fiddling with a virtual copy I cannot see any change in the size of the associated XMP file. In addition, when I copy the original NEF file and its XMP file, rename them, and import these derivative files, only the retouched original image comes up – I cannot see any virtual copy. This suggests that the XMP file does not contain information on the virtual copy/copies…
    For this reason whenever multiple versions seem to be reasonable, I create renamed version(s) of the same NEF+XMP files, import them, and make some changes in their settings. I know, this is far not a sophisticated solution…
    Question 7: Where and how the settings of virtual copies are stored?
    Question 8: Is it possible to generate separate XMP files for both the originally retouched image and its virtual copy/copies and to make them recognized by LR when importing them into a new catalog?

    A part of my problems may be caused by selecting LR for a challenging private project, where image retouching activities result in bigger than average volume of adjustment data. Consequently, the catalog file becomes huge and vulnerable.
    While I understand that something has gone wrong for you, causing Lightroom to be slow and unstable, I think you are combining many unrelated ideas into a single concept, and winding up with a mistaken idea. Just because you project is challenging does not mean Lightroom is unsuitable. A bigger than average volume of adjustment data will make the catalog larger (I don't know about "huge"), but I doubt bigger by itself will make the catalog "vulnerable".
    The causes of instability and crashes may have NOTHING to do with catalog size. Of course, the cause MAY have everything to do with catalog size. I just don't think you are coming to the right conclusion, as in my experience size of catalog and stability issues are unrelated.
    2. I may be wrong, but in my experience the size of the RAW file may significantly blow up the amount of retouching-related data.
    Your experience is your experience, and my experience is different. I want to state clearly that you can have pretty big RAW files that have different content and not require significant amounts of retouching. It's not the size of the RAW that determines the amount of touchup, it is the content and the eye of the user. Furthermore, item 2 was related to image size, and now you have changed the meaning of number 2 from image size to the amount of retouching required. So, what is your point? Lots of retouching blows up the amount of retouching data that needs to be stored? Yeah, I agree.
    When creating the catalog for the 1500 NEF files (21 GB), the starting size of the catalog file was around 1 GB. This must have included all classification-related information (the meaningful part of which was practically nothing, since I had not used rating, classification, or collections). By the time of the crash half of the files had been processed, so the actual retouching-related data (that should have been converted properly into the XMP files) might be only around 500 MB. Consequently, probably 22.5 GB out of the 24 GB of the catalog file contained historical information
    I don't know exactly what you do to touch up your photos, I can't imagine how you come up with the size should be around 500MB. But again, to you this problem is entirely caused by the size of the catalog, and I don't think it is. Now, having said that, some of your problem with slowness may indeed be related to the amount of touch-up that you are doing. Lightroom is known to slow down if you do lots of spot removal and lots of brushing, and then you may be better off doing this type of touch-up in Photoshop. Again, just to be 100% clear, the problem is not "size of catalog", the problem is you are doing so many adjustments on a single photo. You could have a catalog that is just as large, (i.e. that has lots more photos with few adjustments) and I would expect it to run a lot faster than what you are experiencing.
    So to sum up, you seem to be implying that slowness and catalog instability are the same issue, and I don't buy it. You seem to be implying that slowness and instability are both caused by the size of the catalog, and I don't buy that either.
    Re-reading your original post, you are putting the backups on the SSD, the same disk as the working catalog? This is a very poor practice, you need to put your backups on a different physical disk. That alone might help your space issues on the SSD.

  • Adobe Photoshop Album 2.0 to Adobe Photoshop Elements 12 Organizer catalog conversion

    I'm having trouble converting Adobe Photoshop Album 2.0 catalog to Adobe Photoshop Elements 12 Organizer.  I get a Conversion Failed error which tells me to repair with the program that created it.  I have tried several things including deleting all .avi files from the catalog, deleting references to missing files and backing up then trying to convert from an external HD.  I'm running Vista Home Premium on a HP laptop.  The Organizer optimize and repair don't seem to help in this case.
    Does anyone have any history with this or advice?

    Please refer to following KB article which deals with catalog conversion failures:-
    http://helpx.adobe.com/elements-organizer/kb/elements-catalog-conversion-fails.html

  • Conversion problem in PURCHASE ORDER

    Hi all,
       wrong conversion was done in Quantities/Weights tab of item overview during creation of Purchase Order,instead of putting order unit  " 1 tonne  = 1000kg" it was wrongly fix as "5 tonne = 4536kg",  the order has been receive and issue , but during stock taking this conversion problem is giving wrong Quantity for the material in MB5B . Pls what can i do to resolve this.

    Hi
    If stock exists  then kindly do the reverse process as below
    1.Cancel material docuemt---MBST (Material document no and fiscial year)
    2.Delete the P.O line items --Me22n
    3.Enter the fresh line items in the same P.O
    If partial stock Exists then do the Physical inventory process to adjust the Stock
    Regards
    Damu

  • How to debug file content conversion problems?

    Hi,
    I'm trying to debug a file content conversion problem.  I'm mapping a few nodes in an IDOC to a file of fixed length fields.  I'm using the "<Node A>.fieldFixedLengths", "<Node B>.fieldFixedLengths", "<Node C>.fieldFixedLengths", etc. parameters to specify the fixed length records.
    However, a certain node (for e.g. Node B) is causing a problem and if it is present in the IDOC, the output file does not get created.  Upon checking the XI monitor, I notice that the file gets mapped correctly and thus the problem lies when the file adapter does the file content conversion.  How do I debug this because there is no descriptive error in the XI log?  If this node is not present, the file gets generated fine.
    Thanks,
    Basant Gupta

    Hi,
    If your SXMB_MONI shows, success status, then go to RWB->Message Monitoring->Message display tool and then check Audit log for the analysis,
    So it wil help you debug the situation.
    If there is no error, then check RWB->Component Monitoring->Adapter Monitoring for you file communciation channel..
    /people/michal.krawczyk2/blog/2005/01/02/simple-adapter-and-message-monitoring
    Regards,
    Moorthy

  • PSE10 Catalog Conversion from Windows XP to Windows 7-64

    Hi,
    I have a catalog conversion issue when moving from Windows XP to Windows 7-64 while at the same time upgrading from PSE8 to PSE10.
    All my photos on the Windows XP machine were in the following folder:  
    C:\Documents and Settings\My Name\My Documents\My Pictures
    Files were transfered across the network using Windows Easy Transfer to the new computer. I then installed PSE8 and was able to see my photo folders in the Organizer Folder View at the path listed above.
    After installing PSE10 the location of my photo files remain in the same folder but are not accessible through Folder View in the Organizer.  I can see all the photos in Date View.
    In other words, the PSE10 folder view doesn't show the old "Documents and Settings" path under Computer\C: even if I set the View to show Hidden files.  It does, however, show the entire folder path under "C:\Users\My Name\Pictures" but none of the folders are marked as being included in the Organizer.
    There seems to be a Windows alias between "C:\Documents and Settings\My Name\My Documents\My Pictures"   and   "C:\Users\My Name\Pictures"   but the Catalog is not picking it up.
    Any ideas?
    Thanks,
    Paul

    Hi,
    You just hit on something there.  After opening the timeline I clicked on one of the bars and Voila! a group of folders appeared in the folder view containing all of my photo folders.  Seems there was a "Documents and Settings" folder INSIDE the  Pictures folder at the same level as all the individual photo folders.
    Strange thing...drilling down into the "my pictures" folders ALL folders are marked as having photos in the organizer even though many are not part of the database. 
    So, here's the path:
    C:\Users\Paul Valentine\Pictures\Documents and Settings\Paul Valentine\My Documents\My Pictures\
    To add insult to injury, every time you click on the "+" sign to expand a folder, PSE10 decides you want to go all the way back to the top of the folder list so you then have to navigate back to the folder you just expanded.  That's a real pain.
    So, is there any good way to get things moved "back" to the proper location?
    BTW, Thanks for all the great help...and Ken I might just have to try the repair technique if I continue to hit the brick wall...
    Paul

  • Why did adobe photoshop elements 13 stop catalog conversion of elements 12?

    I loaded my new adobe photoshop elements 13 fine. but when I told it to convert my 12 catalog to 13 it looked like it was converting up to 100% then it came up with catalog conversion error

    If you open the Organizer and go to Edit>Preferences>Camera or Card Reader, do you have Auto Launch Adobe Photo Downloader on Device Connect checked?
    Try checking that if you don't.

  • Oracle to Mysql character set conversion problem!!! PLZ IGNORE

    Hi Experts,
    I have created a database link from Oracle 10g to Mysql 5.
    I have installed Oracle Gateway 11g for this purpose.
    When i retreive the data from sql plus the text is displayed as question marks.
    Oracle 10g Database character set is WE8MSWIN1252
    Mysql character set --->latin1
    Character set of ODBC connector for mysql is  latin7
    Character set in the parameter file of HS folder is WE8MSWIN1252When i retrieve data from sql developer the text is fine(as i think it directly takes the character set of target) but
    when i login from sqlplus i get question marks!
    I have another post in Heterogeneous Connectivity forum
    Re: Oracle to Mysql character set conversion problem!!! PLZ HELP
    Kindly update your comments there,
    @@@@@@@@@@@@@@2
    Appreciate your help,
    regards
    Edited by: user10243788 on Apr 21, 2010 3:25 AM

    It is OK to post a globalization-related question in this forum in addition to the forum pertaining to the main technology. Not all experts follow all possible forums on OTN. Of course, you should cross-link the posts to let people merge the answers.
    Regarding the problem itself, make sure that SQL*Plus has the right NLS_LANG setting in the environment. On Windows, in the Command Prompt:
    C:\> set NLS_LANG=.WE8PC850
    C:\> sqlplus ...On Unix:
    $ setenv NLS_LANG .WE8ISO8859P1   (or NLS_LANG=.WE8ISO8859P1; export NLS_LANG)
    $ sqlplus ...-- Sergiusz

  • Codepage conversion problem

    Hello,
      In a DB to DB scenario, I am getting this error "Error: Unexpected error converting database resultset to XML, codepage conversion problem?" on the side of the sender adapter. I am not able to see any messages or trace in IE-Monitoring. Is there any log wherein I can find out the problem as to where it is occuring?
    Regards,
    Sanjay

    Hi Sanjay,
    The JDBC sender adapter returns the rows selected from the database in the follwoing format.
    <resultset>
    <row>
    <column-name1>column-value</ column-name1>
    <column-name2>column-value</ column-name2>
    <column-name3>column-value</ column-name3>
    </row>
    <row>
    <column-name1>column-value</ column-name1>
    <column-name2>column-value</ column-name2>
    <column-name3>column-value</ column-name3>
    </row>
    </resultset>
    This error occurs , when the source datatype you have created for the JDBC adapter does not match with this format. I would suggest that you check the source format along with the occurence of your field.
    Regards,
    Bhavesh

  • Raw conversion problem

    I have Photoshop Elements 6 (Camera Raw 4.2) and a Nikon D7000 (Camera Raw 6.3 minimum).  I am using DNG converter 8.1 to create DNG files, but these still will not open in Elements.  I am selecting compatibility of Camera Raw 4.1 in the conversion program.  What else can I do?

    Sorry it took me a long time to reply.  If I send to dropbox (which I can), can I restrict the images to specific email addresses, or will it be accessible to anyone?  Not that I care about the image particularly, as it was only a test.
    Once I have an idea of this, I will do a final test & send the data to dropbox.
    Date: Wed, 19 Mar 2014 15:12:51 -0700
    From: [email protected]
    To: [email protected]
    Subject: Raw conversion problem
        Re: Raw conversion problem
        created by ssprengel in Photoshop Elements - View the full discussion
    It seems like you're doing everything that you're supposed to be doing, and it is not working.  I don't have an explanation why that is, but can you share an original NEF and its DNG via www.dropbox.com or similar and others can test with a newer version of ACR to make sure there isn't something corrupted wtih the files.
         Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6225513#6225513
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6225513#6225513
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6225513#6225513. In the Actions box on the right, click the Stop Email Notifications link.
               Start a new discussion in Photoshop Elements at Adobe Community
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Journals conversion problem.

    Hello,
    We have a currency conversion problem with the journals table.
    Steps:
    1.- We insert a journal in Local Currency (LC) with the journals functionality. Both convert at average rate (for example), so when we run currency conversion rules the value is converted in Legalapp application, but not in Journal Table. So if the users or auditors need to see all the journals in EUR is not possible to extract with the journals reports.
    2.- Also we have the problem when we apply the carry forward rules for the next year, and the RE-Open functionality. Example, the flow of the year N applies at average rate, when we make the carry forward rule it goes to Opening Balance flow, and this opening balance doesn´t have currency conversion rule (AS-IS)(we cannot use an OPEAVG rule because we need the historical value in the opening balance flow). So we lose the EUR position value because we don´t have a journal to apply the RE-OPEN functionality.
    3.- We have the possibility of inserting the Journal in LC and EUR (Group Currency) also, but here you are obligating to the users to manually convert the values of each account of each journal, and can be mistakes of the value that the user insert in the Journal Entry, with the values of the application (converted with the currency conversion functionality).
    Do you know how can we solve this error?
    Regards,

    Hi,
    1. Journal tables contains just values for LC and only the posted journals are converted.
    The Corrency conversion will be applied just for journal posted not for all journals.
    You can see the value reflected into application just checking the the reports for special Data Source used by journal.
    Journal module is used for adjustment which means the auditors can see the adjustment into local cuurency and just the final value posted. The rest of journal not posted has no importance because they don't have any impact for database values.
    2. I don't think I understand the point which means I will leave other people to help ou with this poin
    3. I don't understand why you have to run Currency Conversion manually.
    When you input the journal you will execute default logic or you can execute journal.lgx logic.
    In any of these module if you place currency translation you will have your figures automat converted.
    Regards
    Sorin Radulescu
    Edited by: Sorin Radulescu on Dec 2, 2009 3:35 PM

  • Lightroom catalog permission problem!

    Hi everyone,
    please help me solve this problem. I reinstall OS X last night to new Yosemite. I did clean install. I made TM backup of my old OS X on external LaCie hdd. I copied my catalog from the backup into my pictures folder on an internal hdd. When I tried to open it this message pops up "Lightroom cannot use the catalog named “Lightroom 5 Catalog” because it is not writable and cannot be opened.". Just to be clear the "get info" permissions are set for "Me" R/W. I don't have any different file inside the folder "pictures" only my catalog.ircat. I can't open original file from the LaCie backup, also permission problem. Thanks for help.

    it's all ok. The file for some reason have some info written about the owner. I did change that but it does not matter and still don't work. If I want rename the file then I have to put the password and that is why LR can't work with it. I found the solution already (after 5 hours searching the internet) This helped me http://backdrift.org/fixing-mac-osx-file-permissions-and-acls-from-the-command-line I used sudo chmod -N /here is path to the file/ and enter. This solved all my trouble and I can open the catalog without problems.

  • Dreamweaver cc html entity conversion problem in mac -NO utf-8 related answer please

    I probably am fighting against a bug existing in DW for a while, and i'm really on the edge of bursting out! 
    Here are the specifications:
    Dreamweaver CC from creative cloud (also tested w/ CS5.5 too) installed on mac, OS and DW user interfaces are english, and on mac turkish keyboard layout is also installed.
    I have been using DW for maybe 15 years, since it was macromedia.. But was always on windows. This is the first time I use it on mac. Here is my problem step by step:
    1- Dreamweaver > Pereferences > New Document > Default Encoding: Western (ISO Latin 1) (NOT UTF-8 PLEASE, IT KEEPS THE CHARS UNCHANGED, ISO LATIN1 IS IMPORTANT)
    2- Go to Design View,
    3- There are 6 special characters in Turkish (times 2 for the caps versions of course), type:
    ĞÜŞİÖÇğüşıöç
    4- Go back to code view, what i should have seen was:
    &#286;&Uuml;&#350;&#304;&Ouml;&Ccedil;&#287;&uuml;&#351;&#305;&ouml;&ccedil;
    But I see:
    Ğ&Uuml;Şİ&Ouml;&Ccedil;ğ&uuml;şı&ouml;&ccedil;
    There are 3 chars (and capital versions) NOT converted to html entity at all. Which were: ĞŞİğşı
    But I should have seen them as: &#286;&#350;&#304;&#287;&#351;&#305;
    Any help would be appreciated, I do not want to leave my old friend DW just because of a weird conversion problem...

    Ok, when you look at the code view, what do you see exactly?
    do you see unconverted
    ĞÜŞİÖÇğüşıöç
    or converted
    &#286;&Uuml;&#350;&#304;&Ouml;&Ccedil;&#287;&uuml;&#351;&#305;&ouml;&ccedil;
    Here is one of my reasons:
    I sometimes create newsletters in turkish for my customers, and the html files i prepare are sent to customers attached as inline through various versions of outlook or thunderbird, or through i completely different email sender company (none is sent by me, i only create the html file). And most of the time the headers and some coding are cut off from the code when used to send as newsletter, and i have no control at all on it. so i have to create absolute correct viewed/rendered html files since i have no control at all on which sending method will be used or which os or browser or mail system will be used to open it...

  • PDF Conversion problem

    Hi ABAPers
    While sending smartform as a mail attachment(PDF Format) i am facing problem.
    While opening the PDF attachment in SOST (T-code), It shows a error pop up.(I.e., Conversion Problem in PDF). Some pages are getting opened as a blank page and some are not getting opened.
    What may be the prolem.
    Please help Me out ............
    But it works properly in IDES version.
    In IDES i have ADOBE 5.0 Version, In Live server it is ADOBE 6.0 ,7.0.

    Hi,
    Thanks for your feedback
    There is no problem in the coding , is there any thing we have to do in configuration level regarding PDF ?????
    *& Report  ZVNPAML
    REPORT  zvnpaml.
    TABLES: somlrec90.
    DATA: it_zvnpa  TYPE TABLE OF zvnpa,
          it_zvnpa1 TYPE TABLE OF zvnpa,
          wa_zvnpa  TYPE zvnpa,
          it_head   TYPE TABLE OF zvnpa,
          it_head1  TYPE TABLE OF zvnpa,
          wa_head   TYPE zvnpa,
          wa_head1  TYPE zvnpa,
          fmname    TYPE rs38l_fnam,
          tot       TYPE zvnpa-wrshb,
          otfout    TYPE ssfcrescl,
         outopt   type SSFCRESOP,
          pdftab    TYPE TABLE OF tline WITH HEADER LINE,
          datab     TYPE TABLE OF itcoo WITH HEADER LINE,
          conpar    TYPE ssfctrlop,
          mailrec   TYPE swotobjid,
          outopt    TYPE ssfcompop,
          jobopt    TYPE ssfcresop,
          jobout    TYPE ssfcrescl,
          w_return  TYPE ssfcrescl,
          it_otf    TYPE itcoo OCCURS 0 WITH HEADER LINE,
          binsz     LIKE sood-objlen,
          i_tline   TYPE TABLE OF tline WITH HEADER LINE,
          wa_buffer TYPE string,"To convert from 132 to 255
          i_record  LIKE solisti1 OCCURS 0 WITH HEADER LINE.
    DATA: wa_doc_data   TYPE sodocchgi1,
          it_pack       TYPE TABLE OF sopcklsti1,
          wa_pack       TYPE sopcklsti1,
          it_mailhead   TYPE TABLE OF solisti1,   " OCCURS 1 WITH HEADER LINE,
          wa_mailhead   TYPE solisti1,
          it_mailbody   TYPE TABLE OF solisti1,      "  OCCURS 0 WITH HEADER LINE,
          wa_mailbody   TYPE solisti1,
          it_receiverid TYPE TABLE OF somlrec90,  " OCCURS 10 WITH HEADER LINE.
          wa_receiverid TYPE somlrec90,
          it_attach     LIKE solisti1 OCCURS 0 WITH HEADER LINE,
         wa_attach     TYPE solisti1,
          lncnt         TYPE i.
    DATA: lv_spool TYPE tsp01-rqident,
          wa_line  TYPE tsp01-rqident,
          it_pdf_output TYPE TABLE OF tline.
    SELECTION-SCREEN BEGIN OF BLOCK vendor WITH FRAME TITLE text-w03.
    *PARAMETERS: pa_lifnr TYPE lfa1-lifnr,
               pa_bukrs TYPE zvnpa-bukrs,
    PARAMETERS:     pa_augdt TYPE zvnpa-augdt.
    SELECT-OPTIONS: pa_mail FOR somlrec90-receiver NO INTERVALS.
    SELECTION-SCREEN END OF BLOCK vendor.
    SELECT * FROM zvnpa INTO CORRESPONDING FIELDS OF TABLE it_zvnpa1
                        WHERE augdt =  pa_augdt
                        AND   bukrs =  '2000'
                        AND   flag  <> 'X'.
                                                 konto = pa_lifnr AND
                                                 bukrs = pa_bukrs AND
    IF it_zvnpa1 IS NOT INITIAL.
      SORT it_zvnpa1 BY konto.
      LOOP AT it_zvnpa1 INTO wa_zvnpa.
        APPEND wa_zvnpa TO it_zvnpa.
        CLEAR: wa_zvnpa.
        AT END OF konto.
          SORT it_zvnpa BY ttref augbl wrshb shkzg.
    *it_head[] = it_zvnpa[].
          LOOP AT it_zvnpa INTO wa_zvnpa WHERE shkzg = 'S'.
            APPEND wa_zvnpa TO it_head1.
            CLEAR: wa_zvnpa.
          ENDLOOP.
    *delete adjacent duplicates from it_head comparing ttref.
          SORT it_head1 BY ttref augbl wrshb shkzg.
           LOOP AT it_head1 INTO wa_head1.
            tot = tot + wa_head1-wrshb.
            wa_head = wa_head1.
            AT END OF ttref.
              wa_head-wrshb = tot.
              APPEND wa_head TO it_head.
              CLEAR: wa_head,tot.
            ENDAT.
            CLEAR: wa_head1.
          ENDLOOP.
          SORT it_head BY ttref augbl wrshb shkzg.
          CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
            EXPORTING
              formname = 'ZVNPASF'
            IMPORTING
              fm_name  = fmname.
          conpar-no_dialog = 'X'.
          conpar-getotf    = 'X'.
          outopt-tddest    = 'LOCL'.
          outopt-urlcall   = fmname.
          outopt-tdnoprev  = 'X'.
         outopt-tdnewid   = 'X'.
          CALL FUNCTION fmname
           EXPORTING
      ARCHIVE_INDEX              =
      ARCHIVE_INDEX_TAB          =
      ARCHIVE_PARAMETERS         =
              control_parameters         = conpar
      MAIL_APPL_OBJ              =
      MAIL_RECIPIENT             =
      MAIL_SENDER                =
              output_options             = outopt
              user_settings              = ' '
            IMPORTING
      DOCUMENT_OUTPUT_INFO       =
              job_output_info            = w_return
      JOB_OUTPUT_OPTIONS         =
            TABLES
              it_zvnpa                   = it_zvnpa
              it_head                    = it_head.
         READ TABLE w_return-spoolids INTO wa_line INDEX 1.
         IF sy-subrc = 0.
           lv_spool = wa_line.
           CALL FUNCTION 'CONVERT_OTFSPOOLJOB_2_PDF'
             EXPORTING
               src_spoolid              = lv_spool
               no_dialog                = ' '
               dst_device               = 'LOCL'
             TABLES
               pdf                      = it_pdf_output
             EXCEPTIONS
               err_no_otf_spooljob      = 1
               err_no_spooljob          = 2
               err_no_permission        = 3
               err_conv_not_possible    = 4
               err_bad_dstdevice        = 5
               user_cancelled           = 6
               err_spoolerror           = 7
               err_temseerror           = 8
               err_btcjob_open_failed   = 9
               err_btcjob_submit_failed = 10
               err_btcjob_close_failed  = 11.
          it_otf[] = w_return-otfdata[].
          IF it_otf[] IS NOT INITIAL.
            CALL FUNCTION 'CONVERT_OTF'
              EXPORTING
                format        = 'PDF'
                max_linewidth = 132
              IMPORTING
                bin_filesize  = binsz
              TABLES
                otf           = it_otf
                lines         = i_tline.
            LOOP AT i_tline.
              TRANSLATE i_tline USING ' ~'.
              CONCATENATE wa_buffer i_tline INTO wa_buffer.
            ENDLOOP.
            TRANSLATE wa_buffer USING '~ '.
            DO.
              i_record = wa_buffer.
              APPEND i_record.
              SHIFT wa_buffer LEFT BY 255 PLACES.
              IF wa_buffer IS INITIAL.
                EXIT.
              ENDIF.
            ENDDO.
          ENDIF.
          IF i_record[] IS NOT INITIAL.
            it_attach[] = i_record[].
           CALL FUNCTION 'SX_TABLE_LINE_WIDTH_CHANGE'
            EXPORTING
              LINE_WIDTH_SRC                    = '132'
              LINE_WIDTH_DST                    = '255'
              TRANSFER_BIN                      = ' '
             TABLES
               content_in                        = i_tline[]
               content_out                       = IT_ATTACH[]
            EXCEPTIONS
              ERR_LINE_WIDTH_SRC_TOO_LONG       = 1
              ERR_LINE_WIDTH_DST_TOO_LONG       = 2
              ERR_CONV_FAILED                   = 3
              OTHERS                            = 4
           IF sy-subrc <> 0.
            MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
           ENDIF.
           it_attach[] = w_return-otfdata[].
           IF it_pdf_output[] IS NOT INITIAL.
             it_attach[] = it_pdf_output[].
            wa_mailbody-line = 'Dear Sir / Madam,'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'Please be informed that we have remitted the payment towards your outstanding bills as per the attachment:'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = ' '.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = ' '.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'Best Regards,'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'Mary. G '.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'Finance department'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'Intimate Fashions (I) Pvt Ltd'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = ' '.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'Please do not print this email unless it is absolutely necessary.  Become environment friendly.'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'E-MAIL DISCLAIMER.'.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'If you are not the addressee of this mail, please delete this. Intimate Fashions does not accept any liability on the improper usage of this mail. It may also be legally '.
            APPEND wa_mailbody TO it_mailbody.
            wa_mailbody-line = 'privileged. Internet communications cannot be guaranteed to be timely, secure or virus free'.
            APPEND wa_mailbody TO it_mailbody.
            DESCRIBE  TABLE it_mailbody LINES lncnt.
            wa_doc_data-obj_descr  = 'Remittance details - Brunet'.
            wa_doc_data-expiry_dat = sy-datum + 10.
            wa_doc_data-obj_name   = 'TRIAL'.
            wa_doc_data-sensitivty = 'F'.
            wa_doc_data-doc_size   = lncnt * 255.
            CLEAR wa_pack.
            CLEAR wa_pack-transf_bin.
            wa_pack-doc_type   = 'RAW'.
             wa_pack-transf_bin = ' '.
            wa_pack-head_start = 1.
            wa_pack-head_num   = 0.
            wa_pack-body_start = 1.
            wa_pack-body_num   = lncnt.
             wa_pack-doc_size   = lncnt * 255.
            APPEND wa_pack TO it_pack.
            CLEAR: lncnt,wa_pack.
            DESCRIBE  TABLE it_attach LINES lncnt.
            wa_pack-transf_bin = 'X'.
            wa_pack-head_start = 1.
            wa_pack-head_num   = 1.
            wa_pack-body_start = 1.
            wa_pack-body_num   = lncnt.
            wa_pack-doc_type   = 'PDF'.
            wa_pack-obj_name   = 'VNPA'.
            CONCATENATE 'Vendor Payment Advice' '.PDF' INTO wa_pack-obj_descr.
             wa_pack-obj_descr  = 'Vendor Payment Advice'.
            READ TABLE it_attach INDEX lncnt.      "INTO WA_ATTACH
             wa_pack-doc_size   = ( lncnt - 1 ) * 255 + STRLEN( it_attach ).
            wa_pack-doc_size   = lncnt * 255.
            APPEND wa_pack TO it_pack.
            CLEAR: lncnt,wa_pack.
            wa_mailhead = 'Vendor Payment Advice'.
            APPEND wa_mailhead TO it_mailhead.
            CLEAR: wa_mailhead.
            LOOP AT pa_mail.
              wa_receiverid-receiver = pa_mail-low.
              wa_receiverid-rec_type = 'U'.
              APPEND wa_receiverid TO it_receiverid.
              CLEAR:wa_receiverid.
            ENDLOOP.
           wa_receiverid-receiver = 'xxxxx'.    "(I have given mail id here )
           wa_receiverid-rec_type = 'U'.
           APPEND wa_receiverid TO it_receiverid.
           wa_receiverid-receiver = 'xxxxx'.    "(I have given mail id here )
           wa_receiverid-rec_type = 'U'.
           APPEND wa_receiverid TO it_receiverid.
           wa_receiverid-receiver = 'xxxxx'.    "(I have given mail id here )
           wa_receiverid-rec_type = 'U'.
           APPEND wa_receiverid TO it_receiverid.
           CLEAR:wa_receiverid,lncnt.
            CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
              EXPORTING
                document_data                    = wa_doc_data
                put_in_outbox                    = 'X'
                commit_work                      = 'X'
           IMPORTING
              SENT_TO_ALL                      =
              NEW_OBJECT_ID                    =
              TABLES
                packing_list                     = it_pack
                object_header                    = it_mailhead
                contents_bin                     = it_attach[]
                contents_txt                     = it_mailbody
                 CONTENTS_HEX                     = it_attach
              OBJECT_PARA                      =
              OBJECT_PARB                      =
                receivers                        = it_receiverid
             EXCEPTIONS
               too_many_receivers               = 1
               document_not_sent                = 2
               document_type_not_exist          = 3
               operation_no_authorization       = 4
               parameter_error                  = 5
               x_error                          = 6
               enqueue_error                    = 7
               OTHERS                           = 8.
             IF sy-subrc = 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              LOOP AT it_zvnpa INTO wa_zvnpa.
                wa_zvnpa-flag = 'X'.
                MODIFY it_zvnpa FROM wa_zvnpa TRANSPORTING flag.
              ENDLOOP.
              MODIFY zvnpa FROM TABLE it_zvnpa.
            ENDIF.
          ENDIF.
          CLEAR: wa_zvnpa,it_zvnpa,it_otf,it_otf[],w_return,lncnt,
                 wa_doc_data,
                 wa_head,it_head,it_head1,
                 i_record,i_record[],
                 i_tline,i_tline[],
                 it_pack,
                 wa_pack,
                 it_mailhead,
                 wa_mailhead,
                 it_mailbody,
                 wa_mailbody,
                 it_receiverid,
                 wa_receiverid,
                 it_attach.
        ENDAT.
      ENDLOOP.
    ENDIF.

Maybe you are looking for