Workspace I’m uploading from FME Form (2024.0.1.0) returns this error.
Failed to update definition of database type 'Microsoft SQL Server (JDBC)' - FME Flow encountered an error and reported the following message. Database type Microsoft SQL Server (JDBC) cannot be edited. Request to http://XXXXXXXXX/fmeapiv4/databasetypes/Microsoft SQL Server (JDBC) returned status code 422.
Is a workspace that has SQL Executors pointing to a SQL Server database and outputs results to a XLSX file on my laptop.
Thanks for the info. When publishing from Form to Flow, the year and major version should ideally be the same. There is a chance things will still work, but you may run into issues like this. I recommend authoring workspaces in FME Form 2024.2 b24783 to match your version of FME Flow.
The warning icon is just letting you know that the connection already exists on FME Flow and will be overwritten if you leave it checked off when publishing. However, based on the error you’re seeing, this might not actually be happening. If you publish from Form 2024.2, then I would expect the error to go away.
Hi @thomastupuivao, can you please confirm that the version of FME Flow you’re publishing to is also 2024.0.1.0? Or a 2024.x build that is newer than 2024.0.1.0? This may be caused by a version mismatch.
If you look for the connection on FME Flow (Connections & Parameters > Database Connections), is it there and does your workspace run on Flow despite the error? Are you able to publish other types of database connections without error?
I’ve noticed that when I upload the workspace at the “upload connections” window, there is a ‘warning icon’ when select my SQL server connection. Not sure if thats expected or not?
Thanks for the info. When publishing from Form to Flow, the year and major version should ideally be the same. There is a chance things will still work, but you may run into issues like this. I recommend authoring workspaces in FME Form 2024.2 b24783 to match your version of FME Flow.
The warning icon is just letting you know that the connection already exists on FME Flow and will be overwritten if you leave it checked off when publishing. However, based on the error you’re seeing, this might not actually be happening. If you publish from Form 2024.2, then I would expect the error to go away.
@mathiku Is there an additional error message logged in the translation log? It may be a different issue entirely, 422 is a fairly generic error saying the Flow API couldn’t process the request.
For example, do you have a reader/writer that was registered to a translation service that has been modified or deleted? On the last “Register Services” step of publishing to FME Flow, click edit next to each registered service. Remove any readers or writers that are showing as registered, but no longer exist in the workspace. They will be red.
If this doesn’t help, please submit a ticket with the full translation log capturing any errors during publish.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
