By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,282 Members | 1,569 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,282 IT Pros & Developers. It's quick & easy.

VC++ (v5sp3) components failing no Server 2003/ msvcrt.dll / oleaut32.dll

P: n/a
I have a problem with some VC++ (v5 sp3 compiled in debug mode) server
component which perfrom Data Acces. These have been in production on
NT4.0 and w2k. However when we try to use them on Server 2003 we only
get partial functionality. So far we have noticed that when the
components are returning large set of data that they fail. The
following errors are entered in the Event Log and point to msvcrt.dll
and oleaut32.dll. In this caseFinParticipantDA.exe is the server
component which fails.

 Category: (100)
Type: Error
Event_ID: 1000
User: N/A
Faulting application FinParticipantDA.exe, version 0.0.0.0, faulting
module *msvcrt.dll*, version 7.0.3790.1830, fault address 0x00038efa.

 Category: (100)
Type: Error
Event_ID: 1000
User: N/A
Faulting application FinParticipantDA.exe, version 0.0.0.0, faulting
module *oleaut32.dll*, version 5.2.3790.1830, fault address 0x0000476b

See below for version differences in MSVCRT.dll and OLEAUT32.dll:
Windows 2000 Windows 2003
MSVCRT.dll 6.01.9844.0000 7.00.3790.1830
OLEAUT32.dll 2.40.4522.0000 5.02.3790.1830

We have tried DLL redirects, side-by-side, manifest file, and our best
attempt at statically linking the DLLs. Nothing has worked so far.

In tracing the code....there is some concern with the use of BSTR and
t_bstr_t. We have as suspects memory mangement, string functions, etc.

Does anyone have advice/input/ideas on how to work this out? Originally
I was trying to isolate the DLLs (staticallylink, etc), but had little
success (other than breaking it more). I would be curious as to other
experience with this? I now am now more suspect this may be an issue of
old code being running into Microsoft's new security enhancements
(handling buffer over runs, memory management, etc).

Mar 7 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.