Getting 500, "Could not find stored procedure 'Security_GetRoles', but /health show no errors

carl.westman_8110

Having some wierd behaviours with Proget after updating to 25.0.10 my /health responds 200 and shows that there are no issues, so no alerts are firing

{
"applicationName": "ProGet",
"databaseStatus": "OK",
"databaseStatusDetails": null,
"extensionsInstalled": {
"ProGet": "25.0.10",
"Inedo.SDK": "3.1.0",
"Amazon AWS": "3.1.3",
"InedoCore": "3.0.5",
"Azure": "3.1.2"
},
"licenseStatus": "OK",
"licenseStatusDetail": null,
"versionNumber": "2025.10 (Build 11)",
"releaseNumber": "25.0.10",
"startTime": 1758271289653,
"serviceStatus": "OK",
"serviceStatusDetail": null,
"replicationStatus": {
"serverStatus": null,
"serverError": null,
"clientStatus": null,
"clienterror": null,
"incoming": [],
"outgoing": []
}
}

But trying to go to the website I only get http error 500

The logs show an error "Could not find stored procedure 'Security_GetRoles'

2025-09-19T09:04:08.8094686Z info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
2025-09-19T09:04:08.8095216Z       Request starting HTTP/1.1 GET http://proget.dev.companyname.com/health - - -
2025-09-19T09:04:08.8097717Z info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
2025-09-19T09:04:08.8099365Z       Request finished HTTP/1.1 GET http://proget.dev.companyname.com/health - 200 619 application/json 0.3870ms
2025-09-19T09:04:10.6672063Z info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
2025-09-19T09:04:10.6672953Z       Request starting HTTP/1.1 GET http://proget.dev.companyname.com/ - - -
2025-09-19T09:04:10.6687087Z An error occurred in the web application: Could not find stored procedure 'Security_GetRoles'.
2025-09-19T09:04:10.6778579Z info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
2025-09-19T09:04:10.6779411Z       Request finished HTTP/1.1 GET http://proget.dev.companyname.com/ - 500 0 - 10.6553ms
2025-09-19T09:04:13.8057598Z info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
2025-09-19T09:04:13.8058173Z       Request starting HTTP/1.1 GET http://proget.dev.companyname.com/health - - -
2025-09-19T09:04:13.8064277Z info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
2025-09-19T09:04:13.8064479Z       Request finished HTTP/1.1 GET http://proget.dev.companyname.com/health - 200 619 application/json 0.4290ms
2025-09-19T09:04:13.9852857Z info: Microsoft.AspNetCore.Hosting.Diagnostics[1]

Anyone stumbled upon something similar and have any ideas on how to fix this?

Cheers
Carl

viceice

I same problem but a different error:

2025-09-19T11:31:52.055874602+02:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
2025-09-19T11:31:52.055917374+02:00       Request starting HTTP/1.1 GET http://proget.xxx.de/ - - -
2025-09-19T11:31:52.058745038+02:00 An error occurred in the web application: XX000: cache lookup failed for type 641322
2025-09-19T11:31:52.110076806+02:00 info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
2025-09-19T11:31:52.110107728+02:00       Request finished HTTP/1.1 GET http://proget.xxx.de/ - 500 0 - 54.3259ms

2025-09-19T11:30:23.356843497+02:00 Running Connector Cache Check...
2025-09-19T11:30:23.369384274+02:00 Getting list of connector responses...
2025-09-19T11:30:23.381026135+02:00 Unhandled exception: XX000: cache lookup failed for type 641314

Downgrading to 25.0.9 doesn't help. I recently migrated to integrated PostgreSQL.

carl.westman_8110

@viceice does your /health also show "no problems"?

carl.westman_8110

I also got an error like this

Unhandled exception: Could not find stored procedure 'Executions_FailRunningExecutions'.

viceice

it returns code 200, so i assume yes

viceice

@carl-westman_8110 said in Getting 500, "Could not find stored procedure 'Security_GetRoles', but /health show no errors:

Unhandled exception

i don't see those, only the XX000: cache lookup failed for type exceptions

carl.westman_8110

Reverting to 25.0.9 did actually work in our case So there seems to be some issue with 25.0.10

atripp

Hi @carl-westman_8110 ,

The error message means that the database wasn't updated as per normal during the start-up process. It's hard to guess why, as we have special handling for that.

It's likely that restarting the service would have fixed it, but downgrading and then upgrading would also force an upgrade as well. Unfortunately it's hard to say at this point.

Upgrading to 2025.10 should be fine.

Thanks,
Alana

carl.westman_8110

@atripp Ahh ok, maybe that was what fixed it :)