Importing Uncompressed AVI Caused PGC Internal Software Error During Burn

When I export from PPro using uncompressed AVI and import that into Encore, the DVD burn blows up with a PGC internal software error. Somebody told me to export from PPro using DV-AVI instead of uncompressed, and that should fix things. Since that's going to take a day or so (this is a big/77 minute project) to export/import/transcode, I'd like to know why Encore doesn't like uncompressed AVI, and what's the difference between uncompressed AVI and DV-AVI? The DVD project passes validation without error, imports the assets without a problem, and the preview works fine for the entire show. Yet the build/burn fails!

Trenton,
Rather than uncompressed, you could try a lossless codec like
Lagarith
or
version 2.1.1 of HuffYUV
. Try Lagarith first if you want to experiment; HuffYUV can sometimes throw Encore for a loop if the clip length is longer than about 10 - 12 minutes.
That said, I have to agree with Harm - the MainConcept DV codec used in Premiere Pro is so good that a single generation loss from recompression for DV source footage (and that only for altered frames) is trivial and will not be noticed by your audience. It probably won't even be noticed by you unless you spend hours comparing individual frames. And who has time to do that? :)
-Jeff

Similar Messages

  • PGC Internal Software Error During DVD Build

    After weeks of editing my 77-minute feature and days of DVD authoring effort, it's more than a bummer to see this appear during the final DVD build process:
    PGC "Analysis" has an error at 47:21:29 internal software error %0 line . . . PGC Info; name=Analysis, ref FPGE time 47:21:29.
    I verified the project before the build and there were no errors/warnings. I tried several times and get the same error at the same spot; I tried creating an image and the same error takes place at the same spot. I previewed the entire thing in Encore and everything plays/sounds great. All the footage/sound was imported as two large, uncompressed DVI files exported from PPro 2.0. The video is 16:9, 24p. Most of the sound came straight from the source video feed, except for two WAV files containing theme music.
    What can I do to get this production finished-- of course, I am behind schedule...

    So, finally I've found the source of the problem and a workaround!
    First the source:
    when Encore has to transcode a video it must corrupt the file, because it's the transcoded file that causes the problem, I tried this by importing a transcoded file into Encore 1.5 there it came with the same error.
    Now the workaround, ok maybe it isn't quite a workaround but it's a way to go:
    What I did was: I built my project new in Encore 1.5, because Encore 2.0 has a problem importing the videos by me, but if you would just import the videos in 1.5 and let 1.5 transcode them so that all of them would fit on a DVD you should be able to import the transcoded files in CS3 and it should work, no guarantee.
    Other possibility: try opening your project in encore 2.0 and re import your videos there and let 2.0 do all of the transcoding, that might work too!
    But for certain: don't let encore CS3 do all the transcoding!
    I'm working with PAL files I don't know if it will be the same by NTSC, but it's worth a try!
    If anybody feels like reproducing the bug, here is the way to do it:
    Make a project in Encore CS3 and import Videos encoded by premiere as MPG2-DVD (I think: .m2v .wav) and set the transcoding options to automatic, encore should have to transcode the files. Then let encore make the DVD, at some point you should get that nice PGC error!

  • Internal Software Error during burn to DVD in Premier Element 9

    During a burn to DVD in Premier Element 9 I encountered an internal software error (.\Vobulator\BlockPlanner\BlockPlanner.cpp line 215). What does this mean? What is the solution?

    You'll be better served by posting your question in the dedicated Premiere Elements forum:
    http://forums.adobe.com/community/premiere_elements?view=discussions
    Ken

  • Adobe Premiere 13- internal software error during disc burn

    Hello,
    I have a MacBookPro, 10.9.3 2.66 GHz 8gb
    I am using Adobe Premiere 13 to burn a Elementary School Memory DVD.
    I finished the creative portion of my dvd project, rendered the project and then burned a dvd successfully. Upon playing it, realized I made a creative error in my menu (Thumbnail photos didn't match the titles), so I fixed my markers and solved that problem. I did not re render the project and went straight to Burn another DVD. At 98% completion I got the following error.
    internal software error /DVA/premiere/elements/molecules/pre12/pre-mediacoreCS7/E
    Do you think the cause for the error due to my failure to RE Render the project? Any ideas?I am a newbie to Premiere.
    Thank you,
    Jean

    First, see if you are able to burn your DVD files to a folder on your hard drive rather than directly to a disc.

  • Internal Software Error while Burning to DVD Disc

    I am using PE3 and during the latter part of the burn, the process stopped and the following error message was displayed.
    .\Vobulator\Block Planner\Block Planner.cpp.line215
    Had no trouble the first time. Have tried burning to both +R and -R. Would appreciate any help, as I don't understand this message, or what I can do about it. Thanks

    I assume that you are using Encore CS4 for this Project. Is that correct?
    Now, let's look at your SlideShows. Is there any chance that the Audio is longer than the Video (the slides and their Duration), by even one Audio Unit? If so, then extend the Duration of the Video by a tiny amount. I do my SlideShows in PrPro, and always have about 2-3 Frames more Video, than Audio. I find Encore's SlideShow feature to be rudimentary at best. Also, make sure that your still images have been resized to the Project's Frame Size, outside of Encore. This would be true if you were doing SlideShows in PrPro too.
    Last thing, Encore can have issues with MPEG Audio. This can either be in muxed AV files, or Audio streams, like MP3. In general terms, MPEG is not even an optional Audio stream for DVD-Video. In PAL-land, it is "optional," but that is falling out of favor. The exception is the DD AC3 Audio stream, but it is unique. If I had MP3's, I would convert to PCM/WAV 48KHz 16-bit outside of Encore, and NOT use anything MP3. If I am doing the Transcoding in PrPro, prior to Import into Encore, I always do so as elemental/elementary streams, i.e. one Audio-only and one Video-only file. I then Import the Video-only file as a Timeline, and the Audio-only file as an Asset. Once into Encore, I just drag the Audio-only file to the appropriate Timeline, where it snaps into place.
    Oh, one more thing: ganging Assets on the same Timeline can be problematic, and for some of the things mentioned above, like slightly longer Audio, than Video, plus gaps. I always have one Video Asset per Timeline, and then use Play Lists for my navigation.
    Good luck, and hope that this helps.
    Hunt
    PS - if this is related to Encore, there is a great forum for that program, with some excellent subscribers, like Jeff Bellune and Neil Wilkes. You can get some very good and specific responses from them. Here is the Encore Forum link - see you there.

  • Internal Software error PGC  for encore CS3 !!! solved  !!!

    Almost everybody here knows the next error:
    PGC "timeline name" has an error at xx:xx:xx:xy internal software error : %0, line timeline name - PGCINFO: name= timeline name, ref=BPGC, time=xx:xx:xx:xy
    Where the y in time stands for the length of the timeline minus 2 frames. The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
    It kept me awake for weeks and after reading this forum several times and comparing encore CS3 with encore 2.0 filenames I found the solution.
    This Error is a bug in encore witch has nothing to do with blank filename spots and sonic coding or codecs or planning your workflow with a pencil but pure with the combination Adobe Premiere Pro CS3 and Encore CS3.
    This is what generates the problem:
    In Adobe Premiere Pro CS3 you build project with video, sound and chapters. Then you export the project via the Media Encoder not Multplexed.
    Premiere CS3 then creates the following files:
    filename.M2V (video file mpg)
    filename.AC3 (audio file ac3)
    filename.M2V.XMPSES (an adobe file with preview info and chapter pointers)
    filname.XMP (??)
    It is the .M2V.XMPSES file witch creates the PGC error. If you use the MULTIPLEX DVD option then ADOBE will not create the .M2V.XMPSES file so there will not be an error. This trick mentioned by ADOBE and many others is just to go around the bug instead of solving it. Also with multiplex you have just one sound track. I use two sound tracks like 5.1 and a 2.0 track witch you can choose in a menu.
    Some people say it is the blank spots. Also not true. They have probably just erased the blank spots of the M2V file and forgot the .M2V.XMPSES file.
    When you just delete the .M2V.XMPSES file and then open the M2V and AC3 file in Encore as a new asset, make a timeline and menu's and the project will built and burn. Only if you delete this .M2V.XMPSES file Encore takes a longer time to import the M2V file and will be without the chapter points.
    Almost everything else will work like menu with sound and even a movie background (use M2V files). Only the motion buttons in a menu still wont work unless you use a black background !?!. Haven't figured this out yet. Only solution for this is use Encore 2.0. In this older version also the motion buttons will work without error's (everything else also so why buy CS3??)
    Here is what you must do create a DVD without errors:
    -Create a project in Premiere Pro, even with chapters.
    -Write down all chapter points (minutes:seconds:frames)
    -Create two new unique maps in explorer for example D:DVD1 and D:DVD2
    -Export in Premiere with Media Encoder without the Multiplex:DVD but with NON to the D:DVD1 map
    -Copy from D:DVD1 only the M2V and AC3 files to D:DVD2
    -Start up Encore DVD CS3 or 2.0
    -Create a new unique project in Encore for example "DVD" and save this in the map D:DVD2\
    -Then use Save-as (under file) and pinpoint to D:DVD2\dvd to be sure that all Encore's files are placed in this folder.
    -Select M2V file and make new timeline.
    -Make chapter points (you wrote down the points, did you?)
    -Create menu's, even with sound (AC3) and movie background (M2V)
    -Then render project if you have used a video for menu background
    -Finally Built and burnnnnnn!!
    -If you like to use motion buttons in a menu then use Encore 2.0
    I have double checked my work flow and it really works. I have built a project and burned with success Then I deleted the timeline and the M2V file. Copied the .M2V.XMPSES file in the used folder. Re loaded the M2V file in encore (this time much faster! and with chapter points). Tried to built and burn and back was the error. Also this happened in in Encore 2.0!!
    Hope that this will solve the PGC error once and for all !!!
    Marcel W
    system:
    acer aspire AMD 64 3800+
    2 GB
    250 GB hard drive for system
    750 GB hard drive for movie
    software Adobe Encore 3.0.1.008, Premiere PRO 3.2.0, Photoshop CS3 10.0, All upgraded
    NERO 7
    No Internet

    > Where the y in time stands for the length of the timeline minus 2 frames.
    This can actually vary, and so far at least, I don't think we've seen a pattern as to type of pgc error based on how many frames from the end it reports.
    > The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
    Number of menus is not relevant; the iteration of the first letter is more related to subsequent occurrences of the error. In my current tests it did not always update; they may have been too similar.
    > This is what generates the problem...
    Well, the problem does not occur every time you do what you describe, any more than it occurs every time spaces are left in the file names. What you have is, as some other suggestions, a workaround. Thats not bad, and I wonder if you are onto something as to what is contributing to the problem.
    So, on to the interesting part whether the xmpses file, or at least what Encore is doing with it, is contributing something. I took an old test project that throws the PGC error and did some experiments.
    Background. I am a user who does get the pgc errors regularly, but not always. Creative Suite Production Premium, with PPro CS3 3.2.0 (374) and Encore 3.0.1.008. Pentium 4 2.8GHz 2G RAM, XP SP3, Multiple drives, Nvidia GEforce4 MX440 i.e. an older system. I have lots of stuff loaded and running, including virus protection and firewall, so there are any number of potential conflicts. But I get no crashes, and only one problem other than the pgc. (PPro and Encore monitor windows do this diagonal thing I suspect the display card, but the drivers are up to date. Maxing and then back to fit fixes it.)
    If you want to attempt to replicate my studies, here is a link to my problem clip and the first Encore project I describe.
    http://www.videoandcomputer.com/test/pgc_test.htm
    This project involves a very short AVI export from PPro CS3 - just over 8 seconds - called pgcbad_clip1.avi. Just to answer any question, the source is dv camera capture, and the source and avi export I use are dv avi type 2. There were no effects added on the timeline.
    Test 1: Create a project in Encore CS3. Use the sunset menu and delete all the buttons except "play all." Import the avi as a timeline. Set the timeline end action as "return to last menu" and set the button link to the timeline. Auto transcode. (Project settings are 8mbps max and a3c.) Check project shows okay; there is never a problem with that. Build to a DVD folder in a new folder. This project throws the pgc error.
    Test 2: Now create a new Encore project in a new folder. Use the same process, except import as timeline the m2v and a3c files from the first run. (I.e. if the clip is pgcbad_clip1.avi, in the test1 project folders, there is a folder called pgcbad_clip1.avi that has 6 files.) Note that in the folder they are imported from is an xmpses file from the first project's encore transcode. The build again fails with the pgc error - same frame, etc, but I really think the frame number doesn't matter.
    Test 3: Now create another new Encore project in a new folder. Use same process, but before importing the m2v and a3c as timeline, delete the xmpses file. Drumroll...... Build succeeds!
    Go figure.
    This is not the repeatable bug option weve been looking for, but based on a clip that always fails, it does demonstrate the odd event of deleting the xmpses file as a workaround. I wonder if that will give adobe something to work with.
    Can anyone else get my clip to work/not work in a straight project?
    Test 4: Just to answer the question since the avi file fails here, will the elemental option succeed? I exported elemental m2v and wav from PPro, used the same project process, and transcoded the wav. That build also works! I have seen this work both ways. I have had projects where the elemental failed, and an avi export worked. I do believe the elemental options work more consistently. But my project that I completed yesterday used all avi exports, animated buttons in the submenu, - no pgc error.

  • CS3 Encore -- Internal Software Error at (specified TC); keeps DVD from building

    Regardless of whether I export directly to Encore or export as .avi or .wmf and then import to Encore, this error follows clips and not others.  Usually the TC stated in the error message is about 3 seconds from the end of the clip.  Sometimes I can work around by shortening the clip in Premiere and re-exporting it, but not always.  When I shorten the clip, I usually get the same error message, but now the TC is approx 3 seconds from the new end of the shortened clip.
    The clip names are not overly long and I have no blanks in them.  The actual error message is:
    PGC "<filename>" has an error at <TC>.
    Internal software error: %0, line <filename> -PGC Info: name = <filename>, ref = Gpgc, time = <TC>
    Again, things I have tried which usually do not help are: renaming the clip; shortening the clip; exporting as different file type and then importing to Encore.
    Anyone who can give me a silver bullet for this will be my new best friend!
    Thanks,  Kirk

    This part is for CS4, but might help
    Encore CS4 Roxio component problem http://forums.adobe.com/thread/400484?tstart=0
    More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
    http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
    Also
    Long File Names Cause Crashing http://forums.adobe.com/thread/588273
    And #4 Here http://forums.adobe.com/thread/666558?tstart=0
    And This Message Thread http://forums.adobe.com/thread/665641?tstart=0
    Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/

  • PPro6 to Encore "internal software" error

    I encoded in PPro6 and then imported an mpeg2 project as a timeline from PPro6 into Encore.  When I try to burn a DVD, I get an error message: PGC "" has an error at 00;00;00;00.  Internal software error: 50, line "" Info: name = "", ref= Bpgc, time = 00;00;00;00;00.
    The project was fully rendered in PPro.  I've re-exported 3 times, and it happens every time. 
    I did a search on the Forum, and found one other person who had this problem, but their problem turned out to be with their audio.  My project has no audio at all.  Just video.
    Thank you for any help/ideas/suggestions you may have! I'm totally flummoxed.

    Stan Jones wrote:
    The .xmpses file is an xml (type) file.
    Rename the file .xmpses.old and the .xmp renamed as .xmp.old (I don't recall for sure whether there was ever any benefit to renaming the .xmp file. We want to maximize the chances that it works, so rename both.)
    Can I just say Stan I am so so grateful for this post. So easy to do and solved my problem!!! I was beyond fed up with the whole thing. After having such problems with Dynamic Link causing slight flickering in my videos I have tried to go back to Exporting with my own settings for Encore in CS6 but found it caused so many more problems than it ever did in previous versions of the programmes. I tried exporting the sequences in so many different ways, different bit rates, including Encore chaptering before Encore and even nesting. Had so many different errors like 52102, line 332 and this PGC error was the final one and my biggest problem. Cannot believe how simple it was. I normally chapter within Encore anyway so changing a little file name of the other 2 connected files of my sequence really was no bother at all.
    I honestly think this is the answer to many of the problems that I have had in Encore as the errors although in different forms, more often than not, seem to be chapter related.
    it is now 1.45am and because of you I can now go to bed to get up and film another event in the morning. CHEERS! (don't worry I'm a girl lol)

  • Internal Software Error: %0

    I get the following error message after Encore 2.0 prepares the slideshows and goes to the next step. All of the video material is prepared and, the progress window is in the middle of "Planning Audio for movie". Any suggestions for a fix?
    Adobe Encore DVD
    PGC "Yosemite Valley" has an error at 00;00;20;04.
    internal software error: %0, line Yosemite Valley - PGC Info: name = Yosemite Valley, ref = Ipgc, time = 00:00:20:04
    OK
    Thanks.

    So, finally I've found the source of the problem and a workaround!
    First the source:
    when Encore has to transcode a video it must corrupt the file, because it's the transcoded file that causes the problem, I tried this by importing a transcoded file into Encore 1.5 there it came with the same error.
    Now the workaround, ok maybe it isn't quite a workaround but it's a way to go:
    What I did was: I built my project new in Encore 1.5, because Encore 2.0 has a problem importing the videos by me, but if you would just import the videos in 1.5 and let 1.5 transcode them so that all of them would fit on a DVD you should be able to import the transcoded files in CS3 and it should work, no guarantee.
    Other possibility: try opening your project in encore 2.0 and re import your videos there and let 2.0 do all of the transcoding, that might work too!
    But for certain: don't let encore CS3 do all the transcoding!
    I'm working with PAL files I don't know if it will be the same by NTSC, but it's worth a try!
    If anybody feels like reproducing the bug, here is the way to do it:
    Make a project in Encore CS3 and import Videos encoded by premiere as MPG2-DVD (I think: .m2v .wav) and set the transcoding options to automatic, encore should have to transcode the files. Then let encore make the DVD, at some point you should get that nice PGC error!

  • Encore CS3 - Build error: "internal software error"

    Hi All,
    I'm fairly new to Encore but I've spend a lot of time figuring out how it works to the point that I think I've got it (menus, links, etc). Here's my problem: 
    I've exported a video with chapter points from Premiere CS3 into Encore (no problems). I've created all the menues and links to their respective chapters in Encore (no problems). I "checked" the video. Clean - no errors. I've "previewed" the vidoe in Encore - works perfectly. However, when I go to "build" the video, I get the following error in a pop-up window:
    "PGC "Master" has an error at 00;43;38:01. internal software error: %0, line Master - PGC Info: name = Master, ref = Fpgc, time = 00;43;38:01"
    "Master" is the name of the timeline that I have imported into Encore from Premiere.
    In this case, the time (00;43;38:01) is the very last frame of video.
    I've tried building both directly to a DVD burner  and just creating a DVD image. Both give me the same error. I've also tried the process by 1) exporting from Premiere to Encore directly and also exporting from Premiere to an MPEG2 file saved on the desktop and then importing that into Encore. Same error, however, the time of the error is different (in one case, the time of the error was some time during the timeline, not the end or beginning).
    Finally, a couple of weeks ago during my "learning process" I created a very simple timeline in Premiere with no chapters, exported to Encore and burned it. No problems with that.
    Oh, I'm running a 4 year old IBM T41 laptop w/ 2GB of memory. Although not the fastest, I haven't run into any h/w or s/w related issues...yet. I just doesn't scream.
    Can anyone provide help here? I'm STUMPED!!
    Thanks,
    Greg
    Redwood City, CA

    Some of us experience this pgc error (only in CS3) and have found no real solution.  There are a variety of workarounds.  I believe the most persistent version is the result of some unidentified combination of hardware and software.
    I believe that there are 3 variations, and they may have different implications: timelines (your issue), motion menus, and slideshows.
    Copies of projects and assets taken to a machine/user who does not experience the error work fine.  Some users have done a ridiculous amount of testing (I'm one), and some have declared a solution (I am not one, and believe there are probably multiple causes).  Since CS4 is out, I doubt we will ever see any further resolution, and, since the problem can not be reliably repeated in a new project with new assets, no "bug" was ever demonstrated.
    The first rule is to use flawless workflow.  (I don't find a link right off to Neil Wilkes' and Jeff Bellune's descriptions, but one example is never changing assets with Encore closed.)  But I have instances in which I was perfect (ha, ha), and the error occurred.
    In most instances, one or more workarounds can be used.  If you used a muxed file, do it again with demuxed.  If you used files that were in the same folder as the xmpses files (the files premiere creates to carry project/chapter info), delete the files other than the m2v and wav and reimport the asset as a timeline. (You will have to redo the chapter markers.  It is best to delete the old file from the project, and have the newly imported file renamed.  However, I have done it various ways successfully.)  If you have long file names with spaces, shorten and remove the spaces.
    You report one version of the error in which the time location is in the middle of the asset and not a frame or two from the end.  This is not common for the persistent version of this error, and raises the question as to whether there is an actual problem in your asset.

  • "Internal Software error: %0, line%1" when burning to DVD

    I recently upgraded my Premiere Elements 8 to 10 on my Dell laptop running vista.  I have a 24 minute slide show with some video clips in it and a menu.  I can output to avi, etc but cannot burng a DVD.  Everything looks normal until it gets to 99% of the burn then I get the error "internal software error: %0, line%1" and my DVD is ejcted and I have to cancel out of the burn process.  I've read various other similar problems on here but with slightly different error messages.  I've tried outputting an avi file, importing it and burning to DVD from that but get the same error message.  Any ideas?

    duuneistein
    I do not work for Adobe, nor am I affiliated with it in any way. No relatives there either. I come with no bias in my remarks to follow.
    I have Premiere Elements 11 on Windows 7 and 8.1 64 bit and decided to take a look at what you feel is a bug in Premiere Elements 11 when it comes to burn to disc DVD-VIDEO on DVD using MPEG2 and .mp4 source files.
    I took 1920 x 1080 @ 29.97 progressive frames per second (AVCHD.mp4) and 1920 x 1080 @ 29.97 interlaced frames per second (MPEG2.m2t) into a Premiere Elements 11 NTSC/DSLR/1080p/DSLR 1080p30 project, added menus, and did a burn to disc NTSC  DVD-VIDEO Widescreen on DVD-RW disc. The total duration of the Timeline was 5 minutes. And the burn dialog presented with
    Space Required 375 MB and Bitrate of 8.00 Mbps.
    I used Premiere Elements 11 on Windows 7 Professional SP1 64 bit for the above test. That computer has 8 GB of RAM installed and has about 900 GB of free hard drive space. The computer used an internal LG Blu-ray DVD burner for the burn to.
    I have never run into this "error internal software error: %0, line%1" in any version of Premiere Elements on Windows XP 32 bit or Windows 7, 8, or 8.1 64 bit in the past or tonight when I did this test.
    Whatever you are encountering I cannot confirm the built in existence of a Premiere Elements 11 bug in this regard. This would suggest to me that you should consider looking outside of Premiere Elements software as the cause target. If you would like me to cross check those MPEG2 and .mp4 sources that were involved in this error "internal software error: %0, line%1", I would be glad to do that for you if you send sample via a Dropbox link posted in your thread.
    But I suspect the answers are in the Windows Vista on which you are running Premiere Elements 11 or perhaps on some incompatibility or resource considerations between Windows Vista and Premiere Elements 11 (for that matter any version beyond your Premiere Elements 3.0/3.0.2). Unfortunately I do not have Windows Vista to incorporate into the testing. Do you have access to a Windows 7 or 8 computer?
    ATR

  • Internal Software Error:.\Vobulator\Titleplaner\CVOBUPlanner.cpp,Line 331

    I am very frustrated...
    I am using Encore CS3 on a relatively fast system with 2g of ram. I have successfully burned disc using Encore CS3 but it is a crap-shoot. Sometimes it works and half of the time I get this:
    Internal Software Error:.\Vobulator\Titleplaner\CVOBUPlanner.cpp,Line 331
    I am trying to burn a simple disc - nothing crazy. A static menu with three chapters linked to 3 points on a 1hour and 45minute avi file in the timeline. I organize it check the project and everything is fine. I start the build and it begins to transcode - everthing is still good. After the transcode it begins to organize the disc or something - and that is when I get the error message.
    I click OK on the dialog box and notice that the video in the timeline is now only 5 frames long and the audio is still there. (I thought the video had totally dissapeared but when I zoomed in for a closer look I realized it had ben reduced from almost 2 hours to 5 frames.) I look to the project window and it shows that the AVI has been transoded and it shows that time of the transoded file is normal length.... I am lost.
    Anyone have any ideas?
    Mat Cain

    Long File Names Cause Crashing http://forums.adobe.com/thread/588273
    And #4 Here http://forums.adobe.com/thread/666558?tstart=0
    And This Message Thread http://forums.adobe.com/thread/665641?tstart=0
    Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/
    Also, for Encore CS4 Roxio component problem http://forums.adobe.com/thread/400484?tstart=0
    More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
    http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS

  • Internal Software error %0 ref=Hpgc time 00:01:56:19

    Created a slideshow timeline in encore using the slideshow function. When building I get the above error. he time reference refers to the middle of a particular slide.
    I have tried the following:
    1. Removing the audio
    2. Removing the slide that stradles this time code
    3. Removing the pan and zoom effect
    4. Removing the transition
    but I still get exactly the same error at exactly the same time code. Any ideas? Originally rendered this in Premier CS3 and then imported the mpgs into Encore, but the dot crawl was appaling on the resulting dvd, so through I would try doing directly in encore.
    Any help much appreciated.

    Jeff Bellune, "internal software error: %0, line "title of project" - PGC Info:" #1, 21 Dec 2006 8:49 am

  • Get '500 Internal Server Error' during SIP INVITE - cause 44

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;
    mso-bidi-font-family:"Times New Roman";
    mso-bidi-theme-font:minor-bidi;}
    Get ‘500 Internal Server Error’ during SIP INVITE - cause 44
    Have you ever seen anything like this before?  It usually works, but intermittently, we see calls get rejected.  It somehow seems related to high loads on the router.  We reduced the occurrences by changing our code to throttle the number of SIP INVITEs we send, but this doesn’t scale well.  Once it occurs, the only way to clean it up is to do a shut/no shut on the voice-port associated to SIP INVITE.
    Any suggestions on how we can proceed to debug this issue?
    BACKGROUND:
    Cisco 2811 running (C2800NM-ADVENTERPRISEK9-M), Version 12.4(24)T3, RELEASE SOFTWARE (fc2)
    NAME: "2811 chassis", DESCR: "2811 chassis" PID: CISCO2811
    NAME: "9 Port FE Switch on Slot 0 SubSlot 1", DESCR: "9 Port FE Switch" PID: HWIC-D-9ESW
    NAME: "WIC/VIC/HWIC 1 Power Daughter Card", DESCR: "9-Port HWIC-ESW Power Daughter Card" PID: ILPM-8
    NAME: "Two port E1 voice interface daughtercard on Slot 0 SubSlot 2", DESCR: "Two port E1 voice interface daughtercard" PID: VWIC-2MFT-E1=
    NAME: "Two port E1 voice interface daughtercard on Slot 0 SubSlot 3", DESCR: "Two port E1 voice interface daughtercard" PID: VWIC-2MFT-E1=
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 0 SubSlot 4", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "High Density Voice2 Network module with on board two port interface  on Slot 1", DESCR: "High Density Voice2 Network module with on board two port interface " PID: NM-HDV2-2T1/E1
    NAME: "2nd generation two port EM voice interface daughtercard on Slot 1 SubSlot 0", DESCR: "2nd generation two port EM voice interface daughtercard" PID: VIC2-2E/M
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 2", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 3", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 4", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    NAME: "PVDMII DSP SIMM with four DSPs on Slot 1 SubSlot 5", DESCR: "PVDMII DSP SIMM with four DSPs" PID: PVDM2-64
    WIRESHARK:
    No.     Time        Source                Destination           Protocol Info
          2 0.057246    10.194.154.136        171.68.115.156        SIP      Status: 100 Trying
    Frame 2 (471 bytes on wire, 471 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 100 Trying
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41a-100875-517454db
            From: <sip:[email protected]:5060>;tag=82f4a00-9c7344ab-13c4-45026-41a-4ea64c5a-41a
            To: <sip:[email protected]:5060>
            Date: Wed, 08 Sep 2010 20:47:49 GMT
            Call-ID: 80e4f50-9c7344ab-13c4-45026-41a-10aff3f4-41a
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Length: 0
    No.     Time        Source                Destination           Protocol Info
          3 0.071428    10.194.154.136        171.68.115.156        SIP/SDP  Status: 183 Session Progress, with session description
    Frame 3 (1109 bytes on wire, 1109 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 183 Session Progress
       Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41a-100875-517454db
            From: <sip:[email protected]:5060>;tag=82f4a00-9c7344ab-13c4-45026-41a-4ea64c5a-41a
            To: <sip:[email protected]:5060>;tag=48645D8-1175
            Date: Wed, 08 Sep 2010 20:47:49 GMT
            Call-ID: 80e4f50-9c7344ab-13c4-45026-41a-10aff3f4-41a
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 8759 6996 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 8759
                    Session Version: 6996
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 18710 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 18710
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                   MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
          4 0.089917    10.194.154.136        171.68.115.156        SIP/SDP  Status: 200 OK, with session description
    Frame 4 (1116 bytes on wire, 1116 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 200 OK
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41a-100875-517454db
            From: <sip:[email protected]:5060>;tag=82f4a00-9c7344ab-13c4-45026-41a-4ea64c5a-41a
            To: <sip:[email protected]:5060>;tag=48645D8-1175
            Date: Wed, 08 Sep 2010 20:47:49 GMT
            Call-ID: 80e4f50-9c7344ab-13c4-45026-41a-10aff3f4-41a
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: replaces
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 8759 6996 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 8759
                    Session Version: 6996
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 18710 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 18710
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                    MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
         7 1.661867    10.194.154.136        171.68.115.156        SIP      Status: 100 Trying
    Frame 7 (469 bytes on wire, 469 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 100 Trying
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100eca-13593e22
            From: <sip:[email protected]:5060>;tag=82f4b98-9c7344ab-13c4-45026-41c-669825d-41c
            To: <sip:[email protected]:5060>
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5138-9c7344ab-13c4-45026-41c-3f6bfc7-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Length: 0
    No.     Time        Source                Destination           Protocol Info
          8 1.676056    10.194.154.136        171.68.115.156        SIP/SDP  Status: 183 Session Progress, with session description
    Frame 8 (1107 bytes on wire, 1107 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 183 Session Progress
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100eca-13593e22
            From: <sip:[email protected]:5060>;tag=82f4b98-9c7344ab-13c4-45026-41c-669825d-41c
            To: <sip:[email protected]:5060>;tag=4864C1C-10F8
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5138-9c7344ab-13c4-45026-41c-3f6bfc7-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 7991 6854 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 7991
                    Session Version: 6854
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 17660 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 17660
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                    MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
         10 1.700567    10.194.154.136        171.68.115.156        SIP      Status: 100 Trying
    Frame 10 (471 bytes on wire, 471 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 100 Trying
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100f04-2fde97a9
            From: <sip:[email protected]:5060>;tag=82f4d30-9c7344ab-13c4-45026-41c-5c20b753-41c
            To: <sip:[email protected]:5060>
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5320-9c7344ab-13c4-45026-41c-7fbe4865-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Length: 0
    No.     Time        Source                Destination           Protocol Info
         11 1.726376    10.194.154.136        171.68.115.156        SIP/SDP  Status: 200 OK, with session description
    Frame 11 (1114 bytes on wire, 1114 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 200 OK
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100eca-13593e22
            From: <sip:[email protected]:5060>;tag=82f4b98-9c7344ab-13c4-45026-41c-669825d-41c
            To: <sip:[email protected]:5060>;tag=4864C1C-10F8
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5138-9c7344ab-13c4-45026-41c-3f6bfc7-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
            Allow-Events: telephone-event
            Remote-Party-ID: <sip:[email protected]>;party=called;screen=no;privacy=off
                [Expert Info (Note/Undecoded): Unrecognised SIP header (Remote-Party-ID)]
                    [Message: Unrecognised SIP header (Remote-Party-ID)]
                    [Severity level: Note]
                    [Group: Undecoded]
            Contact: <sip:[email protected]:5060>
            Supported: replaces
            Supported: sdp-anat
            Server: Cisco-SIPGateway/IOS-12.x
            Content-Type: application/sdp
            Content-Disposition: session;handling=required
            Content-Length: 264
        Message Body
            Session Description Protocol
                Session Description Protocol Version (v): 0
                Owner/Creator, Session Id (o): CiscoSystemsSIP-GW-UserAgent 7991 6854 IN IP4 10.194.154.136
                    Owner Username: CiscoSystemsSIP-GW-UserAgent
                    Session ID: 7991
                    Session Version: 6854
                    Owner Network Type: IN
                    Owner Address Type: IP4
                    Owner Address: 10.194.154.136
                Session Name (s): SIP Call
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Time Description, active time (t): 0 0
                    Session Start Time: 0
                    Session Stop Time: 0
                Media Description, name and address (m): audio 17660 RTP/AVP 18 101
                    Media Type: audio
                    Media Port: 17660
                    Media Protocol: RTP/AVP
                    Media Format: ITU-T G.729
                    Media Format: DynamicRTP-Type-101
                Connection Information (c): IN IP4 10.194.154.136
                    Connection Network Type: IN
                    Connection Address Type: IP4
                    Connection Address: 10.194.154.136
                Media Attribute (a): rtpmap:18 G729/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 18
                    MIME Type: G729
                    Sample Rate: 8000
                Media Attribute (a): fmtp:18 annexb=no
                    Media Attribute Fieldname: fmtp
                    Media Format: 18 [G729]
                    Media format specific parameters: annexb=no
                Media Attribute (a): rtpmap:101 telephone-event/8000
                    Media Attribute Fieldname: rtpmap
                    Media Format: 101
                    MIME Type: telephone-event
                    Sample Rate: 8000
                Media Attribute (a): fmtp:101 0-16
                    Media Attribute Fieldname: fmtp
                    Media Format: 101 [telephone-event]
                    Media format specific parameters: 0-16
    No.     Time        Source                Destination           Protocol Info
         13 1.727645    10.194.154.136        171.68.115.156        SIP      Status: 500 Internal Server Error
    Frame 13 (526 bytes on wire, 526 bytes captured)
    Ethernet II, Src: Cisco_0d:3c:c0 (00:1f:ca:0d:3c:c0), Dst: HewlettP_06:71:52 (00:1f:29:06:71:52)
    Internet Protocol, Src: 10.194.154.136 (10.194.154.136), Dst: 171.68.115.156 (171.68.115.156)
    User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
    Session Initiation Protocol
        Status-Line: SIP/2.0 500 Internal Server Error
        Message Header
            Via: SIP/2.0/UDP 171.68.115.156:5060;rport;branch=z9hG4bK-41c-100f04-2fde97a9
            From: <sip:[email protected]:5060>;tag=82f4d30-9c7344ab-13c4-45026-41c-5c20b753-41c
            To: <sip:[email protected]:5060>;tag=4864C50-3C3
            Date: Wed, 08 Sep 2010 20:47:51 GMT
            Call-ID: 80e5320-9c7344ab-13c4-45026-41c-7fbe4865-41c
            CSeq: 1 INVITE
                Sequence Number: 1
                Method: INVITE
            Allow-Events: telephone-event
            Server: Cisco-SIPGateway/IOS-12.x
            Reason: Q.850;cause=44
                Reason Protocols: Q.850
                Cause: 44(0x2c)[Requested circuit/channel not available]
            Content-Length: 0
    Thanks!
    -John

    Since it appears you are a Cisco Employee, my recommendation is that you use the many internal resource available to you (including, but not limited to) , like TAC access, internal forums, team leaders, etc.
    This not to give the casual reader, the impression that the best source of support at Cisco is a customer's public forum.

  • How do you get Encore to work? Internal software error.

    I've made a new project with Encore CS4 consisting of mainly slideshows and about 2 movie timelines. I've created menus to be how i want them.
    When i go to build the project about 9/10 it doesn;t work. Sometimes it just crashes and gives a crash report. other times it does all the building slideshows and motion menus then starts the prepare build and comes up with internal software error, and build stops.
    This is extremely frustrating as it takes serveral hours to get to this stage every time because it has to re build all the slideshows.
    It has only worked once, and it wasn;t quite what i wanted so i made some minor adjustments (added a pic in a slideshow, or music to a menu) and since have tried twice to rebuild it and it hasnt worked.
    Encore seems like it could be really good but all its bugs make it a piece of crap.

    I don't remember the dimensions, but I have read messages that pictures that are too large will cause problems... maybe someone will come along who knows the actual size and can tell you
    Also... This is aimed a Premiere Pro, but may help
    First, work through all of the steps here http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with the DETAILS asked for in the questions at the end of that link

Maybe you are looking for