Problem after re-install
I re-installed 2.2.2 over my 2.2 install and now get the following error:
Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.
This stored proc exists in the database and the params (database name, etc) are correct in the web.config file.
This only happens when trying to access the issues in the DB - all else seems to work fine.
Thanks for your help
Matt
mhopkins
· 1 |
|
Wednesday, September 19, 2007, 10:38:23 AM |
0
|
Hi Matt, There are two places in the Gemini web.config where you should specify database connections. Please double check them BOTH.
|
||||
|
0
|
I have them set in the following two areas: |
||||
|
0
|
Does the profile database exist? If so, did you run the installcommon.sql and installprofile.sql scripts? |
||||
|
0
|
The profile database exists and contains the stored proc that is being reported in the error. |
||||
|
0
|
I can add users, see the project - I just can't view/amend/create issues. |
||||
|
0
|
Please make sure that the owner of the objects is dbo. |
||||
|
0
|
yes - it is. I said, the DB was working fine before the re-install.... the only area of the DB that the web interface does not seem to be able to access is the issues list... |
||||
|
0
|
The error is that the web app can not "see" the profile database. It might be that the profile connection string is wrong or the user does not have access. |
||||
|
0
|
How is it that it can "see" the projects, versions, users, etc? |
||||
|
0
|
Here's the full text of the message: |
||||
|
0
|
It can "see" projects etc.. because they use the Gemini database schema! The error points to the ASP.NET profile schema, which means that you either did not set the profile connection string in the web.config file or you have not set up the profile database. |
||||
|
0
|
[[sorry for the delay in responding]] |
||||
|
0
|
<add name="ProfilesServer" connectionString="data source=YOUR SERVER NAME HERE;initial catalog=DATABASE;user id=USER;password=PASSWORD" providerName="System.Data.SqlClient"/>
|
||||
|
0
|
That connection string already existed in the web.config: |
||||
|
0
|
OK - I have solved it. This was a bit of a "doh!" moment... the new install created a separate directory with a new web.config... sorry about the trouble but I'm back online now. |
||||
|