Alarm failed Jan1 2012

Alarm failed to activate - was set after midnight new years Jan 01 2012. Is there a fix or just or are we still neck deep in conjecture?
(version 4.2.1 (8c148)
Luckily my colleagues have a sense of humor

Is this a joke, or did it actually fail to activate?
I suggest you report it.
bugreport.apple.com

Similar Messages

ICal Alarms Fail Repeatedly

Since upgrading to Leopard (currently 10.5.7), iCal alarms have failed to appear several times. That is, they work for a while, then stop working. This didn't happen at first. But when it was clear iCal alarms were not working (I ran several tests) I called Apple. The expert had me delete a number of files (Cache folder and several plists) and restart the computer. Problem solved.
Or maybe not. About a week later alarms failed again. I called Apple again, and talked to two experts. The first had me restart the computer. An alarm popped up. Then she had me delete several things and try another test--no alarm. I restarted the computer again and an alarm popped up. A test in a new user account worked, so apparently the software is OK.
Next she passed me to expert #2. He had me make sure iCal and iCal Helper were in the list of startup items. He was certain this would solve the problem. 2 tests (iCal running, iCal not running) both produced alarms. Problem solved.
Or maybe not. Another week has passed and alarms failed again. Tried a test--failure. I restarted the computer and alarms DO work again. But why is that necessary when for years (in earlier versions) it wasn't?
I'm about to call Apple again. But does any expert not employed by Apple have any ideas?

Charles,
Hopefully, Apple will come up with a solution as I'm obviously not the only person having this problem.
I concur, but in order for Apple to be informed of this problem you should also Provide iCal Feedback.
;~)

Nokia 5800 v31 calendar alarm fail

HI!
I have upgraded my 5800 xm to v31.
Now i have the clock bug, the alarm always goes off 3 or 4 minutes after the hour i expected.
Worst than that is that every time i set a calendar alarm it doesn't do anything! When i go to calendar it says:
"1 or more calendar alarms failed due to hour change"
Does anyone have the same problem? Is there a way out?
Best regards
Sandgrain

There has also been cases of users changing snooze time from 5 to 10 min ( just the changing, whatever time you set it to) and solves the alarm for a little while. The bug is totally random.
My first 5800 on v30 had this issue - did a reset and it fixed the alarm for about 4 days before it continued to go off a couple of mins late. My second 5800 on 31 did not have it the first 3 weeks untill one night... You might be lucky or you might not be. It's totally random so chanchans advice getting a 3rd party alarm would be the thing. V40 solves it.

Alarm fails to go off

It seems like my iPod Video's alarm clock function fails to go off if it isn't connected to a power source, and if the alarm is set to more than a few minutes away; as though it goes into a power-saving mode, from which the alarm functionality can't wake it up. This never used to happen...

i had this problem..
when you go in to the clock feature- where it shows a list of the clocks you have, make sure the clock is black and not white. if its white it means its out of sync with the actual time and date you have set on your ipod.
i had some trouble with this, but it seems to only happen if i go a while without hooking it up to my computer

Recovery points failing on 2012 R2 x64 virtual server via DPM 2012 R2 x64 - The parameter is incorrect (0x80070057)

I'm getting this on only one of my many virtual servers for some reason.. i've dug around.. i saw there may be a "private" fix for this issue..
The specific message is:
The replica of Volume D:\ on server02.domain.local is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points,
but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))
This is not a sharepoint server..
Any thoughts here
EDIT:
I am not seeing any indication of errors on the event viewer of the server being backed up..
Tech, the Universe, Everything: http://tech-stew.com

Hi,
We have released the fix in UR1.
Issues that are fixed in System Center 2012 R2 Data Protection Manager Update Rollup 1
Issue 1
A 0x80070057 error occurs when a session is closed prematurely. This error is caused by a failure during a consistency check.
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.

2012 R2 guest VM creation from template fails - SVMM 2012 SP1

