As a rule I access OPENVPMS with Firefox. however recently I began using Chrome for a number of reasons and I have started getting the following errors...We use the stand alone installation of Chrome to avoid the significant bloat chrome introduces to systems that install it as a user app.

The error is random but always occurs on a page with a datechooser box

EPDateChooser.prototype.clearTime = function(date) { date.setHours(0,0,0,0); return date; ........................ if (!processor || !processor.process) { throw "Processor \"" + processorName + "\" not available."; } processor.process(messagePartElement); } complete = true; } finally { EchoServerMessage.status = complete ? EchoServerMessage.STATUS_PROCESSING_COMPLETE : EchoServerMessage.STATUS_PROCESSING_FAILED; } ....... if (EchoServerMessage.processingCompleteListener) { EchoServerMessage.processingCompleteListener(); } EchoServerMessage.processAsyncConfig(); } catch (ex) { EchoClientEngine.processClientError("Cannot process ServerMessage (Phase 2)", ex); throw ex; And Ex is Value of EX is ex: TypeError arguments: undefined get stack: function getter() { [native code] } arguments: null caller: null length: 0 name: "getter" prototype: getter constructor: function getter() { [native code] } __proto__: Object __proto__: function Empty() {} apply: function apply() { [native code] } arguments: null bind: function bind() { [native code] } call: function call() { [native code] } caller: null constructor: function Function() { [native code] } length: 0 name: "Empty" toString: function toString() { [native code] } __proto__: Object message: "this is not a Date object." set stack: function setter() { [native code] } arguments: null caller: null length: 1 name: "setter" prototype: setter __proto__: function Empty() {} type: undefined __proto__: Error arguments: undefined constructor: function TypeError() { [native code] } name: "TypeError" stack: undefined type: undefined __proto__: ErrorPrototype message: "Cannot process ServerMessage (Phase 2)"

It generally throws 2 errors in quick succession then disposes of the error call and locks up with the screen displaying the usual grey box with Please Wait ..reloading the screen clears the error with no loss of data.

I also get this non fatal warning Resource interpreted as Script but transferred with MIME type text/plain: "http://ascot1:8080/openvpms-demo/app/1?serviceId=Echo.ClientEngine". _______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf