Many SharePoint scripts are run using the native Windows Task Scheduler to automate actions while end-users are enjoying the portal experience.
Most of these are triggered at various intervals to update lists, send automatic email notifications, reminders or some important business information to stakeholders. At various instances, I recd. issues from end-users complaining about not receiving information on time that were triggered off using the task scheduler.
My investigation revealed that the Windows Task Scheduler has tasks that were running indefinitely with their status frozen on “Running”. This was an obvious concern as most of the scripts took fraction of a second to execute. Furthermore, if I right clicked an affected item and choose to “End Task” produced absolutely no effect.
Immediate response would be to end up rebooting the server or finding some other way of killing svchost.exe tasks that could kill your SharePoint processes if they were dependent on any. It was not the scripts in itself but the scheduler threads that launched and then hung themselves.
With a bit more digging around and research, I discovered that restarting the task scheduler service did the trick. Just launch Services.msc and restart the Windows Task Scheduler. The status on the hung tasks should clear themselves or refresh to reload new status.
I’m not sure what caused this to happen. Will debug my scripts to see if they are causing it to hang.
Nevertheless, one more issue workaround for making life easier…!
You might have wondered about how to setup Failover Cluster inside Hyper-V Virtual Machines. As you know, the major element of a cluster is the shared storage piece. Inside Hyper-V VMs, iSCSI is the only supported method of providing shared disks over virtual NICs.
Here are detailed steps on how to create Highly Available resources inside Hyper-V Windows Server 2008 R2 VM.
Check this out on Mark’s blog
“From an IT standpoint, one of the great new capabilities of Windows 7 and Windows Server 2008 R2 is the ability to securely connect clients to the corporate network without going through a VPN. This capability, called DirectAccess , establishes bi-directional connectivity with a user’s enterprise network every time a user’s DirectAccess-enabled portable computer connects to the Internet, even before the user logs on. You can now download the Infrastructure Planning and Design (IPD) Guide for DirectAccess to help you design a DirectAccess infrastructure.” *
* The above excerpt has been copied from an MS Technet newsletter.
“The Windows® 7 and Windows Server® 2008 R2 operating systems introduce DirectAccess, which allows remote users to securely access enterprise shares, Web sites, and applications without connecting to a virtual private network (VPN). DirectAccess establishes bi-directional connectivity with a user’s enterprise network every time a user’s DirectAccess-enabled portable computer connects to the Internet, even before the user logs on. Users never have to think about connecting to the enterprise network and IT administrators can manage remote computers outside the office, even when the computers are not connected to the VPN.”