I have a very stupid problem, because the way BIDS works is just hilariousy idiotic. Short Story: 1) When i try to edit script tasks it will complain about "failed to create project at some random path in temp folder" and wont open anything. I cannot edit script tasks anymore. THe project is essentialy dead to me. REboot or restart wont help. I spent five hours on this project and i dont want to do all that work from scratch! 2) I cannot port my solution to antoher computer or place because it links to the files in appdata/local/temp folder of the pc for some reason. If i delete that folder or port the solution, it will complain about some file in temp folder called "3jews....tmp" and will say that solution is unopenable. Need help to resuce my project and be able to continue working on it! Long Story: When you make a project, BIDS stores its files in a separate folder: a solution file, a project file, a package file etc. You might have thought, you can now carry your solution over by copying this folder. WRONG! The BIDS actually stores files of the solution in /Users/name/AppData/Local/Temp folder! And It cannot open a solution/package/project without files from that folder, now what kind of idiotism is that? It all started with BIDS not saving my script task changes, then telling me "cannot create project in folder blablabla" when i tried to reedit the script task. It helped restarting the BIDS once, then it stopped helping at all. Now, when i deleted the TEMP folder in question (hey, its called TEMP for a reason, because its TEMPORARY means NOTHING PERMANENT is stored there!) the solution will no longer open! It will complain some file in temp folder is missing and will say solution is unreadable. More than that, i manually opened in notepad EVERY solution file, EVERY file in the directory where my solution is stored. IT DOESNT CONTAIN THE LINK THAT BIDS COMPLAINS FOR! It complains for some "3jews...tmp" file but this file is never linked in any of the solution files. My solution folder has SLN and SUO file and one folder It has dtsx, database,dtproj, and user fie and one folder It has dtsx file. Not a single one of theese files (they are all text files) references such file, unless the link is somehow encrypted, in which case this is utter nonsence since who would encrypt something in an XML file if XML file was made for information to be human readable in the first place? Now, five hours of my work destroyed by stupid Microsoft program, even if i restore the deleted temp folder i still cannot edit scripts nor can i try to port my project to another computer to see maybe it will work there (i previously successfully developed BIDS projects on another computer). This is so stupid, i just cannot understand how can Miscrosoft get away with charging money for products this bad.

what i understood, you are not able to open script task editor. am i correct? please correct me if i am wrong. meanwhile have a look at this thread.. may this help you. Let us TRY this | My Blog :: http://quest4gen.blogspot.com/

Yes, ONE of my problems is creating a new script (randomly, not aways) or editing ONE of the already present (exact one, others work) result in this: Cannot show Visual Studio Tools for Applications Editor Additional Information: Failed to create project at location (random name) Also, this message never shows when i first open an empty script, but, if it is going to show, then it wont save changes (no matter if i save them with diskette icon or not) i do to the script, and on next attempt to edit it, will show the error. Also, now on 3rd try i managed to edit and save script task, BUT, if i create a web reference, and use it in code, when i save changes and exit, the package says "code is missing" and when i open script editing, the reference is gone, and ofc using it in code is invalid, BUT, i CANNOT make antoher reference with same name, it will change to "name"1. More than that, in order for web refernce to "stick" i sometimes have to do it twice or thrice (mostly reference2 does the job....). How stupid is this? And now i reopened the solution and i AGAIN cannot edit the said script task. FFS. ----- Yes i see alot of people having complains with "cannot find assembly" but my case is a "failed to create project at location" one, i dont think they are similar. By the way, the path it points to is damn legal and exists on my system (there is such folder in /appdata/local/temp/2/ssis/)

