account

[Guest]

Hi is it possible that with my current account I cannot make use of your library? I logged in years ago, but never really tried your product. Now I would like to do. bye

[Guest]

Hi Andreas You should still be able to use your account and your login even though it has been a while since you signed up. You should download the monitor library that fits your platform and use one of the product key (that can be located inside our app) to register usage on your product. What are you experiences now and what is stopping you from using the library. I'll be more than happy to guide you along so just drop a few lines on what is holding you back and I'll help you as best I can. Best regards Soren EQATEC Team

[Guest]

Hi Soren Thanks for reply, I made now a new account with my private email address and could do the thing. Now I will try to include it in my CF application, but will take some time cause other things are to be done first. May be afternoon I will be so far.   kind regards Andreas 

[Guest]

Hello Soren Got an NotSupported exception when loading the monitor, is that related to the Demo Code? The eqatec.analytics.monitorcf.dll is on my compact framework device. Here the exception + stack trace and some pictures: System.NotSupportedException ist aufgetreten. Message="0x80131515" StackTrace: at EQATEC.Analytics.Monitor.NativeMethods.GetDisplays() at EQATEC.Analytics.Monitor.OSInfo.GetScreenInformation(OSInfoObject osInfo, ILogAnalyticsMonitor log) at EQATEC.Analytics.Monitor.OSInfo.GetOSInfo(ILogAnalyticsMonitor log) at EQATEC.Analytics.Monitor.AnalyticsMonitorFactory.Create(AnalyticsMonitorSettings settings) at EQATEC.Analytics.Monitor.AnalyticsMonitorFactory.Create(String productId) at Server.Form1..ctor(Int32 startarg) at Server.Program.Main(String[] args) [cid:[e-mail]08FE90] kind regards Andreas

[Guest]

Hi Andreas That sounds like a bug on our part (and such an exception should have been caught internally in the monitor). I'll look into this straight away and get back to you as quickly as possible Best regards EQATEC Team

[Guest]

Hi Andreas I've had a quick look at the code and as far as I can tell we have at least a few catch-all exception handlers guarding the code that throws the exception (which apparently happens because some of our native P/Invoke calls to resolve device properties is not supported on your CE platform). Could you please confirm whether you are able to continue execution (i.e. pressing F5 and letting the program continue) or if this exception crashes/terminates the program? Dependent upon your settings you may have checked off "Break on all exceptions" when debugging and our internal exception is being caught as well as pauses the debugging session. Hoping to hear from you soon Best regards Soren EQATEC Team

[Guest]

Yes the application is running and when I check off this [cid:[e-mail]080] I do not see your exception. So you mean I can ignore that safely? If yes, I would have another question. Does my machine where your tool is running need to have direct internet access or what kind of preparation do you need for your IP packets to be transmitted to your server. Are company internal routers or bridges a problem ? I ask because I do see no results in my dashboard and may be I need to check the pipe from my device to your servers. Our machines are running on a subnet here that is separated from usual networking, and is connected somehow via some tools that I do not know so I can access it from my developer PC from our usual subnet(what has internet access of course).  kind regards Andreas

[Guest]

Hi Andreas Yes, If you check of that box you should not have the debugger break on our internal exceptions (I wish there were some way we could hide this, but apparently not, see http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2486532-allow-the-debugger-to-stop-on-user-handled-and-thr) As far as internet connectivity, then yes, the device/machine where our machine is running needs some kind of internet access. By default we try to get to our servers (at eqatec-monitor.com) using http, port 80 and any default proxy settings on the machine/device. If you are aware of any other settings that are needed to access the internet, for instance utilizing the connection to your developer PC) then that has to be configured. You can do so using the Proxy setting when creating the monitor instance (see http://api.eqatec.com/analytics/dotnet/html/P_EQATEC_Analytics_Monitor_AnalyticsMonitorSettings_ProxyConfig.htm) This is usually a configuration issue on the device. A good preliminary test is checking if the device is able to connect to the internet (e.g. google.com) using e.g. the standard browser if available or using a very simple application that just creates a WebRequest and gets a response. Once the device is able to connect, our monitor library should be able to use same connection. Of course you may have internal router policies etc. that only limits connections to certain internet addresses. We use standard http and port 80 since that has the highest chance of being permitted inside corporate networks but your specific setup may be different. Hope this helps. If you need further details or assistance, please don't hesitate to get back to us Best regards Soren EQATEC Team