I've had a long-standing problem that every so often, when I open an SSIS package (2012), the designer pane is blank (all white).
If I try to view the code, it comes up, but the file name in the tab shows up as blank.
If I try to execute it, I get a message saying "Unexpected internal error: " -- and nothing else.
Rebuilding doesn't seem to help.
Unloading / Reloading the project doesn't help.
If I try to save the file, I get an error, "Object reference not set to an instance of an object."
Closing the entire application usually does the trick, but when I have dozens of packages in one solution, it's brutally slow.
I've noticed one other fix, which is to rename the package, which is obviously not ideal... but it does seem to indicate that the name of the package is what's causing the problem. If I rename the package back to the original name, the problem re-appears.
I've also tried deleting the metadata for the graphical rendering, but that doesn't do anything either.
Curious if anyone has seen this problem and has a solution. I saw nothing helpful online.
For me this problem was resolved in two simple steps below.
Rebuild the Project.
Close Visual Studio & reopen.
I know this is an old post, but this is a common thing I run into and I want to make sure its answered.
Open the package that gives you the white screen.
While open, rename the package (suffix it with 1).
Close the package.
While closed, rename the package back to the original name.
This has worked every time for me.
Related
For some reason, PhpStorm has decided to all of a sudden get stuck at "Loading project...", which seems to be at the step of "Scanning files to index...".
No matter how long I leave it it doesn't get any further, and the window reports it is "Not Responding".
I've read a potential solution is to "Invalidate caches", but that's pretty hard to do when I can't even get the program to function.
How can I do this step manually, or is this the correct way to handle this?
I even tried creating an empty folder and opening that as a new project, but same issue.
I have a complex MS Access 2013 database with tens of forms. On one of the forms, I have button with vba procedure back to it, which returns values from MS SQL(ADODB) and puts them into the textboxes.
Problem is, whenever i click this button, it steps into compile menu as if there was a breakpoint, but in fact there is no breakpoint. Of course there are no errors / MsgBoxes and If I just click F5 or F8, it goes well.
Has anyone the Idea, what may be wrong?
Phantom Breakpoints can usually be fixed by copying the line which stops the code execution into notepad. Then delete the line from the VBEditor and insert it again from the notepad.
If this doesn't work, try decompiling the database:
Open cmd and enter the following:
<full path to your database> /decompile
example:
C:\testDB.accdb /decompile
In fact you can just re-paste it from the clipboard, you don't need to use notepad. But don't paste it back into the same line. Delete the bad line.
Phantom Breakpoints don't go away with a restart.
This issue has been around for years and yet MS won't address it. Annoying!
Phantom Breakpoint strikes again :(
This showed up in such a strange way that I feel compelled to post it somewhere. This seems like the most obvious place, but I'm glad to move these comments elsewhere as appropriate.
I have an Access 2010 ACCDE giving me this same error: "Requested type library or wizard is not a VBA project" when I click a button on the main navigation form. I try an earlier version with same references and exactly the same code (in the nav form and other areas relating to the button) and it works fine. However, when I open the ACCDB used to build the "bad" ACCDE, and click the same button, I get a different error: Error 16 - "Expression too complex".
I fixed the issue by commenting out the associated VBA lines in the nav form and duplicating the uncommented code below the original lines.
The strangest part was that it wasn't until after several debugging sessions that it started behaving as the original posting above, where the it would break to the invisible breakpoint. It displayed the misleading errors above before that.
My standard practice now is to use Clear All Breakpoints (under Debug menu) after all development sessions. Hopefully that will prevent this in the future.
The phantom breakpoint thing has been an issue for a couple of versions from what I remember. Between that, and the new thing where the code window activates just by floating over it- even if you don't click in that window- I'm not sure I can endure anymore "Improvements". Hell the the program ran pretty damned good about 3 versions ago! Honestly the new "fluff" they've added - alternate colors on report lines-or other data in tables- I don't use any of that and spend more time taking off alternative line colors when I don't want it!
Fix more bugs and spend less time on new features!!!
Ghost breakpoint within referenced accdb code library!
Had a very similar problem. While starting the application it stops highlighting a line in yellow. Unfortunately the highlighted line was in a referenced accdb library for additional code which I share between different databases. The other databases still worked fine with the identical part of code. Deleting the ghost breakpoint line didn't help (references are read only anyway), so, the source of the problem should be within the code of the calling database and not where the call runs into a ghost breakpoint.
Toggle the reference then, of course with save and restart, stopped the ghost breakpoint.
Just in case there is somebody with the same problem connected to referenced code.
I have posted this on google-apps-script-issues (https://code.google.com/p/google-apps-script-issues/issues/detail?id=4723&can=4&colspec=Stars%20Opened%20ID%20Type%20Status%20Summary%20Component%20Owner) but with no response I am getting desperate as all my sheets and scripts are breaking down. So I hope someone here might have encountered this and have some idea for me how to handle this.
Some of my exiting scripts (including some in spreadsheets) suddenly started throwing the exception 'Library with identifier LabelServices is missing (perhaps it was deleted?)'.
I tried deleting the library reference in some of the scripts that were throwing this error and re-adding it but the same error comes up. I even defined a new library with the same name and try to use it instead. Still the same error.
Most likely a related error, when trying to open project properties to these scripts I see the message 'Something went wrong. Please reload.' and the hourglass never stops. This happens at both standalone scripts and ones embeded in spreadsheets.
Please note that if I add the same library to a new script then there is no problem and the library works perfectly.
I would like to add that even if I remove the library and also any calls or references to the library the problem still persists.
Link to a script where this happens is available at https://script.google.com/d/1ptevXwu25z9Vo88zX0XOyaQk5pE5MmzwDbb-lMglNY1lzz1HBBiAeJxn/edit?usp=drive_web
You can copy it and play with it. You should get the same problem.
Appreciate any help!!!
Andrew. First of all thank you as you triggered something in my mind. I went all the way bottom up and checked each script and a library it was calling. There were obviously dependencies, however nothing that should have been a problem. a couple of libraries even though in development mode seem to cause a problem. I had to create a new version but it was not enough just to update their version in other scripts. In the calling scripts I had to remove all libraries and re-add them one by one while testing whether the project properties shows up or not. I just wish Google would have a utility to clearly highlight what was wrong because I can't figure it out though I went twice through their documentation in regard to libraries and development mode. Since I have about 30 libraries or so, not to mention spreadsheets and apps it took me nearly a whole day... Thanks again!
To all, it seems that there is a problem where sometimes libraries get out of sync (at least that's the best way I can describe it). You may need to create new versions for the libraries (even though these are in development mode. And in each problematic script remove and re-add the libraries (in at lease a couple of transactions - first remove and confirm then add - and better one at the time while checking that your project properties opens properly). This solved the problem for me.
So after switching over to Sublime Text last year, it has become my editor of choice, and I have installed several different packages via the excellent Package Control and basically customized it all to my liking. After a couple months of infrequent use, I jumped back into a code-intensive project and fired up ST2 only to find that none of my packages are working.
After some digging, it finally occurred to me to open my preferences file, only to find all of my installed packages in the "ignored_packages" list. WTF?
Has anyone else experienced this or know what would have caused this? I do some funny things in my sleep sometimes, but not this!
My earlier comment notwithstanding, I think I've figured out what's going on. The issue seems to be Package Control, most likely the new version update to 2.0. I just restarted ST2 after having it open for the past few days, and happened to have the console (Ctrl`) open, and saw that several of my packages, including Tag, Terminal, and SublimeREPL, were added to the ignored packages list. This typically happens when a package is being updated or removed, and is done so it can't be used halfway through the operation before everything is synced. At any rate, for me there was some sort of error, and I had to force quit Sublime and restart it. I immediately checked my preferences, and sure enough several packages were in the "ignored_packages" array.
So, I'm guessing something like this happened to you, and for whatever reason the packages weren't removed from the ignored list, possibly because the system update didn't complete normally. Hopefully this won't happen again, but if it does you'll know where to look. Additionally, if it does happen again, I'd submit an issue on Github, as this may be a bug.
Update
My issue on Github has been merged into this one, and if you scroll all the way down to the bottom wbond has a fix for now: Download Package Control 2.0.1-beta, put it in your Installed Packages folder (removing the one that's already there), and adding the repository https://sublime.wbond.net/prerelease/packages.json by selecting Preferences -> Package Control -> Add Repository. Restart ST2, and see what happens, especially after restarting multiple times. If you still have bugs or odd behavior, please add to the issue.
I am adding this even if it's an old thread because the answer did not solved my problem, but it pointed me in the right direction.
Since it was a problem due to Package Control trying to update packages and I didn't want to mess with repos and stuff, first I tried to upgrade the packages "manually" using Package Control and I noticed that there was a 1-to-1 match between the items in the ignored_packages array and the packages that needed to be upgraded.
After updating, just remove the packages from the array and restart ST2: no more weird ignored packages in the array.
I am making some changes to a Flex 3 project and have run into trouble. I am using Flex Builder 3, working on a PC. Everything was working as expected throughout my first day of code updates, but on day 2 Flex started behaving badly.
The problem started when I removed a component, and then got an error that it couldn't find the specified component in some accompanying AS3 code. No problem, I updated the reference so it wouldn't look for the old missing component (a form item). When I compiled the project in debugger to check my work, it failed when it got to that part, and gave an error that it couldn't find the component I'd removed. However, my code had fixed the problem, and the error was referencing a line of code that wasn't there any more. I proceeded to change the file around greatly, and even resorted to creating a new file, changing the name of it, and then recompiling it. I did a clean compile as well, rebooted my machine, restarted Flex, but every time it gives an error referencing the bit of code that isn't even there any more. It's as if it's loading a cached project each time (both in debugger and run mode).
For reference, here's the error I'm getting:
ReferenceError: Error #1069: Property Winter Cost not found on views.PopupUsage and there is no default value.
Well, the file "PopupUsage.mxml" doesn't even exist any more and is not referenced in my project at all, but it's still being referenced by Flex when I compile the files. Any ideas? What can I do to make Flex move on and look at my code?
Thanks in advance!
The only time I have encountered this issue is when I've been developing an application that uses another SWC in the project build path. Where I've come undone is not referencing the SWC project in the project properties build path, but only referencing the SWC itself. If you have the SWC project code imported and you're editing it, then you can see this type of behaviour, appearing as though there's a mysterious cached version of your app, where in fact its simply the build path that isn't quite right.
So check your project properties build path for this issue, it sounds obvious, but I've lost count of the amount of times I've quickly imported the code for a library and forgotten to reference it properly in the application I'm using it in!