- Microsoft Sql Server Error 53
- Microsoft Sql Server Error 64
- Microsoft Sql Server Error 5133
- Microsoft Sql Server Error 5133 Download
- Microsoft Sql Server Error 258
Today I was having following error and found the work around Create database failed with error 5133 on Microsoft SQL server 2012 With following ERROR. Jan 14, 2015 Error: 5133 SQL Server while attaching the Database When we attaching database to the server we may get below error - Microsoft SQL Server Management Studio Attach database failed for Server 'XXX-XX-XX'.
Microsoft Sql Server Error 53
I just installed SQL server 2012 on Windows 2012 today. After the install, I changed the database settings to create database files in f:mssql instead of the default. i verified the confired and running values.
Create database fails to create the .mdf and .log files with the following error -Directory lookup for the file 'f:msqldatatest.mdf' failed with os error 5. (Access is denied).
This error occurs when I run sql server service as domain account. The domain account is an administrator and has full control on volume F.
Microsoft Sql Server Error 64
If I run the sql server service as local system, I am able to create the database with mdf files on f: drive.
Microsoft Sql Server Error 5133
My sysadmin confirms and I have verified that the domain account has full control on f:
Microsoft Sql Server Error 5133 Download
I look forward to your suggestions.
closed as off-topic by Max Vernon, Paul White♦, RLF, Mark Storey-Smith, Shawn MeltonJan 2 '15 at 23:47
This question appears to be off-topic. The users who voted to close gave this specific reason:
- 'Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background).' – Max Vernon, Paul White, RLF, Mark Storey-Smith, Shawn Melton
2 Answers
This is now fixed. SQL Server can noow see the additional volumes besides. C:. It required applying this small changes and a server reboot. It turned out to be a VMWare HotAdd bug. Here is direct link to the VM Knowledge base article: http://kb.vmware.com/selfservice/microsites/search.dolanguage=en_US&cmd=displayKC&externalId=1012225
There is a sysinternal tool called Process Monitor (MS tool) http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx that it like a 'packet capture' for Windows. No need to install it, just download and run on the server. It outputs a lot of information but has great filtering capabilities.1. Start the capture2. Run through the process of creating the new DB until you get the error3. Stop the capture
Microsoft Sql Server Error 258
Then filter out everything but SQL Server process and look for Access Denied. It might give you more ideas of why you're having issues.