Category: windows

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.     + CategoryInfo          : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc    eption     + FullyQualifiedErrorId : PSSessionOpenFailed

check: https://localhost/powershell

if it says module WinRM not found, edit C:WindowsSystem32InetsrvconfigApplicationHost.config file.

insert         <add name=”WSMan” image=”C:Windowssystem32wsmsvc.dll” />

under <globalmodules> section

may need to restart iis (iisreset in commandline). When running EMS it may take a while before finally connecting, then it’s plain sailing.

taken from: http://jaminquimby.com/joomla253/servers/81-windows-server/windows-server-2008-r2/473-cluster-name-resource-failed-registeration-in-dns

In DNS Management (dnsmgmt.msc):

1. Find the VirtualClusterName that is failing to register.
2. Right-Click Properties.
3. Select Security Tab.
4. Click Add.
5. Click Object Types.
6. Check off “Computers“; uncheck other options selected.
7. Enter in the name of the cluster (a.k.a Cluster Name Object (CNO)).
8. Click Check Names; Verify that the entry has been found.
9. Click OK.
10. Give the CNO FULL Control over this record.
11. Click OK.

To unload performance counters for ESE, perform the following steps:

• Close down any running versions of Performance Monitor and stop any other monitoring services that might be attempting to use those counters
• Open the Exchange Management Shell
• Type add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup and hit enter
• Type remove-perfcounters –definitionfilename “C:Program FilesMicrosoftExchange ServerV14BinperfAMD64eseperf.xml” and hit enter
  Note: Ensure that the path is changed to the correct location of eseperf.xml on your server

To reload performance counters for ESE, perform the following steps

• Close down any running versions of Performance Monitor and stop any other monitoring services that might be attempting to use those counters
• Open the Exchange Management Shell
• Type add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup and hit enter
• Type new-perfcounters –definitionfilename “C:Program FilesMicrosoftExchange ServerV14BinperfAMD64eseperf.xml” and hit enter
  Note: Ensure that the path is changed to the correct location of eseperf.xml on your server

http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.aspx

WSIM is used to create an xml file which can be used to automate installations of Windows 2012 servers.
The default settings (the ones that you may find in official documentation) are heavily biased towards US.
Here there are the settings that will get you going if you need to use the GB locales:

Components->[windowsPE->amd64_Microsoft-Windows-International-Core-WinPE__neutral

InputLocale: 0809:00000809
SystemLocale: en-GB
UILanguage: en-US
UserLocale: en-GB

Components->[windowsPE->amd64_Microsoft-Windows-International-Core-WinPE__neutral->SetupUILanguage
UILanguage: en-GB

Components->Specialize->amd64_Microsoft-Windows-Shell-Setup__neutral
TimeZone: GMT Standard Time

• this is enabled per VM; shutdown the VM
• edit the vmx file, adding the following lines:

  hypervisor.cpuid.v0 = "FALSE"
  mce.enable = "TRUE"
  vhv.enable = "true"

   

Event Type:    Error
Event Source:    MSExchangeCluster
Event Category:    Services
Event ID:    1005
Date:        06/03/2013
Time:        15:00:06
User:        N/A
Computer:
Description:
Exchange HTTP Virtual Server Instance 100 : The IsAlive check for this resource failed.

I have Exchange 2003 running in a Windows 2003 cluster. One of the cluster resources, “Exchange HTTP Virtual Server Instance” kept failing sometimes immediately after bringing it online (even description given above). The problem was intermitent, so it was difficult to replicate it in a production environment.

I have logged a call with Microsoft and their engineer was happy to observe that “it’s working now” and leave it like that. As I pushed him to give me a proper root cause, he declined by saying that I need to have “premium” support as opposed to the “professional” one that I had.

Anyway, enough of the perils of scripted support provision, which most of you reading this will already know about.

From what I was able to work out, the cause to this is lack of kernel memory and the solution is given here:

http://support.microsoft.com/?id=934878

In short go to registry

Click Start, click Run, type regedit in the Open box, and then click OK.

Click the following registry subkey:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesHTTPParameters

On the Edit menu, point to New, and then click DWORD Value.

Type EnableAggressiveMemoryUsage, and then press ENTER.

On the Edit menu, click Modify.

In the Value data box, type 1, and then click OK.

On the File menu, click Exit to exit Registry Editor.

You will need to (re)start HTTP.

the timeout errors in windows (error 1053) can be addressed by adjusting the UI timeout (default 60 seconds).
Check for the SMH log for entries such as this:
MAJOR 11/19/2012 2:19:24 PM
UI Timeout (limit: 120s) — vcagent(HPVersionControlAgent):359s||vcrepository(HPVersionControlRepositoryManager):0s||elm(backwardscompatibility):0s

which indicates that the one of the agents needed more time than that specified by the UI Timeout limit.

get the instance name:

select convert(nvarchar(128), serverproperty('servername'));