We are currently having an issue with a .NET application (developped in Visual Studio 2008). It is installed on a Windows 2003 Server R2, along with IIS 6.0.
The IIS login page loads fine, we enter the username and password, then hit "validate". This launches the connection to the database (Sybase 9.0.2 EBF 3221). As soon as it tries to connect, an error page appears with the folllowing error :
Server Error in '/Approbation' Application.
The 'ASAProv.90' provider is not registered on the local machine. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
We tried to register the two following sybase dll (dboledb9.dll and dboledba9.dll) on the server (we had the same error appear for another application last week (regular executable, not through IIS), we registered those and that fixed the issue for that application), but this did not fix the issue for our IIS application, we still get the same error. This is hapenning at one of our client's location. I installed this application with the same setup on a Windows Server 2003 R2 locally at our office and everything works perfectly. I also tried installing it on Windows XP on 3 different PC, they all work perfectly too.
I modified the IIS settings to use ASP.NET 2.0, and I also modified the permissions on the directory "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files" so that "NETWORK SERVICE" has full access to it.
I'm wondering if it's a permission issue, or somehow the dll are not properly registered, or could it be a dll missing in the assembly, etc.?
We're using ASAProv because our consultant (he's the one that designed this program, not me) tells me he could not view/use procedures in Visual Studio 2008, only functions and tables. With ASAProv he could see and use procedures.
Any help would be much appreciated. If you need more information, just let me know.
Thank you, Dominic Marcoux
Implies that the OLEDB provider cannot be located in the registry information - and sounds like you have registered it, at least for 32-bit applications (e.g. your application that is not IIS). Is this a Windows 2003 x64 installation? If so, IIS will be running as 64-bit - you would also need to register the ASAProv.90 x64 OLEDB provider for IIS to use this.
answered 19 Mar '13, 08:25