Gemini 2.0.3 - Application crashes when trying to fetch a deleted or non-available issue
Gemini 2.0.3 - Application crashes when trying to fetch a deleted or non-available issue
When a user either enters an issue number (in the URL or in the Find issue box) of an issue that has been deleted the system crashes.
If a user tries several times (about three times) to open an issue page with an issue number higher than the highest number issue, the system crashes also.
We are using Gemini 2.0.3.
Please help.
Thanks!
Ori.Cohen
· 1 |
|
Wednesday, February 10, 2010, 10:00:10 AM |
0
|
What is the error you are getting? |
||||
|
0
|
Hello, Thank you for the quick reponse! The application does not give any error message and nothing with an error is added to the EventViewer. What happens is that the application pool is immediately stopped and the service becomes unavailable and needs to be manually started. This is a very big problem for us. Have you not encountered such a problem before? I have not found any such report on your forums. How could that be? Could we be doing something wrong, or have something incorrectly configured? I realize that upgrding to the new version may be generally a good idea, though as version v3.6.3 is so far ahead of the version we are currently using, that the breaking changes between the two versions could make this upgrade very dangerous to us. The Gemini Issue-Tracker is a mission-critical work-tool in our enviroment. We can't afford having this service being corrupted or having stoppages in this service. Do you have some document that details the breaking changes between these two versions? Do you have some document that contains instructions for upgrading from v2.0.3 to v3.6.3 (DB, application, IIS etc.)? Thank you. Ori |
||||
|
0
|
We have not seen this before. What is the application pool running as (it should be classic.net)? |
||||
|
0
|
Hello, This is currently running on the IIS of MS Windows 2003 Server. There is no option but classis.net :) We have deployed our Gemini on several different machines and got this problem everytime. This is very frustrating. There must be something wrong we are doing or application configuration we missed, if you say this is the first time you heard of this bug. This is a very serious bug for us. Please do whatever you can to find the missing configuration we need to set or whatever setting or other that could cause such a problem. Regards, Ori |
||||
|
0
|
There is nothing else we can think of at the moment. If there are no errors in the logs then what exactly happens? Does the app pool shut down? |
||||
|
0
|
Hello Saar, Yes, that is exactly what happens. Unfortunately this happens in absolute consistency - everytime. We really need this fixed and I am not very reassured that even if we upgrade our system to user the new Gemini version, that this will be fixed. I really need your advice. Thanks. Ori |
||||
|
0
|
You can simply restore a backup of the database, upgrade it to 3.6 and see if this error happens. No need to renew license as this is just a test to see if the app works in read only mode. |
||||
|