Dec Premiere update mxf file problem

The new update has taken all the mxf clips in a current project I was working on (5 different sequences with 4 cameras in each) and duplicated some and moved them all around in the timeline leaving my project which is due to be delivered on Mon morning useless. I will simply have to start from scratch as I have been let down by the update process yet again. Does anyone have a fix for this please. I really shouldn't update when I have active projects but that is all the time.
Please help

Thanks Mark, I finally worked that out for myself and re synced all the edits using the clips that Prem was now seeing as one file. The problem i then had was that it changed it all back again when I imported it into After effects for colour correction. Nightmare but I got there in the end. Never update mid project is the lesson for today.
Steve

Similar Messages

Premiere Pro MXF files problem

When I first imported in to Premiere Pro (CC7.2.1) all of my MXF files from a Sony F55 all worked perfectly. Immediately I could preview the files in the source window and use the metalogging to skim through them. Additionally I could create and export sequences and preview them in realtime at 1/2 resolution - preview was quick and fluid.
Two weeks later and i'm struggling to get any sort of preview on the same premiere projects. I open a project, and if I try to preview a clip in the source window I sometimes get frame one and audio, but never any sort of playback. If I try to preview a sequence I just get media pending, a black screen or audio only.
I haven't moved any clips from their original folder and it isn't complaining it can't find them. It never seems to render them no matter how long I leave it.
Interestingly, If I use the direct link to speedgrade then they play instantly in speedgrade
I'm using a MBPR with CUDA Mercury.
When I open another project with AVCHD files all seems to work ok, but any of the several projects I have with these MXF raw files fail to preview anything.
Any help grately appreciated.

This forum is actually about the Cloud, not about using individual programs
Once your program downloads and installs with no errors, you need the program forum
If you start at the Forums Index http://forums.adobe.com/index.jspa
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll
http://forums.adobe.com/community/premiere?view=discussions

MXF File Problems

I was shooting on the C300. As I went to transfer the CF card, the card crashed. I took the card to a recovery center where they were able to recover the footage. However, all the clips are now in one .MXF file. It says the file is 15.49gb but only says it has a duration of 5 seconds. If I run it in VLC player, it plays the whole set of clips from the file but I am unable to scroll through it (fastforward/reverse). When uploading to premiere cs6 I get "Importer detected a generic error". I am able to see every clip via VLC, but not able to edit it. At a loss right now.

Francis,
From the manual i have:
Merge All Clips = Merges the MXF stream files within each clip and also merges multiple selected files into a single file.
Merge Each Clip = Merges the MXF stream files within each clip but keeps multiple selected files as separate files.
Regarding the audio issue:
In Premiere Pro CS6 you can set the Default Audio Tracks so your files import as stereo instead of dual mono/multichannel mono media. I don't know if this was an option in CS5, but i think it is not.
In CS6 you do this:
1. Edit > Preferences > Audio ("Premiere Pro > Preferences > Audio" on the Mac)
2. Under Default Audio Tracks, change Multichannel Mono Media from "Use File" to "Stereo".
3. Click OK.
Note that it won't affect already imported clips. This preference setting affects clip when you import them.
/Roger

Adobe premiere update/aspect ratio problem/vista

Can someone please help...
I have already set up a video in Premiere 6.0 with a 16:9 aspect ratio. When it exports, the aspect ratio is between 16:9 and 4:3. My DVD authoring program reads it as 4:3, and cuts off part of the video, or adds black bars to the sides, depending on the the export settings.
I have read that the premiere6.1 update, which I have downloaded will fix this issue, but it will not install in windows vista.
is there an update that will install in vista out there somewhere?

There is no such thing as a 6.1 update... there is 6.01 and 6.02 and nothing any later
Since Premiere 6x is SO old, it is not surprising that it doesn't work properly on Vista
You might want to download the trial of Premiere Elements (which has a different forum) to see if it will work for you

Updated JAR files problem

Hey guys, I just updated my jar files from myfaces-api.jar to myfaces-api1.1.5.jar or something like that. Then all of a sudden my submit function does not work. It keeps having a javascript error...
form has no properties
oamSetHiddenInput("linkDummyForm", "autoScroll", "0,0")adminHome.jsf (line 91)
oamSubmitForm("linkDummyForm", "adminMenu:_idJsp1", undefined, undefined)adminHome.jsf (line 128)
onclick(click clientX=0, clientY=0)
ack! i have no idea what im supposed to do! thanks in advance!
-Arch_Bytes

The MyFaces user mailing list might get you better results than this forum.

Problem rendering MXF files Premiere Pro CC 2014

I'm working with MXF files on a project that has pretty normal cross dissolves etc. The footage is mostly 60p and I'm using the occasional time remapping effect etc. The closer I've gotten to the finished edit now suddenly the timeline will render up to about 90%- 95% then stall slowly rendering for 20-30 minutes or more.
I'm working on a 3.5ghz Core i7 iMac - 32 GB of ram. Up to this point it's been pretty seamless working with these files. I've also upgraded to Premiere CC 2014.
This is very very frustrating at this point though since it seems completely random when a clip might take 3 seconds to render or 3 hrs.

Got the same Error. Previous I worked with a GTX 760, and was hoping to get it fixed with using a GTX 780 6GB. But just as you, didn't solve the Problem.
Usually I got the Problem solved, with exiting Premiere, restarting it, reset my Workspace. Then the Problem of having the bugged Workspace was gone. And also the Problem of the missing Video Tracks.
At the moment I started on a new Project. Pretty simple, with only a 21 second DV footage. And here I was switching tabs with my Browser, came back to the Project, and the Video Tracks were gone. I saved, closed Premiere, restated and the Video Tracks are still missing.
So I made a new Sequence, voilá the Video Tracks are there. Thus I need to copy and paste the Tracks onto the new Sequence.
But that is not really a solution!
I was on the Phone with Adobe, and on Chat, but they couldn't help me. They suggested to get a Tesla or Quadro Card, or at least a GPU that got confirmed as working on their page. I did that, but obviously, that is not the issue.

Problem importing canon c300 mxf files into Premiere Pro CC 2014

I recently shot some footage with a c300 at 24fps, slog2, 2 audio chanels. I copied the "contents" folder of each cf card to my macbook pro hard drive by dragging across in finder.
When I search from within Premiere Pro's media browser for my files, they show up only as VLC icons, and when I click to import them, I get an error message along the lines of 'unsupported format or damaged file".
I can double click the files in finder and they open in VLC fine.
I'm running the latest version of Prem Pro, Yosemite on my macbook pro which has 2.8ghz i-7 processor, NVIDIA GeForce GT 750M 2048 MB graphic card.
Does anyone know why this is happening?

You could try to convert your XAVC MXF files into MPEG, then load them again , but the new codec may not be well handled by some converters.

Imported Canon xf305 MXF files keep copying themselves in Premiere Pro CC (October 2014)

Hi. My Adobe Premiere CC keeps getting worse with MXF files. This is a progressing BUG Type problem with each update. As each Premiere update comes out my program behaves even more bizarre. Upon original import, they're fine. Turn off computer and next day my half hour piece all-of-a-sudden turns into 25 copies of the first 5 minutes. So I delete the rest of the copies and whats left I loose 4/5th of the program. So I input files and they're ok,,, 2 hours later they're no audio on 1/2 of the program, or all of the individual Icons in the files bin have turned into one same picture of the first piece copies 10 or 20 times? Or I edit my footage and the next day I turn on the computer open the program and all my footage is not in the bins or timeline, yet they play perfectly fine on their own in the media drive with another player?
WHAT IS GOING ON WITH PREMIERE? It's Absolutely Unusable?
Old drives? I don't think so, It's a relatively new computer with two (5 month old Solid State Drives) Besides it all works great with another player?

4. Then I Open PremiereProCC, create a new project and point everything to that project folder on the M (media) drive.
5. Next I go to media bin within the new project, right-click and choose "Import Media", grab all the new footage and hit open.
6. The roughly 1 hour project taped at 750p @ 50mps, takes about 1.5 hours to populate into the bin.
7. Finally I drag all the clips (roughly 10 of them) onto the new timeline, where it takes another roughly 30 minutes to populate onto the timeline.
Item 4 ..explain "point"
Item 5 ...Media Browser I assume?
Item 6 ...thats far too long and indicates an issue. Should be maybe a minute and then maybe some pek conforming
Item 7 ...far too long and indicates a problem, Should be virtually immediate.

Why is Premiere getting an error when trying to export .MXF files?

Hello!
I have a video that I need to submit to DMDS and it must be a .mxf file. This is the first time I've ever had to export a .mxf so I am not too familiar with the type. I have been exporting every other type of file for years and never had an issue (H.264, quicktime, etc.). However, when I try exporting .mxf I get the generic rendering error which then stops the export.
The first time I tried, the video was down to 12 minutes left (after about 2 and a half hours) when I got the error.
The next time, it crashed right away with over 2 hours still remaining.
So it does not seem to be a corrupt clip because: A) I've been rendering this video out as other file types for rough previews, drafts, etc and it's worked fine and B) The 2 crash times were on opposite ends of the spectrum.
I am running an iMac with OSX 10.7.5, 3.06 Ghz Intel Core 2 Duo with 8GB ram...I am using Premiere Pro Version 6.0.0
I do have Third Party plug ins installed but have never had an issue exporting in the past, only with this .mxf file.
Thanks in advance for any and all help!

If you have GPU accelertation enabled in Premiere Pro, try switching to Software Only.
Are you queuing the job to AME or clicking "Export" in the Export Settings dialog (which encodes directly through Premiere)? Whichever path you're going down, try the other one.
I'd also keep an eye on your resource usage, especially RAM, while encoding in progress. With 8GB of RAM, I'd be surprised if that were the problem.
Lastly, if you're encoding through AME, then you might want to post on that product's forum: http://forums.adobe.com/community/ame

Trouble importing .mxf files into Premiere Pro CS6

Having problems importing MXF. file types into my Premiere CS6 project. I will go to import the folder and the yellow loading bar will come up to say that it's importing. Then it will freeze and the color wheeled loading symbol will come up (I'm using a Mac) and will just sit there. From there I'm forced to do a force quit on my project and re-open it again. Is there any way to fix this issue and if so what is the problem causing this issue?
Also my mac is running on OSX v10.7.5 and Premiere is running on cs6 v6.0.2

Yes, MXF should play perfectly in PP CS6, but if you can't work this out at this point, you may wrap your MXF video to something intermediate. as a matter of face, Adobe Premiere Pro CS6 seems to work fine if you import your MXF clips directly from a camera or camcorder, but if have already copied MXF recordings your HDD or you downloaded them from somewhere else, the import error may occur.
So i suggest you convert the MXF footage to something mezzanine we would recommend DNxHD.mov (if you are on a PC) or Apple ProRes .mov (if on a mac). those two intermediate codecs are good mezzanine codecs that handle recompression well and standup well in other areas of post-production (color grading, graphics, compositing, etc,). You can see what I wrote about the solution. "Why Premiere Pro CS6 can't import MXF files?" i hope that it is helpful to you.

MXF files won't import into Adobe Premiere CS6

I can't get mxf files to open in Adobe Premiere CS6. I'm working on the newest Mac Book Pro- OS X Yosemite 10.10.1. I tried importing the files through the media browser but I can't open them that way either. I see the mxf video icon but when I try to open it I get this error message -"the importer reported a generic error." I ran all the updates for adobe and apple, but still these files don't open. Help please.

If I double click on the word holiday, it just shows the file folders. In the file folders the mxf files still don't open.

Premiere CS4 I Can't Import .MXF files but Adobe assures me i can?????

Hi I have Adobe Premiere CS4 and I am trying to import some videos to it and they are in .MXF format. Premiere issues me "codec missing or unavailable" and I don't want to download some sort of converter. Isn't Premiere supposed to support .MXF files?????????

Not sure about CS4, I started with CS6. And hope I'm not being preachy here, but an awful lot of troubles over MXF files have the same root problems. Even some very experienced editors have had issues with this. The vast majority of the times this error comes up people have not imported as PrPro needs it ... MXF files are a form of AVCHD ... the camera makes separate (and oft fairly short) sections of video file and matching audio files, stored on the cam in separate folders, with a database to tell any further software use which pieces are part of the same "full-length" clip, and that data is stored in a different folder-tree from the other files. If you don't properly import the whole folder tree, PrPro says ... no go.
So ... when uploading onto the computer, or moving the files around to various drives, you ALWAYS need to take the entire folder-tree from the camera and move it intact. Some other softwares manage to sort out MXF/AVCHD files while the top level folder didn't get copied, PrPro probably will choke. Next, you need to navigate to the files in the Media Browser and then select and "Import" those files, then work them from the Project panel.
Oh ... and often times if these are on external drives, PrPro can be picky about seeing/working with them.
Neil

Adobe Premiere CS6 'Create new Trimmed Project' Crash with .MXF files

Yesterday I started to back up all our students work, and found that the "Create New Trimmed Project" no longer works in CS6 with .MFX files.
Adobe Premiere CS6.0.3, crashes when I try to "Create New Trimmed Project" under "Project Manager"
This only happens when there are .MXF files in the Sequence.
As we use Panasonic P2 cameras at this university, this is a problem, as this is the format that they shoot in.
As a test I have made a Project with only one .MXF file placed on the sequence, and it crashes.
This happens on my Macs and Windows machines with Adobe Premiere CS6 .
Adobe Premiere CS5.5 works fine, and does not crash.
Unfortunately I cant save a CS6 project as a CS5.5
If you don't have any .MXF files to test this,
You can make your own .MXF files by exporting any video file as "MXF OP1a" or "P2 Movie" Format, (the Preset setting is irrelevant - any preset will cause it)
P.S.
Using "Collect files and Copy to new Location" under "Project Manager" works fine, but does not reduce project size as much.

I also discovered this behavior last summer. Unfortunately the best (lame) answer I could find was that "Some formats, such as Long GOP based media files, cannot trim media, or add handles." Source: http://help.adobe.com/en_US/premierepro/cs/using/WS1c9bc5c2e465a58a91cf0b1038518aef7-7c72a .html
That's not very specific, but in my case at least (and it sounds like in your case, too) .MXF may be another file type that cannot be trimmed. If I remember correctly, the answers I got from others was that they were able to export fine. My machine (and maybe yours) has an issue that nobody else seems to have encountered. So none of the prescribed remedies allowed me to move forward in this regard.
After much searching, asking and several suggestions from various Premiere communities, I gave up and moved on.
Use Remove Unused and then Collect Files and Copy to New Location. At least that can help you if you have a lot of clips. In my case, it didn't help much, because my very short clips were edited from very long takes, so as Premiere sees it, not much was "unused".
Be aware that "Project Manager does not copy and collect After Effects compositions that are dynamically linked to an Adobe Premiere Pro project. Project Manager does save the Dynamic Link clip in the trimmed project as an offline clip, however."
Wish I could offer you more.

Premiere CS6 MXF problems?

Hi since i installed premiere CS6 i have a lot of problems
THE PC that i have is win 7 pro 64 bits SSD disk for systems and 2 HDD SAta of 2TB each one
Video card envidia GT650 , 8 GB Ram
first problem >> premiere don't start usually i have to press shift + left control in order enter to premiere
also on the timeline the video always freeze
sometimes proyects don't open, i have to create a new one and them import the proyect that didn't work
today i have problem with Error Compiling Movie: Unknown Error
i can't render now
i try to render in little part, but before it get 100% the render increase and decrease and never end to render??? for example 98.5% them 98.1% them 98.7% 98.9% 97.5% and the loop continue
i think could be problem due to MXF fileS?

Hi!! thanks por the quick reply
Yes, the mayority of time i have to acces premiere holding down Shitf+alt
also make a new sequence each time that i have problems fix all but today, i create several sequence but Error Compiling Movie: Unknown Error can't fix so i'm not able to render this proyect

Deployment Problem: Cannot update archive file

Hi!
I am trying to deploy an EAR for my Projekt "PegasusServerApp". The Application had been deployed on the server before but I removed it using remove_app on a telnet client. (and it is really gone! at least I cannot see it anymore in the visual administrator nor in the telnet client)
Another attempt to deploy the (re-worked) Application fails with com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file PegasusEJB.jar
What makes me suspicious is a detail from the deployment log: Update: Selected development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19' updates currently deployed development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.11.18.52'.
Why is it "currently deployed" when I removed it before?
Has anyone an idea what goes wrong?
Here is the complete deployment log: (from the Developer Studio)
02.12.2004 19:30:07 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Deploy Thread] INFO:
PegasusApp.ear -> Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7111 - 630_SP]/>
<!NAME[C:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20041202182935.log]/>
<!PATTERN[C:\usr\sap\J2E\JC00\SDM\program\log\sdmcl20041202182935.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter]/>
<!LOGHEADER[END]/>
Dec 2, 2004 7:29:37 PM   Info: -
Starting deployment -
Dec 2, 2004 7:29:37 PM   Info: Loading selected archives...
Dec 2, 2004 7:29:37 PM   Info: Loading archive 'C:\usr\sap\J2E\JC00\SDM\program\temp\temp21072PegasusApp.ear'
Dec 2, 2004 7:29:44 PM   Info: Selected archives successfully loaded.
Dec 2, 2004 7:29:44 PM   Info: Actions per selected component:
Dec 2, 2004 7:29:44 PM   Info: Update: Selected development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19' updates currently deployed development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.11.18.52'.
Dec 2, 2004 7:29:44 PM   Info: Saved current Engine state.
Dec 2, 2004 7:29:44 PM   Info: Error handling strategy: OnErrorStop
Dec 2, 2004 7:29:44 PM   Info: Update strategy: UpdateAllVersions
Dec 2, 2004 7:29:44 PM   Info: Starting: Update: Selected development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19' updates currently deployed development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.11.18.52'.
Dec 2, 2004 7:29:44 PM   Info: SDA to be deployed: C:\usr\sap\J2E\JC00\SDM\root\origin\isenergy.de\PegasusServerApp\localhost\2004.12.02.19.02.19\temp21072PegasusApp.ear
Dec 2, 2004 7:29:44 PM   Info: Software type of SDA: J2EE
Dec 2, 2004 7:29:45 PM   Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 2, 2004 7:29:56 PM   Info: Begin of log messages of the target system:
04/12/02 19:29:46 - ***********************************************************
04/12/02 19:29:53 - Start updating EAR file...
04/12/02 19:29:53 - start-up mode is lazy
04/12/02 19:29:56 - com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file PegasusEJB.jar
                     null. Reason:
                          at com.sap.engine.deploy.manager.DeployManagerImpl.makeTempEar(DeployManagerImpl.java:3755)
                          at com.sap.engine.deploy.manager.DeployManagerImpl.makeNewEar1(DeployManagerImpl.java:3721)
                          at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:522)
                          at com.sap.engine.deploy.manager.DeployManagerImpl.update(DeployManagerImpl.java:511)
                          at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:196)
                          at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96)
                          at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224)
                          at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60)
                          at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186)
                          at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:46)
                          at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83)
                          at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60)
                          at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:72)
                          at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73)
                          at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59)
                          at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:127)
                          at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:96)
                          at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:57)
                          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                          at java.lang.reflect.Method.invoke(Method.java:324)
                          at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127)
                          at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38)
                          at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:81)
                          at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67)
                          at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76)
                          at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:280)
                          at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43)
                          at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39)
                          at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50)
                          at java.lang.Thread.run(Thread.java:534)
04/12/02 19:29:56 - ***********************************************************
Dec 2, 2004 7:29:56 PM   Info: End of log messages of the target system.
Dec 2, 2004 7:29:56 PM   Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Dec 2, 2004 7:29:56 PM   Error: Aborted: development component 'PegasusServerApp'/'isenergy.de'/'localhost'/'2004.12.02.19.02.19':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file PegasusEJB.jar
null. Reason:
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Dec 2, 2004 7:29:56 PM   Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Dec 2, 2004 7:29:56 PM   Error: -
At least one of the Deployments failed -

Hi again!
It appears that the problem is related to some resources within the PegasusEJB.jar: almost all resources like .xml files are neatly located unter rsrc/de/isnenergy/pegasus/... where they can be found by their corresponding classes. The classes have packages like de.isenergy.pegasus.... . Some resources, however, are located under rsrc/icons and there is no package icons. (don't ask me how they are found)
this may be the reason! When I remove the icon-resources, I can deploy my EAR.
agree?
Jan-Peter

Dec Premiere update mxf file problem

Similar Messages

Maybe you are looking for