Premiere Pro CC 2014 8.1.0 crashing constantly

I am relatively new to Premiere.
I've been working on a short commercial for about 10 days with a variety of source material, effects, etc.
Ran into the following situation over the past few days... the program works for a few minutes after opening... 
then after doing an edit or two and rendering a section or two, the program is unable to play back..or respond at all.
I am forced to close the project. And when I try to quit Premiere, it won't quit and I'm forced to force quit the program and start over again.
I'm pretty frustrated at this point as I've hardly been able to get any real work done on this project for a few days.
Macbook Pro 2012, 2.9Ghz Intel Core i7, Mavericks 10.9.5, 8GB RAM, ext USB 3.0 7200RPM hd...
As I mentioned, I'm new to this program. More of an audio guy.
I know there are so many potential contributing factors.
Any pointers would be greatly appreciated.

This seems to be an issue for me A LOT too. I can't keep Premiere open for more than 2 minutes at a time right now. The Customer Service rep from India did a "Team View" on my computer before and after 45 minutes finally fixed the issue. But I can't seem to get a hold of customer support right now. I hope you and I both find a solution soon. Good luck!

Similar Messages

  • Adobe Premiere Pro CC 2014 keeps lagging and crashing

    My Adobe Premiere Pro CC 2014 keeps lagging and crashing to a point where I cannot do my job. When I open my premiere file, I can work on my timeline for maybe two or three minutes before it lags, freezes, and then finally crashes. I'm at a loss of what exactly is causing my problem because I edit primarily H.264 files and my sequences are not complex in any sense of the word. I've been dealing with this for days and I cannot seem to find a solution. If anyone has any advice please let me know because I am desperate. Thank you.
    Specs:
      Model Name: Mac Pro
      Model Identifier: MacPro6,1
      Processor Name: Quad-Core Intel Xeon E5
      Processor Speed: 3.7 GHz
      Number of Processors: 1
      Total Number of Cores: 4
      L2 Cache (per Core): 256 KB
      L3 Cache: 10 MB
      Memory: 16 GB
      Boot ROM Version: MP61.0116.B05
      SMC Version (system): 2.20f18
      Illumination Version: 1.4a6

    Hi Dana,
    Can you go to File-Project Settings-General and change the video renderer to Software Only Mode.
    Check if that works or not.
    Are you using any third party plug-in's for Premiere Pro?
    Thank You
    Arjun

  • I am using 4K Footages for editing in Premiere pro CC 2014, but its getting crash in between at every 15 to 20 mins. Kindly suggest how can it be solved, does any plugins or settings needed to edit 4K footages? Also would like to mention that footages fra

    I am using 4K Footages for editing in Premiere pro CC 2014, but its getting crash in between at every 15 to 20 mins. Kindly suggest how can it be solved, does any plugins or settings needed to edit 4K footages? Also would like to mention that footages frame rates are 29.97 and i have set timeline to 25 FPS is requirement by client. kindly revert. Thanks

    Thanks Richarad ..It has solved the problem but still crashes some times .As the programme has the break (bumper)after every five minutes ,i hope it will not compress bumper time too after export.

  • Premiere Pro CC 2014 playback freezing and crashing with new iMac i7

    Using Premiere Pro CC 2014 and having constant playback freezing and software crashes on a brand new iMac i7.
    Here are the specs:
    iMac i7 4.0GHz 5k Retina
    32 GB Ram
    AMD Radeon R9 M295X 4GB graphics card
    512GB Solid State Drive
    I was on chat yesterday with an Adobe tech. Although playback/render settings show the OpenCL option to utilize the AMD graphics card for processing, I was advised to switch to "Software Only" as that card is not supported yet. I had to re-render my 45 minute documentary (which doesn't appear to be any faster than it was on my old 2011 iMac by the way) and it still has the same issues.
    So frustrating? Anyone else experiencing this? Any advice? I hope I didn't just buy this "super machine" in vein.
    Thanks,
    Jason

    Hi All,
    Taking some tips from Kevin Monahan. If you haven't already gone through this list please do so.
    Sign out from Creative Cloud, restart Premiere Pro, then sign in
    Update any GPU drivers
    Trash preferences
    Ensure Adobe preference files are set to read/write
    Delete media cache
    Remove plug-ins
    If you have AMD GPUs, make sure CUDA is not installed
    Repair permissions
    In Sequence Settings > Video Previews, change the codec to one that matches your footage
    Disconnect any third party hardware
    If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
    Disable App Nap
    Reboot
    Best,
    Peter Garaway
    Adobe
    Premiere Pro

  • Premiere Pro CC 2014 freezes frequently and crashes

    Since upgrading from Premiere Pro CC to Premiere Pro CC 2014 my projects crash in regular intervals, which didn't happen before.
    All my settings and presets have been pulled across fine, but suddenly relatively slim projects get stuck during editing, rendering or exporting. The progress bar stops, the preview screen freezes and that's it. I can only radically crash the sucker. I did delete all preview files and it improved marginally... only that the time until it froze took a few minutes longer.
    I'm on 64bit high-end Windows 7 machine and have never had this problem with previous versions of Premiere Pro.
    Very frustrated.

    @bendubb37: I'm not the least bit defensive about complaints regarding the stability and general quality of the program. As a quality engineer on the Premiere Pro development team (not a member of the technical support team), I'm quite familiar with many if not most of the problems--both those that are legitimate bugs in our code and those that result from conflicts with OSes, hardware, codecs, other programs, etc. I genuinely appreciate having customers come to this forum to report issues they're having. Such reports sometimes help us identify bugs that we weren't aware of, and they always help us to prioritize bugs to fix based on which issues are biting the most customers and having the greatest impact on their productivity and satisfaction. And naturally I understand the frustration and anger of customers who are wrestling with one problem or another in the program.
    What I took issue with was cutco's derision of a perfectly valid troubleshooting step recommended by a technical support agent and his assertions that a) "This community is kind of useless" and b) "Adobe is absent." Cutco graciously acknowledged that he had let his frustration get the best of him.
    As to the oft-repeated claim that CC2014 is buggier and less stable than prior versions, I submit that it's a problematic claim to substantiate, at least based on anecdotal personal experience or taking the pulse of this forum & others. There's no question that some customers who enjoyed smooth sailing with an earlier version are experiencing problems with CC2014. But I know for a fact that this release included fixes for a significant number of bugs, including crashers, so many other customers who were having problems with earlier versions are now cruising along without a hitch (or at least without those old, fixed hitches). Alas, those people are not frequenting the forum to sing the praises of CC2014.
    My point here is simply that claims about the relative quality of one release versus others can be a distraction from the more important--and much more concrete--fact: a certain number of customers using CC2014 are having Problem X, which didn't happen in CC7.x. The more we can learn about Problem X--and the more clearly we can differentiate X from Y and Z, which may manifest similarly--the sooner we can nail down the cause.
    Don't get me wrong: there is an objective trajectory of a product's quality. Unfortunately, even when you have a large pool of data in front of you, the trajectory doesn't lend itself to quantification. You can't simply count the number of deferred bugs, for instance, because not all bugs are equal. You can't even go by the number of known crashers because some are extreme edge cases while others lurk in the path of mainstream workflows. That said, for people like me who spend our working lives trying to deliver the highest quality possible, the trajectory our program's quality is a common topic of discussion.

  • Premiere Pro CC (2014) - 8.0.0 crashes at every turn

    Hello,
    I am a long time Adobe user (both print and video production specialist).  I was very excited to dive into the new Creative Cloud update.  The only program I started to use since the 8.0.0 update is Premiere Pro.  Since the update, I get a wide variety of crashes.  The list below are examples of crashes I am encountering.
    The entire (7.2.2) CC suite ran flawlessly before the (2014) update.  I never had these problems before!  I'm afraid to open the other (2014) programs to find out they wont work properly.
    1) The open and close crash (Generic message telling you it has to close due to a problem).
    2) I made three edit changes, then went to, 'render selection' and got a generic crash report with it closing the program.
    3) When opening a project, it is never the way I left it, meaning the sequence I was working on needs to be re-opened and re-rendered from my sequence bin.
    4) Crashes when watching a playback after timeline is rendered.
    5) During a playback the viewer will freeze on its current frame but the playhead and audio keep moving as if nothing is wrong.  Then a minute later it will show the correct frame the playhead is on and then you get the crash notice and it closes.
    I have already un-installed and re-installed it.
    My system Specs are:
    iMac OS X
    27-inch, Mid 2010
    Processor  2.8 GHz Intel Core i5
    Memory  16 GB 1333 MHz DDR3
    Graphics  ATI Radeon HD 5750 1024 MB
    Software  OS X 10.9.3 (13D65) Maverick
    Dual Monitor display
    Any suggestions!?!?! Help!Kevin Monahan

    I wanted to let people know that this has helped very much.  There are still slight issues here and there but not big enough to halt a project.  There probably is something similar for Window users.  Big Thank you to John T Smit and Kevin Monahan.
    For MAC users do the following (posted by John T Smit above):
    -next link says After Effects, but check YOUR permissions !!!
    -http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
    -Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
    -more Mac 10.9.3 https://forums.adobe.com/thread/1491469
    -Enable Mac Root User https://forums.adobe.com/thread/1156604
    -more Root User http://forums.adobe.com/thread/879931
    -and more root user http://forums.adobe.com/thread/940869?tstart=0
    John or Kevin, are there similar instructions for people on the Windows OS? 
    Thought it would be nice to have for Window users who come across this thread such as Life. Documentedencountered.

  • Updated to Premiere Pro CC 2014 - keeps freezing and crashing

    Everything was fine and dandy until I updated to the latest version last week. Now every 10 minutes, or sometimes randomly, my timeline will freeze on a frame and I'll have to restart the program. Other times, it just crashes and gives me the "quit unexpectedly" message.
    What's going on and how do I fix? I'm on a Macbook Pro Retina 13" late 2013, 2.8GHz Intel Core i7, 16GB memory, Intel Iris graphics, OSX10.9.4.

    I am having the same issue.
    Adobe Premiere Pro CC Crash on Splash Screen

  • Premiere Pro CC 2014.2 has been crashing within 10 minutes of opening a project. Usually when scrolling, but not always. What can I do?

    Sometimes it does it without scrolling, just on it's own. 
    PC. HP Z800 16 GB Ram Dual quad core Xeon  NVidia Quadro 3800 card.
    I started this project last week and went an entire day without a crash.  Since then the only major change to the computer was installing Quick Books 2015.
    Sometimes when I reopen PPRo after the crash, I get an error message that says Mercury GPU hardware not found, opening in software only mode, but that is maybe one time out of five.
    Any thoughts?

    Hi Chris,
    Chris Skrundz wrote:
    Sometimes it does it without scrolling, just on it's own.
    PC. HP Z800 16 GB Ram Dual quad core Xeon  NVidia Quadro 3800 card.
    I started this project last week and went an entire day without a crash.  Since then the only major change to the computer was installing Quick Books 2015.
    Sometimes when I reopen PPRo after the crash, I get an error message that says Mercury GPU hardware not found, opening in software only mode, but that is maybe one time out of five.
    Any thoughts?
    You may want to update your GPU drivers.
    Quick Books is less suspect, but you might try uninstalling it temporarily if updating GPU drivers does not help.
    Thanks,
    Kevin

  • Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

    Running out of options and ideas...
    Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode.  The crash is a software crash, Windows continues to run fine.
    I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc.  https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
    Windows event is not that helpful to me:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00007ff5ecb4de40
    Faulting process id: 0x1dc8
    Faulting application start time: 0x01d04a503cd82df2
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: unknown
    Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
    Faulting package full name:
    Faulting package-relative application ID:
    I have wiped adobe off the machine and reinstalled - same problem.  I have tried projects that crash the machine on other machines and it works fine.
    The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
    Spec:
    5K iMac running bootcamp and Windows 8.1
    Intel Core i7-4790K @ 4.0 GHz
    32 GB ram
    1TB SSD
    AMD Radeon R9 M295X 4GB GDDR5
    I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great.  Guess it was my time for a problem, but I'm open to new ideas to try...
    Finally - I hope someone from Adobe reads this.  I have spent 2 nights on the phone with support.  The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem).  Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
    Thanks in advance to anyone with ideas on things to try,
    Cheers!

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Premiere pro cc 2014 crashing my system

    I have a new Mac book pro (2014) 16 gbs ram.. everything is upgraded to max. downloaded the new premiere pro CC 2014. and it's crashing my system every time.
    it takes about 4 mins. with the spinning ball. Then all the processes and plugins load in.  Then it says "premiere pro couldn't find any capable video play modules. Please update your video display drivers
    and start again" WHICH IS FREAKING IMPOSSIBLE SINCE I AM ON A MAC BOOK PRO. So sick and tired of companies not working out glitches in this crap. Could someone please help. I am so
    angry and frustrated here.
    Sean

    Somewhat figured it out and extremely frustrated.
    I created another new user with administrative privileges. When i did this i got AE CC 2014 and Premiere Pro CC 2014 working. However, they will not work in my regular main account which has
    administrative priviledges.  On the phone with ADOBE they told me that it was a permissions issue and that it was Apple's Problem. Which I CALL B.S.!!!
    I tried to repair permissions in disk utility knowing full well that it wouldn't fix the issue. How on earth would apple know what the permissions errors in folders or files are for Adobe products!!
    I was very angry and upset with the Adobe technical support for this issue.
    On the new mac pro i am using i was able to create the new administrator account and erase the old administrator account since i have 0 documents or old data that i have on it other than programs.
    However, on my mac pro. I have well over 15 years of data on it including 100 GB of music, etc... that i simply can't just erase away.  Not too interested in working on 2 different accounts either.
    Not sure what to do now and i am extremely frustrated.

  • Premiere Pro CC 2014 Crashes During Media Export

    Hi, I have diligently applied several of the fixes listed here:
    Re: Premiere Pro CC 2014 freezes frequently and crashes
    However, Premiere Pro CC crashes at about 10% of the video export -- it gets through the audio stuff as far as i can see.

    yeah, checked out the article.
    my computer is not shutting down. premiere is crashing. the media exporter is crashing.
    it gets through the audio then it crashes during the video processing.
    i even tried to hit pause every 2 seconds.
    a test exports fine from premiere 6.0, but i am concerned that 6.0 might crash if i rebuild the whole project.
    hmm i have an idea.
    obviously i would much rather the software worked.

  • Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

    This is a project that I have been successfully encoding in short segments until now.  Now when encoding, session runs about 10-15 minutes and then ends without error messages. 
    Removing effects and changing to Mercury PB Engine SW did not help. 
    Also tried disabling metadata as suggested in another forum. 
    When CUDA used, logged as "Encoding failed."  When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
    Premiere Pro Build 8.1.0 (81)
    Media Encoder Build 8.1.0.122
    Windows 7 Professional
    Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
    8 GB RAM
    NVIDIA GeForce GT 610 (9.18.13.3788)

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

    Hello there,
    Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
    I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing  problems with the New Mac Pro. Is that true? Or is there other issue?
    Thank you and looking forward to hear back,
    Maruf

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Adobe Premiere Pro CC 2014 has stopped working

    Today I've encounter an issue with Adobe Premiere Pro CC 2014 where it will crash on launch, with the error statement, Adobe Premiere Pro CC 2014.0 has stopped working. I've tried uninstalling, reinstalling, rebooting, uninstalling and reinstalling graphics drivers, with no avail. I was even connected to a tech support member who was helping me when the program crashed and now I can't reconnect with that member. I'm at a loss of what to do but any help would be greatly appreciated
    My Computer specs are:
    AMD FX-8350 Eight-Core Processor 4.00Ghz
    8.00 GB Ram
    Nvidia GeForce GTX 570 -driver GeForce 340.52 (7/29/2014)
    Windows 7 64-bit.

    A variety of issues can cause PPRO to crash on launch. Here are some of them:
    a problem with the Preferences, or some other pref-related file in the Profile-<USERNAME> bin.
    the graphics driver
    having an integrated graphics chip as well as a graphics card. Disabling the integrated chip often fixes this.
    having Nvidia CUDA drivers installed on a system with an AMD card
    third-party plug-ins
    a problem with the cache files.
    a problem with the project file (if you're loading a project...)
    folders that Premiere writes to being set to read-only
    the user not having administrator rights
    a conflict/incompatibility with some OS setting
    a problem on the licensing/authentication side.
    A log file might help identify the cause of the crash. Please right-click 'My Computer', select "Manage," look under 'Event Viewer->Windows Logs->Application' to see if there's an event there from Premiere Pro. If so, copy the contents of that log and paste them here.

  • Premire Pro CC 2014 and Media Encoder Crash During Launch

    Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.0.169
      Application Timestamp: 536f4f89
      Fault Module Name: ImageRenderer.dll
      Fault Module Version: 8.0.0.169
      Fault Module Timestamp: 536f2c18
      Exception Code: c000001d
      Exception Offset: 00000000001f5382
      OS Version: 6.1.7600.2.0.0.256.1
      Locale ID: 1033
      Additional Information 1: 0b2d
      Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
      Additional Information 3: fa9f
      Additional Information 4: fa9f59f642d335ee71c6667e52000d39

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

Maybe you are looking for

  • Installation problem with adobe elements on Mac

    Nothing shows up when I insert disc 3 of adobe photoshop elements into my Mac. When I go to DVD player and push play it says "supported disc not available". I don't know what else to do. I have tried turning my Mac on and off and have switched the si

  • Error in the SAP ERP 6.0 Installation

    Hello everybody, i have a error in the phase 43 of 46 in the ERP 6.0 Installation. Here are my UTL_configure_usages.log , i hope everone can help me by the solution. It´s my first time at the Installation of a SAP System. +Path   : Exception : The Us

  • How to install winRT 8.1 app on tablets without a domain?

    I created an app and need to install it on 4 win 8.1 tablets. I created an package through vs->store->no to upload to store. I tested it on the tablets using a temp Microsoft developer license. I read a lot and found out that are 2 main ways to deplo

  • Backup is asking for a dvd - why when don't have dvd burner?

    When trying to use the backup feature of version 8 I'm getting the message, "There is a file whose size is bigger than that of a blank CD. You need to insert a blank DVD." I don't have a dvd burner and can't find a file bigger than a cd.

  • Application role

    I create application roles and assign them to an enterprise role at jazn-data.xml in jdeveloper. However, after deployment I cannot find these application roles. But I can find the enterprise role.