Dear Excel Gurus

resolved prior issue with non-updating excel RTD satisfactorily, to find
that rolling out the DLL to client machines is somewhat patchy. Some
machines work fine, some not.

RTD server is in VB.NET 2005. Visual Studio 2005 and .NET up to 3.0 on
the development machine (on which it works fine). Tried this on two
machines with .NET 3.5 installed and works fine on there too (with DLL
copied into Excel directory and a registry settings script run - the
latter generated from regasm on the development machine). One of these
machines has Excel 2003, the other both 2003 and 2007, all working fine
with the RTD server.

Trying this on two other machines gives "#N/A", indicating some RTD
issue. Got this intially on machine with only up to .NET 2.0 installed
(Excel 2003). Upgraded the machine to .NET 3.5. Same result.
Reregistered the DLL and rebooted. Same result. Using some VBA to
Application.RTD.RestartServers results in "Run-time error '1004': The
format of the file '[dll name]' is invalid.".

The development machine's registry lists a 'CodeBase' component for the
registry entries for the DLL that the other machines do not.

Any suggestions?

Thanks, Craig

Hello Craig,

Were you able to find a solution to your problem below. I am facing exactly the same issue.

Please do reply back if possible.

Thanks, Shri

On Wednesday, July 23, 2008 7:43 AM Craig Burton wrote:

Dear Excel Gurus

resolved prior issue with non-updating excel RTD satisfactorily, to find
that rolling out the DLL to client machines is somewhat patchy. Some
machines work fine, some not.

RTD server is in VB.NET 2005. Visual Studio 2005 and .NET up to 3.0 on
the development machine (on which it works fine). Tried this on two
machines with .NET 3.5 installed and works fine on there too (with DLL
copied into Excel directory and a registry settings script run - the
latter generated from regasm on the development machine). One of these
machines has Excel 2003, the other both 2003 and 2007, all working fine
with the RTD server.

Trying this on two other machines gives "#N/A", indicating some RTD
issue. Got this intially on machine with only up to .NET 2.0 installed
(Excel 2003). Upgraded the machine to .NET 3.5. Same result.
Reregistered the DLL and rebooted. Same result. Using some VBA to
Application.RTD.RestartServers results in "Run-time error '1004': The
format of the file '[dll name]' is invalid.".

The development machine's registry lists a 'CodeBase' component for the
registry entries for the DLL that the other machines do not.

Any suggestions?

Thanks, Craig