Btw, following an advice in a similar thread, uninstalling VSTA and repairing SQL installation did not help :( running a script that cleans something (removes reg keys and folders) didnt help either :(

I am really not sure why you are getting this error. Please share your complete error message with us. work around: You may have to reinstall the .Net framework to get the file issue corrected. Let us TRY this | My Blog :: http://quest4gen.blogspot.com/

Once again. This is the whole error. Cannot show Visual Studio Tools for Applications Editor Additional Information: Failed to create project at location <user folder>\appdata\temp\ssis\2\<random name about 20 letters and numbers long> This is actually a fresh virtual machine and i just installed lastest 3.5 framework with patches sp's and fixes. Maybe i installed something wrong? Which files do you suggest to install to get the "good" framework? There are so many "frameworks" out there, really, i had to install like five files (framework, sp for it, 3 fixes for it).

Hi there, As I'm aware of it, SSIS doesn't maintain ANY persistent information in TEMP. The only persistent information is stored in the DTSX - all those other files you mention (SLN, SUO, DATABASE) are all supporting files maintained by Visual Studio to help manage your "project" and "solution". (Those are almost meaningless concepts in IS development, because they have no effect at "runtime.") What SSIS does use the temp folders for (in your case) is creating an "on the fly" Visual Studio project to host your script. It creates that on the fly every time you open a script for editing, and then discards it once you're done editing. So yes, it's temporary, as it should be. Now - I'm not saying you aren't having a problem! My suggestion (so far) is to make sure that your TEMP paths in your system are set appropriately, to folders that you have complete read/write access to. Not sure how any of that could have gotten messed up, but those are the straws I'm pulling. Another suggestion - just to try something completely different - is to try opening your solution on another machine to see if it has problems. Talk to me now on

Hello yes the temp problems were because SSIS is too dumb to recreate temp folder if it doesnt exist... But Cannot show Visual Studio Tools for Applications Editor Additional Information: Failed to create project at location <user folder>\appdata\temp\ssis\2\<random name about 20 letters and numbers long> is still there and the folder exists this time, but it still fails to create project at location. I will try to port the project to another pc to see what happens...

There's got to be something else going on, because SSIS isn't "too dumb" to "recreate" that folder if you open the package on another machine, where it never existed anyway. Second, you direct your anger at the inanimate to VSA/VSTA rather than SSIS - because it's that subsystem that's misbehaving for you. Talk to me now on

Well, if you actually delete that "temp" folder then you cannot open any SSIS package anymore, try it! At least, at my machine, it happens like that. It just thinks that the folder is there, no matter what happened. I think, its kinda shortsighted not to check if a temp folder is there before you attempt to write to it, right? And you cannot even say "setup must have made that folder and you have no reason to delete it" since it must have some way to create that folder, because if i make a new user, that user should be able to use the BIDS installed on this PC. This means that somehow, somewhere BIDS knows how to make that folder. It just doesnt attempt to! It presumes that the folder should be there once made, and this is what i call stupid, because, hey, it is! Its like trying to access anything in the computer world without checking if it exists. I know you can skip the check like "if it existed 5 seconds ago, it should be there" or "if it existed when app launched, it should be there" but you cannot expect that something in the user folder is there after the program was closed and reopened...

Then there's something really weird going on with your install. On my Win7x64 BIDS 2008, I can delete the SSIS folder under C:\Users\me\AppData\Local\Temp and start up any package with a script in it. As soon as I open the script editor, it creates the SSIS folder. Somehow something in your install is really screwed up. Have you tried a repair and/or reinstall? What version and bitness of OS, SQL, etc... do you have? Talk to me now on

2008 server 32 bit. sql 2008 r2 enterprise. I tried repair, i tried uninstalling VSTA, and i cannot uninstall sql server, its used! You mean, i should remove BIDS as an option and then add it back?

Can you please try to open your package on another machine? Let us TRY this | My Blog :: http://quest4gen.blogspot.com/

Yes sorry for delay. No transfering to another pc (where i was working fine with the ssis projects before, "fine" meaning having other bugs and problems, like random crashing... but not this one) didnt help. I am getting same error when opening same scripting task. TITLE: Microsoft Visual Studio ------------------------------ Cannot show Visual Studio 2008 Tools for Applications editor. ------------------------------ ADDITIONAL INFORMATION: Failed to create project at location "C:\Users\AVAndronov\AppData\Local\Temp\4\SSIS\9d38b03235c1496ba9a9f56b2da2f7ec"! (Microsoft.SqlServer.VSTAScriptingLib) ------------------------------ The given path's format is not supported. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------

Can you please load your package at some shared location? I would like to investigate the same. Let us TRY this | My Blog :: http://quest4gen.blogspot.com/

Oh ____, this now happens on ANOTHER installation of BIDS.... now another part of my work is screwed, nice! I'm uploading it now. http://ifolder.ru/19323853 I know its russian, but its free and fast unlike those rapidshare ____ that makes you wait. Go to the link, you'll see the captcha, input captcha numbers into the box to the right and press ENTER, the page with link will open, link will look like http://ifolder.ru/download/... so you can ctrl+f "http://ifolder.ru/download" to find it quickly The file is archived in a 7 zip format (open source zip archiver). Open the file, open the "(NYI)Create query to create the table and configuration string" script task, open its code, get the error TITLE: Microsoft Visual Studio ------------------------------ Cannot show Visual Studio 2008 Tools for Applications editor. ------------------------------ ADDITIONAL INFORMATION: Failed to create project at location "C:\Users\Administrator\AppData\Local\Temp\2\SSIS\8828eb81d5114cb59705dddb01d53e21"! (Microsoft.SqlServer.VSTAScriptingLib) ------------------------------ The given path's format is not supported. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------

What i also found: 1) I changed %TEMP% but it didnt effect BIDS. I even closed and reopened. It still uses previous temp folder for some reason 2) The buggy name changes every time. I mean the 828eb81d5114cb59705dddb01d53e21 is random. It will always crash for the same script task and work for another script task. Always. Therefore the script task must be the problem, not the path it shows as faulty... 3) Copying the script will result in copy also being corrupted 4) If you once opened and saved and reopened a script i have never seen it to corrupt afterwards. It must mean it gets somehow corrupted on first edit attempt...

