I am using Hangfire.AspNetCore with ASP.NET Core v1.0.
My Database is SqlLite.
As far as I found, there is no proper SQLite driver for hangfire for .NET Core.
So, I decided to work without any dashboard.
So, what I have configured is like the following:
In Startup.cs, in ConfigureServices method
services.AddHangfire(configuration => {});
And in Configure method, I am using this
app.UseHangfireServer();
But I am getting the next error:
An exception of type 'System.InvalidOperationException' occurred in Hangfire.Core.dll but was not handled in user code
Additional information: JobStorage.Current property value has not been initialized. You must set it before using Hangfire Client or Server API.
I don't need dashboard, so I did not configured dashboard.
Can anyone please help?
The error is telling you that you have not configured a job storage provider. It's got nothing to do with the dashboard. Even without the dashboard you must have a storage provider.
There is in-memory storage available via Nuget called Hangfire.MemoryStorage that you can use if you don't require persistent storage for your background jobs.
Related
Getting this warning Data won't be synchronized. No GraphQL endpoint configured. Did you forget Amplify.configure(awsconfig)? which I assume is the reason my data isn't being synced to the cloud and is only working locally while testing my application.
I have read many of the pasts posts about this issue and have followed all the steps such as configuring the endpoint url in aws-exports.js but nothing I'm finding online is working. Anyone have any success with this issue using API key as the default auth setting?
My Flutter app on web has been using Firebase Cloud Messaging for a long time without error. Today, with no changes, it is giving the following error:
Error: [firebase_messaging/failed-service-worker-registration] Messaging: We are unable to register the default service worker. Failed to register a ServiceWorker for scope ('http://localhost:50093/firebase-cloud-messaging-push-scope') with script ('http://localhost:50093/firebase-messaging-sw.js'): The Service Worker system has shutdown.
Can anyone explain why this error is occurring now? I suspect something must have changed on Firebase's end, because my code has not changed.
If you're using an older version of Firebase Cloud Messaging plugin, you might need to follow this setup guide to create a default app settings for web. On current version of FCM, you can follow this initialization guide to add the FCM plugin on your app.
I have a .NET Core 3 Web API that has some external dependencies like Azure SignalR and Azure CosmosDb. I have create a Monitoring Controller which I want to check if the service is healthy by for example pinging those two dependencies.
I haven't found any documentation about how to do this. I know that for example, for Table Storage I can call a method "If table exists" so if it returns true, I know the service can communicate with that dependency.
There is a way to call those dependencies?
PS: I don't want to use 3rd party packages to perform this, I want to know if those services provide this kind of methods.
I know that for example, for Table Storage I can call a method "If table exists" so if it returns true, I know the service can communicate with that dependency.
There is a way to call those dependencies?
If you'd like to achieve same for Azure SignalR and Azure CosmosDb, you can try:
1) To check Azure SignalR service, can use management API to get details of Azure SignalR service.
2) To check Azure CosmosDb, can use this API to check if the database you want is existing.
I have created a Linked Service using key vault and then used that Linked service in Data Linked Service (Azure SQL database). Both Linked services independently tested successfully. I have used that in a very simple pipeline, while I am debugging the pipeline, it gets failed with an error:
'Invalid linked service reference. Name: '.
This is referring to Key Vault linked service.
When I trigger the pipeline, it works fine. I have published my changes so many time but no success.
So my basic query is - My pipeline is not working on Debug, however it is working fine with Trigger now.
I had faced exactly the same problem, I performed the following actions:
Save all existing pipelines
Validated all
Publish all
Closed the datafactory browser window/tab
logged back into datafactory
Opened the pipeline again and the debug worked fine. I didn't have to touch the Azure Vault configuration. Its most likely to do with cached vault configuration (or a sync issue with the cached vault config)
When a pipeline is working by trigger, but not by debug, that suggests either: there is a difference between the published version and the version in the UI, or, you have parameters that depend upon the trigger.
It's very strange thing I have noticed in Linked Service in ADF. I have selected Azure Key Vault near to password and just passed AKV linked service name there and it worked.
That suggests that JSON is not properly working with Azure key vault services in Linked Services. Well, my issue has been resolved however logically I am still unclear.
If any one looking for resolution of same, please refer below. Thank you.
Key Vault Linked Service
I have signed up for the trial version of oracle cloud data base.
Where can I find the host URL that I need to use in my Java dynamic web project of eclipse?
Thanks in advance.
Basic knowledge about the trial request and details needed :
After you request a trial service from Oracle Cloud, you'll be provided with a few details: Identity Domain, Temporary password, and your username.
By using them you'll login to your trial cloud account from here:
[https://cloud.oracle.com/sign_in][1]
Accessing the service from Eclipse
When it comes to access your Database Cloud Service from Eclipse:
You need to add the Oracle Cloud plugin from the Eclipse Market (Help Menu->Eclipse Marketplace)
You'll add the Oracle Cloud connection window to the interface (Window Menu->Show View->Other)
Create a new connection where you follow the steps with the proper details you have about your account.