[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 413
  • Last Modified:

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

Hi

Urgent help needed.

I have taken over a vb.net 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
{2A75196C-D9EB-4129-B803-931327F72D5C}\2.8\0\tlbimp
C:\InfoMatic\Noble\NobleServ\NobleServer\obj\Interop.ADODB.dll

Many thanks

Hylton
0
tcss
Asked:
tcss
2 Solutions
 
RobertRFreemanCommented:
The interop.ADODB.dll requires ADODB.dll, ensure this is also installed on that machine.

Ideally your project would use ado.net (throught the .net library) to do data access.
This must be a converted vb 6 app.
0
 
toddhdCommented:
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:

http://support.microsoft.com/?kbid=870669
http://www.microsoft.com/downloads/details.aspx?FamilyID=4D056748-C538-46F6-B7C8-2FBFD0D237E3&DisplayLang=en
http://www.microsoft.com/security/incident/download_ject.mspx

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.
0
 
tcssAuthor Commented:
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.

tcss
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now