Got this error when click on login. Any idea where i went wrong?

Thanks.

Hi, Jenson. Had this previously been working, and now it stopped, or is this the first time you're trying to log in to O4W?

Thanks,

- Bryan Shumsky

Revelation Software

First time. Where did i go wrong? I am using Windows7 64bit home premium and i use a 32bit java runtime to load the oesocketserver.

It did not give me any error.Is it my OECGI3 registry? Any idea?

Is the message _just_ "Cannot process query", with nothing else displayed?

Did you follow the O4W getting started guide to configure everything?

Other than your username and password, can you post what your registry entries look like, and tell me exactly _where_ in the registry you put them?

NO. It displayed a very very long list that i cant copy. I manage to copy some.

Cannot process query: /%3Ft/examples/oecgi3.exe/O4W_LOGINtt0tCGI/1.1toffttext/html%2Capplication/xhtml+xml%2Capplication/xml%3Bq%3D0.9%2C*/*%3Bq%3D0.8ttthttp%3Alocalhost/exam….. Let me know what to look out for. Yes, i follow the guide. The registry, i follow exactly like the guide. I put it in the Hkey_local_machine, software, wow6432node, revsoft, oecgi3, examples. The entries i follow the guide but the guide did not say about a password. I also tried http://localhost/examples/OECGI3.exe/inet_trace and got the error cannot process query with a long error. Is this OECGI3 or then oesocketserver problem? Look more like OECGI3. Any ideas? </QUOTE> —- === At 21 JUN 2011 02:04PM bshumsky wrote: === <QUOTE>Hi, Jenson. Yes, it does seem like a failure in the web server to communicate with oecgi3.exe. A few more questions: - Is this IIS? What version of Windows are you using? - What version of OpenInsight? - Did you follow the directions for registering the oecgi3.exe "handler" in IIS (if you're using IIS)? It seems like the handler for oecgi3.exe may not have been set up correctly. Please take another look at the OECGI3 quick start guide (which should be in your "documents" folder under OpenInsight) to see if that helps. </QUOTE> —- === At 21 JUN 2011 06:04PM Richard Bright wrote: === <QUOTE>Just as a general observation - is not what I believe to be a fully supported network platform. That is, it may well function fine where the db is on the host PC - but I would not hold my breath on it working in a network context. I guess if you are sticking to OI and web publishing you may get away it. </QUOTE> —- === At 22 JUN 2011 08:31AM Jenson Goodwood wrote: === <QUOTE>I am using IIS 7 that comes with my Windows 7 64 bit home premium. Yes i did follow but no game. Still got the error. Where did i go wrong? Is it because its windows 7 64 bit home premium? </QUOTE> —- === At 22 JUN 2011 09:38AM Jenson Goodwood wrote: === <QUOTE>Does O4W work with windows 7 64 bit home premium? Anyone using it? </QUOTE> —- === At 22 JUN 2011 09:43AM Jenson Goodwood wrote: === <QUOTE>Oh forgot to tell you i am using the oi9.2.1 evaluation. What a bummer, cannot get it running to evaluate it. Help please, hope to solve this before it expires. </QUOTE> —- === At 22 JUN 2011 09:55AM Jenson Goodwood wrote: === <QUOTE>Could this be because of the 32bit java runtime running on my machine? But it can load the oesocketserver without error. I got both the 32 bit and 64 bit JRE and i use the 32 bit to load the oesocketserver and get no error. So the oengineserver should be ok right? Seems like OECGI3 not communicaiton with it. Wonder why? </QUOTE> —- === At 23 JUN 2011 08:43AM Jenson Goodwood wrote: === <QUOTE>Has any one got this error before or i am the only one? Bryan? Please help. </QUOTE> —- === At 23 JUN 2011 05:44PM Jared Bratu wrote: === <QUOTE>Can you post back the results of the http://localhost/examples/OECGI3.exe/inet_trace test. I understand it's a long error but based on the previous error you displayed for /O4W_LOGIN I'm wondering if you don't have a re-write rule or something mangling the URLs. Please run this command: %systemroot%\system32\inetsrv\appcmd list config ] iistemp.txt Email iistemp.txt to me [email protected] and I'll post the relevant sections back. It may also be worth while to clear out the IIS config and start from scratch. Home Premium isn't supported but it may work. One limitation between Home and Pro versions it the limit of 5 concurrent file share connections to the Home Premium server. If you are trying to configure this within the evaluation period please give me a call at the Revelation Office and we will work through the process together. </QUOTE> —- === At 24 JUN 2011 09:20AM Jenson Goodwood wrote: === <QUOTE>Emailed you. "One limitation between Home and Pro versions it the limit of 5 concurrent file share connections to the Home Premium server." What does this means? For a normal O4W webpage how many concurrent file does it take up? I also need information regarding licensing too. </QUOTE> —- === At 24 JUN 2011 04:44PM Richard Bright wrote: === <QUOTE>Jenson, I think part of the issue is intended use. As I previously said, if you are simply running OI on this home premium host and try using O4W on this same machine, you would possibly not come up the security and network OS limitations, however if you were planning to use this machine across a network, and particularly more than peer-to-peer ie - domain then the OS is not upto it. I'm sure Microsoft will explain the reason better than I can, but essentually they leave out a whole chunk of network functionality from the home premium, and price accordingly. If you were using the home premium web browser to access O4W across a network, I imagine that functionality would not be impaire - but Jared or Bryan would clarify / correct / confirm. If you are using the home premium OS as the platform for OI as a database server to other hosts in a network, then, as stated their are limitations; this is - imo - not the right platform. If you are using IIS on home premium for O4W publishing, the OI database being on this host, you may or may not hit some limitations of the OS network security / and or limitations within the home premium version of IIS - but pure speculation on my part - Jared would comment on that. </QUOTE> —- === At 01 JUL 2011 08:41AM Jared Bratu wrote: === <QUOTE>Richard, you're exactly right. For the most part, for a lot of the users, home and business versions of windows work. It all comes down to knowing your target audience and designing the application to meet that audience. In the corporate environment where our target market is, there are additional features that just aren't supported in home versions. Single sign on requires a domain membership. IIS7 has specific web server connection limits. Limits are also placed on the number of file share connections. So if you're goal is to test and develop the home version should work for your needs but in the long run we don't want to recommend the home version because we are designing OpenInsight to meet the needs of corporate users. </QUOTE> View this thread on the forum...