Del,
I don't have precious info now: I can tell you I tried using two different
dotnet ODBC classes, the old Microsoft.Data.ODBC (which was to download as a
separate dll, because not part of framework 1.0) and System.Data.ODBC, then
added to framework 1.1. And the error occurs with both.

The strange thing is my app has been running for months on framework 1.0
without this kind of problems; when recompiled on 1.1 I started having these
problems, so that I'll try to go back to 1.0 as soon as I find a pc to test
this (don't want to install the old Visual Studio on my pc, where I'm using
VS 2003, because I'm sure it would break something!).
I'm not sure this could solve, but this should be quicker to test than
trying to modify psqlodbc.

It would be interesting to understand if anybody gets such an error without
using aspnet or dotnet in general, so to exclude or confirm this is a dotnet
problem and not psqlodbc.
Can anybody help?

Bye,
Al.



-----Original Message-----
From: Del Stoliker [mailto:dstoliker@alphagraphics.com]
Sent: giovedì 9 giugno 2005 17.33
To: Alberto Velo
Cc: pgsql-odbc@postgresql.org
Subject: RE: [ODBC] ODBC Error in logs

> Del,
> this is the same error I have - see my previous post - with my ASPnet app.
> I
> thought it could be a dotnet framework bug (odbc classes), but you're not
> using .net are you?
>
> Al.

Hi Al,

Actually, yes, the Altiris tools make extensive use ASPNET. I googled
around a bit and noticed that there are people using the mysql odbc drivers
with .net apps having similar problems. So... maybe it is a .net bug -
which I have to admit I'm bummed about. I think the chances of getting this
fixed if it was a problem with the odbc driver are much better than getting
MS to fix something so it works with open source odbc drivers.

If you have any other insights on how to get this working I'd sure
appreciate it. I've had to pull this piece out of production since it keeps
crashing our server.

Thanks,

Del


>
> -----Original Message-----
> From: Del Stoliker [mailto:dstoliker@alphagraphics.com]
> Sent: mercoledì 8 giugno 2005 16.41
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] ODBC Error in logs
>
> Hi, I recently installed psqlobbc-08_00_0101 on a Windows 2000 Server box.
> We're getting an error showing up in the Event Viewer:
>
> Event Type: Error
> Event Source: COM+
> Event Category: SVC
> Event ID: 4194
> Date: 6/6/2005
> Time: 4:45:03 PM
> User: N/A
> Computer: [COMPUTER NAME]
> Description:
> The system has called a custom component and that component has failed and
> generated an exception. This indicates a problem with the custom
> component.
> Notify the developer of this component that a failure has occurred and
> provide them with the information below.
> Component Prog ID: 0[ODBC][Env 12d514e8]
> Method Name: IDispenserDriver::CreateResource
> Process Name: aexsvc.exe
> The serious nature of this error has caused the process to terminate.
> Exception: C0000005
> Address: 0x12EAFFEF
> Call Stack:
> psqlodbc!SQLGetDiagFieldW + 0x29F
>
> We're running PostgreSQL 8.0.1 on a Fedora server. If it matters,
> "aexsvc.exe" is part of the Altiris suite of tools.
>
>
> Thanks,
>
> Del
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)


---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend