Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when using SSIS #51

Closed
LSMetag opened this issue Oct 30, 2017 · 9 comments
Closed

Crash when using SSIS #51

LSMetag opened this issue Oct 30, 2017 · 9 comments
Assignees
Labels

Comments

@LSMetag
Copy link

LSMetag commented Oct 30, 2017

Hi !

First, I really love your product. But It makes Visual Studio crash each time you try to run a SSIS package.
Visual hangs until you closes it.

So you can't use SSIS if BuildVision extension is enabled. I hope you'll be able to fix that.

Cheers

@StefanKert
Copy link
Owner

Hey there!

Thanks a lot for the kind words and also thank you for taking the time to posting this directly to GitHub :)

Sorry to hear that this is happening for you. Is it possible to get more details? Do you see anything in the Activity Log? Do you have a screenshot that shows your VS instance during the crash? Also can you please provide some more details on SSIS. I haven´t worked with SSIS within Visual Studio yet so it would be great to get an example package if you can provide one.

I assume that you are running on the latest version of BuildVision, but just to assure that this is true please let me know which version you are using.

Cheers :)

@StefanKert StefanKert added the bug label Oct 30, 2017
@StefanKert StefanKert self-assigned this Oct 30, 2017
@LSMetag
Copy link
Author

LSMetag commented Oct 31, 2017

Sorry it's a professional project, so I can't show much.

executing first task

When I do "right click => execute" on the first task, the EDI becomes completely unresponsive.

Here is the request of the first SQL Task that removes every table in a database:

EXEC sp_MSForEachTable 'DISABLE TRIGGER ALL ON ?'
GO
EXEC sp_MSForEachTable 'ALTER TABLE ? NOCHECK CONSTRAINT ALL'
GO
EXEC sp_MSForEachTable 'DELETE FROM ?'
GO
EXEC sp_MSForEachTable 'ALTER TABLE ? CHECK CONSTRAINT ALL'
GO
EXEC sp_MSForEachTable 'ENABLE TRIGGER ALL ON ?'

GO

The issue is SSIS has its own compiler/builder and there may have a conflict.

Here is the log (I had to remove .xml extension to attach it here)

Activity.log

Thank you for your attention !

Cheers

@StefanKert
Copy link
Owner

Thanks for the details! I was able to reproduce this bug and will take a look at it asap. Don´t know if I can fix it this week, but I will keep you up to date on the state of this.

@StefanKert
Copy link
Owner

StefanKert commented Oct 31, 2017

Just to give you a quick update on this:

I already fixed the issue but I need to do further testing. The problem we´re facing is a Visual Studio Bug and sp the best thing I can do to „fix“ this issue is finding a Workaround.

I will see if I can do further checks tomorrow so that I can pre-release 2.1.1 for you to test it.

Cheers :)

@StefanKert
Copy link
Owner

As said yesterday I had the time to test it out today. I created a basic solution with a SSIS project and it worked out with the newest build. You can grab the artifacts here https://ci.appveyor.com/project/StefanKert/buildvision/build/2.1.1.144/artifacts

Please let me know if this workes out for you too and if you found any further issues. If everything is fine, I will push a new release.

Thanks for your help!

@LSMetag
Copy link
Author

LSMetag commented Nov 1, 2017

Thank you for being so prompt to answer ! I can't test before monday (I took days off) because I only got SSIS at work. But I trust you. I'll tell you if I get other issues.

@StefanKert
Copy link
Owner

Great. No worries. Just let me know if you had time to check it out and if it worked. Thanks and have a nice day off :)

@LSMetag
Copy link
Author

LSMetag commented Nov 6, 2017

It's fixed with this build ! Thank you !

@StefanKert
Copy link
Owner

Great! Thanks for the info. Glad to hear that it is working out :). I will deploy a new version this week so that everyone can get this fix :)

Thanks for your help! If you got any further feedback, bugs or ideas please let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants