Hello Forum,
I have a great problem using Gupta .NET Dataprovider on Windows Server 2008 R2 x64 in an IIS 7.0 / .NET Framework 3.5 environment. SQLBase Server and client version is 11.0.2. When accessing the database using Sqltalk no problems occur. But when I try to access the database with an ASP.NET application, the IIS process is shut down and an error message like "System.AccessViolationException: Attempted to read or write from or into protected memory." (orignal text in german: "Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben.")
So the problem is, that it is not possible to access the SQLBase with an ASP.NET application under IIS 7.0 / .NET Framework 3.5 / Win2008 Server R2 x64. All components are configured as 32 bit applications - as they really are 32 bit apps. Therefore the IIS application pool parameter "32-bit applications" is set to true. When trying to start the webapp without a database connection, it works. But when loading SQLBase Client with Gupta .NET dataprovider, the IIS process stops an windows eventlog shows the following error:
=== Eventlog entry ===
Protokollname: Application
Quelle: Application Error
Datum: 16.12.2009 10:15:09
Ereignis-ID: 1000
Aufgabenkategorie:(100)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: WIN2008-CERTSRV
Beschreibung:
Name der fehlerhaften Anwendung: w3wp.exe, Version: 7.5.7600.16385, Zeitstempel: 0x4a5bcd2b
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.1.7600.16385, Zeitstempel: 0x4a5bdb3b
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000cdcbb
ID des fehlerhaften Prozesses: 0xca8
Startzeit der fehlerhaften Anwendung: 0x01ca7e304359d212
Pfad der fehlerhaften Anwendung: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Pfad des fehlerhaften Moduls: C:\Windows\SysWOW64\ntdll.dll
Berichtskennung: 816cf81c-ea23-11de-8b55-0024212e319d
=== end ===
We urgently need a solution for this problem. In other case we must recommend to our customers to use MS SQLServer or Oracle on X64-Systems.
Thanks for your help,
Matthias Schölzel
Problems with .NET Dataprovider on Windows Server 2008 X64
Re: Problems with .NET Dataprovider on Windows Server 2008 X64
Hi Matthias,
Did you get this worked out? Have you tried the .NET driver from SB11.5? Please let me know if you don't have access to this driver and I will get it to you.
Best regards,
Mike
Did you get this worked out? Have you tried the .NET driver from SB11.5? Please let me know if you don't have access to this driver and I will get it to you.
Best regards,
Mike
Re: Problems with .NET Dataprovider on Windows Server 2008 X64
Hello Mike,
the problem is still there. It is not possible to access a SQLBase from an ASP.NET application on a 64 bit Windows 2008 Server. I tried to use the latest .NET dataproviders for SQLBase 11.5 and the DLL "Unify.SQLBase.Data" instead of "Gupta.SQLBase.Data". Then IIS process is not shut down, but other server errors occur:
"Unify.SQLBase.Data.SQLBaseException" - Failed to fetch next row in the result set.
Additional SQLBase message:
10446 SQL UBC Unicode conversion failed.
Reason: Failed to convert input( or output) buffer to (or from) Unicode format.
Remedy: None.
I think, I am not the only one suffering under these problems. I found this article here:
https://support.guptatechnologies.com/supportforum/viewtopic.php?f=38&t=2462
So all the problems are older than one year and still no fix in sight... As Windows Server 2008 R2 only exists as a 64bit version it is unacceptable that Unify does not provide customers with running 64bit versions of SQLBase neither with a running .NET Dataprovider that also works with IIS7 in an ASP.NET environment.
Regards,
Matthias
the problem is still there. It is not possible to access a SQLBase from an ASP.NET application on a 64 bit Windows 2008 Server. I tried to use the latest .NET dataproviders for SQLBase 11.5 and the DLL "Unify.SQLBase.Data" instead of "Gupta.SQLBase.Data". Then IIS process is not shut down, but other server errors occur:
"Unify.SQLBase.Data.SQLBaseException" - Failed to fetch next row in the result set.
Additional SQLBase message:
10446 SQL UBC Unicode conversion failed.
Reason: Failed to convert input( or output) buffer to (or from) Unicode format.
Remedy: None.
I think, I am not the only one suffering under these problems. I found this article here:
https://support.guptatechnologies.com/supportforum/viewtopic.php?f=38&t=2462
So all the problems are older than one year and still no fix in sight... As Windows Server 2008 R2 only exists as a 64bit version it is unacceptable that Unify does not provide customers with running 64bit versions of SQLBase neither with a running .NET Dataprovider that also works with IIS7 in an ASP.NET environment.
Regards,
Matthias
Re: Problems with .NET Dataprovider on Windows Server 2008 X64
Hi Matthias,
I would like to take this offline with you. Please contact me at mike.vandine@guptatechnologies.com.
Best regards,
Mike
I would like to take this offline with you. Please contact me at mike.vandine@guptatechnologies.com.
Best regards,
Mike
Re: Problems with .NET Dataprovider on Windows Server 2008 X64
Can you please give some information about the state of x64 and SQLBase .NET Dataprovider? Is there a integration planned in future?
Re: Problems with .NET Dataprovider on Windows Server 2008 X64
We will have 64bit SQLBase drivers (NDP, OLE DB, ODBC) coming with SQLBase 11.6 later this year.
Best regards
Best regards
Who is online
Users browsing this forum: [Ccbot] and 0 guests