Complete Lightroom Import Failure on Upgrade

I have just upgraded from the Lightroom release candidate to the new 3.4.1 (64 bit) version and I find that I cannot use the import function at all without causing a complete program crash.
When clicking on the Import button, or using the menu selection, I immediately receive a "Program Not Responding" message and Lightroom crashes. This happens whether there is a camera plugged into a USB port, or a card into a memory reader, or with nothing connected at all.
I have done the following without success.
System Restore to before 3.4.1 64 bit
Reinstall of 3.4.1
Uninstall and reinstall of Lightroom
Deleted preferences file
Reboots throughout the processes
Windows 7 (64) Home
Import has worked flawlessly from Vers 2 on with 3 camera makes and 2 Phone cameras
I have searched these forums and the KB but I see nothing that appears to match my case.
I would appreciate help or a pointer to an Adobe technical support email address which for some odd reason related to growing frustration I just can't seem to find on the website.
Rick Grant
Calgary

It has taken some 4 hours but I am back in business -- I don't know why.
After posting my problem I did a complete scrub of all Lightroom mentions on my machine using a 64 bit program uninstaller that went after every mention of the program including the registry entries. The only things I left alone were the catalogs.
I then tried the following without success . . .
Installed 3.4.1
Uninstalled again, ran Ccleaner, installed 3.3
Repeated uninstals but this time removed all catalogs
Disabled all malware/virus and most services and processes
Reinstalled boxed 3.2
Upgraded
Frequent reboots throughout and continued removal of Temp/etc files with CCleaner
In each case the simple act of clicking on the Import button would result in a program crash and despite Microsoft's kind offers no suggestions for fixing the problem ever came forth.
Once in a while I would get as far as a list of folders in the Import dialogue but any click on any of them brought about the crash.
During all of this I was also testing by plugging one of my cameras into the USB port that I had always used for Imports.
But, for some reason that I can't remember, I happened to plug a card reader into a completely different port and suddenly the Import function started to work.
I tested with all of my cameras as well as that same reader and card on the original port that I have always used and everything worked fine, and has continued to work fine since through a final upgrade back up to 3.4.1 and the reinstallation of my original main file catalogue.
I have no idea why things have started working again nor do I know how to avoid the problem in future.
Rick Grant
Calgary

Similar Messages

Premiere Elements 9 PC: Major Importer Failure

