I made some research:

1. the stored procedure do not exist in the gemini database, but the sp exist in the database called geminiaspnetdb.

3. the error still exist.
The last SQL query before the error is
"exec dbo.aspnetCheckSchemaVersion @Feature = N'Profile', @CompatibleSchemaVersion = N'1'"
Question: on what database runs the query. Of course the statement will fail at the gemini database, because the sp do not exist at the gemini database.

That's what I can do. Now I need help.

4. Question: should the database user exist in both database as database owner and what right must he have to every stored procedure?

Did you amend the web.config profile connection string to point to the profile database?

it looks fine to me:

  <connectionStrings>
    <add name="ProfilesServer" connectionString="data source=10.10.0.12;initial catalog=GEMINI;user id=;password=*" providerName="System.Data.SqlClient"/>
  </connectionStrings>

the sql database name is gemini (lower case),
the name in the connection string catalog is in capitals (is this important)

if we purchase your upgrade support, how fast can you help / upgrade the solution?

You need to amend this connection string to point to the profile database, in your case gemini_aspnetdb (obviously you might need to change the user and password as well).

Our upgrade support will be able to do this tomorrow morning - providing we have access to the server. But I do not think you need it, hopefully the above will solve your issues.

Thank you. No I can access issues, can create issues, modify issus... (I changed a value in the connection string in the web.conf to: catalog=GEMINI_ASPNETDB;)

BUT, I found two data errors (no errors in the admin protocol).
1. All assigned ressources in all projects are now empty!

2. All issues have now empty components!

Version, priority etc. values existing in each issue.
Of course, before update to V2.20 all issues had have assigend ressources and components.

by the way, this is the result of the upgradev2.2.sql script:

C:\Dokumente und Einstellungen\admin>osql -S 10.10.0.12 -d * -U gemini -P * -i "C:\Programme\CounterSoft\Gemini Project Issue Tracking\Gemini Database
\upgradev2-2.sql"
1> 2> 3> 4> 5> 6> 7> 8> 9> 10> (1 row affected)
1> 2> 3> 4> 1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 1> 2> 3> 4> 1> 2> 3> 4> 1
> 2> 3> 4> 5> 6> 7> 8> 9> 10> 1> 2> 3> 4> 5> 1> 2> 3> 4> 1> 2> 3> 4> Meldung 270
5, Ebene 16, Status 4, Server S-GEMINI, Zeile 3
Spaltennamen müssen in jeder Tabelle eindeutig sein. Der Spaltenname
'affectedversions' wurde in der personalfilters-Tabelle mehrmals angegeben.
1> 2> 3> 4> Meldung 2705, Ebene 16, Status 4, Server S-GEMINI, Zeile 3
Spaltennamen müssen in jeder Tabelle eindeutig sein. Der Spaltenname 'comment'
wurde in der users-Tabelle mehrmals angegeben.
1> 2> Meldung 2705, Ebene 16, Status 4, Server S-GEMINI, Zeile 1
Spaltennamen müssen in jeder Tabelle eindeutig sein. Der Spaltenname 'active'
wurde in der users-Tabelle mehrmals angegeben.
1> 2> 3> 4> (1 row affected)
1> 2> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> (0 rows affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> (1 row affected)
1> 2> 3> 4> 1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 1> 2> 3> 4> 5> 1> 2> 3> Meldung 2705,
 Ebene 16, Status 4, Server S-GEMINI, Zeile 2
Spaltennamen müssen in jeder Tabelle eindeutig sein. Der Spaltenname
'resourcemode' wurde in der projects-Tabelle mehrmals angegeben.
1> 2> Meldung 2705, Ebene 16, Status 4, Server S-GEMINI, Zeile 1
Spaltennamen müssen in jeder Tabelle eindeutig sein. Der Spaltenname
'componentmode' wurde in der projects-Tabelle mehrmals angegeben.
1> 2> 3> 4> 1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 1> 2> 3> 4> 5> 1> 2> 3> 4> Meldung 20
7, Ebene 16, Status 3, Server S-GEMINI, Zeile 2
Ungültiger Spaltenname 'compid'.
Meldung 207, Ebene 16, Status 3, Server S-GEMINI, Zeile 2
Ungültiger Spaltenname 'compid'.
Meldung 207, Ebene 16, Status 3, Server S-GEMINI, Zeile 2
Ungültiger Spaltenname 'compid'.
1> 2> 3> 4> Meldung 207, Ebene 16, Status 3, Server S-GEMINI, Zeile 2
Ungültiger Spaltenname 'assignedto'.
Meldung 207, Ebene 16, Status 3, Server S-GEMINI, Zeile 2
Ungültiger Spaltenname 'assignedto'.
Meldung 207, Ebene 16, Status 3, Server S-GEMINI, Zeile 2
Ungültiger Spaltenname 'assignedto'.
1> 2> 3> 4> 5> 6> Meldung 170, Ebene 15, Status 1, Server S-GEMINI, Zeile 1
Zeile 1: Falsche Syntax in der Nähe von 'constraint'.
1> 2> 3> Meldung 3701, Ebene 11, Status 7, Server S-GEMINI, Zeile 2
löschen von Index 'issues.indcompid' ist nicht möglich, da nicht im
Systemkatalog vorhanden.
1> 2> 3> Meldung 4924, Ebene 16, Status 1, Server S-GEMINI, Zeile 2
Fehler bei ALTER TABLE DROP COLUMN, da die assignedto-Spalte in der
issues-Tabelle nicht vorhanden ist.
1> 2>
C:\Dokumente und Einstellungen\admin>osql -S 10.10.0.12 -d gemini -U gemini -P g
emini -i "C:\Programme\CounterSoft\Gemini Project Issue Tracking\Gemini Database
\createviews.sql"
1> 2> 3> 1> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20>
21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> 40>
41> 42> 43> 44> 45> 46> 1> 2> 3> 4> 1> 2> 3> 4> 1> 2> 3> 4> 1> 2> 3> 4> 1> 2> 3>
 4> 1> 2> 3> 4> 1>

TRANSLATION:
- Der Spaltenname ... mehrmals angegeben = The column name ... was named more than once
- Ungültiger Spaltenname = not valid column name
- Falsche Syntax in der Nähe von 'constraint' = wrong syntax near by 'constraint'
- löschen von Index 'issues.indcompid' ist nicht möglich, da nicht im
Systemkatalog vorhanden = deleting index 'issues.indcompid' could not be done, because it does not exist in the system catalog

Which scripts did you run? It seems to me that you run some scripts more than once.

Can you restore the database?

Yes I run three scripts, as described on page 26 of the gemini installation.pdf:

chapter 11.1 v2.1.x
1. upgrade v2-2.sql
2. createviews.sql
3. createprocs.sql

Yes, I can. I  have a database backup and I need very quick a full runing system.

I consider to purchase the update service, restore the database and do the update again with professional support. I'd kindly request support.

Thank you and best regards