Welcome to the party, pal. I've been fighting with the same problem
for a while and so have a ton of other people. It's all documented on
my blog with a tutorial for creating an Excel Automation Addin with a
shim for COM to call managed functions from formulas. Wish someone
from Microsoft would stick their head into this - it does us no good
to develop code that we can't deploy.
remove.pleaseNebula-RnD.com/
blog/tech/2007/11/excel-tools5.html
If you're using the COM Shim Wizard, check out Andrew Whitechapel's
recent blog entry on a bug fix. I haven't had time to try it but it
could be the solution to all of these problems.
http://blogs.msdn.com/ andreww/archive/2007/11/25/com-shim-clr-loader-bug.aspx
HTH
[quoted text, click to view] "Waldy" wrote:
>Hi there,
> I have written a COM enabled .Net 2.0 library which works fine
>on the machine that I wrote it on. However, when I deploy it on a customers
>2003 server and try and use it, I get the following error:
>
>The remote server machine does not exist or is unavailable.
>
>Why does it think that the library is on a remote machine? I have tried to
>register it using regasm with /codebase and /tlb options, but it makes no
>difference.
See if this helps:
http://www.simple-talk.com/dotnet/visual-studio/build-and-deploy-a-.net-com-assembly/
In my experience it's invaluable to understand what's actually going on when
a client calls into your code, and what the CLSID entries are supposed to
look like. That message could actually be correct, depending on what the
client caller is doing (like a CreateObject with a machine name in it).
--
Phil Wilson
[MVP Windows Installer]
[quoted text, click to view] "Waldy" <someone@microsoft.com> wrote in message
news:e1gpSO1MIHA.5040@TK2MSFTNGP04.phx.gbl...
> Hi there,
> I have written a COM enabled .Net 2.0 library which works
> fine on the machine that I wrote it on. However, when I deploy it on a
> customers 2003 server and try and use it, I get the following error:
>
> The remote server machine does not exist or is unavailable.
>
> Why does it think that the library is on a remote machine? I have tried
> to register it using regasm with /codebase and /tlb options, but it makes
> no difference.
>
>
>