Tag Archives: resolve

[RESOLVED] A process that is being terminated stops responding in Windows 7 or Windows Server 2008 R2 or Small Business Server 2011

You may find that when you try to terminate a process on Windows 7, Windows Server 2008 R2, Windows Small Business Server 2011 SBS 2011 that the termination process stops responding.  The main thread of the process becomes blocked and if you analyse the call stack of the process you will see that a thread is blocked in the ntdll!NtReleaseKeyedEvent() function.  This occurs because of a race condition whereby the main thread that is trying to terminate the process also tries to reactivate another thread when the thread released an SRW lock.

This issue can be resolved by installing a hotfix containing an updated Ntdll.dll driver.  You can find the hotfix download link in Microsoft KB 2582203 http://support.microsoft.com/kb/2582203

[RESOLVED] – Microsoft Exchange 2010 – Appointments exceeding 24 hours changed to multiple day All Day Event on Mobile Phones/Devices

Microsoft Exchange 2010 Service Pack 1 ActiveSync does seem to have issues with Appointments exceeding 24 hours that are not all day events (i.e. Friday to Sunday).  I have personally seen this issue with the iPhone 4 and 3GS, both were upgraded to IOS5 which did not resolve the issue.  The latest update “Microsoft Exchange 2010 Service Pack 1 – Hotfix Rollup 6” also does not seem to resolve this problem.

You might wish to test if you have the issue with your ActiveSync enabled Smart Phone or Device, you should be able to replicate the issue by asking a collegue to send you a meeting invite that starts on Friday at 4pm and then finishes on Sunday at 2pm, Once you accept the invite you will find that it has been changed to several all day events (Fri, Sat and Sun) rather than an appointment between the specified time period.

After a long wait it appears that this issue is resolved in Rollup 1 for Exchange Server 2010 – Service Pack 2, you can obtain the Rollup using the link below:

http://www.microsoft.com/download/en/details.aspx?id=28809 – Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995)

You can see the overall list of fixes/changes in Rollup 1 here:

http://support.microsoft.com/?kbid=2645995

The Fix we are most interested in is “A meeting item displays incorrectly as multiple all-day events when you synchronize a mobile device on an Exchange Server 2010 mailbox”

This was original raised in: http://support.microsoft.com/kb/2549255

You will need to ensure that you have updated your Microsoft Exchange 2010 Server to Service Pack 2 before you can install the Rollup so remember to factor extra time in for this.

You can obtain Microsoft Exchange Server 2010 – Service Pack 2 from here: http://www.microsoft.com/download/en/details.aspx?id=28190

Microsoft do seem to be aware of the issue and mention it in this Knowledgebase article

http://support.microsoft.com/kb/2563324 Current issues with Microsoft Exchange ActiveSync and Third Party Devices

Issue 1.6 – Appointment exceeding 24 hours changed to multiple day All Day Event
When an appointment item’s duration exceeds 24 hours, but is not marked as an All Day Event, Exchange ActiveSync changes the item on the device to become a multi-day All Day Event. The next time that the device synchronizes with the mailbox, the change is propagated from the item on the device to the item on the Exchange Server 2010 mailbox.

Solution
Microsoft is investigating this issue. This problem can occur when using any ActiveSync device synchronizing with Exchange Server 2010.

As you can see Microsoft do not currently have a solution to the problem and may well need to contact Apple and/or Google to produce a fix for both the iPhone and Android based handsets.

I would recommend contacting Microsoft Product Support and your mobile phone manufacturer if this issue is affecting you.  The more users that log the issue the higher priority it will be given and the quicker we can expect to see a fix emerge.

Windows Kernel Power Event ID 41 Error

Windows 7 or Windows Server 2008 R2 may restart unexpectedly, you may get a brief glimpse of a BSOD (Blue Screen of Death) and then find yourself back at the Windows login prompt.  When you inspect the Windows Event Log you will find the following event logged

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Event ID: 41
Level: Critical
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The additional info under the event is important because the various bug check codes can indicate different causes.

EventData
BugcheckCode          0
BugcheckParameter1    0x0
BugcheckParameter2    0x0
BugcheckParameter3    0x0
BugcheckParameter4    0x0

Having faced this error recently it eventually turned out that the problem was due to incompatible memory (not faulty memory).  The batch of machines in question were all branded but due to an error with the manufacturers memory compatability matrix had been supplied with the wrong additional memory modules.  When we reverted the machines to the standard 2GB module that was already installed they operated perfectly, we eventually arranged for the additional modules to be swapped and that was the end of the issue.

An important thing to remember is that a memory checker will not show that your memory is faulty if it just incompatible with your particular system or mainboard.

Your system or mainboard manufacturers support should be able to confirm memory compatability and advise on the correct upgrade/type for your system