Problem in excel opening on IIS 5.1
-
I have written a code to upload data from excel to oracle database in asp.net.This code is working fine on local machine. I have hosted this code on web server IIS 5.1 using my credentials(OS window XP SP3, so default IIS is 5.1). Problem : When I login on the server machine using my login id ,the application runs fine. If I try to run this application from another local machine other than server(using same my login id) then also there is no problem. But if someone else logs in into a local machine and tried to run the application using his id then it’s not working.. This is my connection string: OleDbConnection oledbConn = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;" + "Data Source=" + Label1.Text + ";" + "Extended Properties=Excel 12.0"); The code fails after oledbConn.Open(); when someone else logs in into a local machine
-
I have written a code to upload data from excel to oracle database in asp.net.This code is working fine on local machine. I have hosted this code on web server IIS 5.1 using my credentials(OS window XP SP3, so default IIS is 5.1). Problem : When I login on the server machine using my login id ,the application runs fine. If I try to run this application from another local machine other than server(using same my login id) then also there is no problem. But if someone else logs in into a local machine and tried to run the application using his id then it’s not working.. This is my connection string: OleDbConnection oledbConn = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;" + "Data Source=" + Label1.Text + ";" + "Extended Properties=Excel 12.0"); The code fails after oledbConn.Open(); when someone else logs in into a local machine
Naturally, if you told us what label1.Text was, we might have some suggestions.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Naturally, if you told us what label1.Text was, we might have some suggestions.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
And this is supposed to find the file using the network, right ? I suspect the issue has to do with the login you're using because it has to do with permission to grab files at random across the network. OR it has to do simply with your login having the right to access files on your computer.
amittinku wrote:
Label1
amittinku wrote:
FileUpload1
Are you attempting to make your code as hard to read as possible ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
And this is supposed to find the file using the network, right ? I suspect the issue has to do with the login you're using because it has to do with permission to grab files at random across the network. OR it has to do simply with your login having the right to access files on your computer.
amittinku wrote:
Label1
amittinku wrote:
FileUpload1
Are you attempting to make your code as hard to read as possible ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
I am agreeing that issue is with some permissions. It is web based application, any one can use it. After accessing the URL from local machine, any user can try to select excel placed in any location on his desktop. So how to do settings on IIS so that any user could do it, not just who configured IIS.
-
I am agreeing that issue is with some permissions. It is web based application, any one can use it. After accessing the URL from local machine, any user can try to select excel placed in any location on his desktop. So how to do settings on IIS so that any user could do it, not just who configured IIS.
It's not an IIS issue. It's a network issue. Your current code will only work if you give the server access to all the computers. But you have the file data, why not write it locally and read it from there ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
It's not an IIS issue. It's a network issue. Your current code will only work if you give the server access to all the computers. But you have the file data, why not write it locally and read it from there ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
i have not got u completely. see code is on webseerver. we r calling from any other machine. When local machine try to access webserver, it asks for username and password, but after that does not open excel file. I did not get "But you have the file data, why not write it locally and read it from there ? "
-
i have not got u completely. see code is on webseerver. we r calling from any other machine. When local machine try to access webserver, it asks for username and password, but after that does not open excel file. I did not get "But you have the file data, why not write it locally and read it from there ? "
I am posting the exact error that i Got at oledbConn.Open(); Exception ex ex.message returns "C:\Users\vikas_aggarwal01\Desktop\Kapil.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides." ex.source returns " Microsoft Office Access Database Engine" The above error comes only when another user tries to do it.
-
I am posting the exact error that i Got at oledbConn.Open(); Exception ex ex.message returns "C:\Users\vikas_aggarwal01\Desktop\Kapil.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides." ex.source returns " Microsoft Office Access Database Engine" The above error comes only when another user tries to do it.
I tried with different user, I am getting similar error: The Microsoft Office Access database engine cannot open or write to the file 'C:\Users\Public'. It is already opened exclusively by another user, or you need permission to view and write its data.