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.




Issues upgrading from v1.9.1 to v2.0.5

web-app

Hi there,

I've just been trying to run an upgrade from Gemini version 1.9.1 to 2.0.5. My process has been as follows:

  • Set up a test server identical to the live server & confirm it works perfectly
  • Stop the IIS worker process that Gemini is running under (stops anyone using the app whilst I'm doing the upgrade)
  • Run 'Upgradev2-0.sql' script against database
  • Run 'CreateProcs.sql' script against database
  • Rename old Gemini working directory
  • Create new Gemini working directory (in the same location as the old one)
  • Copy new Gemini files to this location
  • Modify new Web.Config

My issue is that although the application runs and I can log in, every time I try to access a project or the "My Work" link at the top, I get a page saying "Gemini Application Error" with a link to "View error log" that actually takes me nowhere.

I've tried looking in the errorlog table in the SQL database but there's nothing there.

Anyone had any similar issues? It's extremely frustrating as there don't seem to be any actual error messages anywhere, making it next to impossible to diagnose. Is there any way, for example, to stop the Gemini-generated "Application Error" page and get a proper ASPX failure page with a full stack trace? At least then I might be able to find out what's going wrong...

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

Is the problem only with the "My Work" page?

Please make sure that in your web.config you have updated the FullGeminiURL and connection string.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I too am having a similar issue. I guess similar because I too am wondering if there is a way to not call error.aspx. I can move through the application fine but whenever I do anything that performs a form submission -- try to add a new isse, new comment, even events that do javascript: _doPostBack(), I get the error.aspx and when I view the error log there are no entries. I know this sounds a bit cliche but seriously this app worked perfectly until today. Even email. I'll try to supply as much detail as I can think of:

WIN2K3 Ent.
SQL Server 2005
Gemini 2.0.5
ASP.net 1.1.4332
WSE 2.0 sp3
I installed using .msi installer supplied. Using the default location got everything (web.config)  working well. Then moved files to final location updated the path in IIS. Everything worked fine in the new location. After a few days (today), I get the behaviors listed above. I even went as far as unistalling the app with the .msi, dropping the virtual directory, rebooting, downloading a fresh copy of 2.0.5 and re-installing. Still no luck. I have tried creating a separate app pool, no luck. I can log on to the database and perform CRUD using the Gemini user that would go in the connect string. So I don't believe there is an issue with write permissions in db. Plus the app pulls data fine to display in any other page. Everything in web.config seems to be correct. At least by appearence. (I'm sure someone will ask if FullGeminiURL is written correctly, yes it is). There might be two questions in here.
1. What would cause the app to throw an error (call error.aspx) but not write to the errorlog.
2. What do the files or processes that do a form submission have in common that when they break might lead to uncovering a missed config setting or something outside of Gemini i.e. .net itself. It is not entirely impossible that I could have easily, not knowingly mind you, screwed something up in the .net environment or its users. It seems like that might be the only variable I haven't been able to nail down. I'll post this for now and let someone chew on it for while and hopefully someone might ask the right question that might shed some light on this issue. Oh yea, I get this while logged into Gemini as an admin so the permissions to create issues, etc. are there. Thanks in advance for any help.
-sean


nolelax43
· 1
nolelax43
helpful
0
not helpful

Hi,

Yes, I have ensured that the "FullGeminiURL" is correct.

The issue occurs whenever I try and do anything related to issues - using the "My Work" link, attempting to post a new issue, list unassigned issues etc..

Any help would be most appreciated; as mentioned above, stopping error.aspx being called and just displaying a generic application error would help!

TIA

Rob


RobW
· 1
RobW
helpful
0
not helpful

Can you try and install a new 2.0.5 instance pointing it to a new 2.0.5 database?

If it works, try pointing it to the upgraded database.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Hi,

The upgraded files pointing to a new database works fine - so I'm guessing there's an issue with the upgraded database structure from v1.9.1 to v2.0.5.

Any hints on what should be done? I ran the "Upgradev2.0.sql" script in the "upgrades" folder  followed by the "Createprocs.sql" script. Is there some other order I should use?

TIA,

Rob


RobW
· 1
RobW
helpful
0
not helpful

Is it possible for you to send us a backup of your database?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Hi,

I'm afraid I can't really do that as it contains sensitive data and is over 300Mb in size.

Is there any other advice you can give me? Are there any constraints that may have changed between v1.9.1 and v2.0.5? Is there any way to capture the error messages (be they SQL or ASPX derived)?

Rob


RobW
· 1
RobW
helpful
0
not helpful

Check that you do not have items that are not in the lookups, such as priority id, resolution id etc.. 


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

As far as I can tell there aren't any problems like that.

However I've just realised that, when attempting to register a new user, that fails too - it appears to be some database-driven tasks that are failing. Perhaps the stored procs are not correct? The security context is fine (as I can log in using Enterprise Manager and make changes as the user) so it isn't a permissions problem.

Otherwise, what I can attempt to do is run a DTS job from the old database to a new, clean one, table by table, until I get to the cause of the problem.

Any help greatly appreciated!

Rob


RobW
· 1
RobW
helpful
0
not helpful

Try and run Gemini using an sa account.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Hi,

I'm already doing that in my development environment!

Rob


RobW
· 1
RobW
helpful
0
not helpful

Is your database full?

There should be an error logged in the errorlog table. The possible reasons that this will not happen are:

  1. Database is full
  2. Connection string is wrong (read only?)

 


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Hi,

1. The database is not full (set to grow automatically anyways but has plenty of free space).

2. The connection string is fine - I wouldn't be able to log in if it wasn't.

Any other advice?


RobW
· 1
RobW