Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Editing an issue returns to /Gemini/Main.aspx

web-app

We just licensed Gemini after we successfully used it for a couple of weeks.  I successfully migrated our Rational ClearQuest customer support database to Gemini using a mix of direct SQL and the WSE interface.

When editing an issue, all of our users are configured to Navigate to Issue.  However, usually (but not always according to my users - always for me), I get sent to /Gemini/Main.aspx.  We only have one project.    

This is causing much frustration because our process involves changing the asigned resource (through edit) and then adding a comment and attachment - having to re-find the issue after the edit so we can add the comment is not fun.

We are on 2.0.2 (windows 2000 with inproc session), and I also tried it on 2.0.3 beta 1 on our test server (Windows 2003 w/ ASP.Net state service)

Mark42
· 1
Mark42
Replies (13)
helpful
0
not helpful

Hi Mark,

Does 2.0.3 sort the issue out?

Which versions of .NET framework are installed on the server?

Do you get a message in red on the main page?

It might be a session timeout issue, does it happen after a long period of non activity?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

2.0.3 does not sort the issue out (I tried before reporting the issue just in case)

The test server (Windows 2003) has 1.1 only, but our regular server (windows 2000) has 1.1 and 2.0, but the site is configures for the 1.1 runtime. (we are web developers ourselves and are used to ASP.Net side-by side deployment).

There is no red message, and nothing in the error log.  It happens for some users on some computers, but not every one.

It happens even if I just log in, so I don't think it's session problem.


Mark42
· 1
Mark42
helpful
0
not helpful

Hi Mark,

Do me a test: try using Gemini with FireFox browser (assuming you are using IE). Does the error persist?

 


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Mark,

Ensure that the Gemini webapp is not using a 2.0 application pool in IIS.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Mark,

Do you click on EDIT on the Issues.aspx page, or do you view the issue and then click on edit?

Would be grateful if you could send exact steps to reproduce the problem.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

I normally use Firefox.  It happens in IE, too.

The issue was not resolved in 2.0.3 beta 2. 

The problem happens when I first view the issue, click edit, then click update.  It also happens when I click edit from the list.  I assume that somewhere along the line there is an exception or corrupted post data when Gemini determines where to redirect after the post.

I have played with the test site (on IIS 6) and the issue has gone away for me, but I don't know if it's a fluke or not.  We are using Integrated serurity to the database.  I updated the FullGeminiURL (on the IIS 6 site) to be the fully qualified active directory domain name of the computer (we are on an intranet).  Could there be something to this?

Is there a way to turn on more debugging?  I can see a call to dbo.gemini_logerror sometimes when I run a sql trace (something about a cache miss), but there is never an entry in the errorlog table.

I'd be glad to put an instrumented/debug build on our server and try to capture some logs of the behavior.  It could be resource constraints or something else unknown.

We are interested in the Source Code license, and would be glad to sign a NDA or something if that's necessary to give us a debug build.  I think Gemini is a great product that can do everything we want it to (we have some ideas that may be relavant only to us.).  Gemini is better than most solutions I have seen (the best at the price), and I would love to help get to the bottom of the issue we are having.


Mark42
· 1
Mark42
helpful
0
not helpful

Try this

http://www.countersoft.com/downloads/beta/Geminiv203beta3.zip

Watch the Gemini Error Log!

Thanks for all your input thus far -- we will sort this.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful


I now have one of these
SESSION miss detected - key: ISSUECOMP            2006-02-16 14:21:30.697

and 59 of these
CACHE miss detected - key: LICENSE
UC            2006-02-16 14:21:30.727

in errorlog after installing Beta 3.  I still get redirected to Main.aspx. after editing an issue.


Mark42
· 1
Mark42
helpful
0
not helpful

Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Improved.  Now when I edit an issue, I return to the Issues List.  That is fine when editing from the list.  If I view the issue first, I still go to the issues list, even though My Profile is set to Navigate to Issue after creating and after editing.

When I create an issue, I do correctly go to the viewissue page.

Thanks.  This most recent update will help ease the pain until it's 100%.



Mark42
· 1
Mark42
helpful
0
not helpful

Mark,

Here is the final build: http://www.countersoft.com/downloads/Geminiv20_3.zip

Unfortunately you will alsoways be redirected to the ViewIssue page.

We tracked this down to a problem with Page.Request.UrlReferrer -- under certain circumstances this value is NULL. We think things like Norton Internet Security cause the problem.  So, we have workaround but at the expense of obeying your user preferences.

Do let us know if this build breaks anything else!

Many thanks for all your help -- appreciated.


Harvey Kandola
· 212
Harvey Kandola
helpful
0
not helpful

Ahhhh.  I never thought of Norton.  I made a change to how I access Gemini, and my troubles are gone!  Thank you for all of your hard work...  I wish I had thought of that before, but It least I helped with the logging (and it seems faster).

Our solution:

I had to change the FullURL to include the fully qualified (Active directory) domain name of the intranet server, then added the fqdn to Norton as follows:

For Norton Internet Security and Norton Personal Firewall 2003/2004

To Disable Browser Privacy for specific Web sites

   1. Open Norton Internet Security or Norton Personal Firewall.
   2. Double-click Privacy Control.
   3. Click Advanced.
   4. Click Add Site.
   5. Type in the URL for the site where you want information about your browser disabled, and then click OK.
   6. The URL will appear in the left pane. Click the URL so it is highlighted.
   7. On the Global Settings tab under "Information about your browser," uncheck "Use default settings.
   8. Click OK.


Mark42
· 1
Mark42