Software conflict

[DrSmyth]

Hi,

Been racking my brain over this for a couple of weeks so thought it was time to ask for help... A bit of an overview first:

We've been running Business Objects for a couple of years now, our platform is windows NT4 and the main database we deal with is on a DB2 platform, we use IBM CAE middleware. We also have a custom built application that has been made from VB and is used as a front end for the DB2 database and is called TAPS. This is generally a fairly smooth running operation.

However, we have just expanded to another department at the other end of the country and things are not quite as smooth. After a few teething problems we managed to get Business Objects fully operational on several PC's, but as soon as we got BO operational there was a problem with TAPS. Basically we can't get both pieces of software to work at the same time. As far as i can see, there configuration is the same as ours, except that they are using our repository which is obviously not on there LAN (it's on ours).

As soon as somebody tries to log onto TAPS on a PC that also has BO, they are given a "Class does not support automation or does not support expected interface" error.

I initially tried raising it with BO tech support, but they will not attempt a resolution due to the fact that the conflict is with a custom built piece of software. I'm really looking for any ideas that anybody has about what might be causing this problem...

Thanks

Dr S

 

[DrSmyth]

Nearly forgot, we are currently on version 6.1a of Business Objects

 

[balves]

Generally speaking, it's a DLL Hell problem. BOBJ and TAPS are installing different versions of a crucial DLL. Since you're talking NT, it's probably that the TAPS kit has an older version of the DLL or DLLs than the BOBJ kit.

One of the most common mismatches is in the MDAC software - Microsoft Data Access. The Microsoft KB has several articles on this problem, like this one:

http://support.microsoft.com/default.aspx?scid=kb;en-us;248404

Since you cannot modify the BOBJ distribution kit, you probably need to modify/rebuild the TAPS kit, like:

- find out the version of the DLLs in the TAPS kit and compare them against the same DLLs in the BOBJ kit. Build the TAPS kit with the same version.
- install the TAPS DLLs in the local directory of the TAPS software, not in WINDOWS or WINDOWS\SYSTEM, so that TAPS will find the local version first.

 

[DrSmyth]

Balves,

Thanks for the suggestion, I've forwarded this onto our Support people (Afraid the resolution looks a bit over my ability) and I'll let you know how they get on..

Thanks again for your help though!

Dr S

 

[DrSmyth]

Hi Balves.... Seems to have sorted the problem... Not sure what they did, but they soon got it fixed after your e-mail...