I de-installed SQL server 2005 express some time ago when I installed SQL server 2008 express.
Doing that install required windows installer 4.5.
Now I discover a reason to have SQL server 2005 express again.
(to reconnect to the outlook Business Contact Manager which requres it to connect to the default MSSQL\MSSMLBIZ database)
However, when I install any version of SQL server 2005, it fails for all the important things, like the database engine, with the message that I should upgrade my windows installer to a newer version.
I'm interpreting this as the SQL 2005 installer is experiencing failure and is presuming it is because the installer version is incorrect, and presuming the version is too previous.
But I suspect the version is too subsequent.
Any way out of this?
The error messages are produced by MSI-based installers are notoriously misleading (most installers silently swallow a lot of error conditions and present one single generic error message.) The best thing you could do is sift through the log files created by the SQL Server 2005 installer (IIRC, they're dumped into the %TMP% directory.) That will certainly provide more information.
You could try to uninstall the KB942288 package (Add/Remove Programs, make sure the Show updates checkbox is checked, and locate the corresponding entry.) Here's the corresponding Microsoft KB article as well. No guarantees as to what this will do to your system though, especially since you've certainly performed a lot of install actions since you installed 4.5.
You could also try one or more of the generic MSI debugging techniques described in KB 555175.
Related
I have a server that I am working on that is using Windows 2008 SP2 Enterprise and I have found that the installed version of Robocopy is missing the MT (multithread) switch.
Since I'm working with enterprise hardware, having multiple threads can really help my performance so I'd prefer not to have to remove the switch from the copy operation that I am attempting.
What I don't understand is why the installed version is missing this switch since this is a 2008 windows instance. Was the MT switch introduced in 2008R2?
Is there any way I can safely update this version of robocopy (such as copying the executable from one of my other environments)?
To provide just a little background for contextual purposes this command is being issued as part of an automated backup process developed in SSIS. This process executes normally in other environments, so I'm trying to establish a means of upgrading all the older versions with a more recent version of robocopy to maintain functionality. Otherwise I will have to contextually disable the inclusion of the switch which is a pain.
According to the documentation on Technet, the /MT parameter applies to Server 2008 R2 but not Server 2008. I'm not sure if this is due to just the version of the robocopy executable or some other restriction.
What is the File Version of your robocopy.exe, as shown in the file properties?
You might try to pull the newest version of Robocopy (6.1.7601) out of KB2639043 and see if that works for you. Though, information I found on this thread suggests that newer versions of Robocopy don't work at all on Server 2008.
When I setup SQL Server 2005 this problem appear
Minimum Hardware Requirement (Warning)
Messages Minimum Hardware Requirement
The current system does not meet the
minimum hardware requirements for this
SQL Server release. For detailed
hardware and software requirements,
see the readme file or SQL Server
Books Online.
and I continued setup but I could not found SQL Server Management Studio tools in start menu
As mentioned, you have missed installing SSMS. You can go through the install process again (you don't need to uninstall, just run it again), except this time make sure you put a check mark next to the Management tools when you do feature selections. I'd tell you exactly where it is but i only have a SQL2008 install on hand at the moment.
Your SQL is not completely installed, I suggest you to update all feature in your OS.
may be you installed Express edition?
also Management Studio is free, you can download it from link text
I'm using the Bootstrapper Manifest Generator to make bootstrapper packages for the following redistrbutables:
Microsoft SQL Server 2008 Management Objects
Microsoft Core XML Services (MSXML) 6.0
Microsoft SQL Server 2008 Native Client
Microsoft SQL Server System CLR Types
I have a MsiProductCheck install conditions to determine if the MSI was installed, however as soon as a newer version is released, the check is back to saying that the prerequisite is needed.
I was wondering what the correct way was to determine if these components were installed.
I have the same problem with SQL 2005 Native Client, but I got the SQL 2005 Management Object correct. However I've lost the packages I created and need to recreate them, but now for SQL 2008.
MS should create these packages for us, or at least provide a community for sharing bootstrapper packages. I guess there are thousands of developers trying to figure out how to write the same bootstrapper packages, and all are reinventing the wheel with more or less luck.
Basic Question -
I have installed SQL Server Express 2008 with integrated SP1. This is the database engine alone.
I realise now that I also need the express studio in order to perform a few tasks. I have installed it, however I know that it was the original installer from before SP1 was released.
I have tried it and it appears to work fine but should I install SP1 / could something unforeseen happen in the future?
Some background! -
I wrote out the question and just realised that people probably don't care, so I just summed it up above!
After reading many different sites and guides, the install order for Visual Studio 2008 really confused me.
I really wanted to install SQL Server Express 2008 with advanced services, however on my other machine I had so many problems with it not being detected with Visual Studio, I just wanted an easy life!
I found the download from Microsoft that had SQL Server Express 2008 with SP1 integrated, however it was only the basic engine without any addons. (At the end of the day, as much as I wouldn't mind reporting services, I doubt I will need to use it any time soon).
I installed this, and after applying the hotfix (for x64 sql) my Visual studio can detect and use it no problem.
Now, I want to use Management Studio Express to write a few SQL scripts. The installer is obviously the original one. It seems to work fine, but I cannot find out any information - do I need to install SP1 for it?
Just install it, if its found something it can update - it will, if not... it won't....
Thanks to the wonder of Windows Installer (and I don't mean "I wonder why it's doing that?"--I mean like "This is wonderful!") it is unlikely that you have caused any big issues by running the older version afterwards.
So, yeah, you can probably just install the SQL 2008 Express Management Tools with no worries. If you want to be sure, afterwards just run the SP1 installer and it will make sure everything's up-to-date.
I always make sure to apply patches to client tools as well as server services. There is no reason to take the chance that your client tools have fallen behind in servicing.
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.