PSE 10 Catalog Conversion (from PSE 6) fails

Installed 10, prompted to convert catalog from previous version. All is well so far. Process starts, gets to 34% and hangs. Eventually times out and says conversion failed, that the catalog should be repaired in original app. I repaired in PSE 6 (though it did not say it needed to, did anyway). Then went back to PSE 10. Selected PSE 6 catalog and it completed conversion in 2 seconds 16, 227 photos, I don't think so!) Sure enough no photos came over to PSE 10.
I am now in a state where I can only get to my photos from PSE 10 and can not get the catalog to PSE 10. Please help??

There may be several reasons for this conversion failure, especially from version 6. I had two main catalogs and several smaller ones for projects for friends. Before trying the conversions, I did just like you, a repair and optimize before converting. In most cases, no problems. However I met two different failures.
One was due to the fact I had a couple of pictures in jpeg2000 format. The jpeg2000 format plugin was present in PSE6, not in PSE10.
In that case, instead of asking PSE10 to convert, I did a backup in PSE6 and a restore from PSE10 : bingo, I got a message showing the offending files. So my advice is to use the backup/restore way which does an automatic conversion with less problems.
The second case was on one of my main catalogs, which showed its age, with a lot of transfers between computers via backups on various external disks. I simply used psedbtools to check if something was wrong with my PSE6 catalog. (http://johnrellis.best.vwh.net/psedbtool/).
The result was 4 types of drives errors in the catalog from the 7 shown by John R Ellis... The organizer did handle that perfectly withi PSE6 : I never noticed errors in backup/restore. But as stated in the help documentation, those errors can be very problematic when upgrading to versions above 6.
So my advice now : first try the backup/restore way, then if not successful, install and run psedbtool and report back for more help.

Similar Messages

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

Catalog conversion from PSE Album v2 to v12 isn't working

I've tried all the suggestions of:
     Turning Auto-Reconnect off
     Disable of Auto-Analyzer
     Terminating Auto-Analyzer .exe process in the Task Manager
     Version 2 catalog shows no errors during recovery process
     There are no missing or unconnected files in version 2
Version 2 of PS Album works fine. When attempting to convert the catalog to version 12 it consistantly fails at 14%.
I have over 3700 pictures in the v2 album that I would rather not load from scratch into v12.
Any suggestions would be greatly appreciated.

Find all Missing Files, and either try to reconnect or delete from catalog.
Repair and Optimize catalog.
Then try and convert again.
Cheers,
Neale
Insanity is hereditary, you get it from your children
If this post or another user's post resolves the original issue, please mark the posts as correct and/or helpful accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks.

Lost tags in catalog conversion

In a catalog conversion from PsE 6 to PsE 10 all tags have lost their connections to the actual files: What have I done wrong and how can I solve this issue?

Which tags? Can you please explain a bit more?
Are the tags imported correctly? You mean any search you make with tags shows you empty results?
Thanks
Andaleeb

Keyword exporting bug also impacts catalogs imported from PSE 6

Hi,
I haven't seen any mention of it, but the keyword exporting bug reported for catalogs imported from LR 1.x also impacts catalogs imported from Photoshop Elements 6. i.e. all Keywords imported from my PSE 6 catalog have "Include in export", "Export Containing Keywords", and "Export Synonyms" properties set to false.
I've reported the bug, but as it seems the same as described in KB 405074 (and more importantly, its fix works for formerly PSE catalogs as well!), I'm sure it will be fixed in the next update.
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405074&sliceId=2
Thanks,
Matt

Hi Brian,
When I installed the trial for LR2 I was asked whether I wanted to upgrade my existing PSE6 catalog.
Screenshot of this can be found here: http://dawsons.id.au/temp/pse6-to-lr2-catalog.png
That's it. I haven't imported any keywords via any other method.
Thanks,
Matt
PS I'm impressed with the level of Lightroom team involvement in these forums. I've been a PSE user for at least 5 years and have never received feedback from that team re posts/support calls/feature request/bug reports. I've been a LR user for about two weeks and I've already had Tom and yourself reply to my posts. You've got to be happy with that!

Record 1 :Time conversion from 0CALDAY to 0FISCPER (fiscal year A1 ) failed

Get red error when loading Delta data and the red error is:
Record 1 :Time conversion from 0CALDAY to 0FISCPER (fiscal year A1 ) failed with value 20060426
We went to RSA1 -> Source Systems page, right click on the source system, choose Transfer Global Settings, check "Fiscal year variants" and check "Rebuild tables" and then run it twice, but still not helpful that we always get the above red error!
Any idea?
Thanks

hi Anurag,
You are right that run OB29 on BW, find there is no any period entry for variant A1. Since all the variant should come from R3 by run "Global Transfer Settings" on the source system, I run OB29 on R3 and find the same thing that there is no any period entry for fiscal year variant A1. I will go ahead to ask R3 people to correct it on R3, then conduct the "Global Transfer Settings".
Thanks

Error 3 in Update(The Conversion from 0CALDAY to 0FISCPER failed)

Hi Guyz....
Seriously struck with this issue while loading data into 0PP_C02 using the D.S- 2LIS_04_P_MATNR. I've been getting the error "Time Conversion from 0CALDAY to 0FISCPER (Fiscal Year) Failed... and at update rule I've been getting the error "Error 3 in Update"
I've searched almost all the posts- alas, all are unanswered.
Can anyone please provide me the right soultion...?
Thanks,
Regards,
G!

Hi Gautam,
For converting calday to fiscal period, you need to have fiscal variant and also entries in Table T009B for this fiscal variant.
1) Check whether you have company code populated for all records.
2) Please check whether you have fiscal variant maintained in the company code master data.
3) Check whether you have T009B table maintained.
If not this can be transferred in source system -> Global settings.
Hope this helps.
Thanks,
Krishnan