Hi,
I am trying to create a VM from a VM template and I get error 13206 - Virtual Machine Manager cannot locate the boot or system volumen on virtual machine <NewVMName>.
First, the current setup:
Host OS: Windows Server 2012
SCVMM: 2012 SP1
The VM Template creation process:
- Create a normal VM from SCVMM: Guest OS is Windows Server 2012 R2
- Simple configuration of the guest OS (eg: regional settings, ...)
- Disk within the VM is configured as Dynamic (has one simple partition that is System Reserved and another simple partition for the System (C:))
- Sysprep the guest VM with Generalize and Shutdown options
- Import the syspreped VHDX onto the SCVMM Library (making sure that the transfer is "unencrypted")
- Create the VM Template using imported VHDX (since this is SCVMM 2012 SP1, not R2, the option to select the VHD generation (1 or 2) is not provided)
The VM creation from template process:
- Create a VM from the template with the default values and ticking the box for the VM to "start the virtual machine after deploying it on the host"
The "Job" process:
- Create virtual machine = Completed
- Deploy file (using LAN) = Completed
- Change properties of virtual machine = Completed
- Fix up differencing disks = Completed
- Install VM components = Failed <=Error 13206
Some additional details:
- Hyper-V integration services are not installed on the guest VM
- Repeated the same procedure with both Dynamic and Fixed VHDX
- Original VM was created with only 1 disk for boot drive (no additional disks)
- Original VM does not have any roles or features configured
- The VM Template does not make use of answer files nor is it configured to join the domain
- Enabled SCVMM log tracing using Microsoft kb2913445 and searched the logs using the VHDX ID number - Not found
Any help/guidance is greatly appreciated...
Thank you,
Karim

SCVMM 2012 SP1 does not know of 2012 R2 (that I recall).
Also, the VM must be a Generation 1. Generation 2 creates a UEFI layout on the VHD that SCVMM 2012 has no idea how to handle.
SCVMM actually mounts the VHD when the VM is deployed and looks for disk volume markers to find the OS in the VHD, then injects some startup files. This is the portion of the process where you are failing.
How do I know? I submitted a bug around this in the SCVMM 2012 timeframe. That I believe was fixed around the time of UR4.
I caused the problem to happen by creating my VM with DISM from an image. This did not create the layout assumptions that SCVMM was looking for and blocked template deployment.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Backup Failed - SCCM 2012 SP1

Hi Experts,
I got a Lab environment in which i am trying to backup the site server. I tried many ways to fix it but still the backups are getting failed. When i checked component status SMS_SITE_SQL_BACKUP_XXXXXX is
failed.
Will this be an issue. Please help me to fix it.
I tried below steps like
Windows firewall - Stopped
Verified Install.map
Antivirus file exclusion done on MCAFEE
Restarted the WMI service
Remote file share created for backup content storage
Rebooted the primary site server. Still no joy.
Regards, Pratap

Hi,
Below is the log
Log:
    SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used. $$<SMS_SITE_BACKUP><01-15-2014 12:35:48.352+00><thread=5676 (0x162C)>
Registered this process as a source of "SMS Server" events. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.459+00><thread=5676 (0x162C)>
Registered this process as a source of "SMS Client" events. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.492+00><thread=5676 (0x162C)>
Registered this process as a source of "SMS Provider" events. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.509+00><thread=5676 (0x162C)>
Status message reporting system initialized successfully. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.560+00><thread=5676 (0x162C)>
Locale set to OS value (English_United States.1252). $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.571+00><thread=5676 (0x162C)>
SMS_SITE_BACKUP service 2012 started. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.571+00><thread=5676 (0x162C)>
STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=3556 TID=5676 GMTDATE=Wed Jan 15 12:35:49.571 2014 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.571+00><thread=5676 (0x162C)>
Starting backup - Wed Jan 15 12:35:49 2014 $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.572+00><thread=5676 (0x162C)>
SMS installation root directory = D:\Program Files\Microsoft Configuration Manager. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.630+00><thread=5676 (0x162C)>
Warning: SQL installation root directory is empty.The registry key "SOFTWARE\Microsoft\MSSQLServer\Setup\SQLPath" (populated by ConfigMgr setup) was found empty. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.631+00><thread=5676 (0x162C)>
Site server backup location = D:\SCCM_BKP_SITE. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.631+00><thread=5676 (0x162C)>
SQL backup location = E:\BKP. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.631+00><thread=5676 (0x162C)>
Warning: Backup location and the sms root directory are on the same volume D. Sms Backup creates snapshot of the volume using VSS services and then copies the data to the backup location. It is advisable to have the backup location on a different volume than
the one that has SMS data, so that the writes to the volume is minimal when the volume snapshot is active.   $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.631+00><thread=5676 (0x162C)>
Verified that backup folder D:\SCCM_BKP_SITE exists.   $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.632+00><thread=5676 (0x162C)>
Verified backup service has permission to access the backup folder D:\SCCM_BKP_SITE $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.632+00><thread=5676 (0x162C)>
STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=3556 TID=5676 GMTDATE=Wed Jan 15 12:35:49.632 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
$$<SMS_SITE_BACKUP><01-15-2014 12:35:49.632+00><thread=5676 (0x162C)>
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.639+00><thread=5676 (0x162C)>
Starting VSS initialization... $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.639+00><thread=5676 (0x162C)>
Starting Asynchronous GatherWriterMetadata. $$<SMS_SITE_BACKUP><01-15-2014 12:35:49.692+00><thread=5676 (0x162C)>
Number of writers that responded: 15. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.865+00><thread=5676 (0x162C)>
Reading SMS Writer metadata... $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.990+00><thread=5676 (0x162C)>
Number of FileIncludes: 0. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.990+00><thread=5676 (0x162C)>
Number of FileExcludes: 0. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.990+00><thread=5676 (0x162C)>
Number of Components: 7. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.990+00><thread=5676 (0x162C)>
Component 0 - SCWBackup\SiteServer\SMSServer\inboxes. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.991+00><thread=5676 (0x162C)>
FileGroupFile = D:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes] $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.993+00><thread=5676 (0x162C)>
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.993+00><thread=5676 (0x162C)>
Component 1 - SCWBackup\SiteServer\SMSServer\Logs. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.993+00><thread=5676 (0x162C)>
FileGroupFile = D:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes] $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.994+00><thread=5676 (0x162C)>
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.994+00><thread=5676 (0x162C)>
Component 2 - SCWBackup\SiteServer\SMSServer\data. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.995+00><thread=5676 (0x162C)>
FileGroupFile = D:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes] $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.995+00><thread=5676 (0x162C)>
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.996+00><thread=5676 (0x162C)>
Component 3 - SCWBackup\SiteServer\SMSServer\srvacct. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.996+00><thread=5676 (0x162C)>
FileGroupFile = D:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes] $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.996+00><thread=5676 (0x162C)>
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.997+00><thread=5676 (0x162C)>
Component 4 - SCWBackup\SiteServer\SMSServer. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.997+00><thread=5676 (0x162C)>
FileGroupFile = D:\Program Files\Microsoft Configuration Manager\install.map [Recursive: no] $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.997+00><thread=5676 (0x162C)>
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.998+00><thread=5676 (0x162C)>
Component 5 - SCWBackup\SiteServer\SMSbkSiteRegSMS.dat. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.998+00><thread=5676 (0x162C)>
FileGroupFile = D:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.998+00><thread=5676 (0x162C)>
Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.999+00><thread=5676 (0x162C)>
Component 6 - SCWBackup\SiteDBServer\SMSbkSQLSiteDB.dat. $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.999+00><thread=5676 (0x162C)>
Dependency On SQL Writer , LogicalPath:\\DSQLSTPV01\DSQLSTPV01\SCCMINS, ComponentName:CM_SCW $$<SMS_SITE_BACKUP><01-15-2014 12:35:59.999+00><thread=5676 (0x162C)>
After GatherWriterMetadata SMS Writer status = STABLE. $$<SMS_SITE_BACKUP><01-15-2014 12:36:00.159+00><thread=5676 (0x162C)>
~Info: Sending message to start the SQL Backup... $$<SMS_SITE_BACKUP><01-15-2014 12:36:00.159+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed yet. Waiting 30 minutes for it to abort before starting another backup. $$<SMS_SITE_BACKUP><01-15-2014 12:36:00.299+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:36:00.334+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:37:00.427+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:38:00.457+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:39:00.504+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:40:00.543+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:41:00.579+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:42:00.630+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:43:00.793+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:44:00.834+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:45:00.880+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:46:00.923+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:47:00.963+00><thread=5676 (0x162C)>
Previous SQL backup was not aborted or completed. Sleeping for 60 seconds... $$<SMS_SITE_BACKUP><01-15-2014 12:48:01.172+00><thread=5676 (0x162C)>
SMS_SITE_BACKUP service stopped. $$<SMS_SITE_BACKUP><01-15-2014 12:48:12.416+00><thread=6204 (0x183C)>
STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=3556 TID=6204 GMTDATE=Wed Jan 15 12:48:12.417 2014 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.369+00><thread=6204 (0x183C)>
Backup service was signalled to stop. $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.370+00><thread=5676 (0x162C)>
Error: Failed to send start message to the SqlBackup. $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.374+00><thread=5676 (0x162C)>
SMS_SITE_BACKUP failed. Please see previous errors. $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.374+00><thread=5676 (0x162C)>
STATMSG: ID=5060 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=3556 TID=5676 GMTDATE=Wed Jan 15 12:48:13.374 2014
ISTR0="Error: Failed to send start message to the SqlBackup." ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.374+00><thread=5676 (0x162C)>
SMS_SITE_BACKUP service is stopping. $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.375+00><thread=5676 (0x162C)>
STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=3556 TID=5676 GMTDATE=Wed Jan 15 12:48:13.375 2014 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.375+00><thread=5676 (0x162C)>
Raised backup task failure alert. $$<SMS_SITE_BACKUP><01-15-2014 12:48:13.399+00><thread=5676 (0x162C)>
Regards, Pratap

