I created a SSIS package using SQL Server data tools 2015 a week back.
And today i opened the package and it just shows the blank screen.
I read about this issue here and it seems that was the defect in earlier versions and it is fixed.
Did anyone face this issue in data tools 2015? How can i fix it and save my package?
1) While the package is opened with the white page, rename it in the solution.
2) Save the package and close.
3) Rename the package back original name (while package is closed). This rename will open the package and hopefully set it back so that you can edit it.
This has worked for me, hopefully it will work for others.
All white on open? Just happens from time to time, the stuff is there just close and reopen Visual Studio always makes it come back for me.
But if not you could always find the dtsx file under it all in your users folder:
C:\Users\<yourusernamehere>\Source\Workspaces\<Projectworkspace>
copy it and then pull it back in by right clicking the SSIS Packages folder in Solution Explorer and add existing package see if you can see it then.
Tim's answer above helped but didnt work for me. Instead this worked in Visual Studio 2015:
Close the solution
Move the .dtsx file that will not open to another folder (ex: C:\Temp)
Rename the .dtsx file to the name you want
Open the solution - you should get a message that the package is missing.
In Solution Explorer, right-click on "SSIS Packages" and select "Add existing Package"
Package Location should be "File system". Click the "..." button and select the moved and renamed .dtsx file. click OK
The .dtsx file should now be added in the solution correctly named - and open for editing.
The rename and reopen trick worked for me. I also tried another way. I closed Visual Studio and then located the .suo file under the .vs folder. I deleted that and then reopened and the file reloaded.
I hope that isn't too dangerous an approach; it stops git changes being made when the rename is performed
I have tried the trick to rename the package. It works as long as I keep a new name, but when I rename the package back to its old name, the problem returns. Importing a new copy of the .dtsx file into the same (broken) project did not fix the problem. [Referring to answer by #Joe]
Here is the only solution that always works for me:
Create a new Visual Studio (or SSDT) solution.
At the new project dialogue, choose "Integration Services Import Project Wizard"
A wizard starts up [hit next if at optional "Wizard Introduction"]
At "Select Source" page choose "Integration Services Catalog"
Browse to server and the project deployment you need to fix
This works, but if your deployed SSIS package(s) was not up to date you need to continue with these two actions:
Delete the package(s) in the new (fixed) solution that are old.
Import the newer package(s) via "Add Existing Package" from the problematic solution
I suspect this happens due to a problem in the .database or .dtproj file.
I have just encountered this; solution opens but all blank and no sub folders or files in the Solution Explorer. Tried the above suggestions, but no luck. Right clicked on the solution name and selected 'Reload Project' and all good.
Hope this helps someone.
In the Solution Explorer right click on the .dtsx package file and then click on View Designer.
Related
I'm running into a small but weird annoyance that seems to be happening to other people, too (for example, check out the revision history of SEDE). I have a SQL Server 2008 database project in Visual Studio 2010 that works properly. When I go to commit/checkin to source control, I'm told that my DB project's .dbmdl file has changed, even when I've made no changes to the project!
I'm not sure if the changes are triggered by building my solution (which also includes an ASP.NET MVC application and a unit test project) or by simply opening the DB project, but this is getting kind of annoying and is creating clutter in source control.
Is it possible to stop these changes from occurring, or get rid of the .dbmdl file whatsoever?
If you delete the .dbml file, it is rebuilt without errors or warnings, so I think it's just a cache file for references, intellisense, etc. I'm going to exclude it from source control.
I believe Visual Studio serializes the dbmdl file every time the project is opened. The only possible work around would be to keep the project open.
See related question here. The .dbmdl file is unique per user (and some kind of cache, as said above) and so the right solution is indeed to exclude it from source control.
I am striving to get the source of my issue but no luck. I did check almost all suggestions to fix this problem when publishing project (publishing using right-click, checked DevExpress is not installed).
-Regarding DevExpress the application have some of it's assemblies.
- Cannot publish because a project failed
- Could not find file 'obj\x86\Debug\MyApplication.exe'
I did send publishing diagnostic to the Output and get this :
Task "GenerateApplicationManifest" (TaskId:158)
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2580,9): error MSB3113: Could not find file 'obj\x86\Debug\MyApplication.exe'.
Done executing task "GenerateApplicationManifest" -- FAILED. (TaskId:158)
Done building target "GenerateApplicationManifest" in project "MyApplication.csproj" -- FAILED.: (TargetId:194)
Can someone list all things I have to check to get this issue fixed ?
I just ran into the problem today. In my particular case, it was caused by this Microsoft Windows Update.
I uninstalled that update and publish began working as it always had. This is only a temporary work around and means you should probably regenerate your keys/certificates.
Right click on you Project
Click Publish
Go to Settings Tab
Click File Publish Options
Check All the options in the tab (As seen in attached image)
I had a working SSIS package last week. I came back into the office this morning, opened up the package and tried to open up one of the Data Flow tasks. Double clicking did nothing. I closed the project and reopened it and received an error message that there was a "Catastrophic Error" and that the layout could not be displayed. The Control Flow diagram now only showed my two Sequence Containers.
I made a copy of the dtsx file then went into it manually with a text editor and found that some of the XML was duplicated. I removed the "extra" copy and reopened my package. The empty Sequence Containers are now gone, but I still can't see any of my components. I looked at the Package Explorer and everything is still there, but it's just not displaying in the designer. I was even able to run the package successfully.
Is there any way to rebuild the package so that I can see everything in the designer? Any other suggestions?
Thanks!
I'm not sure why BIDS has decided the layout is junk but you can get around the issue by removing the layout and forcing BIDS to regenerate that information. The graphical layout stuff is a cool idea for conceptualizing how a package is organized but the implementation of storing that information, serialized XML inside XML, is pants.
There are various articles available about how to remove the XML, but this is a more recent example of how to use do this. http://joshrobi.blogspot.com/2012/04/editing-existing-ssis-package-via-ezapi.html
As always, ensure you have a good copy of the package before editing the XML directly.
Do you have a backup of your package - try and restore that to another location first to make sure that is not corrupted.
How are you accessing the package, are you connecting remotely to a server hosting SSIS, or are you using tools located locally on the server?
I've encountered issues when trying to access packages across networks before.
Also, as a word of warning it's not good practice to edit package contents before carrying out further diagnosis!
I've got files in TFS that are not showing in the solution explorer of VS 2010. Another developer committed the files to TFS. I can see the files in TFS, and they are even being copied to my local directory, but they aren't appearing in the solution explorer.
What am I doing wrong?
Also, when my coworker committed his changes, it is marked as changeset 99. When I look at the hierarchy of the main branch (where he committed the changes to), it says the latest version is changeset 9 (which is the changeset that created that branch). Why does the hierarchy view say its latest changeset is 9 when clearly the latest changeset is 99? Am I using the tools incorrectly?
Thanks
This is a 'known' bug in VS/TFS. If you checkout a file from the 'Solution Items', VS goes and removes the file from the project.
To show files on the solution explorer you have to add files to the TFS and you have to update your project files also. You can try Show all files button on solution explorer.
For changeset number issue - pres Ctrl+G on the Source Control Explorer. Enter number 99 or click Find for more search options. Check changeset details or track changeset. Maybe you are checking wrong project collection or it is a bug.
I have a database project (.dbp) open in Visual Studio 2008 as part of a solution. I've added a new sql script to the project. When I try to save the database project so that I can check it in, VS shows me a dialog:
Some Unicode characters in this file could not be saved. To save all the information in this file, use 'Save As'; and select a Unicode encoding.
If I try to use "Save As.." I get exactly the same dialog.
I'm not very familiar with .dbp files, but I have opened the file in Notepad2 and re-encoded it. VS will reload the project but when I try check in the changes, VS says I need to save the file, and if I do, I once again get the above mentioned dialog.
Interestingly, I have no file association with the dbp file, but VS somehow mysteriously knows what to do with it in the context of a solution. Yet you can't open the dbp with VS on it's own. That broke my brain a little bit.
So I'm at a loss and going around in circles. If anybody can help, I'd appreciate it.
Not sure I know why this might have happened but it might be worth getting the previous version of the dbp file from source control and diffing the 2 to see if you can work out what's changed.
This is what I had to do to get around the problem, as there doesn't seem to be a fix that I can create, or find:
Edit the dbp file in an alternative text editor. Add a text entry for the entity that you want to add to the project. For example, to add a script called "Create users table.sql" to the "Changes" folder:
# Microsoft Developer Studio Project File - Database Project
Begin DataProject = "Database Project"
MSDTVersion = "80"
SccProjectName = "SAK"
SccLocalPath = "SAK"
SccAuxPath = "SAK"
SccProvider = "SAK"
Begin Folder = "Changes"
Script = "Create users table.sql"
End
End
Save the .dbp file and reload the project in Visual Studio.