Difference in 'ADODB.Stream' on Server 2003 vs Windows XP

Posted on 2005-04-27
Last Modified: 2012-06-21

Urgent help needed.

I have taken over a project developed with VS 2002.
A portion of the project uses CDo for messages.
The original is written and compiled on an XP Pro machine.
The deployment environment is windows Server 2003.
The app has crashed constantly on the deployment machine. In desperation I installed VS 2002 on the deployment machine and copied the source there to. (Whole solution)

The IDE shows up the following error (possibly the reason for the instant crash on startup).
C:\Development\NobleServ\messageStore\frmShow.vb(527): Reference required to assembly 'ADODB' containing the type 'ADODB.Stream'. Add one to your project.
This is not hapeening the the SP nachine.

How do I go about fixing this. All the references are the same including
Microsoft ActiveX Data Objects 2.8 Library

Many thanks

Question by:tcss
    LVL 16

    Accepted Solution

    The interop.ADODB.dll requires ADODB.dll, ensure this is also installed on that machine.

    Ideally your project would use (throught the .net library) to do data access.
    This must be a converted vb 6 app.
    LVL 8

    Assisted Solution

    I'm not sure you can. MS released a patch for Windows 2000/XP machines due to a security vulnerability regarding ADODB.Stream. See Here:

    Anyway, which in 2000/XP you can simply remove the patch, it is "built in" to Server 2003, and apparantly is sticker then simply removing a patch or altering a registry key. It may still be possible? But I haven't found the solution yet. Moreover, sounds like something you shouldn't mess with anyway... you might need to work-around it.
    LVL 1

    Author Comment

    Got it fixed late last night. It appeared that I may have been refering to different adodb.dll's in various parts of the solution. After checking all dependancies etc I got it to compile on 2003. When moved back to XP the problem resurfaced again. Took a flier by  fixing it on XP and  installing the app (release build) on 2003. It is working now. Hope I have not overlooked anything that causes it to break when client app again.

    Many thanks for the input. As I have said, it is working but the fog has not completly cleared.


    Featured Post

    Threat Intelligence Starter Resources

    Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

    Join & Write a Comment

    A while ago, I was working on a Windows Forms application and I needed a special label control with reflection (glass) effect to show some titles in a stylish way. I've always enjoyed working with graphics, but it's never too clever to re-invent …
    Parsing a CSV file is a task that we are confronted with regularly, and although there are a vast number of means to do this, as a newbie, the field can be confusing and the tools can seem complex. A simple solution to parsing a customized CSV fi…
    It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
    Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

    732 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    22 Experts available now in Live!

    Get 1:1 Help Now