ConnectionError: Connection is closed


#1

Has anyone found a workaround for this MSSQL error/restriction "ConnectionError: Connection is closed."
I am using NodeRED to log data from various PAC based systems to an Aure MSSQL DB.
All is well when I run one flow at a time. The problem occurs when you try to run multiple flows concurrently referencing different tables in the same DB. In other words I have a DB for the customer with different tables for each PAC based process.
Once the connection to the DB is opened by the first flow the others get this error. So far the only way I have found to make it work is to string all the flows together sequentially and let them write to the DB one after the other. However this does not make for a very elegant organization of the flows.
I have tried looking for a different MSSQL Node and played with a couple but no luck yet. From what I have read this seems to be more of a MSSQL server issue, but I am looking for ideas.

Thanks,
Norm


#2

I have the same issue. Anything new on that?


#3

No, not that I know of. All of the demos that Opto 22 has published and I have reviewed seem to only write one table in a given db. So I have stuck with stringing my nodes together so both tables can get updated. Below is an example of the Batch and HTST tables getting updated in the same db.