Sql Server 2008 installation error : Attempt to perform an unauthorized operation - sql-server

I had sql server 2008 r2 express edition in my PC .But i unistalled it ,In order to install Sql server 2008 Enterprise edition trial version in my PC.
But some features in sql server 2008 showing "attempt to perform an unauthorized operation" error during installation process.
My operating system is windows 7 home basic 64 bit.
these are the feature which are showing error while installation:
sql server database engine service
sql server replication
sql server analysis services
please help me with this issue

Here's a couple things to try from people who have had similar problems:
Check: %\Microsoft SQL Server\100\Setup Bootstrap\Log\SystemConfigurationCheck_Report.htm
Copy installation files to disk and run from there.
Run setup as administrator.
Create a new local administrator account and use that to run the installation.
When error occurs, dont exit installation, run process monitor trace, click retry for installation, stop trace, locate registry key where where access denied is, give your account temporary full control on that key, retry again.
Use the slipstream procedure to update SQL Server 2008
This method allows you to update the entire product when you run the SQL Server 2008 Setup program after following one of the following procedures:
Procedure 1: Basic slipstream steps
Follow the following steps to create a slipstream drop that you can use for installing the original media and a service pack at the same time.
Install the following prerequisites for SQL Server 2008.
.NET Framework 2.0 SP2 for SQL Server 2008 Express Edition
You can obtain the .NET Framework 2.0 SP2 from the following Web site in Microsoft Download Center:
http://www.microsoft.com/downloads/details.aspx?FamilyID=5b2c0358-915b-4eb5-9b1d-10e506da9d0f&displaylang=en
.NET Framework 3.5 SP1 for other editions
To download and install the .NET Framework 3.5 SP1, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkID=120550
Windows Installer 4.5
To download and install Windows Installer 4.5, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkID=49112
Download the latest service pack package that matches you system architecture. For example download the x64 package of SQL Server 2008 Service Pack 1 if your system is an x64-based system.
Extract the service pack by running the following command:
SQLServer2008SP1-KB968369-x64-ENU.exe /x:C:\SP1
Run the service pack to install Setup files on the computer. You will receive a Setup Support Files dialog box if the Setup support files have not been installed. You can also run the following file to install the setup support files:
C:\SP1\x64\setup\1033\sqlsupport.msi
Finally,
run the Setup.exe file from the SQL Server 2008 source media by specifying the /PCUSource parameter. For example:
Setup.exe /PCUSource=C:\SP1

I have been googling for this issue a lot but there were no solution working for me. atlast , I formatted my system for a fresh install which worked fr me.

The solution is simple.
1 - Install ONLY "Sql Server Database Engine"
2 - Start installation again and add any other features to your instance
P.S. No need to run as Admin or in Windows 7 compat-mode (if you are installing on 8 or 10)

In my Case, creating an Administrator Windows Account and installing SQL Server worked!
Also you can simply activate the built-in windows Administrator Account by running the "net user administrator /active:yes" command in command prompt(Admin Mode), then log in as Administrator. Now You can Install SQL Server without problem!
Finally I should say that you can use SQL Server from your own normal windows account after Installation and I recommend deactivating Administrator Account by "net user administrator /active:no"

Related

Adding Integration Services to Previous SQL Server Install

I am trying to add integration services to an instance of SQL Server on my machine. When attempting to do so I get the following error:
Some basic googling around has not yielded anything helpful. Does anyone here have any insight?
Check if sqlncli.msi exists in %PROGRAMFILES%\Microsoft SQL Server\100\SDK. If it does not exist use the subsequent steps to download, uninstall, and re-install it to resolve this error.
https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms131321(v=sql.105)?redirectedfrom=MSDN
The SQL Server Native Client header and library files (sqlncli.h and sqlncli10.lib) are installed in the following location:
%PROGRAMFILES%\Microsoft SQL Server\100\SDK
You can distribute (install) SQL Server Native Client through sqlncli.msi. You might have to install SQL Server Native Client when you deploy an application. One way to install multiple packages in what seems to the user to be a single installation is to use chainer and bootstrapper technology. For more information, see Authoring a Custom Bootstrapper Package for Visual Studio 2005 and Adding Custom Prerequisites.
The x64 and Itanium versions of sqlncli.msi also install the 32-bit version of SQL Server Native Client. If your application targets a platform other than the one it was developed on, you can download versions of sqlncli.msi for x64, Itanium, and x86 from the Microsoft Download Center.
When you invoke sqlncli.msi, only the client components are installed by default. The client components are are files that support running an application that was developed using SQL Server Native Client. To also install the SDK components, specify ADDLOCAL=All on the command line. For example:
msiexec /i sqlncli.msi ADDLOCAL=ALL APPGUID={0CC618CE-F36A-415E-84B4-FB1BFF6967E1}
Steps to take if sqlncli.msi does not exist in the documented path
Go to Control Panel and uninstall SQL Server 2012 Native Client
Download Microsoft® SQL Server® 2012 Native Client - QFE https://www.microsoft.com/en-us/download/details.aspx?id=50402 and install
Use SQL Server Installation Center to add SSIS

