We're trying to update our WiX installer to install SQL Server 2008 R2. Regular 2008 seemed to install fine on most machines, but the R2 install seems to fail to install SQLSysClrTypes - so we hit an error with a missing dll called SQLServerSpatial.dll.
Is there a way to get the SQL installer to correctly install this? I have found some discussions of this issue online but no solutions, except for manually installing SQLSysClrTypes.msi after SQL Server.
We want the install to be silent and need the minimum of user interaction.
We're using WiX 3.5 & VS2010.
Edit
Further reading and thinking leads me to understand that SQL 2008 SP1 didn't install SQLServerSpatial.dll either, and it is changes to our code which have made this a requirement now. So my question has become simplier:
Can I configure the SqlServer install to include/install SqlServerSpatial?
or
Can I use WiX to install SQLSysClrTypes.msi (I would need the package.xml and product.xml)? Has anyone done this?
While I am unsure about the changes to SQL Server and why SqlServerSpatial.dll is missing, I can answer with regards to installing prerequisites using a bootstrapper.
Can I use WiX to install SQLSysClrTypes.msi (I would need the package.xml and product.xml)? Has anyone done this?
It sounds like you are using the visual studio bootstrapper. You can use the bootstrapper manifest generator tool to create the bootstrapper manifest (package.xml and product.xml) so that you can create a bootstrapper like you would for other prereqs (for example, the .NET framework).
Of course, if you are open to upgrading to WiX 3.6 (still in beta but pretty stable), you may use the new bootstrapper functionality called Burn to create package bundles in order to chain your packages together.
Related
UWP App not being able to work with MySql
I have made an app in UWP and instead of using SQLLite which seems to be the norm for Visual Studio 2015 I want to use MySql. I have already connected my Azure mysql database to Visual Studio via the 'Server Explorer'.
I'm using MySQL Workbench to update my tables within my connected database from Azure but I cannot actually write any code to access my tables as whenever I try to install MySql.data/.entity/etc in the NuGet Package Manager I get an error.
nuget error
I tried downloading the Mysql installer, the Mysql drivers for Ado and ODBC. I even tried downloading the MySql for Visual Studio option as I found out that Visual Studio is not compatibile with MySql and instead requires the MySql for Visual Studio download but I still have errors whenever I try to use MySql in my code as I need an assembly reference for it but I'm having no luck in being able to get one that doesn't error.
Does anybody have any idea how I could actually use MySql within Visual Studio 2015?
This is what I've been using as my guideline but I can't seem to get past the Mysql.data errors when installing.
http://web3.codeproject.com/Articles/1074242/Designig-your-Azure-MySQL-DB-with-a-UWP-Demo
I have seen a lot of people talk about this but there is no one straightforward fix (I've tried a lot of the fixes, one in particular being to use Vs13 to install Mysql in the Nuget package manager and then it should update within VS15 but as my app is a UWP VS13 does not actually load/read it so that idea isn't good to me, might help anyone else though)
Starting with 6.7, Connector/Net fully supports building Windows Store apps. But using Connector/Net RT is not by install the Nuget package, it just reference the MySql.Data.RT.dll assembly according to MySQL Connector/Net Developer Guide:
Using Connector/Net RT is easy. Simply create a Windows Store application using Visual Studio and then reference the MySql.Data.RT.dll assembly in your project. The code you write should be exactly the same as for normal Connector/Net (including using same namespace MySql.Data.MySqlClient) except for the differences listed above.
You may find this dll at C:\Program Files (x86)\MySQL\Connector.NET 6.79\Assemblies\RT if you have install the connector. You can also download the mysql-connector-net-6.7.9-noinstall.zip to find this file inside the folder. I also have a MySql UWP sample before and has the dll here. Right click your project and add reference for this it will work.
More details please reference this sample
I am getting an error while installing SQL Server 2008. The error is like
SQLServer SetUp requires .NetFramework 3.5 to be installed
But .NET framework 3.5,SP1,VS2008 sp1 is already installed. I have checked in control panel also.
Because of this error I am not able to do daily tasks.
Please help me, where am going wrong?
Even though you install .NET Framework 3.5
sql server installer still ask you to install .NET Framework 3.5.
If you install sql server 2008 Standard ed in windows -server 2008 R2, .NET Framework 3.5 is already built in with windows.
Just go to server manager, click Add Feature and enable it. After that, you can install SQL Server 2008.
This bug had already reported to microsoft see here.
http://connect.microsoft.com/SQLServer/feedback/details/354980/sql-server-2008-setup-requires-microsoft-net-framework-3-5
and solution that helped was
The setup has been successfully completed after installation of .NET 3.5 Service Pack 1 (BETA) and Windows Installer 4.5. It was also nessary to install PowerShell after that.
Go ahead and download the required software and then try again installing.
I had the same problem.
In the installation folder you have some files and three folder (ia64, x64, x86). When I copied the installation folder of SQL Server 2008 I excluded the ia64 and x64 folder.
The solution that worked for me was to not exclude the x64 folder. Maybe it is possible you have missing files. I would download or copy the installation files again!
I have been searching for a while on this and have no real direction on what the problem may even be. I haven't done SSIS for about 5 years and even 5 years ago I only did one or two.
I have Visual Studio 2012 on my machine. I installed SSDT so that I could write an SSIS package. I have the package written and working locally but when I try to set up a job in the SQL Agent on the server I get this error after selecting the package:
I have looked into this error and none of the resolutions I have found are working. My project is already set to not use 64 bit mode. I'm kind of thinking this might have to do with the fact that the version of SQL Server on that machine is just 2008 and that maybe that means it has an incompatible SSIS runtime. I don't know if there is an additional runtime I need to install to get this to work and I don't know if it's backward compatible with the old runtime they are using if that's even the problem.
I can't find any information online about setting up the environment for an SSDT SSIS package..
Please help.
Thanks
You have a package built against the SQL Server 2012 Integration Services object model. You are attempting to execute it on a 2008 instance. Backwards compatibility is not an option.
You need to either update the 2008 instance to 2012 (there is a licensing change to be aware of) or recreate your package using the 2008 model.
There are 2 steps you have to do:
1) Build you package using correct version - Update 2208 Instance to 2012
2) If you have multiple versions install and you try to deploy using .ispac file, it will most likely pick the latest version. To resolve the issue, you have to pick the correct version of Installer by going to where it is installed. In my case it is (C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn)
I have a VB Windows forms application that uses a mysql database to keep track of everything within the application.. The problem that I know will occur is that most of the applications users will not have MYSQL let alone know how to install it properly... To install the application on the users systems I am using the Visual Studio Setup Installer to handle creation of the msi files.. What needs to happen first is the installer needs to check to see if MYSQL is installed on the host system and verify server name.. If true then import database, if not then install followed by import database... The importing is not the issue here... How do I make the installer install mysql with controlled parameters such as server name, etc, etc. Any ideas on this??? I have hammered google for the past 3 hours looking for bread crumbs on this but to no avail...
Usually existing packages (like the MySQL installer) are added as prerequisites. Visual Studio setup projects do not support custom prerequisite creation. However, this can be done by manually generating the required manifests.
You can find the manifests structure here: http://msdn.microsoft.com/en-us/library/ms229223(VS.80).aspx
These manifests can be generated automatically with the Bootstrapper Manifest Generator tool.
After generating the package manifests, you can add all these files (including the package) in a separate folder in the Visual Studio prerequisites folder, for example:
C:\Program Files\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\
You can then select the prerequisite in your setup project properties page.
Well... that's a good question. The first thing that pops up in my mind:
You could build the check in your application instead of the installer and warn the user about it. If needed, you could provide another installer to make sure everything is available (MySQL and the database itself).
I hope it helps you further.
Yours sincerely,
Roland
We currently use a VS 2010 (upgraded from 2008) setup project to install our application, and utilize the SQL Server 2008 install prerequisite.
Well wouldn't you know, management has got it in their head that everything (including prerequisites, but not .net) that's installed by the application must now be uninstalled by the uninstaller.
So I'm trying to modify the installer to uninstall SQL Server Express 2008.
I first thought that I could modify the package.xml dependency for sql server to trigger the right install conditions so I could pass in the uninstall arguments, but I'm at a loss as to what those conditions would be.
Then I thought about using a custom install action and System.Diagnostics.Process to programmatically invoke the sql express installer with uninstall command flags, but I'm not sure if I can guarantee that the installer will make that executable accessible for uninstallation.
Any ideas?
Um, uninstalling sql server express is bad. What if another application was later added that relies on this? Your uninstaller would break that application.
Management is right, though: you should uninstall everything you installed in the first place.
So what is the solution then? As they say, "damned if you do, damned if you don't".
Fortunately, if this is for a desktop application the answer is simple: don't use Sql Server Express Edition. Express Edition is really a server class engine. Sql Server Compact Edition is much more suited to this scenario, and will solve your deployment issues.
If this is for a server application, it's a little trickier. Any well-behaving installer will create it's own instance of Sql Server Express. You then need to make sure you uninstall only your instance (and also make sure your install is well-behaving). This doesn't really solve the problem, but at least it lets you say it's their bug and not your if something breaks after your uninstaller runs. Unfortunately, you still have to build this part manually.