I’m a bit stuck. I have .net6 hangfire server connected to an Azure database server.
When I run a new job on the Development database it works fine.
When I run the same job on the Live database, by simply changing the database name in the config settings, it fails.
There’s no login issue, and another job on the same server works on both Dev and Prod databases.
I also notice that the Server Schema changes on the change of database base - Version 7 Schema becomes Unspecified Schema Version.
My developer says the server is failing before it gets to the SQL Search routine too.
Any thoughts on where I should look for the issue?
We still have no luck. The particular jobs run fine on localhost but not on Azure.
What settings would need to be changed?
Hello
Hangfire is functioning correctly with your Development database but faces issues with your Live database in Azure SQL Server. Check your connection string and authentication details to ensure they are correct and have sufficient permissions. Verify that the database schema and permissions match between environments, as differences can cause problems. Review SQL Server configurations and logs for any errors or compatibility issues. Consider workload and concurrency differences between environments. By systematically checking these areas, you can identify and resolve the issue affecting Hangfire’s performance on your Live database. check https://www.hangfire.io/
Hope it helps !
Thank you
nathaniel
No sorry. Its not a database login issue - its an Azure Server compatability issue.
The Dev site, and Live sites work fine on localhost but not when uploaded to an Azure Server.