I think that I have gone down every troubleshooting road on trying to discover why "all of a sudden" Premiere Elements 9 PC will not import anything via Get Media/Files and Folders into its Organize interface as is its default behavior. The program fails at that point and shows the message "the program is not responding". Yet if you force the closure of that particular project and reopen a new one, you find that those media that failed to import into Organize in the first project now are live and well in the Organize of the new project. You can drag them from the Organize to the Timeline and use them in this new project. All other functions of Premiere Elements 9 PC appear unaffected by this import failure. AND, source media can be video (any format and size) and photos (any size). This happens even with import of the first and only file being a jpg (800 x 600 pixels).
My history of Premiere Elements 9 PC/baddrivers.txt file/ and "incompatible driver messages" is well documented in these forums. That involved Windows XP Professional SP3 32 bit and a NVIDIA display card. And, I have been moving along successfully with Premiere Elements 9 PC for several months. About two weeks ago, I upgraded my computer to Windows 7 Professional 64 bit Intel Graphics Card, and Premiere Elements has been performing great until yesterday when what I call "major importer failure" struck. The computer has about 800 GB free hard drive space and about 2.5 GB out of 4.0 GB of available RAM. All of this worked great for about two weeks and now suddenly this yesterday. Did I do anything different or unusual? I think not. I also have Premiere Elements 7 and 8 on this same new computer, and they continue to function perfectly in all respects, whereas Premiere Elements 9 does not. AND, yes I have had the Premiere Elements 9.0.1 Update installed and in use before and after the importer failure.
Troubleshooting has included
a. Uninstall/Reinstall from Premiere Elements 9 installation disc + uninstall/reinstall of QuickTime + Photoshop Elements 9 as well.
b. System Restore (as well as a restore of an earlier version of the installed Premiere Elements 9.
c. Removal of possible interferring program, such as, Nero InCD.
d. Removal of recent Windows Updates
e. Uninstall/reinstall of Intel driver since at one point in the failure the Edit Mode Monitor was displaying part of the Disc Menu Section while the program was in the Organize Mode.
f. Have looked at permissions, running as Administrator, etc.
One of the things that I will try this morning is installing Premiere Elements 9 PC on the previous system Windows XP Professional SP3 32 bit to see if there is any major importer failure there at this time.
If anyone has the time, I would appreciate any comments on a troubleshooting avenue that I may have overlooked. This appears to be another Deja Vu all over again. I hope not.
Thanks.
ATR

Neale
Thank you for your interest in this issue.
I still have not pin pointed why my Premiere Elements 9 works great EXCEPT it will not import media into the Organize with Get Media/Files and Folders and attempts to do that drive the program into unresponsiveness and extreme difficult closure, even with the Task Manager.
Yes, I have already looked at the workaround that you suggested for moving forward in my Premiere Elements 9 PC project, that is, entering all my source media into the Elements Organizer (can do from Photoshop Elements side) so that the source media thumbnail will be in the Premiere Elements Organize "ahead of time", and I will not have to depend upon Get Media/Files and Folders to get that job done.
But, until I hit the key to this, I think I have an almost perfect better way. My computer is now Windows 7 Professional 64 bit that comes with the Windows XP Mode. Essentially what you have in this mode is a virtual Windows XP Professional SP3 32 bit machine (best I can determine, Microsoft Generic Card). I can install Premiere Elements 9 (same serial number as on the Windows 7), and IT WORKS, no problem with the Get Media/Files and Folders. The one glitch in this perfect solution is setting up to burn to DVD. The Windows 7 Windows XP Mode Virtual Machine will not recognize installed internal DVD/CD drives when you go to write a DVD. The explanation is that the optical drive in XP Mode is a virtual device - read only. I have confirmed this. In order to use Premiere Elements 9 PC burn to disc in this Windows XP Mode , my answer here appears to be plugging in an external DVD burner USB and then using the USB Attach of the Windows XP Mode.
When Premiere Elements 9 PC was released, I was forced into much troubleshooting of the display issues which are very widely documented here. But then I was using "a real" Windows XP Professional SP3 32 bit" with a NVIDIA card. In the trial version, the BadDrivers.txt and VideoRenderer.dll got me through that episode. For me, the purchased version "essentially" was not afflicted with these same problems, and it has been running great. Now when I go to a new computer system for better performance/greater computer resources (by the way, Intel HD Graphics card), Premiere Elements 9 runs great for two weeks and then this no Get Media/Files and Folders matter sets in accompanied by program going completely knocked out by the event. In all of this, old or new, I have Premiere Elements 7, 8, and 9 installed on the same computer. While Premiere Elements 9 is being hit with these issues, Premiere Elements 7 and 8 are not , same computer environment, same source media, same project preset, et al. For me, the Premiere Elements 9.0.1 has not hit the mark.
I have done extensive troubleshooting of the this current matter, too long and involved to go into now. I am preparing a full detailed description of the issue and the troubleshooting that went into the search for a fix. I will be posting it at the forum that I frequent. When I post it there, I will supply a link to it for whomever is interested. I have filed a bug report with Adobe on this matter in abridged format as per the space provided in its bug report online form.
Thanks again for posting.
ATR

Lightroom import problem, or damaged catalogue

Hi, tried to import a large file of large raw pics directly from flash card into lightroom. the file was a bit big and it crashed.
now it wont import at all, even one pic from hard disk.
I ran the catalog optimiser. no change.
I upgraded from 2.6 to 2.7 hoping a bug fix might be there.
no better.
I removed lots of pics to reduce size (had over 8000 pics in lightroom) and re-optimised
but still no import. no error message just no importing.
any ideas anyone?

Hi , thanks John, sorry I have been away for a few days.
I am trying to get a consistent behaviour to a set of circumstances so I can give you specific details, in case it helps you spot the problem or suggest a cure.
here are details of todays experiments...
i now have 3 catalogs set up under the PC user where the problem occurs. (under the windows admin user there is no problem, only the one where the error/corruption has happened.)
the 3 catalogs are - 1. a brand new one I set up to try and see if i could recreate the importing failure
2. the original corrupted one.
3 an exported one from the original above
I have several folders of pictures copied from the flash drive onto the hard drive. the pictures are around 18 to 20 mb each taken in RAW.(pics from this camera have been processed many times before without problem)
If I take a folder with 17 pics in it - it imports fine into the new cat (number 1) but it fails after one or 2 pics in both 2 and 3.
When I import I use the following import settings :
add photos without moving, dont re-import suspected duplicates, dev settings -none, metatdata - none, keywords window - blank, Initial previews minimal.
I start the import, and loads a few pics (sorry when I repeat this sometimes it takes just one and sometimes a 2 or 3), then it stops with the import progress bar showing at top left of screen as partially imported. it hangs there and nothing happens, I come back later but no change. so I close lightroom and it says there is an import in progress do i want to quit or wait. well wait just hangs so i try quit.
When I open the same catalog again, it has the folder showing on the left but only one or 2 pics in it, so I tried the suggestion in your last post, i right clicked on the folder and selected synchronise. it syas it is waiting to import the reamining 14 or so pictures with ticks on 'import new photos', 'show dialog' and 'scan for metadata' so i try the import again. i click to show preview - all the pics show on the preview fine.
but the import tries and stops with the dialog progress bar in the top left and no activity.
I left it for ages but nothing.
As it works fine on the new small catalog and fine on different pc user catalogs, I think the problem must lie in the catalog of number 3 and exporting it (number2) also has the same problem.
So i am thinking I will just have to import all 8000+ pics into a new catalog and bin the old one however i will loose all my tagging and editing etc.
any othe ideas?

Error: Your request could not be completed because a failure occurred while the report was being processed.

Post Author: sagimann
CA Forum: Deployment
Hello,
I'm not sure if this is due to bad deployment, but I suspect it is, at least due to bad environment.
My env is:
Solaris 10 64 bit
Oracle 10g client installed under /opt/oracle/app/oracle/product/10.2.0/client_1
BOXIR2 + FP2.6 installed under /opt/reporting, running under user 'bouser'. by the way, 'tnsping' works via that user.
Important bouser env:
ORACLE_HOME=/opt/oracle/app/oracle/product/10.2.0/client_1
TNS_ADMIN=$ORACLE_HOME/network/admin
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib32
I reboot the box, then start BO like so:
cd /opt/reporting/bobje
. setup/env.sh
./mysqlstartup.sh
./startservers
./tomcatstartup
Then, I import a BIAR file with some reports, and whenever I try to open any report via infoview, I get a gray error message INSTEAD of the input param form:
Error:
Your request could not be completed because a failure occurred while the report was being processed. Please contact your system administrator.
This does not occur in our BOXIR2 on Windows, which is why I'm guess it's a deployment/env issue. The main obstacle I have is: how do I diagnose this? there's nothing in the bobje/logging folder, nothing in the /var/adm/message file except for the following line:
May 5 15:23:23 testbox1 boe_pagesd[3865]: [ID 253862 user.error] A failure occurred while the Page Server was processing report 'test report' (id=777) for user Administrator
pls advise,
thank you.

The solution is to turn off the printer preference (bottom of Page Setup screen) in the Crystal Report before uploading to the Server. Thanks to: http://pinchii.com/home/2011/12/error-adding-reports-to-crystal-reports-server/
The explanation, from a comment in the above linked blog post:
"To elaborate more on the error, what basically happens is that the Crystal Reports engine tries to get the status of the u201Creport printeru201D aka u201Cdefault printeru201D which was present on the system when the report was created, but the printer does not exist anymore. This causes the Crystal engine to error out. By setting the report to u201CNo Printeru201D, it tells the Crystal Engine not to look for that report printer when opening the report."
Edited by: abirdman on Feb 3, 2012 9:49 PM

Lightroom 3 crash after upgrading Lightroom 1 Catalog

I installed Lightroom 3 and upgraded my Lightroom 1 catalog (21,000 photos). It runs through the upgrade process without any problems and opens Lightroom 3, where I can browse through a few screens of images.
However, if I scroll past a certain point in my Grid view, Lightroom 3 stops rendering thumbnails. Double clicking on images fails to render a preview. CPU usage at this point goes from 50% to 0. At this point, Lightroom 3 becomes useless, though I can still scroll up and down, I only see empty grid thumbnail frames.
If I quit the application, I get a beachball, for minutes on end before I force quit.
Console reports the following:
06/10/10 9:53:24 PM Adobe Lightroom 3[506] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERROR SERVER<AsyncDataServer
( Lightroom 3 Catalog.lrcat )>: A command threw an exception.
06/10/10 9:53:24 PM Adobe Lightroom 3[506] ServerProcess [AsyncDataServer( Lightroom 3 Catalog.lrcat )] ERROR Error: ?:0: attempt to
perform arithmetic on field '?' (a nil value)
06/10/10 9:53:24 PM Adobe Lightroom 3[506] Error initializing alternate universe. bad argument #1 to 'pairs' (table expected, got nil)
Deleting all Lightroom 3 prefs, plists, catalog, previews, rebooting and trying the process again results in exactly the same problem.
I can still run Lightroom 1 fine. It has no problem with the Lightroom 1 catalog. I tried optimizing the Lightroom 1 catalog before upgrading, but this
did nothing.
I'm running on a 2007 MacBookPro with 3GB RAM and a 7200 RPM 500GB drive under Mac OS X 10.5.8.

The problem lies in 1 or more "corrupt" catalog entries from the old catalog. I had exactly the same problem going from LR2 to LR3 on a 2009 iMac running 10.6.4. I got the same console error messages and had exactly the same symptoms.
However I discovered that I could start LR3 with a new empty library and then use "import from catalog" to selectively import some parts from my LR2 catalog. There are about 6k images in the LR2 catalog and some folders would work fine and others would fail. After a lot of trial and error I was able to isolate where LR3 would hang and give me problems. And the images that it had a problem with were 2 images from the old catalog that LR2 would not display. Instead LR2 would show a blank thumbnail where the "corrupt" catalog thumbnail should be and would not be able to display that image. For those images, LR2 gave the following console error message:
10-07-01 8:58:48 AM Adobe Lightroom 2[2038] *** WARNING: Method selectRow:byExtendingSelection: in class AgNSOutlineView is deprecated. It will be removed in a future release and should no longer be used.
10-07-01 9:02:04 AM Adobe Lightroom 2[2038] ?:0: attempt to perform arithmetic on field '?' (a nil value)
Aside from not display the thumbnails and images for those two files, LR2 worked fine. When I unselected those two images from the "import from catalog" dialog, I was able to import the rest of my LR2 catalog into LR3 in one shot.
If LR1 fails to display some thumbnails, you could manually note which those are and then use the same process I used. It is still tedious going through a large library looking for blank thumbnails. If LR1 displays all thumbnails correctly then you could try the brute force trial and error approach that I initially used but that is very time consuming.
Hope this helps.

[SOLVED]X start failure after upgrade: dri3,present modules missing

I start X with ~.xinitrc from console, which won"t work after last upgrade --first in two weeks.
(EE) Server terminated with error (1).Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Xorg.log.0 :
[51:778] (EE) intel: Failed to load module "dri3" (module does not exist, 0)
[51:779] (EE) intel: Failed to load module "present" (module does not exist, 0)
Installed packages (EDIT: completed):
xf86-video-intel-2.99.{914-4,916-1}-i686 and also tried with xf86-video-intel-git, with "SNA" acceleration.
intel-dri 10-2.7-3
dri2proto 2.8-2
dri3proto 1.0-1
xf86driproto 2.1.1-3
Linux 3.15.5-2-ARCH i686
Linux CK Atom 3.16.2-1
Issue occurred after upgrading from v2.99.912-1 to v2.99.914+. I was going to try downgrade xf86-video-intel to v2.99.912-1 (as in the first thread in Refs) but went in a dependency conflict, with the older intel driver requiring glamor-egl which conflicts with xorg-server ':-|
Atom netbook
lspci:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
Some refs :
» [SOLVED] X start failure after upgrade https://bbs.archlinux.org/viewtopic.php?pid=1426837
» [Solved] xf86-video-Intel-2.99.912-1 breaks xorg https://bbs.archlinux.org/viewtopic.php?id=182932
Last edited by kozaki (2014-09-12 09:45:53)

The issue occurred after upgrading from xf86-video-intel-v2.99.912-1 to v2.99.914+ and xorg-server-1.15.2-1 to 1.16.0-6 (and -devel).
same issue if:
- Switching accelaration method to "UXA" as per https://bugs.archlinux.org/task/40860
- Adding Option "DRI" "False"
Digged a bit:
- same modules errors but appears to be a Gnome bug (X starts): https://bbs.archlinux.org/viewtopic.php?pid=1441716
- same modules errors but X starts up without problems http://www.linuxquestions.org/questions … 175511372/
makes me doubt if this issue is related to the modules not found. Which is the single indication I found so far x-/
Any light on where can the issue comes from? hardware is pretty much standard even if getting a bit old. Never had Xorg related issue so far on this pancake.
Last edited by kozaki (2014-09-11 11:05:42)

File Import Failure; File has unsupported compression type!

I completed editing my movie about two weeks ago did all the colour correction audio etc last week, and aim to complete the sutitling tomorrow!
But now the problem is that my some of my files are now offline and can't be relinked because I get an error message which says "File Import Failure; File has unsupported compression type"
These files are .MTS which I believe are AVCHD.
So I don't know what has happenned here. Is it the recent update that has caused this or something else?

This have happend to me twice now.
If I remember correctly it have to do with Cloud membership in my case. Both times I have been away on work and when I get home I have a email stating that payment have failed. After I set it right I start up Premiere and I get this failure.
First time the solution was uninstall Everything Adobe and run clean script. Reinstalling did the trick.
That solution is not working in the long run.
Here Adobe needs to do something soon!

Lightroom imports with 100 clarity

Hello people,
i have the strange problem that lightroom imports always with 100 clarity. There is definitely something wrong with my presets, just don't know how to change that. Thanks for any suggestions, tobfl

If you apply a preset during the import process, that preset will be applied to all images that are imported. Another way to apply a preset to all images would be to have multiple images highlighted in the develop module and have auto-sync enabled.
The first thing I would suggest that you try is to reset the clarity on one of those newly imported images, changing nothing else. Then, save new camera defaults. Then I would check in your import dialog to make sure you haven't chosen a preset to be applied during the import process. Next, take a test image and import it.

I have been using a Lightroom 5 including recent upgrades on my Mac Pro laptop for the past 1 year. This was purchased as an upgrade from Lightroom 4 for which I have a serial number. Today I purchased a new Macbook pro and loaded my Lightroom 5 however i

I have been using a Lightroom 5 including recent upgrades on my Mac Pro laptop for the past 1 year. This was purchased as an upgrade from Lightroom 4 for which I have a serial number. Today I purchased a new Macbook pro and loaded my Lightroom 5 however it is asking for my serial number which I have misplaced. I am unable to trace my serial number anywhere. I have even checked my adobe membership to locate my serial number but it does not seem to have any record which is strange as I have been using this software for over a year now and the previous versions since 2009. Could someone help me in my predicament.

Contavct Adobe support thru chat:
Serial number and activation chat support (non-CC)
http://helpx.adobe.com/x-productkb/global/service1.html ( http://adobe.ly/1aYjbSC )

Solution Import Failure Message: Cannot add a Root Component 'GUID' of type 29 because it is not in the target system

Hi all,
Please refer to the error:
Root Components import: FAILURE
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Exception |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Error |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | CrmException..ctor
ilOffset = 0x30
at CrmException..ctor(String formattedErrorMessage, Int32 errorCode, Object[] arguments) ilOffset = 0x30
at ImportRootComponentsHandler.GetSolutionRootsCollection(Boolean throwIfMissing, Boolean skipRibbonCustomization) ilOffset = 0x209
at ImportRootComponentsHandler.ImportItem() ilOffset = 0x8
at ImportHandler.Import() ilOffset = 0x43
at RootImportHandler.ImportAndUpdateProgress(ImportHandler ih) ilOffset = 0x7
at RootImportHandler.HandleNonMetadataHandlers(String[] ImportEntities, ImportHandler& ihForCurrentPath) ilOffset = 0x33
at RootImportHandler.RunImport(String[] ImportEntities) ilOffset = 0x1D8
at ImportXml.RunImport(String[] ImportEntities) ilOffset = 0xE
at ImportXml.RunImport() ilOffset = 0x5BF
at ImportXmlService.ImportSolutionSkipCapable(Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Byte[] customizationFile, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies,
ExecutionContext context) ilOffset = 0x46
at RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) ilOffset = 0xFFFFFFFF
at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) ilOffset = 0x25
at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) ilOffset = 0xCF
at LogicalMethodInfo.Invoke(Object target, Object[] values) ilOffset = 0x4F
at InternalOperationPlugin.Execute(IServiceProvider serviceProvider) ilOffset = 0x57
at V5PluginProxyStep.ExecuteInternal(PipelineExecutionContext context) ilOffset = 0x200
at VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context) ilOffset = 0x65
at Pipeline.Execute(PipelineExecutionContext context) ilOffset = 0x65
at MessageProcessor.Execute(PipelineExecutionContext context) ilOffset = 0x1C5
at InternalMessageDispatcher.Execute(PipelineExecutionContext context) ilOffset = 0xE4
at ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode,
Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)
ilOffset = 0x16E
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, UserAuth userAuth, Guid targetUserId,
OrganizationContext context, Boolean returnResponse, Boolean checkAdminMode) ilOffset = 0x1F1
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset
= 0x2D
at OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset = 0x26
at InprocessServiceProxy.ExecuteCore(OrganizationRequest request) ilOffset = 0x34
at PlatformCommand.XrmExecuteInternal() ilOffset = 0xF6
at ImportSolutionCommand.Execute() ilOffset = 0x20
at DataSource.ImportSolution(Byte[] customizationFile, Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies, IOrganizationContext
context) ilOffset = 0x0
at SolutionImportProcessPage.ImportSolution() ilOffset = 0x123
at SolutionImportProcessPage.ProcessRequestData() ilOffset = 0x4A
at SolutionImportProcessPage.ProcessAction(String action) ilOffset = 0x92
at AppUIPage.OnPreRender(EventArgs e) ilOffset = 0xD
at Control.PreRenderRecursiveInternal() ilOffset = 0x54
at Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x6D3
at Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x3C
at Page.ProcessRequest() ilOffset = 0x14
at Page.ProcessRequest(HttpContext context) ilOffset = 0x33
at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() ilOffset = 0x18D
at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ilOffset = 0x15
at ApplicationStepManager.ResumeSteps(Exception error) ilOffset = 0x10A
at HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) ilOffset = 0x5C
at HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) ilOffset = 0x16A
at ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType) ilOffset = 0x4B
>Crm Exception: Message: Cannot add a Root Component 0ffbcde4-61c1-4355-aa89-aa1d7b2b8792 of type 29 because it is not in the target system., ErrorCode: -2147188705
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Platform.Sql |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Info |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | BusinessProcessObject.ExecuteNonQuery
ilOffset = 0x28
I am getting this coming up in the error log when I attempt to import an unmanaged solution.
After searching on google Type 29 refers to a workflow.
I go into the source system and query the database by the GUID and discover that it is actually a Business Process Flow called 'Phone to Case Process'.
I do not have this process in my target system as I deleted it.
Looks like this is one of the out of the box ones. I don't think we we have changed this one much.
What does this mean and what should I be looking for??
Anyway how do I remove this offending process from the unmanaged solution xml file and attempt to re-import it?
It doesn't look like I can generate the solution again without the offending workflow/process..

