2019-05-28 18:22:22.4622;FATAL-;Rubberduck._Extension;Startup sequence threw an unexpected exception.;Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate Rubberduck.UI.ToDoItems.ToDoExplorerWindow ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Rubberduck.UI.ToDoItems.ToDoExplorerViewModel.UpdateColumnHeadingsOrderToMatchCachedOrder(ObservableCollection`1 columns) in C:\Users\IvenB…
> System.NullReferenceException: Object reference not set to an instance of an object. at Rubberduck.UI.ToDoItems.ToDoExplorerViewModel.UpdateColumnHeadingsOrderToMatchCachedOrder(ObservableCollection`1 columns) in C:\Users\IvenBach\Source\Repos\Rubberduck\Rubberduck.Core\UI\ToDoItems\ToDoExplorerViewModel.cs:line 111
> at Rubberduck.UI.ToDoItems.ToDoExplorerWindow..ctor(ToDoExplorerViewModel viewModel) in C:\Users\IvenBach\Source\Repos\Rubberduck\Rubberduck.Core\UI\ToDoItems\ToDoExplorerWindow.cs:line 24
then the stack trace; each frame begins with at, so what you read at the top of it is where the exception was thrown: the last scope that got to run being the last one to be at the top of the call stack, reading down you follow/"trace" execution all the way back to the top of the stack - which may or may not be the application's entry point, depending on what the code does (and how).
at Rubberduck._Extension.Startup() in C:\Users\IvenBach\Source\Repos\Rubberduck\Rubberduck.Main\Extension.cs:line 235
in a release build, you don't normally have the .pdb files, so the in part is missing
> **Justification** Self-Closing Pair (SCP) completion is currently hard-wired to bail out when the current line is in a comment. That hard-wired behavior needs to be made configurable, and/or improved so that it still kicks in when the current line looks like `'@Annotation|`, so we can get from there to `'@Annotation("|")` with just two (<kbd>(</kbd> and <kbd>"</kbd>) keystrokes.
**Description** When SCP determines that the current line is a comment, instead of bailing out it needs to firs
> Version 2.4.1.4627 OS: Microsoft Windows NT 10.0.17763.0, x64 Host Product: Microsoft Office x64 Host Version: 16.0.11601.20230 Host Executable: EXCEL.EXE
**Description** When i run the Code Inspection tools, in the window there is the message "Rubberduck doesn't see anything yet" with ducks that rotate forever.
The toolbar says "Ready". I cannot click the refresh button on the Code Inspection window neither the refresh link right under the error message.
> Could you check for me whether Rubberduck is configured to automatically run Code Inspections after parsing? Also we default to no logging unless it's the first start after a new installation. Please check whether a logging level other than "None" is set in the settings. Thanks :)
> Yes, the checkbox "Run Inspections automatically on successful parse" is checked. All settings are reset to the default values.
Logging level was set to "No logging". Now I've changed it to "Debug". [RubberduckLog.txt](https://github.com/rubberduck-vba/Rubberduck/files/3232163/RubberduckLog.txt)
I have this nifty yellow warning triangle on my ADO .NET Destination step in my data flow, but I don't see anything in the properties or Edit pane indicating what's wrong with it. Where do I go to find out what's broken not quite right?
> The root cause of this seems to be an incorrect handling of Inspection Cancellation in the ViewModel for the CodeInspections window. The Stacktrace for the COMException in the log suggests that the `SheetAccessedUsingStringInspection` has been run and failed.
``` 2019-05-29 13:18:27.6929;WARN-2.4.1.4627;Rubberduck.Inspections.Rubberduck.Inspections.Inspector;System.Runtime.InteropServices.COMException (0x8001010A): Il filtro messaggi ha indicato che l'applicazione è impegnata. (Eccezione d
> I think the issue relates to the `Unparsed` and `IsRefreshing` flags not being set correctly in the error handling of Inspection result fetching here:
> Warning: 0x802092A7 at Data Flow Task, Temp Table [119]: Truncation may occur due to inserting data from data flow column "Q12" with a length of 50 to database column "Q12" with a length of 5.
which I understand - row 2 of my data set has the survey question while rows 3-x have the answers. I deleted row 2 and tried running it again and I'm still getting that error.
Is it because I created the connection with a file that had that extra data in there?
Found it! (Google to the rescue) On the flat-file source, I had to set output data property to length of 5 instead of the 50 that it was at.
I've got it truncating my temp table then loading the CSV to it.
I have a Stored Procedure that loads the new data from the temp table to the permanent table. Would the logical next step be to have another Execute SQL Step to fire off that stored proc?
If so, can I add a parameter to the whole SSIS package that it can use? The SP requires a parameter so it knows which client the data is for.
I guess it would be simpler/easier/more logicaler/something to make one call to do all the data loading instead of calling SSIS to load the data to the temp table, then another SP call from my VBA code to load the permanent table.
begins to rummage to discover learn how to set/use SSIS package parameters
I'm extremely new to this community and appreciate any and all help. Apologies if my question has been answered before and if so, please point me into the right direction.
Issue: I created a VBA script which inputs an excel files, runs some processing and then asks the user if they want to take ...
> Thanks for the bug report! If you have inspections configured to run automatically after a successful parse, you can use the "main" refresh command as a work-around to refresh inspection results:
!["Ready" parser state button](https://user-images.githubusercontent.com/5751684/58563707-a107e600-81f9-11e9-8554-59c9217b8b07.png)
The default hotkey for this command is <kbd>Ctrl</kbd>+<kbd>`</kbd>.
That said, this inspections toolwindow refresh bug rings a bell and I think it might have be
Potentially dumb question: If I'm designing my SSIS package against my Dev server, do I need to recreate it against the prod server or just edit the appropriate connection managers? Or can that be passed in as a parameter, too?
> Hitting the "main" refresh doesn't resolve the issue. After cliccking i read on the button "Starting", then "Loading reference", "Resolving reference" and finally it display again "Ready" but in the Code Inspection window the error remain the same.
> @IvenBach @Vogel612 I was really only referring to anything that can already be access with a hotkey in some context, as in the "run all tests" which uses a HotKey to get to the tests pane and then another HotKey to run all tests.
> @IvenBach @Vogel612 I was really only referring to anything that can already be access with a hotkey in some context, as in the "run all tests" which uses a HotKey to get to the tests pane and then another HotKey to run all tests.
But I understand if the constraints of the environment don't let you do everything you want. ;-)
Create a query using the sql you have, but slightly modded
PARAMETERS eid long;
SELECT Sum(tblentrys.entryhours) AS TotalHoursPerFunction
FROM tBleExams
INNER JOIN (
tBlBankList INNER JOIN (
tBlExaminers INNER JOIN (
tBlEntrys INNER JOIN tBlActivity ON tBlEntrys.EntryActi...
@Hosch250 You know, you can use mcafee for that too...
> Hitting the "main" refresh button doesn't resolve the issue. After clicking I read on this button "Starting", then "Loading reference", "Resolving reference" and finally it display again "Ready" but in the Code Inspection window the error remain the same.
> Warning: 0x80049304 at Data Flow Task - Load Temp Table from CSV, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
The fix appears to be obvious. The question is "is this something I need to be concerned about?" and if so, "right now?"
While we do avoid DoCmd as much as possible, it is inevitable in some situation. Saving is one of them -- I suspect that it's the one that does the writes to the streams within the Access file.
Yay! got a parameter added to SSIS. Boo! I have to specify the full path & file name (unless someone has a tip), so now I have to modify the SP to pull just the file name from the full path.
Just outta curiosity, why does the Execute SQL Task have 2 green lines from it? Can I have 2 different tasks kick off simultaneously once it's finished?
wow... this is kinda spooky. I think I've got all this working now. I just need to figure out how to call my SSIS package from my VBA code and I'm golden!
if you figure out anything simpler than setting up a SQL Server Agent job involving an SSIS Package Execution proxy user, a stored procedure in msdb that starts the job, and a stored procedure in a DB the VBA code can access & run... let me know, I'm interested :)
ALTER procedure [dbo].[UpdateMaterialInventory]
with execute as 'SqlAgentProxy'
as
begin
execute msdb.dbo.sp_start_job N'NDS-ManualMaterialInventory';
end
ALTER procedure [dbo].[UpdateMaterialInventory]
as
begin
execute msdb.dbo.UpdateMaterialInventory;
end
had to create a SSISProxyCredentials object (under Security/Credentials) that uses the identity of the SSIS service account
oh, and it's fire-and-forget: VBA gets to know when the job starts, but not when it ends!
IOW it's a bloody mess
much easier from .net actually, no idea - the only .net code I have that runs SSIS packages is... itself in a SSIS package
@MathieuGuindon i wanna tell the guy exactly that... but i dont wanna get black marks for telling people they are stupid
screwit....
Maybe you should change your column headers to prevent such errors from happening. Using spaces and special (non alphanumeric) characters in fields is a recipe for disaster.. — KySoto40 secs ago
@KySoto I don't think that's fair. Remember, SharePoint is meant to be accessible to non-programmers, to enable them to do their things without having to involve IT. The screwup is not on the users but on the SharePoint programmers who didn't come up with a good convention of converting captions into programmatic names.
Users don't give a fig about whether the name is easy to work with for the programmers; they want their TPS report to look purty.
But because Microsoft can't do it right, the users now have to care about extraneous details like whether it's a good programmatic name or not.
Oh.... fun fact! You can't change the programmatic name once you've created the column! Yay!
Actually, since it's fire & forget, I really do need a for each loop - I've only got one temp table (I guess I could have more), so I need them to run synchronously, not async.
i.e. I load client 1's data to the temp table, then load that to the final table and flag it as client 1. Then truncate temp table, load client 2 data to temp, then move load to final, flagging as client 2.
Lather rinse repeat
Maybe the whole process needs a rethink now...
would putting it in a ForEach loop in SSIS ensure they run sequentially, or would it fire off the SP/Data Flow/SP process as fast as it can and leave everything to fend for itself?
Make SSIS drop a marker file on some network share on success, and use a (client-side) FileSystemWatcher to fire an event when the marker file shows up?
This provides a native WinAP + VB/VBA way of doing the job, I expect:
http://books.google.com/books?id=46toCUvklIQC&pg=PA757&lpg=PA757&dq=windows+api+monitor+directory+changes+vba&source=bl&ots=jmMY4sJFK4&sig=KCB6B_soEA9_JzjlhyNZvSC91w4&hl=en&sa=X&ei=cUAMUsDzOe3iyAHu8YGwAg&ved=0CFIQ6AEwBw#v=onepage
I was looking at it from the perspective of minimal modifications to what I have, not a more serious rewrite. When in the forest, one tends to only see the tree trunks...
thx. Interesting... Looking at this MS tutorial showing how to call a SP from SSIS, there is a IsQueryStoredProcedure setting that is set to False and disabled, but doesn't seem to need to be set to True in order to execute a SP.
Meme: Skiwi (verb), e.g. "skiwi'd"
Originator: IvenBach (?)
Cultural Height: VBA Rubberducking (2nd monitor?)
Background: Skiwi has long been renowned to consistently have well over 1000 open tabs in his browser. "To skiwi something" means to open a browser tab and leave it opened to get back ...