O4W and IIS "Cannot process query" (O4W)
At 22 JUL 2010 05:04:15PM Andrew Roberts wrote:
I had originally posted this in the beta forum just before the release of 9.2, but I wanted to share the resolution in case someone else runs into this issue (as I spent a several days trying to resolve it with Bryan's help).
I was getting the following error attempting to login to O4W on a server running IIS 6 and Windows server 2003:
"Cannot process Query: /o4w/oecgi3.exe/O4W_LOGIN%3FO4WControlBackup%3DBTNLOGIN%26o4wNAME%3DO4W%26o4wPWD%3DO4W%26BTNLOGIN%3DLogin%26O4WDispatch%3DO4W_LOGIN"
INET_TRACE worked and did not indicate any issues. With Bryan's help we realized that full pages were working, but pages with updates would generate the error.
It turned out that UrlScan 3.1 for IIS (a free downloadable IIS security tool from Microsoft with no UI, just a DLL and an INI file) was blocking urls with dots in the path name by default. The path at issue was " /o4w/jquery/1.3.2/js/". Changing the parameter "AllowDotInPath=0" to 1 in the file \%windir%\system32\inetsrv\urlscan\urlscan.ini resolved the issue.
At 04 MAY 2011 12:33PM Sandra Burgos wrote:
This sounds like the same issue I'm having. However, I can't find a urlscan folder anywhere in the system. I'm running IIS 7. Any ideas?
At 04 MAY 2011 04:03PM bshumsky wrote:
Hi, Sandra.
So, you're able to access some default INET pages (like INET_TRACE) and it works OK, but when you're trying to access O4W pages you get an error? Are you getting the error on _all_ O4W pages, or only when processing a "response"? Are you seeing the error with the O4W wizard tools, or with your own custom stored procedures using the O4W APIs?
Thanks,
- Bryan Shumsky
Revelation Software
At 09 MAY 2011 01:49PM Sandra Burgos wrote:
Well, today the page is back. Here is what happened… I created a new form using the API (not the wizard). It is a basic login page (username/password fields). Once it logs you in successfully, it redirects the user to another page. (very simple, right?). Well, from the toolkit main page, if I click on any of the options listed there, I'm taken to this one page. For some reason, the login is not working right now so I can't get past it.
Since I don't have a way to access the code from the toolkit homepage, I tried on changing it using the System Editor. That's when all of the sudden, I started getting the 'cannot process query' message. I guessed I had to somehow 'refresh' the system but I tried restarting IIS and that did not make any difference.
Today (5 days later), I go back into that system and the login page shows up again.
So I guess I need to understand how can I trigger that 'refresh'? and also, is there a way to debug O4W code?
At 09 MAY 2011 02:06PM Dave Harmacek wrote:
Outside of the O4W Toolkit you can refresh by going to the server hosting oecgi2.exe or oecgi3.exe. In Administrative Tools start Services. Scroll down to OEngineServer, right-click and choose Restart.
I'm planning a blog entry on how I debug O4W Basic+.
Dave