Ical alarm fails occasionally

Hello,
I set up daily alarms in iCal for things I have to do at exactly the same time everyday. However, once in a while, iCal will either fail to send the alarm or the alarm shows up several hours after the scheduled time. It happens sporadically and I have not found any correlations with other things with my Mac. Does anyone has any clue/solution to this?
Thanks!

Welcome to the discussions Jennifer.
It sounds like you have more serious problems than a missed alarm!
To establish whether your problems are user-based or system based, you could make a new user, log on as that user, and run iCal. Add a few events, set a few alarms, make an extra calendar or two (but don't subscribe to any) quit and restart iCal a couple of times and let us know how you get on.
AK

Installing Yosemite failed om 2012 Mac PRO

I have tried to install Yosemite on my Mac PRO (OS X 10.9.5) It looked good in the beginning but turned out to be a total disaster.
I couldn't start my computer again. I tried it again but it failed again! Now I put OSX 10.9.5 back on again and luckily it works. Only lost a couple of files.
Good lesson: make a back-up before installing Yosemite!!!!! Use the Time Machine and a separate hard disk.
What is wrong with Yosemite or the Mac PRO that it doesn't work??
Please help.
Suggestion to alle Mac PRO users don't install Yosemite until this problem is solved by APPLE.

First, look at this article and see if your model can do an Internet Recovery: Computers that can be upgraded to use OS X Internet Recovery. If yours needs the firmware update, then do that before moving on.
Install Mavericks, Lion/Mountain Lion Using Internet Recovery
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Internet Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
Partition and Format the hard drive:
Select Disk Utility from the main menu and click on the Continue button.
After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
Reinstall Lion/Mountain Lion. Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Install button. Be sure to select the correct drive to use if you have more than one.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
This should restore the version of OS X originally pre-installed on the computer.
If for some reason your hard drive cannot be repartitioned or is not even visible in Disk Utility, then the drive has failed and needs to be replaced.

Offline Servicing Keeps Failing SCCM 2012 SP1

Has any one seen this? Below is my log file.
The Schedule with ID 16777266 will be run now. It's run time is at Wed Jan 23 21:25:19 2013 Eastern Standard Time SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 5468 (0x155C)
Schedule with ID 16777266 is active SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 5468 (0x155C)
Schedule processing thread started. ThreadID = 0x270 (624) SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 5468 (0x155C)
1 Schedule(s) are marked for RunNow by the administrator SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 624 (0x0270)
1 Schedule(s) are scheduled to be run at this time SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 624 (0x0270)
Processing started for Schedule with ID 16777266 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 624 (0x0270)
STATMSG: ID=7900 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=B04SCCM.gstboces.org SITE=GSB PID=2780 TID=624 GMTDATE=Thu Jan 24 02:25:19.490 2013 ISTR0="16777266" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:19 PM 624 (0x0270)
Initialization of schedule processing succeeded SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
There is an image associated with this schedule. SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
Total number of individual updates to be installed is 49. SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
STATMSG: ID=7903 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=B04SCCM.gstboces.org SITE=GSB PID=2780 TID=624 GMTDATE=Thu Jan 24 02:25:22.682 2013 ISTR0="GSB00118" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
Copy image ( ID GSB00118, size 6591 MB ) SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
copying file from '\\b04conmgr\images\w8baseTSTX64.wim' SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
to 'C:\ConfigMgr_OfflineImageServicing\GSB00118\w8baseTSTX64.wim' .... SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:25:22 PM 624 (0x0270)
Copying (25% complete)... SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:26:18 PM 624 (0x0270)
Copying (50% complete)... SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:27:05 PM 624 (0x0270)
Copying (75% complete)... SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:27:49 PM 624 (0x0270)
Copying (100% complete)... SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:28:34 PM 624 (0x0270)
STATMSG: ID=7905 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=B04SCCM.gstboces.org SITE=GSB PID=2780 TID=624 GMTDATE=Thu Jan 24 02:28:34.068 2013 ISTR0="GSB00118" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:28:34 PM 624 (0x0270)
[Schedule ID 16777266] Started processing image package with ID GSB00118 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:28:34 PM 624 (0x0270)
STATMSG: ID=7906 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=B04SCCM.gstboces.org SITE=GSB PID=2780 TID=624 GMTDATE=Thu Jan 24 02:28:34.099 2013 ISTR0="GSB00118" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:28:34 PM 624 (0x0270)
Image package file with ID GSB00118 contains 1 image(s) SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:28:34 PM 624 (0x0270)
Processing image at index 1 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:28:34 PM 624 (0x0270)
Mounting image at index 1. Image file='C:\ConfigMgr_OfflineImageServicing\GSB00118\w8baseTSTX64.wim', MountDirectory='C:\ConfigMgr_OfflineImageServicing\GSB00118\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite' SMS_OFFLINE_SERVICING_MANAGER 1/23/2013
9:28:34 PM 624 (0x0270)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 2, MajorVersionLS = 9200, MinorVersionLS = 16384 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:39:44 PM 624 (0x0270)
Content '5df26118-a385-425f-ac7b-d6e0c26f5a7a' not found in content library on this site. Software updates should be distributed to this site. SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:39:44 PM 624 (0x0270)
UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:39:44 PM 624 (0x0270)
Completed processing image package GSB00118. Status = Failed SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
Successfully deleted entry from database for schedule ID=16777259 Name="" assigned to ImageID=GSB00118 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
Updated history for image package GSB00118 in the database SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
Schedule processing failed SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
Processing completed for Schedule with ID 16777266 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=B04SCCM.gstboces.org SITE=GSB PID=2780 TID=624 GMTDATE=Thu Jan 24 02:40:40.929 2013 ISTR0="16777266" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
Deleting
\\?\C:\ConfigMgr_OfflineImageServicing\GSB000A2\ImageMountDir\Program Files\Common Files\SpeechEngines\Microsoft\TTS20\en-US\enu-dsk, FAILED, Win32 Error = 5 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:40 PM 624 (0x0270)
Failed to remove the staging folder C:\ConfigMgr_OfflineImageServicing, GLE = 5 SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:41 PM 624 (0x0270)
Schedule processing thread stopped SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:41 PM 624 (0x0270)
Checking if there are schedule(s) which need to be run at this time. SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:40:41 PM 5468 (0x155C)
This line in the log seems to be where the process errors out.
Content '5df26118-a385-425f-ac7b-d6e0c26f5a7a' not found in content library on this site. Software updates should be distributed to this site. SMS_OFFLINE_SERVICING_MANAGER 1/23/2013 9:39:44 PM 624 (0x0270)
I have looked and this update is deployed and located on the sites distribution points. I am stumped. Anyone else see this before.
Thanks

Hi yannara
you're right about getting this error while offline patching my image.
what I don't understand is the steps to find the KB number?
on my Software Updates pane the only column with guid I found is Update Unique ID and its guid does not match in anyway from the guids I see in the offlineservicing.log file
just to be clear, I update Win8.1 x64 image and I created a search criteria with all Windows 8.1 updates and downloaded them to a package on my site.
Applicability State = INSTALLED, Update Binary = E:\ConfigMgr_OfflineImageServicing\5282016d-a4eb-41fc-97d8-0a5a00e136cc\windows8.1-kb3008242-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 2:57:13 PM 292 (0x0124)
No need to apply this update binary since it's already installed. SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 2:57:13 PM 292 (0x0124)
Content '4e6dbf75-645e-4387-85dc-27bd6db32227' not found in content library on this site. Software updates should be distributed to this site. SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 2:57:13 PM 292 (0x0124)
UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 2:57:13 PM 292 (0x0124)
Completed processing image package ILP000AB. Status = Failed SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 3:01:57 PM 292 (0x0124)
Successfully deleted entry from database for schedule ID=50331650 Name="" assigned to ImageID=ILP000AB SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 3:01:57 PM 292 (0x0124)
Updated history for image package ILP000AB in the database SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 3:01:57 PM 292 (0x0124)
Schedule processing failed SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 3:01:57 PM 292 (0x0124)
Processing completed for Schedule with ID 50331658 SMS_OFFLINE_SERVICING_MANAGER 2/18/2015 3:01:57 PM 292 (0x0124)
notice that my problem is not with KB3008242. it is the one after - which I don't get its number. only the GUID.
so apparently, I have no way to find this one annoying update from 140 available updates.
I hope that MS solution is not to deselect each time updates until I will find it manually
any solutions please?
Tamir Levy

Daily Repeating iCal Alarm fails after 4/1/06. DST related?

On two separate machines I maintain, a repeating alarm stopped working after April 1, 2006. The machines were both running 10.4.3, but are in different locations. Each of them has a daily repeating alarm that is set to open an Automator action at 11:30pm daily. Neither machine had the iCal application actually running (they are automation machines...no user), and iCal application probably hadn't been run for some time.
I realized today (April 4) that the last time the event ran was April 1. I opened iCal on each machine, and each case the Automator action immediately ran (even though it was nowhere near 11:30pm).
Hopefully the alarm will work again now. I wonder if this has something to do with the DST change. Any thoughts on what might have happened? Anyone else experience unreliable alarms after the DST change?
PowerMac G5 Quad 2.5 Mac OS X (10.4.6) http://www.markandjo.com/markblog

Welcome to the discussions Jennifer.
It sounds like you have more serious problems than a missed alarm!
To establish whether your problems are user-based or system based, you could make a new user, log on as that user, and run iCal. Add a few events, set a few alarms, make an extra calendar or two (but don't subscribe to any) quit and restart iCal a couple of times and let us know how you get on.
AK

Import Drivers Fail- SCCM 2012 R2

Hello,
I am having issues with importing drivers and adding them to a driver package. The error message that I am receiving is "The SMS Provider reported an error." Our environment has a single SCCM 2012 R2 for the site. I looked through the SmsAdminUI
log file and found this:
[8, PID:5444][09/02/2014 16:32:48] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:32:55] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_B9DDE7DF4661034EC956AC906BFFD363E845403FB0986F0FE59D21EA87042303) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_B9DDE7DF4661034EC956AC906BFFD363E845403FB0986F0FE59D21EA87042303";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:32:59] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:03] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_8F9AF41BF5B833AAE3DD249A3C9D567CD9FA9311B521BC20A4CEB3E36B48E427";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:09] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_ADCC44F92EB0E9B4B03925B054A05AA544097BCF_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:13] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80) has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_C4E6DA78F9AF1BEE85077F65AEE0C6B7A7512E16_B35AE527E5F0B2DF31D07AE67C0217191797CD26C68355231E0EE7E2B71D6F80";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:17] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n
[8, PID:5444][09/02/2014 16:33:17] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters)
at Microsoft.ConfigurationManagement.AdminConsole.Driver.PackagesToDriversControl.UpdatePackage(PackageInfo packageInfo)\r\nConfigMgr Error Object:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\nSystem.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.ExecuteMethod(String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "CIContentSourcePath - '\\\\aps-sccm\\sources$\\Drivers\\Driver Sources\\Dell Precision T1700\\USB\\Drivers\\HCSwitch\\x86' could not be found\n";
ErrorCode = 3;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssppackage.cpp";
Line = 3827;
Operation = "ExecMethod";
ParameterInfo = "SMS_DriverPackage.PackageID=\"APS00049\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
\r\n

Hello,
I am having issues with importing drivers and adding them to a driver package. The error message that I am receiving is "The SMS Provider reported an error." Our environment has a single SCCM 2012 R2 for the site. I looked through the SmsAdminUI log
file and found this:
[8, PID:5444][09/02/2014 16:32:48] :System.Management.ManagementException\r\nGeneric failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, Boolean traceParameters)\r\nManagementException details:
instance of SMS_ExtendedStatus
Description = "This driver (id=SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC)
has already been imported into the driver catalog.";
ErrorCode = 183;
File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspdriverci.cpp";
Line = 712;
ObjectInfo = "SCOPEID_B12D92AC-221E-4E8C-BFFA-3189C7988C63/DRIVER_8377D013536B9BAE158F0E5DE037A5DCCD06FA57_71FC22A08C28649AB32043B429AA6AB726BE536ABB4CAFA083E82699CBD027BC";
Operation = "ExecMethod";
ParameterInfo = "SMS_Driver";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
the driver already exists in the catalog..
http://technet.microsoft.com/en-us/library/2240a538-f7c1-4118-8b7b-894950dd5c34#ImportingWondowsDeviceDrivers
did you "Specify the option for duplicate drivers: Select how you want Configuration Manager to manage driver categories when a duplicate device drive is imported." ??
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Calendar alarm fails to run Automator script if Mac is sleeping

I have an Automator script to run a backup task which is saved as a Calendar alarm to run once every week.
This was working perfectly in Snow Leopard - if the computer was asleep at the alarm time, then it would simply run the next time the computer is woken up.
Then I upgraded to Mountain Lion, and had various issues. First, the alarm got imported to iCloud and caused unwanted pop-up alerts on all my iOS devices, but I resolved that by moving the alarm's calendar from "iCloud" to "On My Mac" (described here).
Now I'm finding that if the computer is asleep at the alarm time, the script doesn't run at all.
I don't want the computer to wake up in order to run the script, but to run the next time the computer is woken up, just like it did on Snow Leopard.
Is this a known difference in behaviour between Snow Leopard and Mountain Lion, and is there any way to get the old behaviour?

As no-one has confirmed whether this is expected behaviour or a bug, I've assumed it is a bug and raised a bug report at http://www.apple.com/feedback/macosx.html.
In the meantime, I've created a repeating task in my To Do list app to remind me to run the backup script once a week (I'm using Cultured Code "Things" for task management).
When the task pops up, I run the Automator workflow MANUALLY by double-clicking on the workflow ".app" file.
It seems insane, but this is the only way I can be sure the Automator script runs once a week.

Why does my alarm occasionally fail to vibrate and make sound?

I use my alarm on my iPhone 5 every day to wake up. I would say that 99.9% of the time it works.
Maybe once every few months, however, the alarm fails to go off. The phone will show the appropriately display (I use snooze, so the snooze button is ready to be pressed). When I last experienced this problem I shut the phone off and turned it back on, and the alarm triggered (noise and vibration) as soon as the phone turned on.
This isn't a case of me hitting snooze or disabling the alarm by mistake. It's not a case of a 3rd party app trying to do something with the alarm. It's not a case of using an outdated OS because I'm currently on the latest (and this has happened on other OS versions, anyway, and happened on my 3GS a few times, too). Even though it doesn't matter (because I have kept it on the same settings since I bought the phone when it came out), my phone is always on silent. So that isn't the culprit either, because alarm works just fine on silent.
This is a major problem even though it is rare. I use this phone to wake up for work. If you google it you'll see others experience the same problem (but I couldn't find a solution).
-Do others experience this problem on here?
-Has Apple said anything about it or at least acknowledged it is an issue?
-How do I get Apple to acknowledge my concerns?
If this keeps happen, even infrequently, my next phone is an Android.

