Application install built with VS damages SQL Server installation

[Andrew Wiles]

Hi

I have an application which (along with many other things) uses the COM
interop classes for "Microsoft Decision Support Objects" (DSO). I have done
no more than included the DSO components as a reference. Prior to including
these I have made heavy use of the ADO classes (yes I know that ADOMD.Net
has recently surfaced :-)

For this application I have built an install package in Visual Studio .Net
2003.

After I install the application using this install package if I make use of
the features that use DSO, or if I open Analysis Manager and attempt to
carry out any normal AS task I am getting the following dialog displayed
multiple times.

"Could not find msmdso.rll in '<application path>\resources\1033\'."

This looks like a registration problem but when I check the registration for
msmdso.rll it looks fine (i.e. points to the resources\1033 directory in the
Analysis services installation.

Does anyone have any idea where to start in locating the reason for this
problem!

Andrew Wiles

[Andrew Wiles]

OK - a bit more information

Somehow I have a copy of DSO version 5.1 registered to the <application
path>\resources\1033 location

I have no idea how this could have happened as I have not been trying to do
anything regarding re-distribution/registration of DSO.
"Andrew Wiles" <aj*@nospam.please> wrote in message
news:Ob**************@TK2MSFTNGP10.phx.gbl...

Hi

I have an application which (along with many other things) uses the COM
interop classes for "Microsoft Decision Support Objects" (DSO). I have done no more than included the DSO components as a reference. Prior to including these I have made heavy use of the ADO classes (yes I know that ADOMD.Net
has recently surfaced :-)

For this application I have built an install package in Visual Studio .Net
2003.

After I install the application using this install package if I make use of the features that use DSO, or if I open Analysis Manager and attempt to
carry out any normal AS task I am getting the following dialog displayed
multiple times.

"Could not find msmdso.rll in '<application path>\resources\1033\'."

This looks like a registration problem but when I check the registration for msmdso.rll it looks fine (i.e. points to the resources\1033 directory in the Analysis services installation.

Does anyone have any idea where to start in locating the reason for this
problem!

Andrew Wiles

[Andrew Wiles]

Further to this thread of investigation if I manually re-register
msmdso80.dll all is well.

However each time I re-apply my VS generated application install it is
always re-registering DSO to the wrong location!?

I have to say that I would not expect the application install to attempt to
register DSO although I may be missing something due to the fact that this
is a redistributable package??

"Andrew Wiles" <aj*@nospam.please> wrote in message
news:ep**************@TK2MSFTNGP09.phx.gbl...

OK - a bit more information

Somehow I have a copy of DSO version 5.1 registered to the <application
path>\resources\1033 location

I have no idea how this could have happened as I have not been trying to do anything regarding re-distribution/registration of DSO.
"Andrew Wiles" <aj*@nospam.please> wrote in message
news:Ob**************@TK2MSFTNGP10.phx.gbl...

Hi

I have an application which (along with many other things) uses the COM
interop classes for "Microsoft Decision Support Objects" (DSO). I have

done

no more than included the DSO components as a reference. Prior to

including

these I have made heavy use of the ADO classes (yes I know that ADOMD.Net has recently surfaced :-)

For this application I have built an install package in Visual Studio ..Net 2003.

After I install the application using this install package if I make use

of

the features that use DSO, or if I open Analysis Manager and attempt to
carry out any normal AS task I am getting the following dialog displayed
multiple times.

"Could not find msmdso.rll in '<application path>\resources\1033\'."

This looks like a registration problem but when I check the registration

for

msmdso.rll it looks fine (i.e. points to the resources\1033 directory in

the

Analysis services installation.

Does anyone have any idea where to start in locating the reason for this
problem!

Andrew Wiles