Comments
15 comments
-
I am getting the same issue after installation this morning - this is bit of a blocker for me. -
Same problem here. Have already created a ticket for it.
I tried to revert to previous version, but that didn't resolve the problem.
I ended up unstalling and reinstalling VS2022.
Then I installed a SCA version from a month ago. That gave no issues.
Then I updated to the last version.. Got the error back.
Reverted to previous SCA version and then I did work again. -
Sounds very similar. I also have a ticket here: https://productsupport.red-gate.com/hc/en-us/requests/281168
-
For those following along. This is what I got back from redgate support:
I have seen this before and it usually happens if you have another Visual Studio extension that uses an older version of the Serilog library. Are you running any other extensions in Visual Studio, not just RedGate's?
If you are, I would recommend trying to disable any other extensions temporarily to see if you can find which one might be causing the error.
If that doesn't work, please let me know.
-
I am the person who reported the conflict with serilog some years ago.
That is not the problem this time. Activitylog.xml doesn't mention serilog problems.
This is a new problem happening only in the latest release of SCA. -
I am getting the same error in the activity log. It started with version 4.4 this morning so I tried updating to version 4.5 but still get the same error. Also tried a Visual Studio repair but still get the error.
-
I am getting this error in VS2022, but not VS2019 (both have the same version). Would rather not have to switch between IDE's to generate scripts.
-
Further from redgate support:
We've since seen other customers experiencing the issue too. We have replicated it, and for an immediate solution, Downgrading to version 4.5.22300.32307 is a workaround.
However, I'll now keep you updated as it is escalated to the development team.
-
As per the above, downgrading to that specific version should be the current workaround. Download link below:
https://download.red-gate.com/checkforupdates/SQLChangeAutomation/SQLChangeAutomation_4.5.22300.32307.exe
The bug has been identified and we're hoping it will be included in the next release of SQL Change Automation. -
I got the same response from support. I have disabled/uninstalled all my running VS extensions, but still getting the problem. I've supplied my change automation log files to the support team - you can view these using the instructions here, in case it is useful:
https://documentation.red-gate.com/sca4/troubleshooting/logging-and-log-files
-
Hi all,
I have been advised the fix is confirmed to be in the next SQL Change Automation release. This should hopefully be released Thursday. -
Good morning all,
SQL Change Automation v4.5.22313 has just been releases which should address this, please pull it down at your earliest convenience and let us know if it resolves your issue. -
The SCA tool window is now opening for me without any errors. Thank you!Peter_Laws said:Good morning all,
SQL Change Automation v4.5.22313 has just been releases which should address this, please pull it down at your earliest convenience and let us know if it resolves your issue. -
I have downloaded from the VS marketplace and it works now. This case could be closed.
-
Delighted to hear it, if you have the time please, marking an accepted answer would help other people suffering the issue find a resolution.
Glad you're up and running, have a good weekend.
Add comment
Please sign in to leave a comment.
I get an error:
Inspecting the file in the error message I get:
/****** UPDATE 2022-11-11 *****************/
This problem is now solved.