Exactly the same problem.
Been late from work several times because the alarm goes silent.
Then when you wake up and check it, there's no ringtones, no alarms, no alerts, no message sounds, nothing from the apps, no keyboard sounds, absolutely nothing coming out of the speaker.
Yes, the mute switch is off. Yes, the volume is on. No, there's no dirt or dust in the headphone plug. I have never once even used the Do not disturb function.
Only rebooting helps.
This happens every once in a while for no apparent reason.
The thing that really disturbs me that this is my THIRD (3rd) iPhone in a row that has the same problem. Since that's the case, I've been very hard trying to figure out - and hoping - that the problem is something that I keep doing. I just don't know what it is.
Been using Nightstand app. Removed it now completely. That probably won't help either.
Had my previous iPhone5 changed to a new one exactly 10 days ago for this very reason, and here we go again - the same bug is here. Not funny.
I have been reading discussion boards a lot and it seems that this is a fairly common problem. However, nobody has come up with a solution.
If someone figures that out, he/she's gonna make a lot of customers happy.

Alarm clock Fails to ring

There is an annoying bug with the Nano alarm clock whereby it fails to ring, and I hope there is a fix for it.
I get this behaviour mostly by doing the following:
Set a recurring alarm to say 7
After midnight on the date of the alarm and before it is due to ring, change the alarm time to one hour earlier.
result is that the alarm fails to ring.
This is a 5th gen Nano. Any fixes out there?

thx, but it has external speakers though it is hooked up to a Bose system overnight.
The alarm does work the mojority of the time, but in some situations (such as outlined above) does not

Alarm failed Jan1 2012

Similar Messages

Maybe you are looking for