Then I'd suggest dropping a new Script object on the page, and copy out your code and paste it in there and move on. The subfolder it uses for the "fake project" will change every time. It's a random GUID because it's only temporary storage used to compile the code you've written. Since it's intended to be temporary (check the behaviour of your other scripts) it doesn't matter what the folder name is - as long as it doesn't collide with an existing folder name, and I'd hope they check for that :) Talk to me now on

Yes, but this makes working with BIDS just painful and stupid! I now have either to: drop new script, edit it, put some random text in it, save, close, open, check it didnt bug, then start writing my code or drop new script, edit it, write code, copy code to notepad, save, close, open, if it bugged i have to make another one and copy my code there, rinse and repeat... otherwise i risk loosing my work! Isnt this just stupid? There must be some reason why it bugs and it must be fixed by Microsoft because otherwise, what are their words of "support" for?...

To be honest, the only conclusion I can make is that your situation is unique. I've been hanging around here for two years now, and this is the first time I can recall someone having this issue. So yes, I think proceeding "as normal" to code your scripts, and only solve this problem when it occurs would be what I'd do. You can always retrieve the script code by opening the DTSX directly, even if the UI is hosed, right? So you never really lose your work... That said, I can definitely understand how this "answer" isn't one! But then, this isn't a Microsoft support site either, and you are getting what you've paid for. Open a Connect issue, and attach your DTSX to it so that the real support engineers who have access to the code can peel it open and maybe see how it got messed up. Or call up support and get them to help you - but you'll have to pay for that. Talk to me now on

