Essentially, I encounter the same problem as the question below, except that the accepted answer does not resolve it. I have neither warnings nor errors in the Error List:
See complete tooltip error message for Data Flow SSIS element in Visual Studio
Similar to the question noted above I can see a truncated warning message on the Data Flow design surface.
However, no corresponding warning is visible in Visual Studio's Error List view.
How can I view the entire warning?
This is a bit misleading from Visual Studio and could have been handled better. The long and the short of it is that the Error List window lists only messages that are related to build issues.
The warnings and errors that you see in design time are related to the execution flow. In other words, a package can be built correctly but is designed in such a way that it will generate an error. For more reading:
MSDN: Cannot see errors or warnings in SSIS - why ?
SQLServerCentral: Cannot see errors or warnings in SSIS – why ?
You will need to run the package in debug mode and then go to the Progress window. From there, you can see all messages (e.g., information, warnings, errors, etc.). Some messages may be so long that they cannot be seen. For those messages, you can click on them and paste them into your favorite text editor.
Note: when you stop debugging, the Progress window changes its name to Execution Results and the error List window becomes available.
Update
Per Hadi's follow-up comment, I was initially able to re-create the OPs problem by just modifying an existing package to create the warning message. I then built and ran the project with without receiving any error messages.
Now, after having left the office and shutting down Visual Studio, I am unable to recreate the error. The Error List window now populates with the messages. I tried building a new package from scratch without any luck either. My best recommendation at this point would be to, as with all Microsoft products, restart the application if it is not working as it should be.
This text truncation issue/bug is not just tooltips.
It's in SSIS Toolbox (description box at bottom) - no way to see the entire text describing the task/component (if not too big you can increase the width of the pane but that is not really acceptable).
(VS/SSDT 2019)
Many things to try
Try to change the combobox selected value from Build + Intellisense to Build only
Open and close the OLEDB Source by double clicking on it, since you tried to build the package the warnings disappears from the Error List, you must revalidate the component to show them
Try to update the Visual Studio 2017 to the latest release
Related
Situation:
I'm using VS 2017 to build an SSIS package for MS SQL 2017. While building a Data Flow, I add the OLE DB Source and Destination. After mapping the destination, VS correctly identifies a truncation issue and gives me the warning message. (I was trying to put an nvarchar(50) into an nvarchar(10).)
I correct the issue by updating the source to limit the column width to 10 characters. SSIS build and runs fine, but the warning message persists.
Question:
Is there some way to force VS to reevaluate the package for warnings/errors? The only way I've found is to delete and re-add the destination, but that is obviously a pain. (Especially when it means remapping columns.)
Am I missing something obvious?
Not terribly. Slightly less painful might be to select a table above/below the current on in the destination. Click OK and then you get errors everywhere. Go back to the original table and the warnings have gone away.
I suppose closing and re-opening would force the designer to re-evaluate the metadata as well. But no, no button or mouse click to say call the underlying object's ReinitializeMetaData() method. At least, I assume that's the call the designer makes and then evaluates conditions like truncation possibilities
You can right-click on the Connection Manager for the components that are throwing errors and warnings (this works for errors too), set it to "Work Offline", and then do the same thing - right-click on the Connection Manager to remove the checkmark on "Work Offline".
When a Connection Manager changes state from "offline" to "online", all of the components and tasks that use it get re-validated.
I don't remember what version I was working with, but I've seen metadata get "stuck" with the wrong input length, and no amount of reinitializing would clear it. I had to open the Advanced Editor and manually change the length of the input column in order to get the warning to clear.
I have a setup created that installs an application, and still does, but it started giving a strange warning at the end out of the blue. So, when the installation process finishes, the following appears:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2810.
So I checked 2810, and it says:
On the dialog [2] the next control pointers do not form a cycle. There is a pointer from both [3] and [5] to [4].
I was not changing anything in the "User interface" or "Custom actions" so this came unexpected. Also the installation completes if you just click ok and everything works fine, it just doesn't look good from a user perspective. Any help or similar issues encountered?
Control_Next: This is probably just the tab-order for the controls on the dialog. See the Control_Next column of the Control Table. You need to find a way to visit each control of the dialog in sequence and sort out so there are no loops or double links.
TAB Order: In the dialog in question (launch the setup and get yourself to the FinishedForm dialog), try hitting TAB repeatedly to see what happens. It might work, but you might see the control order being messed up so TAB unexpectedly moves around the dialog haphazardly going in "reverse" selecting a control already visited or similar.
Fix: Fixing this depends on what tool you are using. You can "test fix" directly in the final MSI using ORCA or a similar tool to edit the Control Table directly (just open the MSI and do it). The real, lasting fix will be in the sources used to compile the setup. WiX, Installshield, Advanced Installer, Visual Studio Installer, or whatever tool you are using. Exact fix depends on tool. A screen shot of the Control Table content could give us the clue we need.
(combining comments into an actual solution)
If you're using the common script EnableLaunchApplication.js within a Visual Studio Installer project, then the 2810 error code is most likely caused by a single line within that script, along with a recent Visual Studio update.
The fix, as mentioned by user Olaf:
in the EnableLaunchApplication.js I changed the line INSERT INTO 'Control' ... and replaced the value 'CloseButton' with 'Line1'. – Olaf Jan 9 at 14:16
With the entire corrected script linked by user Shangwu:
Here is the latest JavaScript without causing error 2810. stackoverflow.com/a/59888956/6079057 – Shangwu Jan 24 at 0:49
The underlying reason can be found in answers by Adam cosby and Stein Åsmul.
I actually had the same problem and my Control Table was over populated just as you mentioned above. I beleive it was related or at least co-incided with the Visual Studio update from 16.3 to 16.4.2. For me I used the Visual Studio Installer too and on the older version of VS it compiles fine but the same commit number on a different machine with the new version it causes the same issue and the Control Table has a lot more Control_Next entries populated. Still not sure how to fix yet though in the source.
Edit:
Ok I discovered the problem. The issue with it now populating more of the Control_Next I can only put down to a the update. However, the automatic entries put in by Visual Studio would have been fine but I realised we had the MSI launch the exe after install using this: Visual Studio Installer > How To Launch App at End of Installer technique.
That meant I was injecting and modifying the Control_Next and thus caused the loop of Control_Next to be non circular. It is worth noting that the Control_Next is basically the tab order of the MSI screen and it must always be closed (imagine the tab without anywhere to go).. Anyway, it was ultimately caused by us modifying on the post build process the Control_Next to add in the checkbox. After working out the last entry on a build without our code running i just modified the original last entry and then slotted in out one there. Now it works fine.
Hope this helps
I am using Visual Studio 2017 to design a SSRS report. Are some of the error messages one sees when they click on the Preview button actually meaningless? For example, I get, "The tablix 'Tablix2' is invalid. The value for the DataSetName property is missing." But when I look at the xml for the rdl file, I can not find any "Tablix2".
Report Properties are empty. When I build, there are no errors or warnings
Visual Studio is probably showing you all the errors from the SOLUTION rather than just the one report. There should a drop down menu below the Error List window title bar with the different scope selections.
It defaults to Entire Solution but you can change it to Current Document.
The errors also don't disappear after you correct them (thx MS). You need to close and re-open VS to not see them.
In my control flow window, I have a data flow task that has a validation warning icon on it. The tool tip text displays a general message: "Validation Warnings Occurred". When I double-click to view it in the data flow task window, none of the objects have a validation warning.
It is is difficult to find the warning in the error list window because I have a over 30 connection managers that do not map to my TFS local path and it produces 2 notifications per un-mapped connection manager.
Is there another way to determine where or what this warning is referring to?
I am using VS 2005 Professional with SSIS version 9.00.05000.00
Those warnings sometimes hang around after the issue has been resolved. Try closing and re-opening the package.
Also you can execute the package and review the Output window.
I 'm working with Visual Studio 10, my project is with monorail and I get a lot of error on my ".vm" files, those errors are not pertinent, and I don't want to see them anymore is there a way.
I tagged this ask with castle monorail, because I guess some users could have the same problem. But I'm sure it's a problem more general.
I get the same problem sometime with aspx or xslt visual studio check the file's validity ( with the own rules) and report the errors in the error list
New Answer:
Unfortunately, these errors are emitted by CVSI, and can be ignored - I agree they're a bit annoying. I've found that they go away if I re-open the solution. Not a great answer, but it's the only one I've found that works.
Previous Answer:
Are these errors ObjectDisposedExceptions?
What are your settings WRT exception handling in VS.NET? Go to Debug -> Exceptions in the menu. If there's a check in the "Thrown" column, then you need to open that up and then find System.ObjectDisposedException and then deselect it.
If you're looking to still break on deselected exceptions which are thrown elsewhere, you're out of luck, as this isn't currently supported by VS.NET.