Visual Studio Build Fails on Configuring SQL Server 2005 - visual-studio

I'm trying to build a setup project in Visual Studio 2005, and it is failing every time, after opening a dialog box labeled Microsoft SQL Server 2005 Tools and configuring for a few minutes. The Microsoft SQL Server 2005 Tools dialog then launches a dialog with the text Failure creating local group SQLServer2005NotificationServices$COMPUTER_NAME. I suspect this failure is because I'm not currently local admin on my machine (a situation I hope will be rectified rapidly), but I don't see why I need to configure MS SQL 2005, as my project does not use it, and in fact has no DB connectivity. How can I get past this step to a successful build?
Related:
Visual studio configures SQL 2008 on every build
Visual Studio Setup and Deployment build fails with no errors
Update: Got my admin back, but this is still taking up time to run, and I'd still like to be rid of it.

I found something about it on Microsoft Connect. Seems like it's a bug. In the reply they linked to a knowledge base article with some workarounds.

Related

SQL Server Integration Services throws "Error Starting Debugging" - Failed to start project

Several of my colleagues and I are experiencing a problem: we are trying to use the Visual Studio Business Intelligence Designer (BIDS) to create and debug SQL Server Integration Services packages. In nearly all cases, we encounter the error below.
We all have SQL Server 2008R2 Management Studio installed, which includes the Visual Studio 2008 BIDS IDE. We all have Visual Studio 2010 installed as our primary development IDE / environment, and connect to a Team Foundation Server source control.
We do not have a source control plugin selected for the BIDS IDE.
We are all running Windows 7 with all the latest service packs and patches (as far as we know- these are customer-managed machines and the patch management details are opaque to us).
The one thing that is different - maybe - between the one system where the SSIS debugger DOES work and the several where it DOESN'T work is that- MAYBE- the operable system has not been used to edit SQL Server Reporting Service RDL files, where the rest have been.
In the Project Properties dialog, under the Debugging options:
We have tried setting the "runInOptimizedMode" option to False - no joy.
We have tried setting the "Run64BitRuntime" option to False- no joy.
We have tried setting the "InteractiveMode" option to "False" - no joy.
Here is the error text as reported by the BIDS interface.
Thanks for any insights you have!
TITLE: Microsoft Visual Studio
Failed to start project
ADDITIONAL INFORMATION:
Error starting debugging. (Microsoft.DataTransformationServices.VsIntegration)
Unable to start program 'C:\Users\\Documents\Visual Studio 2008\projects\DebugTest\DebugTest\Package.dtsx'.
Operation not supported. Unknown error: 0x80040038. (Microsoft Visual Studio Debugger)
BUTTONS:
OK
Run Visual Studio as Administrator that works for me

Visual Studio 2005 Reports and Windows 7

We have recently upgraded to windows 7 and have noticed that there are compatibility issues with my previous version of MS visual Studio 2005.
From taking a look around the web I believe that this issue is due to SP1 for Windows 7. My organisation will not get rid of SP1 just for one or two developers so I need to figure out a work around.
This is the issue...
I have an old MS visual studio website that has a report located on the home. This report was created in MS VS 2005.
Other versions of Visual Studio in have are 2010 and 2012. I have tried to convert the 2005 report into 2010 and this does state that it has been converted but I still cant open or do anything with the report. My 2005 web site is too large to convert or move into 2010 and we can still maintain this 2005 site by opening this up in 2010. It just seems to be a problem with the 2005 report.
I'm running out of options to make a simple change to a report. Anyone else got any ideas? I have even tried to create this report in 2010 and then add this to my 2005 site but this doesn't work.
Regards
Betty.
You say a report and then say that it is a whole site? Why not run a second site in tandom? Make a whole new site and name it differently like
http:// (servername)/Reports2012
Then put reports there. You cannot open a converted report in a site that is for a prior version, you can view it in Microsoft Business Intelligence Studio, BIDS, which is an add on to Visual Studio. If you can upgrade but cannot view it there, there is something wrong with the language file potentially. I would then make a copy of it in the old 2005 BIDS, then take that copy and see if you can upgrade that and if it will work. If that STILL does not work you could make a test report in BIDS 2010(SQL 2012 works on VS 2010, yes weird but true) to assure you can create reports there. Many times people try to open SQL Server 2012 Reports on VS 2012 and it won't work. You need 2010 add on you can find it under All Programs>MS SQL Server 2012>SQL Server Data Tools(They made the naming very confusing as it opens up and display BIDS, but calls itself 'Data Tools' under the programs). Every other version of SSRS lines up with that year of SQL Server to that year of VS. Not 2012.
If the report upgrade still does not work, yet you can create a run a new report fine; I would suggest potentially opening up the file dircectly. Your projects in a Reports solution generally have a file '(something).rdl' that RDL is the actual file and is just XML markup of the language. This is a last resort as you are essentially trying to do manually what the upgrade is failing to do in the xml. You merely copy a working report, and then paste the parts of the old report into their correct sections. Ensure the XML is valid as well.
If you cannot manage that to work you will need to recreate the report from scratch.

SQL Server Compact 4.0 does not work in VS 2010 SP1

