Skip to main content

Unable to open physical file - Operating system error 5: 5(error not found) Microsoft SQL Server: Error 5120


I am trying to attach a database to SQL 2005. This database has not previously been attached. I have only just installed SQL.

I get the following message: Unable to open physical file "C:\ArrowSQL\Arr@Data\Arrow_data.mdf" Operating system error 5: "5(error not found)" (Microsoft SQL Server: Error 5120)".

I have loaded SQL and the database fiel and directory with the same user acccount which is a local adminstrator ont hsi machine. I have checked that I have read/write access to the file.

The machine runs Windows Vista Business. SQL has SP 2 loaded.
Use the below script to find the sql service account

Code Snippet
declare @sqlser varchar(20)
EXEC master..xp_regread @rootkey='HKEY_LOCAL_MACHINE',@key='SYSTEM\CurrentControlSet\Services\MSSQLSERVER',
@value_name='objectname', @value=@sqlser OUTPUT
PRINT 'Account Starting SQL Server Service:' +convert(varchar(30),@sqlser)


After getting the service account try the below steps to provide privilege

  • Right click on the folder C:\ArrowSQL\Arr@Data and click on properties
  • Click on security tab
  • Click on Add button and add sql service account
  • Provide modify privilege and click ok
  • Verify both mdf and ldf have modify privilege
  • Attach the db!

    BEST METHOD.


    You can also try the below alternate method to find service account

    • Goto RUN
    • Type services.msc & press enter
    • In service control manager find the below service w.r.t to your edition.
    For SQL 2000
    MSSQLSERVER -- for default instance
    MSSQL$instancename -- for named instance

    For SQL 2005 & SQL 2008
    SQL Server (MSSQLSERVER) -- for default instance
    SQL Server (instancename) -- for named instance
    • Check the "Log On as" for the SQL service and provide modify privilege to that ID in the folder.


For More Details, Click Here

Comments

Popular posts from this blog

Call User-defined Function on Linked Server :SQL Server

If you try to invoke a user-defined function (UDF) through a linked server in SQL Server by using a "four-part naming" convention (server.database.dbo.Function), you may receive error message. 
The reason is User-defined function calls inside a four-part linked server query are not supported in SQL Server. Thats why error message indicates that the syntax of a Transact-SQL statement is incorrect. 
To work around this problem, use the Openquery function instead of the four-part naming convention. For example, instead of the following query
Select * from Linked_Server.database.dbo.Function(10)
run a query with the Openquery function:
Select * from Openquery(Linked_Server,'select database.dbo.Function(10)') If the user-defined function takes variable or scalar parameters, you can use the sp_executesql stored procedure to avoid this behavior.  For example:
exec Linked_Server.database.dbo.sp_executesql N'SELECT database.dbo.Function(@input)',N'@input int',@inp…

Installing the FrontPage Server Extensions on IIS 7.0

As most people that have installed IIS 7.0 on Windows Vista and Windows Server© 2008 have realized, there are no options to install the FrontPage Server Extensions, leaving only two ways to edit your Web site if it is hosted on a Windows Vista or Windows Server 2008 computer: Edit the Web site locally by using the file system.Use FTP to upload your files to a remote Windows Vista or Windows Server 2008 computer.Microsoft realizes that the FrontPage Server Extensions are essential to many Web hosting companies and developers, and has worked with Ready-to-Run Software to release a version of the FrontPage 2002 Server Extensions (FPSE 2002) for Windows Vista and Windows Server 2008. This version of FPSE 2002 is available for x86 (32-bit) and x64 (64-bit) Windows Vista and Windows Server 2008 as a separate download for IIS 7.0, and you can download this version by clicking the following URL:
FrontPage 2002 Server Extensions for IIS 7.0



Notes:The FrontPage 2002 Server Extensions (FPSE 2002) a…

Pass multiple complex objects to Web API action

Working with ASP.NET Web API, the most unexpected thing is the limited support of POST data values to simple ApiController methods.

When a parameter has [FromBody], Web API uses the Content-Type header to select a formatter. At most one parameter is allowed to read from the message body. The reason for this rule is that the request body might be stored in a non-buffered stream that can only be read once.

A simple principle, you can send any content in HTTP request, it only need to be serializable into a string. So, it could be multiple JSON object. In this example, the content type is "application/json" and the request body is a raw JSON string (not a JSON object).

Here I found a workaround to pass multiple complex objects (using the above principle) from jquery to a WEB API using JObject, and then cast back to your required specific object type in api controller. This objects provides a concrete type specifically designed for working with JSON.

var customer = { "Name&q…