I managed to resolve this issue after looking at this thread:
https://social.microsoft.com/Forums/en-US/fddff17f-1cca-4d33-a666-60c08ad76b0c/crm-2011-import-failure?forum=crmdevelopment
Just modify both solution and customizations xml by searching for the guid and removing the root component

Failure to upgrade Cisco Unity Connection 8.6.2 to 9.1.2

Hi everybody.
Has someone that can help me with follow problem?
I making a Cisco Unity Connection upgrade from version: 8.6.2.20000-76 to 9.1.2.10000-28. But unfortunately we can't sucessfull to make this process.
On the finish of this process, I can see this outup error:
11/23/2013 12:28:55 upgrade_manager.sh|Cleanup exiting - Cached Data: [Vendor= VMware, Inc.
HWModel=VMware
CPUCount=2
CPUType= Intel(R) Xeon(R) CPU E5-2643 0 @ 3.30GHz
CPUSpeed=3300
MEMSize=6144
BIOSVer=PhoenixTechnologiesLTD 6.00 06/22/2012
ObjectId=1.3.6.1.4.1.9.1.1348
OSVersion=UCOS 5.0.0.0-2
SerialNumber= VMware-56 4d e0 4f 4d 85 87 7b-eb 22 0e 52 a7 73 1a 22
VendorOID=1.3.6.1.4.1.674]|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Cleaning up download...|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Cleanup upgrade source area.|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Ejecting DVD (/dev/sda1)|<LVL::Debug>
11/23/2013 12:28:55 upgrade_install.sh|Removing /common/download/9.1.2.10000-28|<LVL::Info>
11/23/2013 12:28:55 upgrade_install.sh|Started auditd...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Started setroubleshoot...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Changed selinux mode to enforcing|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Cleaning up rpm_archive...|<LVL::Info>
11/23/2013 12:28:56 upgrade_install.sh|Removing /common/rpm-archive/9.1.2.10000-28|<LVL::Info>
11/23/2013 12:29:00 upgrade_install.sh|IOWAIT monitor stopped|<LVL::Info>
11/23/2013 12:29:00 upgrade_install.sh|File:/usr/local/bin/base_scripts/upgrade_install.sh:599, Function: main(), Upgrade Failed -- (1)|<LVL::Error>
11/23/2013 12:29:00 upgrade_install.sh|set_upgrade_result: set to 1|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|is_upgrade_lock_available: Upgrade lock is not available.|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|is_upgrade_in_progress: Already locked by this process (pid: 14477).|<LVL::Debug>
11/23/2013 12:29:00 upgrade_install.sh|release_upgrade_lock: Releasing lock (pid: 14477)|<LVL::Debug>
Best Regards,
Claudio Costa
A mensagem foi editada por: Claudio Costa