When restoring backup catalog conversion fails.

when restoring backup catalog conversion fails.

HI,
Could you please try the steps mentioned on the link http://helpx.adobe.com/photoshop-elements/kb/troubleshoot-catalog-backup-conversion-elemen ts.html
-Harshit yadav

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.

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...

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

Error while loading : Time conversion from 0CALDAY to 0FISCPER

Hi ,
I get the following error when loading to an ODs .
My 0FISCPER is mapped to one of the date fields from the extractor (Document date) and also Have 0FISCVARNT as part of data fields .
" Time conversion from 0CALDAY to 0FISCPER (fiscal year ) failed with value 20060405 " .
thanks .

Hello CG
Please refere this forum
Time conversion problem
Thanks
Chandran

Conversion from BO 5.1.9 Deski to BO XI 3.1 SP3 Webi

Hi Everyone,
As part of of our project, we are executing a BO upgrade project and have undertaken BO report migration and conversion from deskI in BO 5.1.9 to WebI in BO XI 3.1. The conversion of reports was assumed to be carried out through the report conversion tool (RCT) of BO XI 3.1 SP3. However, RCT has failed in converting all deskI reports to WebI.
Hence, we are seeking your help & assistance in finding out, the optimal way of resolving the problem. Can you please indicate:
1. Is there any hotfix/patch that SAP can provide for making RCT more robust resulting in elimination of conversion errors/influence the success rate of report conversion?
2. If no hotfix for RCT is present, can we get quick answers from SAP through the alliance for resolution of these report conversion errors? We have received the below errors when we made an attempt at report conversion
1.Breaks in Web Intelligence can only be set on objects present in the block
2 Objects cannot be hidden in Web Intelligence documents
3.Page setup options are not implemented in Web Intelligence (First page number, page order, scale, Fit to N pages)
4.Across options for crosstabs are not available in Web Intelligence -5.Detail variables have no associated dimension in Web Intelligence 6.Conditional or permanent Hide Header not available in Web Intelligence 7.Function not available in Web Intelligence
8.The formula of a global filter in Desktop Intelligence cannot be migrated into a Web Intelligence report filter
9.A formula from a Desktop Intelligence block filter cannot be migrated into a Web Intelligence block filter
10.Unsupported 'Do not retrieve data' option
11.Conditional or permanant Hide Footer does not exist in Web Intelligence
12.Keyword not available in Web Intelligence
13.Unsupported Data Provider
Anticipating your help and cooperation at the earliest. Please let me know if you need any more information.
Many Thanks & Regards,
Sandeep

