An update on this piece of junk that I was fleeced into trying. I regret very much.
UB Extractor Problem
It has now screwed up completely and thats less than a year of rather light usage. Not exactly industrial usage capacity is it. ;-)
Guess what as expected the cowboy company won't cover its maintenance even though it is , well what do you expect from cowboys. And their sad interpretation of why the machine has completely broken down is.
Well you got to laugh, they say the electric board on the panel is broken and it is BECAUSE I cleaned the panel with water so I have to pay for all the parts to replace the electric board. What a joke, imagine if someone came to tell you, we won't fix your washing machine for free while its under warranty period because you cleaned the front panel with a wet cloth. Amazing how cowboy companies talk and bully us with their tactics.
Well, having learnt my lesson, we decided to just throw this thing away and get a good old traditional Siemens extractor with very standard spec with Siemens' own maintenance and it costs less that the above piece of junk.
Don't believe any salesman offering you this piece of rubbish. Avoid, stay away even if its built and demo looks impressive. Don't fall sucker for it. It is an expensive turd.
I recently came across the same problem where some JQuery Code that I had absorbed from Jan Tielens's example just won't work on a Chrome browser.
Then I came across this http://maxmorrow.wordpress.com/2012/06/17/jquery-caml-query-lists-asmx-web-service/
And it was exactly what I was looking for.
$(xData.responseXML).find(“z\\:row”).each(function() {
to this:
$(xData.responseXML).find(“z\\:row, row”).each(function() {
This has struck us finally, where some users who have had account IDs changed in the AD starts experiencing problems accessing the site.
For example, I was once mydomain\kong kong now I have had my ID changed to mydomain\kong lo
You might find the problems of logging into SharePoint site becomes intermittent or seems to work but then suddenly stops working.
You will also find that it is possible that adding the old account ID's access can still work. Although sometimes, SharePoint will prevent you doing it by warning the account is not unique.
It is best for situation like this to do an STSADM -o migrateuser command for these users in order to get rid of the the anomaly with the old account ID lying around in SharePoint's site collection user table.
See post below.
http://littletalk.wordpress.com/2009/12/14/the-user-does-not-exist-or-is-not-unique/
However, the thing to be most careful about is if this has happened to a Service Account that is being used to systematically access SharePoint libraries from say a batch program on a Server.
Granting the access to the old now renamed account ID can have fatal consequences for the WebClient Service that runs. It can crash it and the only way to recover it is to reboot the server or kill it via the task manager after knowing its process ID.
http://support.microsoft.com/kb/2548470
The crash can happen not immediately after granting the access to the old account ID, it can look like all is fine and even files can get written into SharePoint, until all of a sudden may be a Windows Server Audit process runs, it probably flags up the access violation and crashed the WebClient service causing the problem.
