Windows 2008: Transaction support within the specified resource manager is not started or was shut down due to an error.

Follow me Yesterday a client reported an issue that they are unable to create schedule task on a SBS 2011 server, upon checking I found that the schedule task wizard launches fine and goes almost till completion and just as we click on finish we get the following error. Transaction support within the specified resource manager is not started or was shut down due to an error. I felt very lucky when with the first google search I stumbled upon various blogs and articles including Microsoft suggesting the corruption in transaction manager log and  the following command (from command prompt) to resolve the issue quick. fsutil resource setautoreset true c:\ Pumped with adrenaline, I performed the command (from command prompt) and rebooted the server but unfortunately the issue persisted upon the reboot. I did try the reset a couple more times & of course multiple reboots with no success. I went ahead and checked the event viewer which also was giving multiple error while loading. I did find multiple errors in it, mostly about Windows search service failing the start mostly because of again some transaction log. Refer the error events below Event ID 7034: The Windows Search service terminated unexpectedly.It has done this 12 time(s). Event ID 7023 The Windows Search service terminated with the following error: Transaction support within the specified resource manager is not started or was shutdown due to an error. Event ID 1006 The Windows Search Service has failed to create the new search index. Internal error <10, 0x80071a91, Failed to save Crawl Scope Manager changes: >. Event ID 1029 Windows Search Service failed to process the...

Windows 2012: RDP Black screen event ID 7011 A timeout (30000 milliseconds) was reached.

Follow me On a windows 2012 server, client reported RDP black screen randomly, it used to work fine for few days, probably even for months but randomly it used to get stuck on black screen and the only solution was to reboot the server. I have already written an article in this regard which covers most possible reasons for this issue.  You should make sure you  follow that before checking out this one,  this one is specifically if you have the event id 1711 on Windows Server 2012/R2 event log. Source:        Service Control Manager Date:          27-4-2012 7:28:01 Event ID:      7011 Task Category: None Level:         Error Keywords:      Classic User:          N/A Description: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Spooler service.   After ruling out all the obvious reasons on the server listed here, our research reveal that this RDP black screen issue is happening because of some printer drivers installed on the Windows 2012 server.  Although I am not very sure which printer drivers are causing this issue but following are the steps to resolve the concern. 1) Install all the pending windows updates on the server 2) Uninstall all possible printer drivers including PDF writers from the Server.  I recommend that you keep the drivers uninstalled for a monitoring period if possible, otherwise uninstall all the drivers and reinstall the latest copies of only the most required drivers that too, after completing all the steps below. 3) If HP drivers are installed on the server, ensure to either remove them or stop the services Net Driver HPZ12 and PML Driver HPZ12 (if present). 4) Remove...

Windows 2012 R2: Nslookup Fails to query the A record

Follow me Recently a Client reported that he was unable to access his website, We were able to ping the website but if  we  nslookup the same name it gives the error as shown in the screenshot.   It looked like the DNS wasn’t responding in that case the ping should also fail with destination not found error, but that wasn’t happening.  In any case we restarted the DNS server and DNS client service on the server ( this was the domain controller so had DNS installed on itself) but still the nslookup failed to resolve the name of the site. Interesting thing to note is that now we were able to open the website as well on the server but the nslookup was still failing. After having no progress in this troubleshooting, I thought about using some other tool, so I tried Port Query from the same server. I tried to reach google through it and surprisingly it was responding.   This step cleared explains that the server is able to resolve the names just fine ( as Portqry will also use the DNS server listed on this server to resolve the names) and its just the nslookup which is not able to resolve the names to IP. We concluded that nslookup on Server 2012 or probably just this server was buggy and the purpose to write this article was also to suggest not to entirely depend on nslookup on windows server.  Hope this information helps many of you out there. Feel free to report new issues on our forum for expert help or open a paid support incident...

Store Credentials in Remote Desktop Client

Follow me I have been facing this issue since long, Its with the Remote desktop client I use to connect to terminal server. Despite of me putting the check to remember password, it still repeatedly prompts for the credentials. This time I decided to fix the issue, hope this helps you as well The solution is really simple. Follow the steps below- 1. Open the CMD Prompt. 2. Type “gpedit.msc”, hit enter to open the local group policy editor, you can also do same from domain policies if the PC/Server is part of domain. 3. Navigate to- Computer Configuration\Administrative Templates\System\Ceredentials Delegation 4. Open the policy setting “Allow Saved Credentials with NTLM-only Server Authentication” (or “Allow Delegating Saved Credentials with NTLM-only Server Authentication”) 5. Click Enabled and click on “show” 6. Enter the server where we need to connect to with the stored credentials. Wildcard can be used so choose “TERMSRV/*” . 7. Close the screen and run “gpupdate”. After following the above steps, if it still requests for credentials then please reboot you PC. For any further assistance, feel free to start a new thread on our forum. Follow...

Windows 2008 R2: Unable to open server manager or event viewer Error:System.Reflection.TargetInvocationException

Follow me One of the Windows 2008 R2 server suddenly started to have some issue with Event Viewer and Server Manager not loading with following error. System.Reflection.TargetInvocationException Exception stack trace : at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at Microsoft.ManagementConsole.FormView.InternalInitialize() at Microsoft.ManagementConsole.View.HandleInitializationRequest(IRequestStatus requestStatus) at Microsoft.ManagementConsole.View.ProcessRequest(Request request) at Microsoft.ManagementConsole.ViewMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo) at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback) I researched on the issue and found suggestions to uninstall/reinstall or repair .Net 3.5.1. We successfully repaired Dot net on the server with no success with the primary issue. Further research pointed me towards some issues with system fonts can cause this problem, after hunting around bushes for several font settings I finally looked at the following registry location. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts All the values (font names) has data with wierd names ending with numbers like times_01.ttf or arial_05.ttf I went ahead and Exported the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts registry from another working server 2008 R2 and imported it right into the problem server. Voila 🙂 , this resolved the issue for me. I closed and reopened server manager and Event viewer, all comes up just fine. PS: If it doesn’t straight away you may reboot the server Hope this article helps you fix the issue at hand, else start a  thread at our forum for free support or reach us for paid support options....

IIS Application Pool Keeps crashing:A listener channel for protocol ‘http’ in worker process reported a listener channel failure

Follow me A issue was reports on a Windows 2008R2 IIS server where the hosted site was going down repeatedly, Investigation revealed  IIS Application pool keeps crashing with the following event logged in event viewer. Log Name:      System
Source:        Microsoft-Windows-WAS Event ID:      5139
                           Task Category: None Level:         Warning
Keywords:      Classic
User:          N/A Description:
A listener channel for protocol ‘http’ in worker process ‘XXXX’ serving application pool ‘Name of AppPool’ reported a listener channel failure.  The data field contains the error number.   Upon further troubleshooting we found some corruption in IIS binaries, To validate that we executed SFC /ScanNow and checked the Cbs.log (%windir%\logs\cbs\cbs.log). The Log revealed the files which sfc /scannow wasn’t able to repair, we un-installed the updates relevant to those files and installed the latest hotfixes of those files. Rebooted the Server and found IIS working fine. Feel free to report new issue on our forum Follow...