Report Conversion Tool cannot guarantee 100% conversion rates. It's imposible due to functionality differences that still exist between Full Client/Deski and Webi documents.
If you have a report that won't convert - you will have to manualy re-create it in Webi. It'll show you if design you use is even possible there or not.
As to the list of errors you provided - each one has to be reviewed and investigated to see why it happens.
Like #3 - might be due to the fact that Webi has no page options or #13 might indicate unsupported data provider, lust like the error says.
You might want to open a support Incident to properly investigate all the errors you received, but keep in mind - 100% conversion is not possible unless you use simplest reports.

Struts/ADF/Toplink conversion from 10.1.2 to 10.1.3

Hi. We have a J2EE application based on Struts/ADF/Toplink.
We just let the JDeveloper migrate the whole application itself.
We solved a few minor problems, but now we have the greater one:
- we have in domain classes some getX...(), setX...() methods, intended for example
for getting attributes of nested objects or for conversion from String to Date.
In older version, when you had some getXSomeAtr() method in domain class, the attribute
XSomeAttr was automatically generated into Data Control.
In newer version it's not! If you want the attribute to be in data control, you must
have an private attribute XSomeAtr declared in domain class.
Example - we have these attibutes (first two has their own getters and setters and are
mapped in toplink, the third is unmapped)
private Date datum;
private String nazev;
private String XDatumAsDate;
and methods
public String getXDatumAsDate() {
return OurUtils.dateToStringAsDate(getDatum());
public void setXDatumAsDate(String datum) throws ParseException{
Date d = OurUtils.StringToDateAsDate(datum);
setDatum(d);
And the form look like this
<html:text property="XDatumAsDate" .../>
<html:text property="nazev" .../>
Reading is ok, but attempt to modify date in input field ends with
"JBO-35009: Setting attribute for XDatumAsDate in object methodRSICollection failed"
Are we doing something wrong ? We just need to have the date entering under our control and
be able to enter dates in various formats.
Thanks in advance for any comments.

I compared the both old and new data control xml files and found the difference. The previous attribute descriptor has IsUpdateable="true" but the new has IsUpdateable="0".
Manually changing won't help - data control generation of any class regenerates all data controls and puts back IsUpdateable="0". I'm stuck now.

IAS 6 Conversion from NAS 4.0 - Tools

Hi gang,
Has anyone used the IAS-supplied conversion utilities to convert JSPs from
0.92 to 1.1?
We have a number of included/imported JSP for things like headers and
footers, and the conversion tool doesn't seem to like that. This should
work; this sort of thing is very common practice.
convert2jsp11 -ap c:\iplanet\ias6\ias\APPS catalog\customization\gettext.jsp
There seems to be an issue with the AppPath (specified by "-ap" above)
confusing the utility when it tries to process a JSP that imports/includes
another one. In the example above, I get a FileNotFoundException on
"c:\iplanet\ias6\ias\APPS\catalog\customization\catalog\includes\common\foot
_ias_included.jsp"
The "includes/common" folder is under "catalog", but from the message I get
it looks like the utility can't deal the fact that someone, somewhere, might
actually import/include something from a different directory.
Anybody have any ideas for fixing this? I have over 1500 JSPs!! Ugh.
Thanks, in advance.
Scott

hi,
Make sure that your network uses DNS naming.
This error occurs when a machine is not correctly configured to use DNS naming. The default fully qualified host and domain name presented during installation is not correct.
To successfully install, you need to provide a fully qualified domain name that consists of a local host name along with its domain name.
for example yoursystem is a host name and yourdomain.com is a fully qualified domain name.
regards,
saravanan

PSE 10 Catalog Conversion (from PSE 6) fails

Similar Messages

Maybe you are looking for