December 22, 2009 at 9:29 am
All,
First off yes, I realize at this point with SQL2008 we shouldn't be using DTS, but this is out of my control (for now). I need to continue to have support on this new environment.
Anyways, I've been successful using the backward compatibly/DTS designer components and copying the .dll files on Windows 2008 and Windows 7, but it appears that the install fails on Windows 2008 R2:
"Installation of this product failed because it is not supported on this operating system".
Anyone experience this yet and/or find resolution?
Thanks
December 28, 2009 at 2:27 pm
I'm pretty certain that this is because Windows 2008 R2 is 64-bit whereas the DTS Designer is 32-bit. Although I'd think that it would still run using WOW64, the installer for the DTS backwards-compatibility components may be 16-bit, in which case you're out of luck.
January 4, 2010 at 7:04 am
Thanks for the response Mel. That is quite unfortunate to hear ... but thank you.
January 5, 2010 at 3:47 am
I have successfully installed DTS Designer on W2008 R2. This needs to be followed with copying the DTS Designer dll files to the SQL 2008 program folders as noted in BOL.
You also need the SQL 2005 Backward Compatibility components installed in order for DTS Designer to work.
I also set the Windows environment variable SEE_MASK_NOZONECHECKS to 1 and pause the Windows Update service before running an install, as this prevents come warning messages being produced.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 5, 2010 at 6:03 am
EdVassie (1/5/2010)
I have successfully installed DTS Designer on W2008 R2. This needs to be followed with copying the DTS Designer dll files to the SQL 2008 program folders as noted in BOL.You also need the SQL 2005 Backward Compatibility components installed in order for DTS Designer to work.
I also set the Windows environment variable SEE_MASK_NOZONECHECKS to 1 and pause the Windows Update service before running an install, as this prevents come warning messages being produced.
Hi Ed, by changing the NOZONECHECKS, is that how you bypassed the "Installation of this product failed because it is not supported on this operating system" error?
January 5, 2010 at 6:24 am
It was originally added to suppress warnings for the unattended install done by FineBuild. It will also suppress some warnings for an interactive install.
I suggest you try it and see what happens.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 5, 2010 at 6:32 am
Thanks Ed, can you stick with me for a bit longer on this?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
- I see no SEE_MASK_NOZONECHECKS on 2008 R2.
What am I missing?
January 5, 2010 at 6:58 am
The SEE_MASK_NOZONECHECKS environment variable does not normally exist. When it does not exist Windows assumes the setting is off. Use the command SET SEE_MASK_NOZONECHECKS=1 to turn it on, and SET SEE_MASK_NOZONECHECKS= to turn it off.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 5, 2010 at 7:08 am
Ran the SET command, didn't change anything. As soon as I go to install the BC file, it immediately throws that error.
I also tried to install with troubleshoot compatibility. It picked "skip version check" which again did not fix the problem. I'm at a loss to as how you were able to get the install to run.
January 5, 2010 at 7:19 am
Are you running the BC file included in the SQL 2008 media? If you are then it would have been better to have included backward compatibility as one of the features in the SQL install. (Hindsight is wonderful...)
The BC component can be requested for both 32-bit and 64-bit installs of SQL Server 2008, but is only honoured when you do a 64-bit install. If you install on a 32-bit OS then you have to manually run the BC install.
If you are trying to use the SQL 2005 BC media for a SQL 2008 instance this may be the reason it is failing. Look for the SQL2005_BC.msi file in the SQL 2008 media \x64\Setup\x64 folder and run that.
The DTS Designer component is only available in the SQL 2005 Feature Pack, but this version works OK on SQL 2008 (and SQL 2008 R2).
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
January 5, 2010 at 7:36 am
EdVassie (1/5/2010)
If you are trying to use the SQL 2005 BC media for a SQL 2008 instance this may be the reason it is failing. Look for the SQL2005_BC.msi file in the SQL 2008 media \x64\Setup\x64 folder and run that.
This was it ... I was using an x86 install. Everything is up and running, thanks again!
November 8, 2011 at 1:08 pm
Thanks for the location of the Sql2008 SqlServer2005_bc.msi file. Worked like a charm!
My test database on prod database (3rd party app) are not running on the same OS. Aka the file used for test did not work in Prod.
thanks
Daryl
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply