MMC crashes when attempting modification of a protection group in DPM 2012 SP1 RU3
Hi All,
I've got a problem with my DPM 2012 SP1 server for a few weeks now. It's backing up and restoring fine, but when I attempt to modify any protection group, the MMC crashes. This happens even before the modify protection group dialog is displayed, just a few
seconds after clicking 'modify' with the protection group selected.
it was running DPM 2012 SP1 RU1, is now running RU3, this update did not make the difference I was hoping for. Also installation of the DPM console on a remote management server results in the exact same problem.
Below is the error message. Has anyone else had this or a similar problem and solved it?
Thanks,
Jacob
Description:
AppName: mmc AppVer: 4.1.3313.0 ModName: mmc.exe
ModVer: 6.2.9200.16384 StackHash: 7C18B55A
Problem signature:
Problem Event Name: DPMException
Application Name: mmc
Application Version: 4.1.3313.0
Module Name: mmc.exe
Module Version: 6.2.9200.16384
Exception Name: System.NullReferenceException
Exception Point: Microsoft.Internal.EnterpriseStorage.Dls.UI.Dpw.SelectionPage.ConstructAllServersView
Other: 7C18B55A
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1043
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=190175
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Hi
I had the same problem with Sharepoint backups, there was a problem with the protection group so i removed it and added it back. since then no issues.
Similar Messages
-
DPM 2012: MMC crashes when working with 2 particular protection groups
I have a problem with 2 particular protection groups that will not allow me to perform a backup to tape on them. When I try to, the MMC crashes with the following error logged in the application event log:
The description for Event ID 999 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unexpected error caused a failure for process 'mmc'. Restart the DPM process 'mmc'.
Problem Details:
<FatalServiceError><__System><ID>19</ID><Seq>0</Seq><TimeCreated>9/2/2012 3:46:36 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>ArgumentOutOfRangeException</ExceptionType><ExceptionMessage>Index
was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index</ExceptionMessage><ExceptionDetails>System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.CreateRecoveryPointDialog.InitializeForTapeRecoveryPoint()
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</ExceptionDetails></FatalServiceError>
the message resource is present but the message is not found in the string/message table
As this appears to be a problem with just these protection groups (I am able to take tape backups of others without a problem) I decided I would try to remove the group, retain the data and re-create it. When I right click on the group and attempt
to stop protection of the group or modify the protection group, the MMC crashes with the same error above.
One protection group is backing up and Exchange 2010 Archive Database, the other, Lync 2010 SQL Databases (and covers 2 different servers).
Does anybody have any suggestions on how I can get these protection groups behaving as they should and working again?
DPM is 2012 RTM running on a Windows Server 2008 R2 SP1 Enterprise physical server. The servers being protected are running Windows Server 2008 R2 SP1 Standard, the Exchange one is virtual (running on Hyper-V), Lync, one physical, one virtual (also running
on Hyper-V).Hi
First of all verify that below services are running and also check which user account is uses for running the DPM and SQL services.
DPM
DPM Replication Agent
SQLAgent$MS$DPM2007$
MSSQL$MS$DPM2007$
Virtual Disk Service
Volume Shadow Copy
Thanks and Regards Deepak -
Unable to modify or create Protection Groups in DPM 2012 R2 - Error: 31220
"DPM failed to apply the required policies to this protection group since the recovery point limit for this DPM server has been exceeded. (ID: 31220)"
I am trying to add new data sources to our DPM server and continually run into the above message. I get the same error whether I attempt to create a new Protection Group and add the data sources to it... or if I attempt to modify an existing Protection Group
to add data sources to it. I can guess that the obvious answer is "You have too many data sources or to many recovery points for the server to handle..." If that's the case, I need to figure out how to tell how many I have. As best as I can figure
myself, I have less than 150 data sources and less than 2500 recovery points/snapshot/express-full. If there is a tool or a command that I can run to tell that, I'd be grateful to anyone who can point me in that direction.
I have tried to remove inactive member servers that no longer exist from our Protection Groups... no effect. I have tried to completely delete the removed server's data from replica... no effect. We began seeing this issue in 2012 SP1, so I ran
through the upgrade to 2012 R2 hoping that it would resolve the issue... no effect. I am able to remove members from our Protection Groups, but if I try to add an entirely new member or even just a single DB on an already protected member... fails with
above message. I also tried to adjust the retention and backup schedule... fails with above error.
Other than the stock answer from Microsoft that I am truly exceeding some limit, is there any other underlying issue that can cause this to be mis-reported to me? I hope that SOMEONE has an answer or guidance for me.Hi,
Another DPM PowerShell script - this one allows you to delete older recovery points for a selected datasource without having to modify the PG.
#Author : Ruud Baars
#Date : 11/09/2008
#Edited : 11/15/2012 By: Wilson S.
#edited : 11/27/2012 By: Mike J.
# NOTE: Update script to only remove recovery points on Disk. Recovery points removed will be from the oldest one up to the date
# entered by the user while the script is running
#deletes all recovery points before 'now' on selected data source.
$version="V4.7"
$ErrorActionPreference = "silentlycontinue"
add-pssnapin sqlservercmdletsnapin100
Add-PSSnapin -Name Microsoft.DataProtectionManager.PowerShell
$MB=1024*1024
$logfile="DPMdeleteRP.LOG"
$wait=10 #seconds
$confirmpreference = "None"
function Show_help
cls
$l="=" * 79
write-host $l -foregroundcolor magenta
write-host -nonewline "`t<<<" -foregroundcolor white
write-host -nonewline " DANGEROUS :: MAY DELETE MANY RECOVERY POINTS " -foregroundcolor red
write-host ">>>" -foregroundcolor white
write-host $l -foregroundcolor magenta
write-host "Version: $version" -foregroundcolor cyan
write-host "A: User Selects data source to remove recovery points for" -foregroundcolor green
write-host "B: User enters date / time (using 24hr clock) to Delete recovery points" -foregroundcolor green
write-host "C: User Confirms deletion after list of recovery points to be deleted is displayed." -foregroundcolor green
write-host "Appending to log file $logfile`n" -foregroundcolor white
write-host "User Accepts all responsibilities by entering a data source or just pressing [Enter] " -foregroundcolor white -backgroundcolor blue
"**********************************" >> $logfile
"Version $version" >> $logfile
get-date >> $logfile
show_help
$DPMservername=&"hostname"
"Selected DPM server = $DPMservername" >> $logfile
write-host "`nConnnecting to DPM server retrieving data source list...`n" -foregroundcolor green
$pglist = @(Get-ProtectionGroup $DPMservername) # WILSON - Created PGlist as array in case we have a single protection group.
$ds=@()
$tapes=$null
$count = 0
$dscount = 0
foreach ($count in 0..($pglist.count - 1))
# write-host $pglist[$count].friendlyname
$ds += @(get-datasource $pglist[$count]) # WILSON - Created DS as array in case we have a single protection group.
# write-host $ds
# write-host $count -foreground yellow
if ( Get-Datasource $DPMservername -inactive) {$ds += Get-Datasource $DPMservername -inactive}
$i=0
write-host "Index Protection Group Computer Path"
write-host "---------------------------------------------------------------------------------"
foreach ($l in $ds)
"[{0,3}] {1,-20} {2,-20} {3}" -f $i, $l.ProtectionGroupName, $l.psinfo.netbiosname, $l.logicalpath
$i++
$DSname=read-host "`nEnter a data source index from list above - Note co-located datasources on same replica will be effected"
if (!$DSname)
write-host "No datasource selected `n" -foregroundcolor yellow
"Aborted on Datasource name" >> $logfile
exit 0
$DSselected=$ds[$DSname]
if (!$DSselected)
write-host "No datasource selected `n" -foregroundcolor yellow
"Aborted on Datasource name" >> $logfile
exit 0
$rp=get-recoverypoint $DS[$dsname]
$rp
# $DoTape=read-host "`nDo you want to remove when recovery points are on tape ? [y/N]"
# "Remove tape recovery point = $DoTape" >> $logfile
write-host "`nCollecting recoverypoint information for datasource $DSselected.name" -foregroundcolor green
if ($DSselected.ShadowCopyUsedspace -gt 0)
while ($DSSelected.TotalRecoveryPoints -eq 0)
{ # "still 0"
#this is on disk
$oldShadowUsage=[math]::round($DSselected.ShadowCopyUsedspace/$MB,1)
$line=("Total recoverypoint usage {0} MB on DISK in {1} recovery points" -f $oldShadowUsage ,$DSselected.TotalRecoveryPoints )
$line >> $logfile
write-host $line`n -foregroundcolor white
#this is on tape
#$trptot=0
#$tp= Get-RecoveryPoint($dsselected) | where {($_.Datalocation -eq "Media")}
#foreach ($trp in $tp) {$trptot += $trp.size }
#if ($trptot -gt 0 )
# $line=("Total recoverypoint usage {0} MB on TAPE in {1} recovery points" -f ($trptot/$MB) ,$DSselected.TotalRecoveryPoints )
# $line >> $logfile
# write-host $line`n -foregroundcolor white
[datetime]$afterdate="1/1/1980"
#$answer=read-host "`nDo you want to delete recovery points from the beginning [Y/n]"
#if ($answer -eq "n" )
# [datetime]$afterdate=read-host "Delete recovery points AFTER date [MM/DD/YYYY hh:mm]"
[datetime]$enddate=read-host "Delete ALL Disk based recovery points BEFORE and Including date/time entered [MM/DD/YYYY hh:mm]"
"Deleting recovery points until $enddate" >>$logfile
write-host "Deleting recovery points until and $enddate" -foregroundcolor yellow
$rp=get-recoverypoint $DSselected
if ($DoTape -ne "y" )
$RPselected=$rp | where {($_.representedpointintime -le $enddate) -and ($_.Isincremental -eq $FALSE) -and ($_.DataLocation -eq "Disk")}
else
$RPselected=$rp | where {($_.representedpointintime -le $enddate) -and ($_.Isincremental -eq $FALSE)}
if (!$RPselected)
write-host "No recovery points found!" -foregroundcolor yellow
"No recovery points found, aborting...!" >> $logfile
exit 0
$reselect = $enddate
$adjustflag = $false
foreach ($onerp in $RPselected)
$rtime=[string]$onerp.representedpointintime
$rsize=[math]::round(($onerp.size/$MB),1)
$line= "Found {0}, RP size= {1} MB (If 0 MB, co-located datasource cannot be computed), Incremental={2} "-f $rtime, $rsize,$onerp.Isincremental
$line >> $logfile
write-host "$line" -foregroundcolor yellow
#Get dependent rp's for data source
$allRPtbd=$DSselected.GetAllRecoveryPointsToBeDeleted($onerp)
foreach ($oneDrp in $allRPtbd)
if ($oneDrp.IsIncremental -eq $FALSE) {continue}
$rtime=[string]$oneDrp.representedpointintime
$rsize=[math]::round(($oneDrp.size/$MB),1)
$line= ("`t...is dependancy for {0} size {1} `tIncremental={2}" -f $rtime, $rsize, $oneDrp.Isincremental)
$line >> $logfile
if ($oneDrp.representedpointintime -ge $enddate)
#stick to latest full ($oneDrp = dependents, $onerp = full)
$adjustflag = $true
$reselect = $onerp.representedpointintime
"<< Dependents newer than BEFORE date >>>" >> $logfile
Write-Host -nonewline "`t <<< later than BEFORE date >>>" -foregroundcolor white -backgroundcolor red
write-host "$line" -foregroundcolor yellow
else
#Ok, include current latest incremental
$reselect = $oneDrp.representedpointintime
write-host "$line" -foregroundcolor yellow
if ($reselect -lt $oneDrp.representedpointintime)
#we adjusted further backward than latest incremental within selection
$reselect = $rtime
$line = "Adjusted BEFORE date to be $reselect to include dependents to $enddate"
$line >> $logfile
Write-Host $line -foregroundcolor white -backgroundcolor blue
$line="`n<<< SECOND TO LAST CHANCE TO ABORT - ONE MORE PROMPT TO CONFIRM. >>>"
write-host $line -foregroundcolor white -backgroundcolor blue
$line >> $logfile
$line="Above recovery points within adjusted range will be permanently deleted !!!"
write-host $line -foregroundcolor red
$line >> $logfile
$line="These RP's include dependent recovery points and may contain co-located datasource(s)"
write-host $line -foregroundcolor red
$line >> $logfile
$line="Data source activity = " + $DSselected.Activity
$line >> $logfile
write-host $line -foregroundcolor white
$DoDelete=""
while (($DoDelete -ne "N" ) -and ($DoDelete -ne "Y"))
$line="Continue with deletion (must answer) Y/N? "
write-host $line -foregroundcolor white
$DoDelete=read-host
$line = $line + $DoDelete
$line >> $logfile
if (!$DSselected.Activity -eq "Idle")
$line="Data source not idle, do you want to wait Y/N ? "
write-host $line -foregroundcolor yellow
$Y=read-host
$line = $line + $Y
$line >> $logfile
if ($Y -ieq "Y")
Write-Host "Waiting for data source to become idle..." -foregroundcolor green
while ($DSselected.Activity -ne "Idle")
("Waiting {0} seconds" -f $wait) >>$logfile
Write-Host -NoNewline "..." -ForegroundColor blue
start-sleep -s $wait
if ($DoDelete -eq "Y")
foreach ($onerp in $RPselected)
#reselect is adjusted to safe range relative to what was requested
#--- if adjustflag not set then all up to including else only older because we must keep the full
if ((($onerp.representedpointintime -le $reselect) -and ($adjustflag -eq $false)) -or ($onerp.representedpointintime -lt $reselect))
$rtime=[string]$onerp.representedpointintime
write-host `n$line -foregroundcolor red
$line >>$logfile
if (($onerp ) -and ($onerp.IsIncremental -eq $FALSE)) { remove-recoverypoint -RecoveryPoint $onerp -confirm:$True} # >> $logfile}
$line =("---`nDeleting recoverypoint -> " + $rtime)
$line >>$logfile
"All Done!" >> $logfile
write-host "`nAll Done!`n`n" -foregroundcolor white
$line="Do you want to View DPMdeleteRP.LOG file Y/N ? "
write-host $line -foregroundcolor white
$Y=read-host
$line = $line + $Y
$line >> $logfile
if ($Y -ieq "Y")
Notepad DPMdeleteRP.LOG
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights. -
A few SQL related protection group Questions - DPM 2012 R2
Hi - Here is my environment: DPM 2012 R2 backing up SQL 2012 DBs. Some of the DBs are simple recovery model, some are full recovery model in the same protection group.
1) Regarding the fact that DPM only looks to the recovery model when the DB is first added to the protection group, if I ever changed the recovery model in the future, would stepping through the "Modify Protection Group" wizard without changing
anything be the solution for DPM not changing its methodology on the backing up or not backing up the log files? Or would I have to remove the affected databases from the protection group and add them back in?
2) I have disk protection configured for 30 Days, sync every 15 minutes, and application recovery points once per day. Online protection is configured for 90 Days. Does this mean my disk consumption on the DPM side for full model databases will be the full
size of the databases, plus the amount of changes observed over 30 days? OR does it mean it will keep 30 full copies of the DB? I am fairly sure the former.
3) If I do decide to reduce the retention range on the disk side of this protection group to say 14 days, are there any specific issues with changing that after the PG has been working for some time?
4) My former backup solution had an option to run consistency checks after every SQL job. Is that still considered best practice? Would the "Run a daily consistency check" be a better choice than the "Only run if a replica becomes inconsistent"
option that I currently have in place? Would there be any ramifications to enabling this now after this PG has been in place for some time?
Thanks very much!Hi
Q1) Regarding the fact that DPM only looks to the recovery model when the DB is first added to the protection group, if I ever changed the recovery model in the future, would stepping through the "Modify Protection Group" wizard without changing
anything be the solution for DPM not changing its methodology on the backing up or not backing up the log files? Or would I have to remove the affected databases from the protection group and add them back in?
A1)
Changing the Recovery Model of a Database
To change the recovery model of a protected database to the simple recovery model
Stop protection of the database, selecting the retain replica option.
Change the recovery model on the SQL Server database.
Add the database to a protection group.
Q2) I have disk protection configured for 30 Days, sync every 15 minutes, and application recovery points once per day. Online protection is configured for 90 Days. Does this mean my disk consumption on the DPM side for full model databases will be the full
size of the databases, plus the amount of changes observed over 30 days? OR does it mean it will keep 30 full copies of the DB? I am fairly sure the former.
A2) Your disk consumption on the DPM will be for size of model databases plus the amount of changes observed over 30 days.
Q3) If I do decide to reduce the retention range on the disk side of this protection group to say 14 days, are there any specific issues with changing that after the PG has been working for some time?
A4) Not really, but to gain back the potential extra space allocated for the original 30 day retention - you can try shrinking the recovery point volume once the retention range is reduced and the older recovery points are pruned. I would wait until
after midnight to be sure the old RP's are deleted, then try to shrink.
Q4) My former backup solution had an option to run consistency checks after every SQL job. Is that still considered best practice? Would the "Run a daily consistency check" be a better choice than the "Only run if a replica becomes inconsistent"
option that I currently have in place? Would there be any ramifications to enabling this now after this PG has been in place for some time?
A4) A consistency check will only run if DPM detects the replica is inconsistent. Even if you have the option selected to run nightly, if the replica is already consistent a consistency check will be skipped.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
Acrobat 9.4.4 Pro Crashes When Attempting to Open PDF Form
OS: Win XP Pro SP3
The machine worked fine until Acrobat updated itself to 9.4.4 then the problem started. Crashes when attempting to open most PDF Forms - even when freshly rebooted or repaired. I originally thought it was related to a browser or Outlook 2007, but later found that it does it under all circumstances. It is my General Manager's machine having the problem, so I need to get this resolved ASAP. Your experience and assistance is much appreciated.
My temporary fix was to uninstall 9.4.4 - Install 9.0 and turn off automatic updates - worked beautifully. It would be nice to get to the bottom of this so we can update our CS4 products.
Another user reported this problem on May 16, 2011 and no one has replied to his post.
Thanks in advance.Please repost in the Acrobat Windows forum.
http://forums.adobe.com/community/acrobat/acrobat_windows -
Lightroom 6 crashes when attempting to import from camera.
Never had a problem importing from same camera using LR 5.7. LR 6 crashes when attempting to import from camera.
Actually I have found out that it's not related to importing, but to face recognition being turned on (which I had just done shortly before I started the import).
See here for more details: Re: Lightroom 6.0.1 standalone always crashes less than a minute after start -
Adobe Standard 9.1.0 crashes when attempting create .pdf from scanner
Adobe Standard 9.1.0 crashes when attempting "create .pdf from scanner" from a Kyocera Mita KM-2550 using the twain driver. The error encountered is 0xc0000005 at address 0x0000000002d78e70. I have downloaded and installed the latest updates. This is happening on two new PCs with the same configuration. Is anyone else having this problem? Any suggestions?
Spent quite a while on this one.. My problem was related to twain drivers which reside in c:\windows\twain_32. I'm running windows 7 64-bit. First it's usually possible to scan in windows 7 maybe vista and from adobe without even using twain (using WIA). So try renaming the twain_32 folder to _twain_32 and see what happens... If that stops the crashing look at the contents of the twain folder. I had a Dell folder for some printer I wasn't even using. That was causing the crash. I removed the dell folder and renamed the twain folder back to twain_32. Now everything works as designed.
-
ITunes crashes when attempting to play purchased tracks
Hoping someone can help me here. iTunes crashes when attempting to play tracks purchased from the iTunes store. Music imported from CDs still plays fine. They have played preiously but not since downloading and installing 7.0.2.16. QuickTime is up to date and I only have 1 PC authorised. Help!
Dell Dimension 5100 Windows XP ProThere's another thread on here that suggested re-installing iTunes. That works for me (in that the videos play), but I have to re-install iTunes every time I want to watch them which is a pain. So if anyone has a more permanent fix...
-
Just updated to iOS 8.2. Settings app still crashes when attempting to manage music storage.
Thanks for your reply. Any suggestions for ways to fix this? If I've already updated using my phone, am I just screwed?
-
DPM 2012 SP1 4.1.3426.0 - CRASHES WHEN TRYING TO OPEN JOBS FILTERS
I have 2 DPM 2012 SP1 servers and both are behaving the same. They were working fine earlier this week and suddenly MMC crashes when I try to open any Job filter. Everything else appears to be working fine except when I try to view any of the
default Job filters or custom filters I created such as All Jobs or All Jobs in Progress.
Description:
AppName: mmc AppVer: 4.1.3313.0 ModName: mmc.exe
ModVer: 6.1.7600.16385 StackHash: E4489908
Problem signature:
Problem Event Name: DPMException
Application Name: mmc
Application Version: 4.1.3313.0
Module Name: mmc.exe
Module Version: 6.1.7600.16385
Exception Name: System.ArgumentException
Exception Point: System.TimeZoneInfo.ConvertTime
Other: E4489908
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033http://social.technet.microsoft.com/Forums/en-US/cc576f9d-602b-4331-a745-e7bab12a24cf/dpm-console-crashes?forum=dataprotectionmanager
https://blogs.technet.com/b/dpm/archive/2012/01/30/fix-the-dpm-console-crashes-and-logs-event-id-945-when-making-any-changes.aspx
http://support.microsoft.com/kb/2905631/en-us
http://scdpm.blogspot.ru/2011/12/dpm-console-crashes-on-recovery-tap.html
Have a nice day !!! -
DPM 2012 SP1 long term backup fails when protected server reboots
Hi,
we're using DPM 2012 SP1 with Short-term and long-term protection.
We use a daily short-term backup to disk and a weekly long-term to tape.
We are noticing that when a long-term tape backup is running, it fails when we reboot one of the protected servers.
Is anyone else having this issue ? I assumed the long-term tape backup will be created from a disk-recovery point.Hi,
What is the detailed error code in the properties of the failed initial replica or consistency check job ?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
Hi All,
When installing manually protection agent DPM 2012 SP1 on new target computer, I get "Microsoft Software License terms" to accept...
Is there a way to automatically approve the license ? I try various commands like :
/quiet
/quiet /eula:yes
/quiet /AcceptEula:yes
Mike, if you're around any
suggestion is welcome :)
Stephane.
Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.
My DPM blog Yet Another DPM BlogThks Geaux-Tigers,
it works like a charm :)
I also found the DPM technet link: http://technet.microsoft.com/en-us/library/jj650955.aspx
DpmAgentInstaller.exe [/q] [<DPM server name>] [/IAcceptEula]
Stephane
Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.
My DPM blog Yet Another DPM Blog -
Event 917 Console Crash when attempting to modify Disk Only Protection Group
Primary DPM 2012 R2 4.2.1254.0 running on Server 2012 -
In the process of decommissioning a number of old servers - I found that I am no longer able to modify a disk only protection group on one of my primary DPM servers. Console crash - noting error 917. I've seen a number of work around in relation to protection
groups with long term storage, but none noting disk only. Notably, kb 2905631 - long term only protection may cause this issue.
Another thread mentioned that re-syncing / consistency checks on the entire server resolved the issue for them, but I find that rather unnecessary. I've over 13Tb of data on this server, and am trying to remove the last 30GB of an old protection group.
Recap-
Error 917 when removing member from protection group
MMC crash with a 999 marked when modifying the protection group
The event log is not noting any service crashes, or the 917 error in the event log. 999 is getting recorded in the event log.
The description for Event ID 999 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unexpected error caused a failure for process 'mmc'. Restart the DPM process 'mmc'.
Problem Details:
<FatalServiceError><__System><ID>19</ID><Seq>0</Seq><TimeCreated>12/2/2014 5:40:14 PM</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>SqlNullValueException</ExceptionType><ExceptionMessage>Data
is Null. This method or property cannot be called on Null values.</ExceptionMessage><ExceptionDetails>System.Data.SqlTypes.SqlNullValueException: Data is Null. This method or property cannot be called on Null values.
at System.Data.SqlClient.SqlBuffer.get_String()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ProtectionGroup.ReadBackupAndCCWindow()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ProtectionGroup.get_BackupWindow()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.OMCommon.ProtectionGroup.GetPerformanceString()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ProtectedGroupUIElement.AddPerformanceData()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ProtectedGroupUIElement.ConstructDetailsPaneContent()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.CommonControls.UISearchableElement.get_DetailNameValuePairs()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ProtectedGroupUIElement.DisplayDetails()
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ProtectionViewInternal.FillGroupDetails(GroupingListHeaderItem group)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ProtectionViewInternal.UpdateDetailsPane()
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Microsoft.Internal.EnterpriseStorage.UI.CommonControls.GroupingListView.EndUpdate()
at Microsoft.Internal.EnterpriseStorage.UI.CommonControls.GroupingListViewBody.ProcessClick()
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at Microsoft.Internal.EnterpriseStorage.UI.CommonControls.GroupingListViewBody.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)</ExceptionDetails></FatalServiceError>
the message resource is present but the message is not found in the string/message tableHi Mike,
That appears to be the case. A row shows NULL for IMCatalogXML. I'm looking at your script to update the value now based on the following thread - thread .
So far, no rows have been modified.
Since I really don't care about this protected member, is this a row I could just delete from the DB, or how to properly update the data so I can remove it from within the confines of the GUI?
Marketing 2011-05-19 18:59:41.917
B7073B10-DDE6-4EA3-BD8C-1E1497C218D5 NULL
NULL 0
0 0 NULL
2 0
NULL
This PG was definitely around back when this server was DPM 2010.
Regards -
Lightroom 5.4 crashes when attempting to print.
I am working on a MacBook Pro running Maverick and currently printing to an Epson Artisan 50. Earlier in the spring, after a previous LR update, every time I tried to print the application crashed. It did not matter which printer I was using (I also have an Epson Stylus Pro 3800), or if I was printing to a JPEG file. All other printing works fine, including from Photoshop CC. I could not find a solution, but I had to go out of town for several weeks, and by the time I returned Lightroom had been updated again, and I was able to print. I assumed the problem was somewhere in the previous version. Over the weekend Lightroom was updated to version 5.4, and yesterday crashed when I attempted to print. I am at my wits end, as I much prefer the quality of prints from LR, and I have several projects in the pipeline. The crash report follows, but I do not know how to decipher it. Needless to say, when the report is sent on to Adobe, the message I get back is that there is no solution to the problem.
Process: Adobe Photoshop Lightroom 5 [6163]
Path: /Applications/Adobe Photoshop Lightroom 5.app/Contents/MacOS/Adobe Photoshop Lightroom 5
Identifier: com.adobe.Lightroom5
Version: Adobe Photoshop Lightroom 5.4 [955652] (5.4)
Code Type: X86-64 (Native)
Parent Process: launchd [165]
Responsible: Adobe Photoshop Lightroom 5 [6163]
User ID: 504
Date/Time: 2014-06-09 21:46:07.396 -0400
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 761F1024-7EA7-95ED-A204-6BAA8864AAF7
Sleep/Wake UUID: 5BC27E92-0BD0-4DE7-91CD-B62D9DF14E6E
Crashed Thread: 44
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_platform.dylib 0x00007fff8eeb2410 _platform_memset_pattern16$VARIANT$Ivybridge + 64
1 com.apple.CoreGraphics 0x00007fff89c1f7bd CGBlt_fillBytes + 141
2 com.apple.CoreGraphics 0x00007fff89c1a871 argb32_mark + 2907
3 libRIP.A.dylib 0x00007fff91fb0401 RIPLayerBltShape + 1449
4 libRIP.A.dylib 0x00007fff91fae468 ripc_Render + 304
5 libRIP.A.dylib 0x00007fff91faa2e1 ripc_DrawRects + 399
6 com.apple.CoreGraphics 0x00007fff89c14d2a CGContextFillRects + 96
7 com.adobe.ag.ui 0x0000000104d237a8 0x104d1b000 + 34728
8 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
9 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
10 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
11 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
12 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
13 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
14 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
15 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
16 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
17 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
18 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
19 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
20 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
21 com.adobe.ag.ui 0x0000000104d3e35b 0x104d1b000 + 144219
22 com.apple.AppKit 0x00007fff8c61904f -[NSView _drawRect:clip:] + 3748
23 com.apple.AppKit 0x00007fff8c6178c4 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1799
24 com.apple.AppKit 0x00007fff8c617ca0 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787
25 com.apple.AppKit 0x00007fff8c615706 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 841
26 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
27 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
28 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
29 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
30 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
31 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
32 com.apple.AppKit 0x00007fff8c616bc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 6151
33 com.apple.AppKit 0x00007fff8c614eb1 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 314
34 com.apple.AppKit 0x00007fff8c611e9f -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2828
35 com.apple.AppKit 0x00007fff8c5f12fa -[NSView displayIfNeeded] + 1680
36 com.apple.AppKit 0x00007fff8c65674e _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 884
37 com.apple.AppKit 0x00007fff8cc2c061 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_invoke1331 + 46
38 com.apple.CoreFoundation 0x00007fff8f183e17 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
39 com.apple.CoreFoundation 0x00007fff8f183d87 __CFRunLoopDoObservers + 391
40 com.apple.CoreFoundation 0x00007fff8f175468 __CFRunLoopRun + 776
41 com.apple.CoreFoundation 0x00007fff8f174f25 CFRunLoopRunSpecific + 309
42 com.apple.HIToolbox 0x00007fff94140a0d RunCurrentEventLoopInMode + 226
43 com.apple.HIToolbox 0x00007fff94140685 ReceiveNextEventCommon + 173
44 com.apple.HIToolbox 0x00007fff941405bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
45 com.apple.AppKit 0x00007fff8c4ba26e _DPSNextEvent + 1434
46 com.apple.AppKit 0x00007fff8c4b98bb -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
47 com.apple.AppKit 0x00007fff8c4ad9bc -[NSApplication run] + 553
48 com.apple.AppKit 0x00007fff8c4987a3 NSApplicationMain + 940
49 com.adobe.Lightroom5 0x0000000104c9b613 main + 1107
50 com.adobe.Lightroom5 0x0000000104c9b1b8 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8dbb7662 kevent64 + 10
1 libdispatch.dylib 0x00007fff92165421 _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff92165136 _dispatch_mgr_thread + 52
Thread 2:: Worker Thread Dispatcher
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
7 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
8 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
9 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
11 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
12 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
13 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
14 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
15 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
16 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
17 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
18 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 3:: ace
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff9265d800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff9265d9ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff9262e145 MPWaitOnQueue + 192
5 com.adobe.ag.AgImageIO 0x000000010a6e51a6 0x10a4e7000 + 2089382
6 com.adobe.ag.AgImageIO 0x000000010a6e4ed3 0x10a4e7000 + 2088659
7 com.apple.CoreServices.CarbonCore 0x00007fff9262e6c3 PrivateMPEntryPoint + 58
8 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 4:: ace
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff9265d800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff9265d9ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff9262e145 MPWaitOnQueue + 192
5 com.adobe.ag.AgImageIO 0x000000010a6e51a6 0x10a4e7000 + 2089382
6 com.adobe.ag.AgImageIO 0x000000010a6e4ed3 0x10a4e7000 + 2088659
7 com.apple.CoreServices.CarbonCore 0x00007fff9262e6c3 PrivateMPEntryPoint + 58
8 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 5:: ace
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff9265d800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff9265d9ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff9262e145 MPWaitOnQueue + 192
5 com.adobe.ag.AgImageIO 0x000000010a6e51a6 0x10a4e7000 + 2089382
6 com.adobe.ag.AgImageIO 0x000000010a6e4ed3 0x10a4e7000 + 2088659
7 com.apple.CoreServices.CarbonCore 0x00007fff9262e6c3 PrivateMPEntryPoint + 58
8 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 6:: ace
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.apple.CoreServices.CarbonCore 0x00007fff9265d800 TSWaitOnCondition + 108
3 com.apple.CoreServices.CarbonCore 0x00007fff9265d9ff TSWaitOnConditionTimedRelative + 172
4 com.apple.CoreServices.CarbonCore 0x00007fff9262e145 MPWaitOnQueue + 192
5 com.adobe.ag.AgImageIO 0x000000010a6e51a6 0x10a4e7000 + 2089382
6 com.adobe.ag.AgImageIO 0x000000010a6e4ed3 0x10a4e7000 + 2088659
7 com.apple.CoreServices.CarbonCore 0x00007fff9262e6c3 PrivateMPEntryPoint + 58
8 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
9 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
10 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 7:: cr_scratch
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.AgImageIO 0x000000010a5f52b1 0x10a4e7000 + 1106609
3 com.adobe.ag.AgImageIO 0x000000010a7b4b6b 0x10a4e7000 + 2939755
4 com.adobe.ag.AgImageIO 0x000000010a5bf1a1 0x10a4e7000 + 885153
5 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
6 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
7 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 8:: Queue Processor - AgPhotoAvailability
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 9:: AsyncDataServer
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde659 AgConditionLock_wait + 184
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
7 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
8 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
9 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
11 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
12 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
13 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
14 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
15 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
16 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
17 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
18 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff8dbb2a1a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8dbb1d18 mach_msg + 64
2 com.apple.CoreFoundation 0x00007fff8f175fc5 __CFRunLoopServiceMachPort + 181
3 com.apple.CoreFoundation 0x00007fff8f1755e9 __CFRunLoopRun + 1161
4 com.apple.CoreFoundation 0x00007fff8f174f25 CFRunLoopRunSpecific + 309
5 com.apple.AppKit 0x00007fff8c65a05e _NSEventThread + 144
6 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
7 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
8 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 11:: Preview Server
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde659 AgConditionLock_wait + 184
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
7 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
8 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
9 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
11 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
12 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
13 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
14 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
15 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
16 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
17 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
18 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
19 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
20 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 12:: Queue Processor - PreviewFileStore
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 13:: Queue Processor - NegativeQueue
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 14:: Queue Processor - HistogramQueue
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 15:: Queue Processor - RenderQueue_Render
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 16:: Queue Processor - RenderQueue_ReadPreview
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 17:: Queue Processor - RenderQueue_Video
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
12 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
13 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
14 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
15 com.adobe.ag.kernel 0x0000000104cbc149 0x104cb8000 + 16713
16 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
17 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
18 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
19 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
21 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
22 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722
23 com.adobe.ag.kernel 0x0000000104cc159d 0x104cb8000 + 38301
24 com.adobe.ag.kernel 0x0000000104cc216a 0x104cb8000 + 41322
25 com.adobe.ag.kernel 0x0000000104cb9feb lua_pcall + 101
26 com.adobe.ag.substrate 0x0000000104e2861b 0x104e16000 + 75291
27 com.apple.Foundation 0x00007fff9134c76b __NSThread__main__ + 1318
28 libsystem_pthread.dylib 0x00007fff9215b899 _pthread_body + 138
29 libsystem_pthread.dylib 0x00007fff9215b72a _pthread_start + 137
30 libsystem_pthread.dylib 0x00007fff9215ffc9 thread_start + 13
Thread 18:: Queue Processor - RenderQueue_Face
0 libsystem_kernel.dylib 0x00007fff8dbb6716 __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff9215dc3b _pthread_cond_wait + 727
2 com.adobe.ag.kernel 0x0000000104cde5cc AgConditionLock_wait + 43
3 com.adobe.ag.kernel 0x0000000104cd81a7 AgTransitQueue_dequeueToLuaState + 92
4 com.adobe.ag.kernel 0x0000000104cd90a8 0x104cb8000 + 135336
5 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
6 com.adobe.ag.kernel 0x0000000104cc1f01 0x104cb8000 + 40705
7 com.adobe.ag.kernel 0x0000000104cb9f69 lua_call + 36
8 com.adobe.ag.substrate 0x0000000104e34610 AgLua_callWithAutoReleasePool + 84
9 com.adobe.ag.kernel 0x0000000104cc1c3f 0x104cb8000 + 39999
10 com.adobe.ag.kernel 0x0000000104cd014f 0x104cb8000 + 98639
11 com.adobe.ag.kernel 0x0000000104cc1f12 0x104cb8000 + 40722Same here, except it's with JPEG or RAW files. I can import a folder, or an individual picture. However, when I try to import all of my pictures at once (either from external HD or the HD on my computer then i get the same error message and it crashes.
Intel i7 dual core 4th gen
Windows 8.1 64bit
16GB RAM
Lightroom 5.4 (CC) -
Compressor crash when attempting import files with 00* in name
I produce several short video files every day and name them using a sequential five digit numerical naming convention.
I'm finding that whenever I'm near, at or shortly after crossing a 100 mark Compressor crashes when I try and import single files with the following filenames (these are the most recent examples):
20993
21000
21001
21005
The only way to import these problematic files is to select the file before, or after, then Command click on the filename causing the crash. Click Open to import both into the batch, and then click on the file I first clicked on and hit Delete to remove it from the batch, leaving the file with the problematic name.
For Example. I want to import 21005 into Compressor for processing, but every time I try and import it Compressor crashes. So I re-launch Compressor, click the little Q button and click on 21004, then press Command and click on 21005. Click Open, import window goes away to reveal the Batch window. Click on 21004, press Delete button on keyboard leaving me with the file that was causing the crash.
FWIW apart from the file duration/size, there's no difference between these files. In fact I can change the names and the files that used to import fine now crash Compressor when attempt to import with any of the filenames above.
Here's the info behind two of the problem files and also that of the two adjacent files that import fine:
(all files: Dimension: 720 x 480. Codecs: DV/DVCPRO - NTSC. Channel Count: 2. Kind: Final Cut Pro Movie File. No color labels.
20999 (Imports Fine):
File Size: 394,475,469 bytes
Duration: 01'44
21000 (Compressor Crasher):
File Size: 324,052,925 bytes
Duration: 01'26
21001 (Compressor Crasher):
File Size: 339.730.909 bytes
Duration: 01'30
21002 (Imports Fine):
File Size: 348,707,181 bytes
Duration: 01'32
Compressor 2 - 2.0.1
Dual 2 GHz PowerPC G5
1.5 B DDR SDRAM
Mac OS X 10.4.8Hello,
Thanks for the replies/info.
Yes the Panther and Jaguar install disks are retail versions, not specific machine versions. And the Jaguar ones worked for the Powerbook before.
The Powerbook I have is the Firewire 500mhz one, Pismo I think it's called. The hard drive is a 60GB one. I didn't have to partition it before.
Reviewing all the above, it would appear that the problem is me not being able to use an internal, built in CD/DVD drive to install from this time? The only other thing it could be I think is the crash I recently had has had some bad effect -- but that's unlikely right? So, I need to get a new DVD drive? Or is there any other way to get the OS onto the Powerbook without getting another internal DVD/CD drive? Is there anyway to install onto the PB from another machine maybe?
Does that sound right?: not being able to use internal DVD/CD drive is the source of my current problem?
Thanks.
Maybe you are looking for
-
Revert to 10.5.7?
Like many others, I'm experiencing slow/no wifi connection after the 10.5.8 update. I was wondering if downloading and installing the old 10.5.7 update off the apple website will do any good or if it could somehow damage my macbook even more. After i
-
Hi Friends, I am working on scenario where i need to send sales order confirmation to partner and receive purchase order from partner. And this transfer of message will be secured by using certificate. I am able to send message successfuly using cert
-
Problem in Dynamic Where clause..
Hello All, I have a requirement in which i have to do a select statement where (Field1 = 'X') and (Field2 = 'A' or Field2 = 'B'). But if i write it directly, select * from Ztable into table itab where Field1 = 'X' and Field2 = 'A' or Field2 = 'B'. Th
-
Strange and fatal file name / root folder problem. Please help!
Hi there. I wonder if anybody could help me! I am using CS4 but this problem still occurred in CS3. When I set up a new site in Dreamweaver I go through the usual motions selecting the local root folder and images folder. Then when I go into the new
-
Getting cursor rowcount before fetching?
Just checking if this is do-able? Is there a way to find the total number of rows selected by a cursor after opening it, but before fetching anything? I know the cursor attribute %rowcount returns the number of records fetched so far (although I don'