unable to open the physical file operating system error 32

Question

Hi,

I have installed Sql Server 2005 with an instance name.

I am able to login using SQL Management Studio.

When i try to connect using Visual Studio through database explorer (its a VSTA for infopath), I get the error unable to open the physical file operating system error 32.  I am struggling to slove this. 

Any help in this regard would be helpful.

Thanks and Regards,
Vijaybabu.N.S

Answer 1

Seems you are trying to connect to a user instance and the file for the user instance isn´t present. Which edition of SQL Server are you using and what do you see in the Server Explorer ? (Maybe you can upload a file to a image hoster and share your information by posting the link to that picture in your next post)

-Jens

---

Jens K. Suessmeyer http://blogs.msdn.com/Jenss

Answer 2

Hello Jens,

Thank you very much for your immediate reply.

I have SQL Server 2005 Development Edition.

From VSTA (Visual Studio Tools for Applications) i see only Database explorer not a server explorer.  In that i see a tree "Database connection", from here i try to connect database using "Add connection" and do the following steps

1. Select Data Source as -->Microsoft SQL Server Database File (SqlClient)
2. Browse and Select the mdf file
3. From Advance button, I change Data Source Property from .\SqlExpress to .\Vijay (instance name) and turn User Instance to Flase

I get the following error message
Unable to open the Physical file "file path" Operating System error 32

When i turn the User instance to True, I get the following error message
The User Instance flag is not supported by this version of SQL Server

Please help in solving this.

Thanks and Regards,
Vijay

Answer 3

Hi,
Just in case if anybody is still looking for solution to this error, this works for me:
1) Open the VStudio project for which you need to connect to a SQL database
2)Separately, Go to  Start->Run->Services.msc
3) Look for SQL Server (SQLEXPRESS) service and Stop it
4) Start it again
5) Try connecting your database now.

Looks like the reason it works has something to do with User Instance discussion that is going on in this thread.