Well, did you see my file i uploaded? You can join the "unique" club :) I was also stunned to see that, because i used BIDS for like... half a year? Without seeing this bug! And when i first encountered it, i started encountering it over and over again and even on other BIDS installations and projects that never had it! I can only guess it is some kind of consequences that make this up. Like, if you do A-> B ->C you get the bug and only then. A->C or A->C->B wont get you the bug. Something like that. And my working patterns changed over the time that is why is started getting it regulary not having it previously. Could you be more detailed on "Connect issue". Is there a way to (free of charge) make Microsoft look into this bug? I'd gladly provide anything (project files, screenshots, explanations). Problem with paid support is that - well - because the whole ideology sucks, since i (my company) will have to pay for microsoft mistake! Its like you buy a pair of shoes, and the next day you have to pay the manufacturer for fixing holes in them that make water pour in when you walk in the rain. If i pay them for this, what next? The software will be EVEN MORE buggy since it makes customers pay more? But it will! It really will, if people do pay for such "support". I mean, i can understand why would i pay money to someone who i will ask "hey dude, how do i do X in your software i just bought" because this is knowledge sharing and knowledge accumulation is pricy. I can understand why would i pay money to someone who i will ask "i just pressed wrong button and my whole data got deleted can you recover that for me?". But here it is a BUG. Its not working as intended! Its spitting error messages. Its corrupting projects! It is, not me. Why on earth would someone have to pay for helping with THAT? Why on earth should i pay for something i already paid once (when i bought the product)? If anything, Microsoft should pay ME for every bug i find in their software, since: 1) I am helping them finding bugs in their software which is a paid job actualy they should have hired beta testers for in the first place (i know they did but this shows they didnt enough). 2) Which then leads to more statisfied customers in the future meaning i am actually bringing them profit by supplying extensive information about the bug. 3) If you buy something and discover its been faulty manufactured (or is missing parts, etc) you get a refund or a discount, not pay for it! 4) And no there is no excuse to bugs of MS software on MS system on MS compatible software. I have 100% MS software i use on the PC that has the problems. Not a single third-party anything. That means the argument "you have something else that broke your pc not our fault" void.

Connect is a website Microsoft runs that solicits bugs and feedback on their products. You can submit bugs on the site, but as far as I'm aware, they don't guarantee any action on them. You can attach samples, screenshots, comments, etc... Of course, Microsoft is like any other software company - if you want help with their product, they're likely going to want to charge you money to do that. Money talks - Microsoft will surely listen if you open your wallet. However, like many IT people, I agree "the whole ideology sucks" when the scenario you described is oh so close to "it's like a customer buys a pair of shoes, drills holes in them, then wonders why water pours in when they walk in the rain. If I let them call that a bug, what's next? Customers won't do any real work themselves - we'll have to to. We will! We really will if we let people extort us for such "support"." :) (If you work in IT, you'll have to laugh at that, cause in addition to using products that may have bugs, you also have to support users that swear problems exist where you can prove they don't.) And you know all of your arguments are completely invalid, whether they're true or not. Software has bugs, period. Always has, and always will - I think there's a mathematical proof somewhere to that effect. There are just too many moving parts made by too many people - and people make mistakes. It seems highly likely to me that your installation is somehow broken, which has caused some of your scripts to break. Break so badly that a well-behaved install can't recover them. Talk to me now on

On topic of broken installation, as i said before, now i started encountering this bug on every kinds of installations. You mean they all just became corrupt on day X? On topic of bugs: Well, i understand the "bug will always" be discussion wont get anywhere beside trolling so there is no reason to go into it further anyway. I'd like to state something else. No, selling poisonous food and then selling cure for double profit is NOT the ONLY way for IT people to work! This is just the excuse, excuse which is good for IT persons who can get paid for doing crappy job and then get paid second time for fixing it! I can just say that the way i work in the IT, is i offer something that WORKS. Every bug that something i wrote has is to be fixed by me, coupled with apologies and 100% free of charge. Thats how it works here in Russia for me, and for that, my customers or employers are happy to pay me. Like, i wrote a database for one local businessman who wanted to have a tight grip on his managers. After i got my money for the completion of the project, i didnt take more money from him for fixing bugs that I MADE in the first place! Of course, when he wanted more features, that he paid me for. But he paid for features, and bugs - bugs were fixed for free, and asap. If i'd tell him like Microsoft tells us "you buy a black box and then pay me money for fixing anything you dont like with it, be it my bug or feature request", he wouldnt pay me money, and probably would punch me in the face for such insult (because making such an offer seriously menans you consider the person you offer to a complete idiot). Right now i made like 3-4 systems (mostly databases and reporting kind) and every systems runs bugfree. And if a bug happens, and its my fault, its mine to fix! Of course if they want to say go to next version of software and my system doenst work on it, they have to pay me to change it. If their pc gets infected with viruses, and my system doesnt work cos of that, its their problem. But if for example right now that businessman who i made the database 2 years ago calls me and tells me that my base wont let him add any more contracts into table because i made a stupid mistake like presuming there will never be over X contracts and my script bugs when they overflow, he would expect me to fix that for free because he paid me for this fix 2 years ago when i received my payment for project completion! This is included in the software price and it has nothing to do with "lifetime labour" or something. Its a lie that you cannot isolate the problem and blame the exact source, when you actually can. Yes you can. And it works here. And i must say, being on the other edge of the sword (mean, i am the one who has to spend time for nothing 2 years after receiving the money), i cannot say i think i am abused or well, that system is wrong. I think, its just right. Because in the end, with this system, i get paid for QUALITY work. Quick example, people would pay me 3000 euro instead of buying a 2000 euro product because what i make will work, and will be supported (all bugs would be fixed for free, feature requirests would be either free if theyre trivial or reasonable amount). And buying a 2000 euro ready solution is just a potentially broken piece of ____ you cant even get refund for because "Software has bugs, period. Always has, and always will - I think there's a mathematical proof somewhere to that effect. " Sorry, getting into arguments again, bad bad.

To be honest, the only conclusion I can make is that your situation is unique.... Nope, I have the exact same issue with exactly the same error with a project of mine, and the error appeared like lightning from the blue sky a few days ago. But other script tasks are fine in the same SSIS package. The SSIS package can be run and deployed it is just editing it that is not possible. Things I tried that failed: - Repair .Net 3.5 - Uninstall VSTA and then reinstall. Then repair .net 3.5 My setup: windows xp sp3 running on virtual machine (virtualbox) with visual studio team system 2008. SQL server is 10.0.2531.0 running on host OS (windows 7).

1. Well, i understand the "bug will always" be discussion wont get anywhere beside trolling so there is no reason to go into it further anyway. 2. I'd like to state something else. No, selling poisonous food and then selling cure for double profit is NOT the ONLY way for IT people to work! This is just the excuse, excuse which is good for IT persons who can get paid for doing crappy job and then get paid second time for fixing it! 3. I can just say that the way i work in the IT, is i offer something that WORKS. Every bug that something i wrote has is to be fixed by me, coupled with apologies and 100% free of charge. 4. After i got my money for the completion of the project, i didnt take more money from him for fixing bugs that I MADE in the first place! 5. If i'd tell him like Microsoft tells us "you buy a black box and then pay me money for fixing anything you dont like with it, be it my bug or feature request", 6. If their pc gets infected with viruses, and my system doesnt work cos of that, its their problem. 7. But if for example right now that businessman who i made the database 2 years ago .... he would expect me to fix that for free because he paid me for this fix 2 years ago when i received my payment for project completion! 8. i get paid for QUALITY work. Quick example, people would pay me 3000 euro instead of buying a 2000 euro product because what i make will work, and will be supported (all bugs would be fixed for free, feature requirests would be either free if theyre trivial or reasonable amount). And buying a 2000 euro ready solution is just a potentially broken piece of 9. Sorry, getting into arguments again, bad bad. My answers, others may have different opinions: 1. As indicated by Todd, open a Connect issue: https://connect.microsoft.com/SQLServer?wa=wsignin1.0 . If you do, post the link here. Thanks. 2. IT people are at different levels. The super experts really excel. It is downhill from there on. It pays to learn from super experts. It pays in dollars too, not to mention reputation and career. 3. In America you would be called a very good businessman/businesswoman. 4. As a good businessman that is how you defined your business model and it appears working well for you. However, that can only be done for trivial issues. For complex projects, client has to pay for ongoing maintenance. 5. That is how software companies work: you license (not buy) their product and you pay (usually) yearly maintenance. The important thing is to master the maintenance support process. When you call first, usually you get a support trainee... that can be really frustrating. Top-level support is reserved for top $ clients. Once I worked for a software company and I was the shielded resource for top-top clients. 5-6 support staff was my shield. Probably you don't believe this but even small $ customers wanted to get to me desperately. However, they had to go through my "shield", second tier customer support. 6. But they may not admit to the virus. They may say it is your software. In fact, another vendor who sold to them also may blame your software. So now it is still your reputation and time to resolve it. Somebody must pay for it. That is why maintenance contract a good idea. 7. Fixing small things is certainly good marketing, done in America too. However, frequently, a "small" thing fix may take a week. Somebody must pay for your time. The logical party is the customer with a maintenance contract. Demanding extra money for each fix is poor marketing. 8. So you bundled in your services with 1000 € extra fee at sell time. That is good for small fixes and you can appear like Robin Hood. What if the fix costs you 2000 €? Maybe you still can play the Robin Hood, however, in that case you pass the overhead to your other clients indirectly or charge the client in question. BOTTOM LINE: You need a long-term maintenance arrangement with your client which satisfies needs and is financially sound to both parties. 9. You can open a DISCUSSION thread for discussion. BTW - You could not find a single person/company in the Communist ex-Soviet Union which provided such a good service to clients as you do.... Capitalism can do miracles in business operations. Kalman Toth, SQL Server & Business Intelligence Training; SQL 2008 GRAND SLAM