Tks Manish, I just perform a restart on the both nodes on my CUC cluster and after that I did can install this upgrade patch.
Also is very important install the upgrade patch on all servers of the cluster before perform a switch-version on the publisher and then on the others nodes.
Best Regards,
Claudio Costa

File Import Failure with Adobe Premiere Elements 11

I've just installed Adobe Premiere Elements 11 on my Windows computer. I have started a video project, saved it and when I tried to re-open it I got this File Import Failure message "This type of file is not supported or the required codec is not installed". What do I do? Thanks for your help!!

I've just installed Adobe Premiere Elements 11 on my Windows computer. I have started a video project, saved it and when I tried to re-open it I got this File Import Failure message "This type of file is not supported or the required codec is not installed". What do I do? Thanks for your help!!

"File Import Failure Unsupported format or damaged file" in CS6 but fine in CS5.5

Hello All.
Recording in Pal DV AVI from Sony Z5U with MRC1K compact flash recorder.
Imported files to computer using the Sony utility, and also tried dragging and dropping.
Some files import to Premiere Pro CS6.03, but others give "File Import Failure: Unsupported format or damaged file,".
The files that do import show up as 4:3 and I have to modify / interpret footage to get them to show as 16:9,
However, these same files play back just fine in Windows Media Player.
Intriguingly these files import just fine to Premiere Pro CS5.5, and also show up correctly as 16:9.
I can't figure out why some files import into CS6 and others don't....
Anyone else seen this kind of behavior?
(Normally I record in HDV and I've never had problems importing from MRC1K into Premiere, but the client specifically requested DV files for their ease of editing...)
Cheers
Mark
PS When I use the DV recoverer utility on these files they import just fine into CS6....

Hi Jim,
OK, here's the video that imports OK into CS6.03 but that Premiere CS6.03 sees as 4:3:
And here's the one that won't import into CS6.03 but is happily opened by CS5.5 and correctly seen as 16:9:
Can you spot the difference? Thanks for having a look at this.
Cheers
Mark

File import failure in premiere pro on specific files

I have installed the latest version of Premiere Pro CC 2014. I am trying to import several video files that i have recorded on a Canon 5D Mark III. The problem is that while some of the files gets successfully imported, many files cant import because of a error message, file import failure. Unsupported file format etc. I have tried to open this in many media players, and all work fine there. I have even imported these files on the same Premiere Pro-version on a different machine, and there they work perfectly. But on this machine some files just wont open. Does anybody have a clue or tips on how I can fix this? I guess its a problem within the software.

It just seems to pick certain files and reject them.
Which ones does it eject? eg do they have a different file extension from the video files.
Are they rgb?

Why can't Lightroom import or even recognize images have been (saved as) in photoshop

Lightroom 5 dosn't read photos saved as tiff or jpeg from photoshop cc when importing???
i Have both latest version running on iMac latest version as well!
I Have no other problems! I wonder if it's a bug or some annoying ignored feature?
I Tried with tiff psd and jpeg!!

Duplicate thread:
Lightroom import issue!

Complete Lightroom Import Failure on Upgrade

Similar Messages

Maybe you are looking for