I've installed SQL Server compact 4.0 local database and I've added a database. However, if I try to open my database, an unknown errors occurs.
I tried to restart my VS 2010 after install the SQL Server, but it does not help and I cannot open my database.
How to resolve it?
Have a look at the following blog
In this blog you will see that you need to download an additional tool to make it work with visual studio 2010. The link to this tool is present in the same blog (search for the text below) or you may download it using the Web Platform Installer.
Visual Studio 2010 SP1 Tools for SQL Server Compact 4.0
I did not pay attention on a error message: "event log file full".
I just cleaned eventviewer in Windows and all became okay:).
I spied this topic:
I just emptied the event log and tried again:
Windows-R ("Run")
eventvwr
For each event log (in the left hand pane) right-click and select "Clear all events" (backing up the existing log if you care)

TFS 2012 + Visual studio 2012: some settings options return "The user name or password is incorrect"

I've upgraded our TFS 2010 to TFS 2012 without any issues. I can connect to the source control, checkin, everything I need to Work.
But if I go to the settings page for the team project I'm connected to, the following options work as expected:
Team project: Source Control
Team project: Portal settings
Team Project Collection: Source Control
Team Project Collection: Process Template Manager
But the rest of the options on the settings page just gives me this error
I've tried looking at the requests Visual Studio makes to the TFS server using Fiddler, and with the ones that don't work, no requests are actually being made to the server. So it seems like the server is never being contacted for those specific options.
I've tested this on two independent installations of Visual studio 2012, runnning on Windows 8.
EDIT
I just installed VS2010 SP1 on one of the machines, and I can just fine access all of the following settings options: Security, Group Membership, Areas and Iterations, Portal Settings and Source Control.
Looks like a VS2012 issue of some sort.
We resolved our issue with this by running VS 2012 with our domain credentials. We use VMs for development, so we do not directly login into the domain. To run VS, we use the following (as a batch file):
runas /netonly /user: username "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe"
where username is your domain credential.
It sounds like the code is still using some values that are cached on the client after the upgrade. How long ago was it that you upgraded the server?
To test whether that is it, rename your cache folder (with VS 2012 closed) and launch VS 2012 again so it recreates the cache from scratch.
C:\Users\\AppData\Local\Microsoft\Team Foundation\4.0

SSIS Script Editor throws an exception

I have SQL Server 2012, SSIS, SSDT and Visual Studio 2010. I can create a new SSIS package and add a Script Task, but if I attempt to open the Script Editor for that Script Task I get the following error:
TITLE: Microsoft Visual Studio
------------------------------
Cannot show Visual Studio 2010 Tools for Applications editor.
------------------------------
ADDITIONAL INFORMATION:
Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (mscorlib)
------------------------------
BUTTONS:
OK
------------------------------
From my own investigation into this error, I found that Visual Studio Tools for Applications appears to be a part of MS Office 2007 and higher. This seemed like an odd dependency for to have, but I installed MS Office 2010 just for grins. It didn't change anything. What else should I try?
You will also get this error, if you are trying to debug a script task in VS 2010 and Run64BitRuntime is set to true. In order to debug, set it to false.
I was getting this error and nothing I came across corrected the problem until I logged off as my normal user and logged in as my local admin user. Once I logged in as an admin I could edit the script in my package. Once I logged back in as my regular user the edit script button worked for it too.
I assume it needed to register the assembly on the first launch and couldn't with my regular domain user.
I also got this same error when trying to open the Script Editor, but for a different reason. Not sure how it happened, but I had 3 copies of VSTA (different versions) installed. Once I removed all of them and re-installed SQL Server 2012, problem solved. Hope that helps.
For me the solution was:
close bids (I'm on 2008r2)
reopen
edit the script (it allowed me to edit it once after restarting bids)
delete all breakpoints
make a trivial change, such as adding a blank line
save
That solved it for me.
This worked for me without doing any kind uninstall.
My environment:
Microsoft Visual Studio 9.0 (2008)
Solution:
Go to cd "C:\program files (x86)\microsoft visual studio 9.0\common7\ide\"
Execute command vsta.exe /setup /hostid SSIS_ScriptTask. This will open VSTA with blank project. Let it open and then close it.
Execute command vsta.exe /setup /hostid SSIS_ScriptComponent. This will open VSTA with blank project. Let it open and then close it.
Open your solution/packages that contains the script task.
Click Edit button in Script task and it should open now. Just in case if it dont, I would suggest to keep the blank vsta of step 2 & 3 open and then click the Edit button in script task.
Took almost two hours and thankfully it worked for me. I did not have admin right to perform all that nasty uninstall and registry edit solutions.
Hope it helps someone!!!
Reference : http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/vsta-setup-and-configuration-troubles-for-ssis-2008-and-r2-installations.aspx
Cannot show Visual Studio 2010 Tools for Applications editor.
Just follow the below solution:
Go to SQL Server Setup folder.
Inside that folder "redist".
Under that one more folder "VSTA".
Under VSTA folder "X86" and "X64"
Install the VSTA_RT30.
It works fine.
I figured out my problem this morning. When I uninstalled SQL Server 2012 (and the remnants of 2008 left behind when I upgraded last month) I also uninstalled 3 packages that were actually part of Visual Studio 2010. Had I not done this, a reinstallation of SQL Server 2012 would probably have done the trick, but instead I found new errors. When I reinstalled these 3 packages from the Visual Studio 2010 distribution media, everything started working.
The 3 packages in question were:
Microsoft SQL Server 2008 R2 Data-tier Application Project
Microsoft SQL Server 2008 R2 Data-tier Application Framework
Microsoft SQL Server 2008 R2 Transact-SQL Language Service

Resources