1. Well, i understand the "bug will always" be discussion wont get anywhere beside trolling so there is no reason to go into it further anyway. 2. I'd like to state something else. No, selling poisonous food and then selling cure for double profit is NOT the ONLY way for IT people to work! This is just the excuse, excuse which is good for IT persons who can get paid for doing crappy job and then get paid second time for fixing it! 3. I can just say that the way i work in the IT, is i offer something that WORKS. Every bug that something i wrote has is to be fixed by me, coupled with apologies and 100% free of charge. 4. After i got my money for the completion of the project, i didnt take more money from him for fixing bugs that I MADE in the first place! 5. If i'd tell him like Microsoft tells us "you buy a black box and then pay me money for fixing anything you dont like with it, be it my bug or feature request", 6. If their pc gets infected with viruses, and my system doesnt work cos of that, its their problem. 7. But if for example right now that businessman who i made the database 2 years ago .... he would expect me to fix that for free because he paid me for this fix 2 years ago when i received my payment for project completion! 8. i get paid for QUALITY work. Quick example, people would pay me 3000 euro instead of buying a 2000 euro product because what i make will work, and will be supported (all bugs would be fixed for free, feature requirests would be either free if theyre trivial or reasonable amount). And buying a 2000 euro ready solution is just a potentially broken piece of 9. Sorry, getting into arguments again, bad bad. My answers, others may have different opinions: 1. As indicated by Todd, open a Connect issue: https://connect.microsoft.com/SQLServer?wa=wsignin1.0 . If you do, post the link here. Thanks. 2. IT people are at different levels. The super experts really excel. It is downhill from there on. It pays to learn from super experts. It pays in dollars too, not to mention reputation and career. 3. In America you would be called a very good businessman/businesswoman. 4. As a good businessman that is how you defined your business model and it appears working well for you. However, that can only be done for trivial issues. For complex projects, client has to pay for ongoing maintenance. 5. That is how software companies work: you license (not buy) their product and you pay (usually) yearly maintenance. The important thing is to master the maintenance support process. When you call first, usually you get a support trainee... that can be really frustrating. Top-level support is reserved for top $ clients. Once I worked for a software company and I was the shielded resource for top-top clients. 5-6 support staff was my shield. Probably you don't believe this but even small $ customers wanted to get to me desperately. However, they had to go through my "shield", second tier customer support. 6. But they may not admit to the virus. They may say it is your software. In fact, another vendor who sold to them also may blame your software. So now it is still your reputation and time to resolve it. Somebody must pay for it. That is why maintenance contract a good idea. 7. Fixing small things is certainly good marketing, done in America too. However, frequently, a "small" thing fix may take a week. Somebody must pay for your time. The logical party is the customer with a maintenance contract. Demanding extra money for each fix is poor marketing. 8. So you bundled in your services with 1000 € extra fee at sell time. That is good for small fixes and you can appear like Robin Hood. What if the fix costs you 2000 €? Maybe you still can play the Robin Hood, however, in that case you pass the overhead to your other clients indirectly or charge the client in question. 9. You can open a DISCUSSION thread for discussion. BTW - You could not find a single person/company in the Communist ex-Soviet Union which provided such a good service to clients as you do.... Capitalism can do miracles in business operations. Kalman Toth, SQL Server & Business Intelligence Training; SQL 2008 GRAND SLAM