using version 1.0.6
we're testing Mantis.
I had installed first on a internal windows2003 server and used it for some time, no problems at all.
Now I did the exact same installation on a WindowsXp pc in DMZ, copied the MySql database (as a folder) and I all seems to work just fine but :
I get application error #200 just like mentioned in issue http://www.mantisbt.org/bugs/view.php?id=7125
not always. when i retry the same action, all is well.
but then a few times later again and again.
I also get this when adding or modifying users and projects.
not always, but certainly to often.
Any idea's why this happens on the second installation ?
Thank you in advance.
Kind regards
Hans.
APPLICATION ERROR #200
Moderators: Developer, Contributor
This application error happens when you change the current project while you are on some pages that are typically not the common place to change project. This is a reproducible problem that is independent of the operating system, so if this is the one you are having, then you should be able to reproduce it on both installations.
However, you may getting an application error 200 for a different reason. So what you need to mention is when you get it, on what pages, and what is the text of the message.
However, you may getting an application error 200 for a different reason. So what you need to mention is when you get it, on what pages, and what is the text of the message.
Migrate your MantisBT to the MantisHub Cloud
it happens in a veraiety of situations:
=============================================
-start in a issue: view.php?id=152,
-click on Update Issue
-- > bug_update_page.php
"APPLICATION ERROR #200 A required parameter to this page (bug_id) was not found."
-browser back
-click again
No problem
-alter Summary
-click update
-- > bug_update_page.php
"APPLICATION ERROR #200 A required parameter to this page (bug_id) was not found."
-browser back
-Webpage has expired
======================================
Another example is adding a user to a project
starting from manage_proj_edit_page.php?project_id=1
-select Username and click Add User
--> manage_proj_user_add.php
"APPLICATION ERROR #200 A required parameter to this page (project_id) was not found."
===============================================
=============================================
-start in a issue: view.php?id=152,
-click on Update Issue
-- > bug_update_page.php
"APPLICATION ERROR #200 A required parameter to this page (bug_id) was not found."
-browser back
-click again
No problem
-alter Summary
-click update
-- > bug_update_page.php
"APPLICATION ERROR #200 A required parameter to this page (bug_id) was not found."
-browser back
-Webpage has expired
======================================
Another example is adding a user to a project
starting from manage_proj_edit_page.php?project_id=1
-select Username and click Add User
--> manage_proj_user_add.php
"APPLICATION ERROR #200 A required parameter to this page (project_id) was not found."
===============================================
This is very strange. I would suggest you report a bug in the bug tracker and add to it the link to this forum thread.
Migrate your MantisBT to the MantisHub Cloud
HansV: We always had trouble accessing Mantis through the proxy. I assume it was a MS one, seeing as we were an all MS shop... we ended up just setting our browsers to bypass the proxy for the Mantis server.
I don't know who was responsible for the problem, but I do know that we had all sorts of troubles until it was bypassed, sorry...
I don't know who was responsible for the problem, but I do know that we had all sorts of troubles until it was bypassed, sorry...
Narcissus.
We are going to move mantis to a server behind our isa-server, so we can bypass the proxy. I'm sure mantis will do fine internally. Let's see if isa doesn't present a new issue on outside access.
It looks like a proxy or line-scanner sometimes changes the parsed parameters. This happens when accessing the worker pages (how you call 'm?)
Thank you all for the comments.
We are going to move mantis to a server behind our isa-server, so we can bypass the proxy. I'm sure mantis will do fine internally. Let's see if isa doesn't present a new issue on outside access.
It looks like a proxy or line-scanner sometimes changes the parsed parameters. This happens when accessing the worker pages (how you call 'm?)
Thank you all for the comments.