May 14, 2008 at 6:44 pm
This just started happening out of the blue. Nothing changed (that I know of) except that I'm developing on an ETL project. So I get some major code changes done, go to test it by hitting the green arrow and the entire solution tries to build instead of debugging the one package I have open and want to run.
WHAT?
Has anyone seen this before? BIDS is complaining about not having a deployment server and even if I go into the menu and click Start Debug, I get the same problem. Tried restarting my PC, logging off & on, leaving BIDS off for a while, log back in and same problem. It tries to build the solution instead of debugging the one project I have checked out and open then complains because I don't have the "build" pointing anywhere.
Help, please. How do I get this to stop?
Thanks,
May 15, 2008 at 10:01 am
Does it work on another PC? Have you tried re-installing BIDS to see if the problem corrects itself?
May 15, 2008 at 5:49 pm
Other people are using BIDS with no problem on their PCs. I don't have time for a reinstall. My project is due Monday.
I finally closed the project out, started a new solution, added the 2 previously existing projects (1 SSIS, the other SSRS) to the new solution, saved it, uploaded it into VSS and am able to debug on this new solution without it trying to build...
HOWEVER... out of the blue my Toolbox items have disappeared. All of them except 2 Maintenence Tasks (Pointer and DataReader Source). Now all I did was click the little push-pin to Auto-Hide the stupid thing for a while. Then I went into DataFlow, opened Toolbox back up and it was practically empty. (There's a little #13119 header under Maint. Tasks with a message that says "There are no usable controls on this group. Drag an item onto this text to add it to the toolbox).
I had to go back in an add all my Control Flow and Data Flow objects back to the Toolbox. However, now they're not grouped by Source / Destination / Maint. Task. They're all alphabetical in the list and I am SERIOUSLY confused.
I've been using BIDS for almost 2 years now. I've NEVER seen this behavior from it. Has anyone else?
May 16, 2008 at 7:15 am
This kind of bizarre behavior would definitely cause me to re-install. Personally, I would rather take the time to re-install and let it correct itself than have to setup things (such as your toolbox) that should be setup automatically. I know it is a pain and time-consuming to install but how much more time are you wasting working in a buggy environment? You did say your co-workers are functioning just fine which also tells me a re-install should clean it up.
May 16, 2008 at 11:30 am
Jim,
I appreciate your opinion, but I hate doing the half-day to full-day's worth of work uninstalling two programs and re-installing them if there is another perfectly logical explanation for the current behavior.
I would rather research first and see if anyone else has had this issue (and if so, what they did to resolve it) before jumping the gun and tearing apart my system. Especially since I'm working 18 hour days on this project and will likely be working all weekend long to get it turned in on Monday when it is actually due.
After Monday, I could waste the time on an uninstall / reinstall. But again, before I take measures that drastic, I'd like to see if there are other options.
Does anyone else have any experience with this? I can't seem to find anything via Google, but I may be putting in the wrong search phrases.
EDIT: BTW, Jim, if things get worse then they currently are, I will definitely take a re-install into consideration. But it'll have to be something that I can't work around in less than an hour before I consider that tact. Thanks though for the suggestion.
May 16, 2008 at 11:52 am
Brandie,
I had that same #13119 message awhile back in Visual Studio. Deleting the following files under my user profile and reopening Visual Studio fixed that.
CD "C:\Documents and Settings\MyUsername"
CD "Local Settings\Application Data\Microsoft\VisualStudio\8.0"
DEL toolbox*.tbd
May 16, 2008 at 12:05 pm
Brandie,
I can certainly sympathize with you and I don't like the uninstall/reinstall route either. Please let us know if Todd's solution works for you. Seems like a simple solution that I could keep tucked away for a rainy day if it works for your situation.
May 16, 2008 at 3:46 pm
Will do.
Also, just a note. My build problem doesn't seem to exist in other solutions, not even the one I created from scratch and moved my "problem child" existing SSIS packages into.
So it appears to be a solution level problem (sans the toolbox issue) rather than a Visual Studio problem.
Anyway, I'll test the toolbox thing this weekend.
May 19, 2008 at 7:08 am
Hi Brandie,
Not sure about your error message, but I know that when I set my project property "Create deployment utility" to TRUE, it attempts to rebuild every package in the project before it will run...
May be this is what's happening to yours.
Kindest Regards,
Frank Bazan
May 20, 2008 at 5:51 am
FYI: Todd's solution worked for getting rid of the #13119 error message on the toolbox.
Of course, it took a while for VS to reinitialize the toolbox after I deleted everything. Once I reopened SSIS, though, everything was in the original order that I'm used to instead of alphabetically under one heading. COOL! BTW, I didn't see anything under the first path related to the toolbox, only the second path he gave. So, it's definitely a solution for part of my problem.
Frank, where are you seeing this option? When I look in the properties window of my package, I don't see something called "Create deployment utility". Is this hidden in a menu path somewhere?
May 20, 2008 at 6:38 am
Hi Brandie,
If you look in the solution explorer, right click on the project and go to properties, a new box comes up with configuration properties.
If you select the deployment utility branch, you will see 3 options - "deployment path", "allow configuration changes" and "create deployment utility".
Setting the last one to false, hopefully stops the "rebuild all" behaviour.
Kindest Regards,
Frank Bazan
May 28, 2008 at 7:46 am
That's a nice little trick, Frank. Thanks for the suggestion.
Unfortunately, it doesn't quite work for my setup. Apparently when you put an SSRS project in a solution with an SSIS project, the SSRS project tries to build every time you debug one of the SSIS packages.
DOH!
Really, really annoying. I think I might post this to MS's bug/suggestion website so they can get that fixed.
May 29, 2008 at 1:32 am
Brandie, create deployment utility is on your project (under the icon which looks like an AS database0
Right click on this and select the properties.
Look at deployment utility.
If this option is set to true, what will happen is that an integration services deployment manifesto will be created under your bin\deployment folder, and yes, each time you want to debug a single component, it will try to first build the entire project.
Good luck with your deadline man
~PD
ps> Some Dilbert that I thought you would appreciate in this deepest darkest deadline hour of yours
"...I love the swishing sound of a missed deadline as it passes over my head..."
May 29, 2008 at 4:37 am
PD,
It's set to false. But it doesn't change the fact that I can't set the Deployment Utility at all for the SSRS project, which is the problem. The SSIS project doesn't try to build, the SSRS project does. While I'm trying to debug in the SSIS project.
And since Deployment Utility is NOT available on the SSRS project in 2005 BIDS (maybe this has changed for 2008), I'm stuck with the SSRS project building every time I debug a single SSIS package.
May 29, 2008 at 4:55 am
Brandie,
Apologies, I didnt realise there was a second page of postings when I read the thread.
Good luck with this one, I have no idea regarding any of the workings of SSRS within BIDS (still sweating on the SSIS stuff).
If you do find a solution however, please post what was done
~PD
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply