When i tried to run SSMS 2012 as administrator it gives the error "application can not start". I am using windows 8 64 bit and sql server 2012.
Actually yesterday i tried to install ssms 2005 side by side installation but i stopped the installation in the middle as it needed a feature to complete installation so i stopped it. Now i want to access SSMS 2012 as administrator as i have to access integration server which prompt me to access it as administrator which lead me to run SSMS 2012 as administrator.
Any help to resolve this problem will be appreciated.
This is usually due to corrupt registries or some bad uninstall that removed files it shouldn't have. It's existed for years over multiple versions of VS and its shell. SSMS is dependent on the VS framework so it's among the potential victims, also spanning multiple versions.
This blog discusses some of the details of the problem and the comments section has some great feedback and possible solutions. The link should bring you directly to Oyvind Gellein's post whose solution worked for many. You can browse the rest of the page if you want to learn more.
http://blogs.msdn.com/b/visualstudio/archive/2009/10/29/how-to-fix-the-application-cannot-start-error.aspx#10061076
You can also check out this other page for another potential solution
https://mycodepad.wordpress.com/2013/12/07/visual-studio-2012-4-run-as-administrator-the-application-cannot-start-error/
Finally it is resolved by uninstalling all the SQl server components and VS frameworks. Then again reinstalled the sql server with SSMS.
Related
I have seen other posts about this topic where some of the suggestions lead people to check the ProtectionLevel to DontSaveSensitive. I have made sure that is set to DontSaveSenistive, as well as I have checked permissions and made sure where the files/dtsx files are getting called from have ample permissions set for the service account which owns the SQL Agent.
The odd thing is this process was working fine until i went into one of the previous dtsx files and had to update a datatype precision to go from a limit of 1 character to 30 characters. That was literally the only change made to the process, but now I am getting this error. I have gotten this error before, which is when I was set on the path to checking protection level and permissions/ownership. For some reason it went away and began working when i made those changes. None of that stuff (permissions/ownership) is incorrect this time around yet I am getting that same error.
Another weird thing about the process is that it is only the last step which is failing (the FTP step.) When I try to go in and execute the psftp.exe and put in the command which is being passed normally through SSIS execute process task step, the psftp.exe is telling me that the port number is incorrect..yet when I test connection on the connection manager inside VS with the exact same port, it says connection successful.
This error is vague and confusing!
I would love some guidance on some more things to try.
thank you !
SSIS tooling and version
SQL Server 2008 and 2008 R2 can only be edited using Visual Studio 2008 which has the Business Intelligence Design Studio templates installed. Those can only be acquired by having the physical SQL Server iso handy. Developer edition will work, but you need some form of licensed media to get BIDS working.
Visual Studio 2013 is going to attempt to upgrade 2008/R2 to the internals for a SQL Server 2012 installation. There is no going backwards/downgrading once this is done.
Any tooling (dtexec, dtutil, etc) you use must be from the same version otherwise, the first thing the binaries do is update the package to match that version. For execution (dtexec), each time you run a package, there is a delay as the original is upgraded in memory to match and then execution begins (assuming all goes well). It sounds like it's not based on
The package failed to load due to error 0xC0010014...
For deployment (dtutil), you only pay the price of upgrading once and then it's upgraded forever. Which probably isn't what you wanted. Be aware that tools like Visual Studio and SSMS "know" which version of tooling they are associated with so deploying from SSMS 2016 can result in the binaries for SQL Server 2016 SSIS upgrading your 2008 package to 2016 format and then attempting to deploy the now upgraded bits to your 2008 box. It's all very frustrating and not intuitive.
From your comment "In the 2008 version, the play button is greyed out..." That indicates you have opened a File in Visual Studio that is an SSIS package. Visual Studio will open it and paint all the icons on there but it can't actually run a package unless you have an Integration Services project open (and have the BI templates installed).
Assuming you have source control, you can rollback the change that broke everything and try to edit the package properly.
Execute process task
You have an Execute Process Task that is invoking psftp.exe and it's generating a 1 versus a 0. Is that bad? Based on previous workings with SFTP clients, they're rather picky so running it as me on production would fail since I didn't have whatever bits associated to my domain account but the service account had all the right things in their profile and it would run just fine - same machine, same package, just different user.
I'm trying to install SQL Server 2005 on my Win10 x64.
The problem is I can't even select the Database Services and Reporting services I need cause checkbox is disabled.
I had a bit research on this issue but everyone else seems to have problems after the installation began, whereas, I can't even start the progress.
I tried Run program made for previous versions of windows and extract then install sqlncli.msi from SP4 according to this.
Neither of them enable the checkboxes and I'm running out of ideas.
Should I install sp4 without install SQL Server first? Any suggestion would be appreciated.
I had the Visual Studio subscriptions and turns out you can still download the original version of SQL Server 2005 by downloads search(autocomplete won't show it but the search result will).
And the checkboxes are enabled in this version.
If you face problem during the installation, this works for me.
I tried to install MS SQL server, yesterday on my Windows 7 Home Premium 64 bit OS machine, following the instructions provided in a PDF by a company that has done it before.
Everything seemed to say it installed ok. However it didn't seem to install SQL Server Management Studio which is used for a lot of the exercises I am required to do and quite useful in general.
Has this happened to anybody else. Has anyone got any advice for what I can do to fix this.
I did notice that my machine seems to have MS SQL Server 2008 for some reason, I think it must have already been there and is conflicting, perhaps I should uninstall it. What do you think?
I hope you's can help.
Thanks
KR
Sharpie
I'm guessing you downloaded and installed only the db, and not the one with "Tools". The Tools is the one that includes SSMS. No worries you can go here https://www.microsoft.com/en-us/download/details.aspx?id=29062 and download the Tools separately and install it. Expanded the "Details" of the page and this will let you know about the different files you can download.
I have a student who installed SQL Server 2014 with tools, but the Management Studio part did not install. There is no SSMMS.EXE on the machine.
So I tried to reinstall it, and the Management Studio tools come up checked but grayed out, so the SQL Installer will not let me make any changes.
So I tried to uninstall SSMS from the control panel-->uninstall programs. However, it was not there.
So I uninstalled all SQL Server programs, then I killed all running instances, then I deleted all the MSSQLServer files under both program files and program files (x64). Then I updated Visual Studio 2010. Then I tried to reinstall SQL Server.
Again, the tools appeared, but they were checked and grayed out.
Soooo. SQL server thinks the SSMS tools are installed and thus will not let me reinstall them. However, they are not installed, so I cannot remove them.
Any idea how to convince SQL server that the tools are in fact absent?
Caution incomplete answer but several more things to try:
1) Could you provide the link to the download you're using - potentially SQL Server management studio (SSMS) is not included so thus can't be installed? From reading the FAQ's this looks to be the case (http://msdn.microsoft.com/en-us/data/hh322942)
Try this link for installing http://www.microsoft.com/en-us/download/details.aspx?id=29062
2) Another thread covers a potentially related instance where express was also installed and caused a block to install SSMS.
(Can't install SQL Server 2008 R2 management tool (complete))
3) A long shot would be if anything is left over in the registry which is causing the block. See if there is still and entry in [HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server] and if so rename to "_bkp"
The last two suggests are long shots but you could try:
4) Try repairing the installation: http://msdn.microsoft.com/en-us/library/cc646006.aspx
5) Try installing as logged in as another user.
I have been running SQL Server 2005 Express Management Studio ("SSMSE"), and I now have a need to install the full version of Management Studio ("SSMS"). This is a known hassle, but I've not found a comprehensive way to carry it out.
At first, I uninstalled SSMSE, and then ran SqlRun_Tools.msi to install the toolset. I got this error message:
A component that you have specified in the ADD_LOCAL property is already
installed. To upgrade the existing component, refer to the template.ini
and set the UPGRADE property to the name of the component.
I had no idea what template.ini was. So I looked around, and decided to uninstall the rest of the minimal installation of SQL Server 2005 Express on my computer by following Microsoft's advice in KB 909967, "How to uninstall an instance of SQL Server 2005 manually." That bit was very successful.
But when I attempted to run SqlRun_Tools.msi again, I faced this mess when the installer was "Preparing Installation Wizard":
The setup has encountered an unexpected error in datastore. The action
is SetDialogs. The error is : Source File Name:
...\datastorecachexmlschema.cpp
**** Compiler Timestamp: Fri Jul 29 01:13:50 2005
**** Function Name: DataStoreCacheXMLSchema::initScopeRecord*****Sour...
(but replace the asterisks with box chars, which were probably CR-LF's in the original message)
This is very frustrating. Does anybody have any advice for installing the full version of SSMS over top of SSMSE? Any help you can provide would be greatly appreciated!
I have also installed SQL Management Studio before just using the SqlRun_Tools.msi package without any problems but I think if you have previously had any other SQL Server 2005 components installed then you will need to install the Setup Support Files first as this is probably what sets up the component installation sequence. This can be done either by installing from the SQL Server installation media or by running the sqlsupport.msi file as described in the Microsoft KB article.
I resolve this problem
Steps
Go to Add\remove program
unstall SQL server browser
Install support files from CD
Install SQL_Tools.MSI
Well, I roughly found out what the problem was, based on a somewhat cryptic resolution mentioned across a few different forums. This solution suggested that I needed to install Setup Support Files. Maybe it was reinstall, since I removed something with the same name when uninstalling SQL2K5 Express. I'm not sure if they were the same files, between the full version and the Express Edition.
I had tried reinstalling SQLXML4, the Native Client, and MSXML6 just to see if I could get beyond the error involving datastorecachexmlschema.cpp, and each time, I got the same error again. But I tried the technique mentioned in the above link, and it worked perfectly.
Basically, you insert the CD and run just the first part of the installation process, which installs the installation tools, including Setup Support Files. Then you cancel the rest of the installation process, and run SqlRun_Tools.msi instead.
I got great results when upgrading 2008 express to 2008 developer by (running setup) first going to Maintenance->Upgrade Edition, and then (since Management Tools etc was still "express" and I mainly needed the Sql Profiler) I also did a complete "new" installation (Installation->"New installation or add features.."), selecting the existing instance and then selecting all features.
No uninstall or command line necessary.
Behaved the same afterwards, just with new features.