SSIS Error "To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services "

I am using Visual studio ultimate 2012, SQL Server 2017 and Sql Server Data tools 2012. I am working with windows 10 64 bit.
My package consists of script tasks(c#) and Sql commands and it runs successfully from SSDT, but while trying to run my package from CMD i am getting
To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition (64-bit) of Integration Services.
If i make another empty package and try to run it then it runs successfully too.
Please help.
(1) Integration Services (Shared feature) installation
I think that the issue is that you have installed SQL Server Data Tools (SSDT) for Visual Studio but you didn't install the Integration Services (Shared feature) from the SQL Server Installation which is necessary to execute .dtsx packages outside of visual studio.
For more information check the following link:
SSIS Error – “To run a SSIS package outside of SQL Server Data Tools you must install…”
(2) Execute using dtexec(32-bit)
Another thing you can try is to execute package via 32-bit dtexec.
As mentioned in the following Microsoft Documentation:
On a 64-bit computer, Integration Services installs a 64-bit version of the dtexec utility (dtexec.exe). If you have to run certain packages in 32-bit mode, you will have to install the 32-bit version of the dtexec utility. To install the 32-bit version of the dtexec utility, you must select either Client Tools or Business Intelligence Development Studio during setup.
By default, a 64-bit computer that has both the 64-bit and 32-bit versions of an Integration Services command prompt utility installed will run the 32-bit version at the command prompt. The 32-bit version runs because the directory path for the 32-bit version appears in the PATH environment variable before the directory path for the 64-bit version. (Typically, the 32-bit directory path is :\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn, while the 64-bit directory path is :\Program Files\Microsoft SQL Server\100\DTS\Binn.)
More info at:
How to execute a package in 32-bit mode using dtexec.exe?
Also, similar issues was mentioned in other links, you can check them for more information:
SQL Server Central Forum - Run a SSIS package outside of SQL Server Data Tools you must install of Integration
Code Project - How To run a SSIS package outside of SQL Server Data Tools ?
MSDN - To run a SSIS package outside of SQL Server Data Tools you must install Standard Edition of Integration Services or higher
To run a SSIS package outside of SQL Server Data Tools you must install Move File to Archive of Integration Services or higher
SE DBA - Error: “To run a ssis package outside of sql server data tools you must install [send successful email] of Integration Services or higher.”
Adding to Hadi's answer, the change would be to use the right version which in my case was to use
C:\Program Files\Microsoft SQL Server\130\DTS\Binn>
Instead of
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn>
I had the same error and my integration services of 2017 was installed, so the suggested solution was not relevant.
i tried many options including uninstall and re-install, what solved finally was an upgrade to ENTERPRISE EDITION!
I found out that in a server where the dtexec ran successfully an ENTERPRISE VERSION was installed, while in the problematic server there was not an ENTERPRISE edition.
How did i find it? i ran the following in both servers:
run setup.exe file of SQL SERVER 2017 installation
on the left menu you will see "tools" - press the link
find: "installed SQL server features discovery report"
you will see in edition column an empty cell vs. "Enterprise Edition"
which is the successful one!
how did i upgrade in the problematic server?
run setup.exe file of SQL SERVER 2017 installation
on the left menu you will see "maintenance" - press the link
find: "edition upgrade"
follow the instructions, in my case since my organization had an automatic updated key i just pressed "next" a few times until a successful upgrade
good luck!

Bare Bones Setup to Run SSIS Package

I work with Microsoft Access 2016 with a SQL Server 2008 R2 backend. I have used SQL Server Management Studio to create some SSIS package for quick copying of data (right-click DB -> Tasks -> Import/Export).
I was able to create a button in Access to kick off the SSIS package successfully using VBA. I use the Shell function to run the following command:
"C:\Program Files (x86)\Microsoft SQL Server\140\DTS\Binn\DTExec.exe" /F "\\MyPath\MySSISPackage.dtsx". This works on my machine because I'm running my particular instance of DTExec.exe to execute the SSIS package.
I need to set up users' Win10 64-bit computers now so that this process will work for them as well. I don't know if DTExec was installed when I installed SSMS or my local SQL Server Express Edition DB, but the user doesn't need either of these programs. What is the bare minimum I need to install on the users' computers for it to work for them also?
I've done a lot of googling but either the scenario didn't quite fit mine, or I just wasn't understanding what they were talking about. The users will have Microsoft Access only as a start.
Links to download locations would be extra appreciated!
Thanks!
For running SSIS packages in a production environment you must install and license SQL Server. A user who only has Microsoft Access installed cannot run SSIS packages.
You can install and run SSIS packages on your SQL Server (Standard Edition or higher), but not on your clients' PCs.
Once you have credentials all sorted out with DBA team. At min you will need read (select permission) on desired database(s) . Build your ssis in VS2017 locally and test. It will run great I'm sure. And when your ready to deploy you can use steps below.
Steps below outline package deployment mode.

Local SQL Server 2008 R2 database not accessible on Windows 10

I've inherited the job of maintaining an application which uses a local SQL Server 2008 R2 SP2 Express database as a back-end. I successfully installed the application some months back after upgrading to Windows 10 so that I could start testing and development, but after reformatting recently, I've been unable to get the database running. I'm using the exact same installer, and so far as I can tell, everything else configuration-wise is the same, with the exception that I'm now on a newer W10 insider build.
The application installer installs SQL Server 2008 R2 with the following parameters:
/TCPENABLED=1 /ACTION="INSTALL" /SQLSVCSTARTUPTYPE="automatic"
/SECURITYMODE="SQL" /SAPWD="password" /INSTANCENAME="app"
/FEATURES=SQLENGINE,REPLICATION /BROWSERSVCSTARTUPTYPE="Automatic"
/SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /IACCEPTSQLSERVERLICENSETERMS
/INDICATEPROGRESS /QS
The installer is built using Advanced Installer, and is configured to run a database setup script after installation has completed, but when it reaches this step the database times out and the install fails. To test the database I tried using a UDL file, and though the database itself is visible, when I attempt to test the connection I get
"Test connection failed because of an error in initializing provider.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied."
I've tried absolutely everything I can think of to fix this problem. I've removed all traces of every version of SQL Server from my computer, purged the registry of any remaining keys, and deleted any remaining directories. I've checked and restarted all SQL services, tried different SQL service accounts, different versions of the SQL installer, ran the installer(s) as an administrator, ran them in compatibility mode, and checked log files. I haven't found anything helpful on StackOverflow or on Advanced Installer's forums. Nothing's worked, and I'm completely out of ideas at this point.
According the MS only SQL server 2012 SP2 and up are compatible with Windows 10.
You might try this instruction to install SQL express 2008 R2, but I never tried it: https://www.youtube.com/watch?v=DUCbvfFEO34

SQL Server 2005 SP2 or SP3 not updating Management Studio?

I applied SQL Server 2005 SP2 and marked all the components to be updated, including Client tools, but the version in the Help -> About box still has version 1399, while the server does indeed had 3042.
I then re-applied SP2 to only Client tools, and everything ran successfully (again, first time did too) but still, no version update for management studio.
Now, I just applied SP3 with everything successfully, but still management studio version did not get updated.
How can I update it? Or at least how can I uninstall just Management studio so I can install it from a newer DVD?
Thanks.
If you go to Control Panel > Add Remove programs and then choose the appropriate SQL Server installation, this will start the typical install wizard for SQL Server.
You can then select the specific components that you wish to uninstall.
If you are having difficulties with SQL Server 2005 Service Pack 3 may I suggest that you visit the SQL Server Central forums as there are a wealth of resources for SQL Server SP3. It was actually due to user demand from this forum that resulted in there even being an SP3 release.
http://www.sqlservercentral.com/Forums/Forum146-1.aspx
Let me know how you get on.
Cheers, John
I got the Error in sql server sp3 installation log which caused this:
Error Number : 29538
Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
Hate to answer my own question, but I had to manually un-install Client Tools, re-install them using SQL Server 2005 setup, and THEN apply the updates.
It wasn't working by just trying to apply updates over the existing original installation.
And i mention un-installing using the SQL Server 2005 Setup because trying to do it from the Add/Remove Programs dialog won't let you or will give you trouble.

Resources