OleDB Provider for Oracle not found in in Windows Server 2008 with IIS 7 - asp.net

I'm deploying a small ASP.NET (framework 3.5) application in a Windows Server Web 2008 32 bits, IIS 7. The applications needs connection to an Oracle DB in another Server, using the tradicional DataAdapter, Oracle Connection, etc.
I´ve installed correctly the Oracle Client in the server (the server is another server´s client) and I´ve checked that this server has access to the server where the database is.
Even though my app isn´t able to connect to DataBase. The message says that Oracle components haven´t been found. It doesn´t find the OleDB Provider for Oracle or some dll.
¿Something I shluod know about permissions of the ASP.NEt users or something like this?
Some idea??
Thanks in advance.
Gus.

Check the path. It could be that the Oracle client directory is not on the path of the account that runs your ASPNET app.
Actually there are other steps you can go through, to verify the Oracle client install.
This article is old but may be helpful.

Related

Migrating a classic ASP's SQL Server database from a server 2003 to a 2008r2 server

I have a situation where a classic ASP's SQL Server database has been moved from a server 2003 to a 2008r2. The classic asp application stills resides on a server 2003.
Now because I have never done a migrating the only thing I thought I needed to change is the SQL Server named IP address in the application's IIS deployed ini file. Currently I am using anonymous authentication and the default application pool. The application render's to the browser fine. The problem is the application is not pulling any data for the database.
It seems that I have missed something in the configuration process. Has someone done this type of migration and if so provide me a list of thing that they have done to configure the application correct and other settings for the migration?
Thanks,
Steve Holdorf
This is not an asp but a database authentication.
It sounds like you used Windows authentication to connect from asp to the old server. Windows authentication means that asp uses IIS user identity to connect to the database and in your ini-file (or asp files) you do not provide any user/password to connect to sql.
If you want to keep this type of authentication for the new database, then you would need to configure user on the new Sql Server. Look at the old server, you should find the user named similar to domainName\WebServerMachineName$. You would need to create the same user on the new Sql Server and grant the same rights as on the old database. Read more https://msdn.microsoft.com/en-us/library/ff647396.aspx
If this is not an issue, then you should find what is the error message when application is not pulling any data for the database.

Web application deployment

I am buiding an internet web application using c# ASP.NET. I am using my own computer to develop the application. I've installed the oracle database on my computer. In order to deploy this application on the server, does the server have to install oracle client? I already included Oracle.DataAccess.dll in the bin folder.
Yes it does, assuming you're connecting to the database on the same server!
For example, you can connect to remote databases, but the point is where ever the database lives (server or PC), it will need Oracle installed.
The web server you will deploy your application to does not need to have Oracle server but it must have the Oracle client installed (Instant client for instance) + you will have to deploy your database to the Oracle server

Establishing connection to SQL Server Error

I opened my web project today and for some reason I could not gain access to my database files. I get the following exception whenever I try to add, edit or refresh my database:
A network related instance specific error occurred while establishing
a connection to SQL Server. The Server was not found or is was not
accessible. Verify that the instance name is correct and that SQL
Server is configured to allow remote connections.
I took a look at my connection string for any spelling errors and deleted my database and replaced it in the folder I had it in. I can't seem to find a fix for this so any help would be a appreciated. I am using Visual studio 2008 for this web project.
This sounds like the same problem that I had myself awhile back. My problem was that my SQL service pack 1 did not install properly so I had to install Microsoft SQL Server System CLR Types, Microsoft SQL Server 2008 Management Objects and Microsoft SQL Server 2008 Native Client. After that I could create new SQLdatasources but I could not edit the ones I had previously before my problem. I had to restart my computer in safe mode and delete my SQLEXPRESS folder then recreate the database connection in visual studios. When I finished that everything worked fine.
This is the site I got those downloads, http://blogs.cametoofar.com/post/cannot-load-file-or-assembly-microsoftsqlservermanagementsdksfc.aspx

Running asp.NET application on a local computer for testing purposes

I developed a web application for some small company. It connects to an SQL database created in Microsoft SQL server Managment studio 2008. Now they would like to test this app on a local computer before they put it on a server.
My question is, what are all the things I need to make this app work on a random computer running Win with no Visual Studio or SQL server installed?
Thanks for your help.
EDIT: They want to run it on a local computer only.
maybe Microsoft Web Platform Installer 3.0 can help you out.
http://www.microsoft.com/web/downloads/platform.aspx
Install .Net version you are using. It might already be there.
Install/configure IIS
Install SQL Server Express
Your db connection string obviously need to be changed to the local
sql server connection in web.config
Because it is a simple app, just copy the entire app (except proj
files, .cs, .vb files) to that computer
For one, point the connection string at SQL Server on a staging server. The whole idea of testing is to have the same environment as the production server.

ASP.NET application - Error when trying to connect to a SQL Server 2008 instance

Despite that I’m a regular reader of this great forum, this is my first post on it. I believe that this community can help me with the following problem that I have.
I’m trying to publish an ASP.NET website over an IIS 6.0 (Windows 2003 Server), and I have some troubles trying to connect to the database. Curiously, I have installed another ASP.NET website into the same IIS 6.0 with the same properties and security parameters and can connect without problems with the same database. The application that works fine is almost the same that the one that can’t connect with SQL Server (actually is the same but with several modifications).
I’ll enumarate some information related to the problem:
S.O: Windows 2003 Server
SQL Server Engine: SQL Server 2008 SQL Server accept remote connections? Yes.
ASP.NET version: 2.0.50727
The connections via TCP/IP are enabled to the SQL Server instance? Yes.
The corresponding user that I have in the connection string, actually exists into the database with the “owner” role? Yes.
ORM Tool used: nHibernate
I get the following error when I try to run the aplication into the browser:
Error while establishing a connection
to the server. When connecting to SQL
Server 2005, this failure may occur
because the default settings SQL
Server does not allow remote
connections. (provider: Shared Memory
Provider, error: 40 - Could not open a
connection to SQL Server)
In order to isolate the problem, I made some test. For example, using the web app that works fine I can connect without any problema with the database that uses the web app that can’t. With this evidence I concluded that the problem is within the web app and not into the SQL Server instance. I also google it my problem but sadly I can't find nothing usefull to solve it.
If someone can help me I’ll appreciate that.
Thank you so much for your time!
The most likely explanation is that your connection strings are not the same between the two applications. The error in question is talking about the Shared Memory provider, which is not the same as TCP/IP connections.
I've found the problem. In order to solve it, I was install in a virtual machine the same OS (Windows 2003 Server) and IIS (6.0). In this clean enviroment, I've found that the changes that I made in the home page was the problem. This aspx page has Web Parts that I'll investigate to know why is causing troubles with the database connection. I navigate to another page of the web application and it can connect with the database and retrieve information without any problem..but when I try to reach the home page the aplication colapse because of the problem that I tell you in this thread.
I'll post more news about this problem when I resolve it completely
Thanks for your assistance and time.

Resources