Updated the theme causing issue with xml in blogger

Changed the theme because I can,
forgot to check my customisation that I put in before
google's code says use

<script src="https://google-code-prettify.googlecode.com/svn/loader/run_prettify.js?lang=css&skin=sunburst"></script>

which causes a xml error where the delimiter ; is missing

change
& to &amp;

<pre><script src="https://google-code-prettify.googlecode.com/svn/loader/run_prettify.js?lang=css&amp;skin=sunburst"></script>
</pre>

sigh.. 40 mins lost

Troubleshooting Server unable to look up internal FDQN "result too large", unable to RDP to server, but can browse and read eventlogs

 nslookup internaldomain.local

 Troubleshooting Server unable to look up internal FDQN "result too large", unable to RDP to server, but can browse and read eventlogs

Quick answer: port exhaustion, kb out there to fix this stuff.

nslookup

 internalserver.internaldomain.local can't find internaldomain.local: unspecified error

1. clear dns servers

2. added dns servers in Core Data centre

3. tried different dns servers in nslookup

3a. tried local dns server

4. modified host file with internal.local to server

fail

Check firewall (disable)

netsh advfirewall set allprofiles state off

result:

ok

Check Group Policy

Gpupdate /force

result:

Updating Policy...User Policy update has completed successfully.Computer policy could not be updated successfully. The following errors were encountered:The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).

To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.

check time

w32tm /query /peers

more nslookup

set debug

internaldomain.local

result

-------------

truncated answer

connect failed: result too large

-------------

check server's services

net stop dnscache

net start dnscache

net stop workstation

net start netlogon

Check Ports!

netstat -a -n

problem located - port exhaustion !!! 10000's of time_wait

----Hotfix Time---- (with bonus hotfix)

Windows6.1-KB2553549-v3-x64

Windows6.1-KB2264080-x64

there is a better rollup available(windows6.1-kb2775511-x64) but my server is not SP1. 

enjoy.

Java vs Terminal Server 2003 - CLSID

Users were experiencing a Red Cross for the applet, yet my administrative account was able to load the applet.

Looks like java or the installation process for java is not writing all the registry keys to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CAFECA-00xx…..

In IE, Java has a catch all applet version – which will always work (aka the latest version)

<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93

But most java call specific versions of java (for example).

<OBJECT classid=”clsid:CAFEEFAC-0015-0000-0013-ABCDEFFEDCBA




The server(s) for some reason didn't have all the keys in classes root, where compared to my windows 7 desktop.

I believe the install for some reason is writing the keys to HKCU instead of HKLM \classes...etc.

So fix is to add all the version to HKEY_LOCAL_MACHINE\SOFTWARE\Classes

http://pastebin.com/YhmwPTq7 contains my fix for 1.6u24 version

btw, Monitoring the registry when tick/untick the “use next generation java” in the java control panel, it just write all the entries to HKCU.

wmic “Invalid XSL format (or) file name.”

So on my windows 7 box trying to:

wmic product get /format:csv

produces a output:

Invalid XSL format (or) file name.

Located teh csv.xsl file in C:\windows\system32\wbem\en-US

Guessed that it was unable to locate the xsl format file...

so copied it to the local path and it worked !

Confirmed this with Process monitor :-(

It seems to be looking for the correct locale so I added a C:\windows\system32\wbem\en-US to C:\windows\system32\wbem\en-AU

since we all don't live in the US of A... :-|

Alternative options are:

I just copied to C:\windows\system32\wbem\en-US\*.xls to C:\windows\system32