Recently, I've started having a problem with my SQL Server 2005 client running on Windows XP where right-clicking on any job and selecting Properties instead brings me to the New Job window. Also, if I select "View History", I get the history for all jobs, instead of the one I right-clicked on.
This happened to me once before, and I found that I hadn't installed a service pack for SQL 2005. Once I installed it, the problem went away, and I haven't seen it in about a year. I haven't run any updates on it since, and I'm not sure what could have caused this.
As a possibly related note, I've tried installing XP Service Pack 3 on my machine twice, and it just hung on my machine(I started running it on Friday before leaving for the weekend, and it hadn't gone more than5-10% when I got back on Monday). I'm not sure if that fact is related at all, but I thought it possible that the XP update somehow overwrote something that SQL 2005 used before hanging.
Any ideas on what could cause this? I've included the current version info that shows up in SQL 2005.
Microsoft SQL Server Management Studio - 9.00.1399.00
Microsoft Analysis Services Client Tools - 2005.090.1399.00
Microsoft Data Access Components (MDAC) - 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML - 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer - 7.0.5730.13
Microsoft .NET Framework - 2.0.50727.1433
Operating System - 5.1.2600
Update: I reinstalled SQL 2005 service pack 2 on my machine and it fixed the problem. I'll have to see if the problem was caused when I tried installing xp sp3.
I would suggest the following path:
Make sure that you have current backups for the server
Try to get a clean install of the XP service pack
Try reinstalling the client tools on the machine
If that fails, try to install (or reinstall) SP2 for SQL Server
Related
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 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 tried to install SQL Server 2005 Express SP3 x64 on Windows 8 but the installer gives me an error:
An installation package for the product Microsoft SQL server native
Client cannot be found. Try the installation again using a valid copy
of the installation package 'sqlncli_x64.msi'
How can I solve the problem?
I had the same problem. But I also had to perform additional steps. Here is what I did.
Perform the following steps (Only 64bit version of SQL Server 2005 Developer Edition tested on Windows 8 Pro 64bit)
Extract sqlncli.msi / sqlncli_x64.msi from SP3 or SP4. I did it from SP4
Install sqlncli
Start SQL Server 2005 Setup
During setup I received an error
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
Don't click cancel yet. From an installation of SQL Server 2005 SP3 or SP4 copy SQLSERVR.EXE and SQLOS.DLL files and put them in your SQL install folder.
Click RETRY
For STEP 5 above: Although I didn't try looking into SP4 / SP3 setup for SQLSERVR.EXE and SQLOS.DLL but if you don't have an existing installation of SQL Server 2005 SP3/SP4 then maybe try looking into the SP3/SP4 EXE (Compressed file). I am not sure if this may help. In any case you can create a VM and install SQL Server 2005 with SP3/Sp4 to copy the files for Windows 8
I had a different experience loading SQL Server 2005 Express on Windows 8. I was using the installer that already had SP4 applied so maybe that explains the difference. The first error I received was when Setup tried to start the SQL VSS Writer. I just told it to Ignore and it continued. I then ran into the same error Sohail had where the SQL Server service failed to start. There was no point in following the rest of Sohail's method since I already was using a SP4 version of SQLServr.exe and SQLOS.dll. Instead, I just canceled the install rebooted the machine and ran the install again. Everything ran fine the second time around.
The place I found Sohail's technique invaluable was when I needed to install SQL Server 2005 Standard on Windows Server 2012. We have a few new servers we're looking to roll out with Windows 2012 but we didn't feel the need to upgrade SQL Server since the 2005 version has all the functionality we need and the cost to license SQL 2012 on these boxes would have been a 5-figure sum.
I wound up tweaking Sohail's technique a bit by adding steps to revert the SQLServr.exe and SQLOS.dll files so that I could then apply SP4 fully. Below are all the steps I took starting from a scratch install of Windows Server 2012 Standard. I hope this helps anyone else looking to get a fully updated install of SQL Server 2005 x64 on this OS.
Use Server Manger Add roles and features wizard to satisfy all of SQL's prerequisites:
Select the Web Server (IIS) Role
Add the following additional Web Server Role Services (note that some of these will automatically pull in others, just accept and move on):
HTTP Redirection
Windows Authentication
ASP.NET 3.5 (note that you'll need to tell the wizard to look in the \Sources\SxS folder of the Windows 2012 installation media for this to install properly; just click the link to "Specify an alternate source path" before clicking Install)
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibility
Start SQL Server 2005 Install, ignoring any compatibility warnings
If SQL Server service fails to start during setup, leave dialog up and do the following:
Backup SQLServr.exe and SQLOS.dll from C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn
Replace those two files from a working copy of SQL Server 2005 that already has had SP4 applied (alternatively, extract them from the SQL Server 2005 Service Pack 4 distributable using 7-Zip, here's a helpful write-up.)
Return to setup, hit Retry and setup will now run to completion.
Stop SQL Service and restore orignal versions of SQLServr.exe and SQLOS.dll (or else SP4 doesn't think it is needed in the next step)
Install SQL Server 2005 SP4
Install SQL Server 2005 SP4 Cumulative Hotfix 5069 (Windows Update wasn't offering this for some reason so I had to download and install manually)
If you want the latest documentation, install the latest version of SQL Server 2005 Books Online.
Microsoft says the SQL Server 2005 it's not compatible with Windows 8, but I've run it without problems (only using SP3) except the installation.
After you run the install file SQLExpr.exe look for a hidden folder recently created in the C drive. Copy the contents to another folder and cancel the installer (or use WinRar to open the file and extract the contents to a temp folder)
After that, find the file sqlncli_x64.msi in the setup folder, and run it.
Now you are ready the run the setup.exe file and install SQL server 2005 without errors
I found that on Windows 8.1 with an instance of SQL 2014 already installed, if I ran the SQLEXPR.EXE and then dismissed the Windows 'warning this may be incompatible' dialogs, that the installer completed successfully.
I suspect having 2014 bits already in place probably helped.
install "SQL Express 2005 service pack 4" version "directly".
it contains sql Express 2005 inside . dont let the name fool you
runs succesfuly. from my experince
Microsoft SQL Server 2005 Express Edition Service Pack 4 on Windows Server 2012 R2
Those steps are based on previous howto from https://stackoverflow.com/users/2385/eduardo-molteni
download SQLEXPR.EXE
run SQLEXPR.EXE
copy c:\generated_installation_dir to inst.bak
quit install
run inst.bak/setuip/sqlncli_x64.msi
run SQLEXPR.EXE
enjoy!
This works with Microsoft SQL Server 2005 Express Edition Service Pack 4 http://www.microsoft.com/en-us/download/details.aspx?id=184
I was trying to install Microsoft SQL Server 2005 on my Windows 7 pc. When I tried to install it, it tells me that I have a newer version installed on my pc. So, I checked that Microsoft Sharepoint 2010 installed some sql server 2008 tools for me.
I decided to uninstall SharePoint 2010(which I wasn't using) and then tried to install MS SQL Server 2005 again. This threw me the following exception:
Error 1603 installing microsoft sql server setup support files
Searching on Google I found this article: http://support.microsoft.com/kb/916760 but it's not my case actually.
Any help will be appreciated. I really need this to continue working.
I hope this might be useful
http://vivekthangaswamy.blogspot.com/2008/05/none-of-selected-features-can-be.html
Turn on all the Windows Features for IIS - this fixed the problem for me.
This is done via Start -> Control Panel -> Programs and Features -> Turn Windows features on or off.
Has anyone tried installing SQL Server 2008 Developer on a machine that already has 2005 Developer installed?
I am unsure if I should do this, and I need to keep 2005 on this machine for the foreseeable future in order to test our application easily. Since I sometimes need to take backup files of databases and make available for other people in the company I cannot just replace 2005 with 2008 as I suspect (but do not know) that the databases aren't 100% backwards compatible.
What kind of issues would arise? Do I need to install the new version with an instance name, will that work? Can I use a different port number to distinguish them?
I found this entry on technet: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3496209&SiteID=17
It doesn't say more than just yes you can do this and I kinda suspected that this was doable anyway, but I need to know if there are anything I need to know before I start installing.
Anyone?
Yes this is possible. You will have to create a named instance not used by another version of SQL Server as per the previous answer and version 3.5 of .Net installed. Works great!!
Here the list of prerequisites:
.NET Framework 3.5 SP1
Windows Installer 4.5
Windows PowerShell 1.0
If you have Visual Studio 2008 installed you will get a validation error and you cannot install SQL server 2008 until you install Visual Studio 2008 SP1. If you don't have Visual Studio 2008 installed it should not be a problem. So if you do have Visual Studio 2008 wait till August 11th since that is the day that Visual Studio 2008 SP1 will ship
I believe that this is perfectly possible. I am currently running both SQL Server 2000 and SQL Server 2005 on my development server while I transfer applications over.
The only thing you will have to do is create a new instance which isn't already being used by SQL Server 2005.
As with anything new, there will probably be some bugs, however, it should generally "just work".
my experience is after having sql sever 2005 and 2008 on same machine SSIS 2005 does not work properly... specially with script task, data flow and sequence container
You could run just SQL 2008 as the single instance and then attach/create databases with compatability level of 2005? The problem with that is that its a theory. Im not 100% positive that if you create a database on 2008 , with a compatability level of 2005, and then detach it, that a SQL 2005 instance is capable of attaching it.
I think its a good enough chance to try though. But I agree with the previous answers, the multiple instance options will work fine.
Unfortunately, it seems SQL Server 2008 Client Tools requires Visual Studio 2008 SP1, and I'm loath to install a beta of this on my main development machine.
I'll wait until SP1 is RTM before I move on.
Edit: Yes, I do have Visual Studio 2008 on this machine, but I'd like to avoid beta installations of debugger applications. They tend to dig themselves too deep in for my taste.
I have try it with negativ result. The 2k8 installation breaks with a mysterious error-message. The installation-protocol looks fine, but it will not work. After this the 2k5 installation was buggy too.
The 2k8 installation was half-ready, so it´s already in controlpane / software, but uninstallation is not possible.
So my result - don´t do it on a productive server / workstation. If you need both versions, use a virtual machine instead.