I have been attempting to install SQL Server 2016 Express, on my computer, However it keeps failing, and it's not giving me an error message this text written below just keeps popping up and than the installer only gives me the option to close it.
Oops...
There was an error while checking Rules of Sql Server setup.
This happens every time I try to do the basic install, so I tried the custom, all it did was download the files than shut off the installer and just shuts off if I choose the option now.
I am the Admin account of my computer and there is only this account and the guest account. The only indication of the problem is the text and there is no Error Message or Number to accompany it and every time I've tried to google it none of the articles mention the text.
I uninstalled all stuff about SQL from Programs and Features.
And then deleted %ProgramFiles%\Microsoft SQL Server\ folder.
Then Sql Express 2017 setup ran correctly.
For more information:
I recently installed Visual Studio 2017 on my computer and am having issues with SSRS. I previously had 2016, which worked fine, but I had to reinstall the OS on my system and only found 2017 to download. When I try to preview a report on SSRS locally I get the error:
"There was no endpoint listening at net.pipe://localhost/PreviewProcessingService9512/ReportProcessing
that could accept the message. This is often caused by an incorrect address or SOAP action."
I've read other people suggesting to right click the .rdl and click run, but if I do that I get a reporting services error "The item cannot be found." I've also read that the Net.Pipe Listener Adapter needs to be restarted, but this isn't even installed on my machine and I don't see where to install it. I've experimented and found that if I create a new user in SQL Server and grant it administrator privileges then the report preview will work for a short time, maybe 15-60 minutes, before going back to the "endpoint" error. I've even tried uninstalling and reinstalling both SQL Server and Visual Studio, but I get the same problems.
I'm completely stuck here. Does anyone know how to fix this?
Apparently it was a permissions issue. Even though I was logged in as an administrator I need to run Visual Studio under the "run as administrator" mode. This doesn't make sense as I'm logged in as an admin, but at least it works.
When I want to install sql 2014 in windows server 2012 the following error :
Error : Attempted to perform an unauthorized operation.
How to resolve it?
I too got the same error while installing sql 2014, i solved it by moving sql 2014 setup to C drive then run as administrator
It's work for me.
SQL Server 2008 R2
I had attempted to perform an unauthorized for this part of installation in windows 8.1 64bit:
SSISConfigAction_repair_postmsi_Cpu64
Changing installation drive for another drive to C: , solve my problem. Also, I read on another topic, don't close installation panel, because there is a bug while installing SQL Server.
Summary:
don't change installation Drive
don't close installation panel
make sure your source file is fine
run Setup as the administrator
Enjoy
1) So the methodology I used to figure out what was wrong with my system was to use Process Monitor.
I set the filter to listen for processes that contain "Scenario" and processes that contain "SQL".
2) I clicked Retry, and saw an ACCESS_DENIED for HKLM\Software\Microsoft\PowerShell\1\PowerShellEngine.
3) Checked permissions, and ensured that Users have read. Permissions had been set to deny on them.
Additionally, I have McAfee HIPs running on the server, so I also had an error where HIPs wouldn't allow editing of permissions to the Event Log registry.
So, had to have HIPs disabled temporarily, as well.
For some reasons I moved this folder : (Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL) to another drive, then returned it to the same location, but sql server has stopped working, showing this error when trying to start it again:
Windows could not start the SQL Server (MSSQLSERVER) on Local
Computer. For more information, review the System Event Log. If this
is a non-Microsoft service, contact the service vendor, and refer to
service-specific error code 3417.
I tried many solutions discussed in different forums, but none of them work for me.
The folder is not compressed or encrypted.
My sql server version is 2012:
Microsoft SQL Server Management Studio 11.0.3128.0
Microsoft Analysis Services Client Tools 11.0.3128.0
Microsoft Data Access Components (MDAC) 6.1.7601.17514
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.0.8112.16421
Microsoft .NET Framework 4.0.30319.18047
Operating System 6.1.7601
Thanks for your kind help in advance.
Very simple to solve this problem.
Just open RUN window(Window+R) and type services.msc:
Services.msc window
Find the SQL within name column and right click on that.
right click on SQL as in screenshot
You will get properties option, click on properties.
One new window will be open and there you have to click on Log On tab. And select the Local System Account. then apply and okay.
Select Local system Account
After that come again in services.msc window. and right click on sql and click start.
And finally, SQL Server services started successfully. enjoy and keep learning.
Check if you did compress the driver or folder in where you put the .mdf file.
If so, plesae goto the driver or folder, change the compress option by
Properties -> Advanced and unticked the “Compress contents to save disk space” checkbox.
After above things, you should be able to start the service again.
Run this command after opening cmd as administrator
net start mssqlserver /T902
This command is called trace flag 902. It is used to bypass script upgrade mode. Every time when you try to start your sql service it also looks for script upgrades. and when the script upgrade fail your service unable to start. So, Whenever we have such upgrade script failure issue and SQL is not getting started, we need to use trace flag 902 to start SQL.
I hope this will help you..
In my particular case, I fixed this error by looking in the Event Viewer to get a clue as to the source of the issue:
I then followed the steps outlined at Rebuilding Master Database in SQL Server.
Note: Take some good backups first. After erasing the master database, you will have to attach to all of your existing databases again by browsing to the .mdf files.
In my particular case, the command to rebuild the master database was:
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012>setup /ACTION=rebuilddatabase /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=mike /sapwd=[insert password]
Note that this will reset SQL server to its defaults, so you will have to hope that you can restore the master database from E:\backup\master.bak. I couldn't find this file, so attached the existing databases (by browsing to the existing .mdf files), and everything was back to normal.
After fixing everything, I created a maintenance plan to back up everything, including the master database, on a weekly basis.
In my particular case, this whole issue was caused by a Seagate hard drive getting bad sectors a couple of months after its 2-year warranty period expired. Most of the Seagate drives I have ever owned have ended up expiring either before or shortly after warranty - so I'm avoiding Seagate like the plague now!!
This usually occurs when the master.mdf or the mastlog.ldf gets corrupt . In order to solve the issue goto the following path C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL , there you will find a folder ” Template Data ” , copy the master.mdf and mastlog.ldf and replace it in C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Data folder . Thats it . Now start the MS SQL service and you are done
I have had the same error recently. I have checked the folder Log of my Server instance.
x:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\
and I have found this errors in logs
Starting up database 'master'.
Error: 17204, Severity: 16, State: 1.
FCB::Open failed: Could not open file
x:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).
Error: 5120, Severity: 16, State: 101.
Unable to open the physical file "E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf". Operating system error 5: "5(Access is denied.)".
Error: 17204, Severity: 16, State: 1. FCB::Open failed: Could not open file E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 5(Access is denied.).
Error: 5120, Severity: 16, State: 101. Unable to open the physical file "E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf". Operating system error 5: "5(Access is denied.)".
SQL Server shutdown has been initiated
So for me it was an easy fix. I just added proper access rights to this files to the sql server service account.
I hope it will help
In My case I had to Upgrade the SQL Server since evaluation licence had been expired.
What is System Event Log saying?
Have you tried to repair:
Sql Server Installation Center -> Maintenance -> Repair
I was getting this error today. And above answers didn't help me. I was getting this error when I try to start the SQL Server(SQLEXPRESS) service in Services(services.msc).
When I checked the error log at the location C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log, there was an entry related TCP/IP port.
2018-06-19 20:41:52.20 spid12s TDSSNIClient initialization failed
with error 0x271d, status code 0xa. Reason: Unable to initialize the
TCP/IP listener. An attempt was made to access a socket in a way
forbidden by its access permissions.
Recently I was running a MSSQLEXPRESS image in my docker container, which was using the same TCP/IP port, that caused this issue.
So, what I did is, I just reset my TCP/IP by doing the below command.
netsh int ip reset resetlog.txt
Once the resetting is done, I had to restart the machine and when I try to start the SQLEXPRESS service again, it started successfully. Hope it helps.
Go to the services and check if the SQL Server (MSSQLSERVER) service is running stop it and start your SQL Server (SQLEXPRESS) service it should work.
see the image:
Make sure both drive have the same partition - ( like FAT or NTFS, preferably NTFS ) also make sure he NETWORK SERVICE account, has the access.
Database rebuild fixed it for me as well. Also had to restore the old database from backup as it got corrupted during power outage...
The copy master.mdf procedure did not work for me.
i had the same problem before
the error code 3417 : the SQL SERVER cannot start the master database,
without master db SQL SERVER can't start
MSSQLSERVER_3417
The master database records all the system-level information for a SQL Server system. This includes instance-wide metadata such as logon accounts, endpoints, linked servers, and system configuration settings. In SQL Server, system objects are no longer stored in the master database; instead, they are stored in the Resource database. Also, master is the database that records the existence of all other databases and the location of those database files and records the initialization information for SQL Server. Therefore, SQL Server cannot start if the master database is unavailable
MSDN Master DB
so you need to reconfigure all settings after restoring master db
solutions
replace master mdf and ldf files with the same files from another instance of sql Server as long as its the same version reference
Rebuild System Databases refrence
reinstall sql server
I copied a master.mdf und mastlog.ldf from another Computer (luckily, we have a lot of Clients with the same configuration, otherwise template data would be perhaps necessary). I backed up the damaged master.mdf and mastlog.mdf. After that I replaced the bad ones with the ones from another Computer. And it worked. I needed to start the MSSQLSERVER Service of course. But, after that I had Problem that the user was already existing but orphaned (error code 15023), I executed the query
USE Database_name
EXEC sp_change_users_login 'Auto_Fix', 'username'
after that, everything was working smoothly. Hope this helps you and many thanks for this thread, saved me :)
Just rename the current ErrorLog to any other name like Errorlog _Old and change any old Log file to Error log file
try to start the SQL server services.. That's it. it will work..
Sql server error log file got corrupted. that is why it gives the problem even when you have all permissions.. when you delete it. new file will be generated.
I encountered this issue after changing database location. And I solved it by moving system databases back to their default locations. Although I will recommend not to move system databases like master and model to some other location. But if you want then you can refer to this article: https://learn.microsoft.com/en-us/sql/relational-databases/databases/move-system-databases?view=sql-server-2017
Re-entering credentials will help to start the services:
Start > Services
Right click on SQL Sever > Properties
Log On
Re-enter credentials and apply
Start the services now
The reason behind getting this Error Code : 3417 may be as follows:
One cause may be due to the Network account for the Data folder in
Program files.
The other reason may be because of some Windows
settings changed somehow.
Example: If for some reasons you have moved this folder (Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL) to another location then returned it to the same location. So, though it was returned to the same location the server may stop working and show error code 3417 when trying to start it again.
How To Fix SQL Error 3417
Go to "C:Program Files Microsoft SQLServerMSSQL.1MSSqLData"
Security/Permission settings
Network Service Account
Add a Network Service account
Then again check all
As stated here, you can try this third party tool as well.
A few times now, I've experienced various instances MS SQL Server to fail with this error after a Windows update. Most of the quick fixes above did not work for me.
What did:
copy all production databases over to some safe place
remove everything SQL Server via add/remove programs
get the latest SQL Server Express or Dev & install it
move the databases over to their home and reattach them.
For me, this was the fastest solution. Trying to find the cause of the error and fixing it is an afternoon of googling misty error messages. But YMMV.
In my case problem was about evaluation period expiration. I also went through this thread of StackOverFlow.You can investigate your problem by going to Event Viewer --> Windows Log (Application) and then search for your error id. For Step by Step guide to view error id in event viewer visit this...
When running the SQL Server 2008 setup, I receive the following error message:
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
Unable to open Windows Installer file 'G:\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi'.
Windows Installer error message: The system cannot open the device or file specified.
.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
...
Please let me know how can i fix this is as i am unable to continue the installation process ... please help!
Regards
This happened to me. The installer actually seemed to be working with no error for over 2 hours, but I knew something had to be wrong with that. I restarted it left it overnight and came in to see the error mentioned in your post.
Copying the files from the CD to the hard drive, and then running the setup.exe from there helped me resolve the issue. I see that in the comments below the selected answer this is sort of mentioned, but the comments ended with hoping it would fix the problem, and for me it did.
Try to copy .msi to drive C:\ and execute it from there.
This answer relates to installing a 2008 R2 service pack, not installing 2008 from scratch, but this question was one of the first results when searching for the error message. Might help someone...
I got the same "The system cannot open the device or file specified." message.
I looked in the setup installation logs here: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
Found the error, and the file it was looking for in the Windows\Installer directory.
Went to the Installer directory, found the file, backed it up, and deleted it.
Ran the setup again, and got a more meaningful error, explaining the missing file, and the corresponding file from the initial installation, in my case, 2008 R2 SP1.
Downloaded SP1 on my PC, extracted it, dug out the file, in my case, sql_common_core.msp.
Just copied that file to the server, ran it, it repaired/installed/did something quickly.
Ran the setup again and everything went through just fine.
A whole lot of details regarding fixing these types of setup errors is here: http://support.microsoft.com/kb/969052/en-us
This unfortunately, is very open-ended. I'm assuming G:\ is a removable media drive? Are you able to see the file path in explorer?
The same problem was with me. I turn off my windows firewall and re-try it, and it works for me. You can turn off your firewall while installing SQL Server.