Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Where is the "Import Log File" for PSE 2025?

New Here ,
Feb 25, 2025 Feb 25, 2025

Copy link to clipboard

Copied

Is there a PSE 2025 Import Failure Log, and if so, where is it? Just imported about 40K images to my newly-downloaded product.

 

Unsurprisingly, there were failures.

 

I'd like to review them, more efficiently than I can by scrolling up and down in the small notification window that appears in the application.

 

How can I?

TOPICS
How to , Import and export , Organizer , Problem or error , Windows

Views

81
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guru ,
Feb 26, 2025 Feb 26, 2025

Copy link to clipboard

Copied

You can look at them all day long, however, I think you are setting yourself up for a truckload of frustration-- the error logs can be daunting, and actually contain about 99.98% of info that the average user doesn't need to be bothered with-
 
To access the import failure log for Adobe products, navigate to your computer's application support folder, usually located within the "Adobe" directory, where you'll find log files detailing import attempts, including errors and failures; you can typically open these log files with a text editor to analyze the specific reasons behind import issues within your Adobe software like Photoshop, Premiere Pro, or Lightroom. 
 
Key points about Adobe import failure logs:
  • Location: Depending on your operating system, the log files are usually found in a path similar to: C:\Program Files (x86)\Common Files\Adobe\Installers (Windows) or /Library/Logs/Adobe/Installers (Mac). 
     
  • File format: These log files are usually plain text files with a .log extension. 
     
  • Interpreting the log:
    • Date and Time: Each log entry will be timestamped, allowing you to pinpoint when an import failure occurred. 
       
    • Error codes: Look for specific error codes or messages within the log to identify the cause of the import issue. 
       
    • File details: The log may also include information about the file that failed to import, such as its path and format. 
       
 
How to access and analyze the import failure log:
  1. 1. Open the log file:
    Navigate to the appropriate Adobe installation directory and locate the relevant log file.
  2. 2. Use a text editor:
    Open the log file using a plain text editor like Notepad (Windows) or TextEdit (Mac).
  3. 3. Search for errors:
    Scan the log for keywords like "error," "failed," or "unable" to identify problematic import attempts.
  4. 4. Investigate error details:
    Analyze the specific error messages and associated file information to understand the cause of the import failure. 
     
 
Important considerations:
  • Product-specific logs:
    Different Adobe products might have their own log files specific to import functions. 



Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 26, 2025 Feb 26, 2025

Copy link to clipboard

Copied

Thanks for your detailed response.  I think the key is your last line: "Different Adobe products might have their own log files specific to import functions."  That's the log file I cannot find for Elements Organizer 2025.  I had already found the "install.log" file you mention, and--indeed--it's very confusingly formatted.  However, the events recorded in it seem specific to the install process, and not the import process.

 

When I import to Elements Organizer 2025, a small dialog window appears at the end showing information (5 lines at a time, and I have to scroll right to see the full line each time, for each instance of import failure. (The messages make sense, and are along the lines of "The file already exists in the catalog." "The file is damaged or is in a format that cannot be included in Elements Organizer."  That sort of thing.)  Unfortunately, the path and file name included for each instance is bogus: File name is given each time as "Use" with a sequential number appended, and a path as if the file were in the root directrory.  (As in C:\Use24.ORF, C:\Use25.JPG, C:\Use26.JPG and so on. None of those reflect the real path or file name; I assume the extensions are correct.)

 

I can't select all the text from the window and save the information as a text file.  All I can do is respond OK, at which point that window, and its information which--itself isn't all that helpful because the file names are wrong--disappears.  And it doesn't seem to be found in any file anywhere on the PC. (Windows 11).

 

I did notice the reference to .ORF files being in an unrecognized format, so I searched them out.  I have 69 of them (apparently they're a RAW Olympus format).  So I copied all 69 files into a separate folder, and tried importing just that folder.  Again, the window popped up, this time informing me that 69 files were in a format that could not be included in Organizer 2025, and naming and numbering them C:\Use01.ORF, C:\Use02.ORF, through C:\Use69.ORF.  I searched the PC again, and can find no log file anywhere containing even just this marginally helpful data, and the file names are wrong.

 

Because of the .ORF extension "clue," I can take these 69 files (which I can edit in other applications, and open them up and save them as another file type, and try to import them again.  But some of the files that say they're "damaged or in a format that cannot be included in Elements Organizer" have .JPG extensions.  Even if I were to use the excruciatingly slow procedure of scrolling left and right and up and down through this 5-line modal window, I'd still have no idea which files they are, because the names are recorded incorrectly in the window ("C:\Use02.JPG," "C:\Use03.JPG), and no way of knowing if they might be photos of my late husband or my dead dog, and if I might want to try and correct the problem and import them again.

 

It's inexplicable to me that Adobe doesn't record this data in a useful format and retrievable format, with the correct path and name of the files that failed to import.  I just did this exercise with Excire last week, and it came up with a very nice and readable text file of import log failures and reasons why.  That program has its own idiosyncrasies and some substantial defects, but it does a much better job in this respect than Adobe. 

 

Baffling.   But thanks for trying to help.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 26, 2025 Feb 26, 2025

Copy link to clipboard

Copied

LATEST

The notification window has (hidden) handles in the corners and sides that allow you to drag out the sides of the window so that you can read the full path.  This was introduced a few versions ago.  But I see that (at least in the dark mode of Elements 2025) the handles are not visible.  In any event, click on a corner or middle-side of the window and you will be able to drag it out.

 

Ashampoo_Snap_Wednesday, February 26, 2025_14h33m43s_multi.pngexpand image

 As for your ORF files, have you installed Adobe Camera Raw from the Help menu?  If you have installed it, then what is the model of Olympus camera that is the source of the files?  If it is brand new, there are ways to update the version of Camera Raw to the latest.

 

Also, how are you importing all of the files?  I assume that some were performed through a bulk import.  But did you import any From Camera or Card Reader, using the Adobe Photo Downloader?  If so, show us a screenshot of that dialog when you import the files.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines