-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitea 1.6.2 failed to start after restart with error Invalid object name 'SYS.INDEXES' #6201
Comments
Hi @Noderino, first thing is you'll likely want to upgrade to the latest version as we've fixed some major security vulnerabilities, also the DB library has been updated which might solve the problem. Are you able to connect directly to MSSQL to run queries manually against it? |
Yes i can connect to MSSQL without a problem. I also tried to replace gitea.exe with newer versions and latest but i am still getting same error. |
This is the log before first "Invalid object name" error. 2019/01/29 18:45:40 [...routers/repo/http.go:137 HTTP()] [E] invalid credentials |
Which version of your database? |
SQL Server 2014 |
@lunny Do you mean version number in dbo.version table? It is 74 |
@Noderino No. I means your SQL Server. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
This issue has been automatically closed because of inactivity. You can re-open it if needed. |
[x]
):2019/02/27 19:59:03 [I] Log Mode: File(Info)
2019/02/27 19:59:03 [I] XORM Log Mode: File(Info)
2019/02/27 19:59:03 [I] Cache Service Enabled
2019/02/27 19:59:03 [I] Session Service Enabled
2019/02/27 19:59:03 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: sync database struct error: mssql: Invalid object name 'SYS.INDEXES'.
Description
This happened after i restarted my server. If there is any other way that i can provide more info please let me know.
Screenshots
The text was updated successfully, but these errors were encountered: