MSScript control problem...

[user]

I have several vb.net apps that use the MSScript control to provide
basic scripting. On one machine in particular, these apps refuse to
start, stating:

An Unhandled exception of type 'System.IO.FileNotFoundException'
occurred in MyApp.exe
Additional information: File or assembly name AxInterop.MSScriptControl,
or one of its dependencies, was not found.

Although the entire app directory contains everything, including the
script control, the app bombs with this error only on one machine out of
several. How can I check to see what dependencies the MSScript control
needs, and narrow down my search for problems?

-Sam

[Herfried K. Wagner [MVP]]

* us**@domain.invalid scripsit:

I have several vb.net apps that use the MSScript control to provide
basic scripting. On one machine in particular, these apps refuse to
start, stating:
An Unhandled exception of type 'System.IO.FileNotFoundException'
occurred in MyApp.exe

Additional information: File or assembly name
AxInterop.MSScriptControl, or one of its dependencies, was not found.
Although the entire app directory contains everything, including the
script control, the app bombs with this error only on one machine out
of several. How can I check to see what dependencies the MSScript
control needs, and narrow down my search for problems?

Are you sure the control is properly registered on the computer? It's a
COM component, so run "REGASM.EXE".

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[user]

Herfried K. Wagner [MVP] wrote:

Are you sure the control is properly registered on the computer? It's a
COM component, so run "REGASM.EXE".

Actually, I left out a bit of info: The app is stored on a linux server,
although it is "run" from a windows box. The app's entire install was
"moved" from a window box to a linux server, which worked perfectly. The
exe is seen from the windows machine, and run from there. We recently
purchased a new linux server, nearly identical to the first, and when
the app was moved this problem began. If we move it back, it runs fine.
We're at a loss as to why it only fails on the second linux server.
There are no other apps or ocxs or anything on the first linux box.

The app does run fine locally on the windows box as well.

This is quite the mystery.....

[Herfried K. Wagner [MVP]]

* us**@domain.invalid scripsit:

Actually, I left out a bit of info: The app is stored on a linux
server, although it is "run" from a windows box. The app's entire
install was "moved" from a window box to a linux server, which worked
perfectly. The exe is seen from the windows machine, and run from
there. We recently purchased a new linux server, nearly identical to
the first, and when the app was moved this problem began. If we move
it back, it runs fine. We're at a loss as to why it only fails on the
second linux server. There are no other apps or ocxs or anything on
the first linux box.

Just for clarification: You try to run the app on a Windows machine,
but the app is physically placed on a Lin*x machine? You will still
have to run "REGASM" for the Script Control.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[user]

Herfried K. Wagner [MVP] wrote:

Just for clarification: You try to run the app on a Windows machine,
but the app is physically placed on a Lin*x machine? You will still
have to run "REGASM" for the Script Control.

Correct. Hm....I guess I was thinking that the local registration of the
scriptcontrol was enough.

Okay, I successfully registered the first file with
regasm \\linuxserver\Interop.MSScriptControl.dll

and tried the second file with

regasm \\linuxserver\AxInterop.MSScriptControll.dll

but it failed with the error:

RegAsm error: File or assembly name Interop.MSScriptControll, or one of
its dependencies, was not found.

A similiar error to the original problem.....is there a way to list what
these dependencies might be?