THis has happened to a few people. Possible solution is at http://forums.nbn.org.uk/viewtopic.php?id=2926 about 4 posts down

I am not sure about this and we will need to try a few things. Is it just this and the NBN and Phenology addins which are causing the problems. If so it could be permissions, because both these addins modify the database. Have you tried installing any other addins and if so did they work ? If not can you try removing one of the standard addins (say update last key) and reinstalling it.  You can remove an addin via tools/Install/addin Module/Remove. Close Recorder open it again and then try to reinstall the addin via tools/Install/addin Module/Install. You can find the addin file in the addin folder of R6 (eg LastkeyUpdate.ocx).  If this works then the problem is not in the registration of the addins, but in the addins themselves.  As a first step can you please try this and let me know how you get on.

 
We also know that some anti virus software will not let the addins in  – it may be sitting in quarantine

Mike

Thanks. The fact that at least one addin instlalled suggest that it is not in the .dll, which  is good news. Looks like it might be a permission problem in writing to the files.   If you look in the folder is the LastKeyUpdate.ocx file there ?   If it isn't can you see if you edit files in this folder. There should be one or two Readme text files in there which you could try opening in notepad and saving again.

This looks to me to be a permissions problem. You can write to the files, so this suggests it is  something to do with writing to the registry or with registry entries. This would fit  with you being able to install an existing entry, but not a new one. Can you check with your IT dept to see if this might be the problem. 

Have yiu checked the registry as in John's post  http://forums.nbn.org.uk/viewtopic.php?id=2926

One more thought - might you have used a different drive mapping or UNC path to get to the addin file to install, compared to the one in your registry? The registry setting is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dorset Software\Recorder 6 - Addin Path. Ignore the Wow6432Node bit of the path if you are on a 32 bit Windows.

We had this problem. It was an anti-virus thing. See my moment of revelation on this thread (post 9):

http://forums.nbn.org.uk/viewtopic.php?id=1021

You probably need to get the ICT department stop the anti-virus quarantining the addins.

We now seem to have solved the problem; the addin needs to be saved to the add-ins folder in Recorder 6. This is contrary to the instructions in the ReadMe (with the Add in Unpack the files from the supplied .zip file to some convenient directory accessibleby the computer running Recorder 6 (but NOT to the Recorder\Addins directory!))

Howver this location does come up in one of the suggested solutions in the forum threads at http://forums.nbn.org.uk/viewtopic.php?id=2926 post#4

Hi,

Bouncing this thread as I'm also having trouble installing AddIns on a 32-bit Windows 7 workstation.

Also getting the ‘The specified file is not a COM server and cannot be registered’ and ‘The following addin has been successfully installed: [name_of_addin]’.

I've checked as many threads on here as I can find, checked the Registry settings (paths and path formatting), ensured DLL files are registered, run RecorderSystemCheck.exe without any errors, put the OCX file in the Addins directory and I can't fix the problem.

I am an administrator on the workstation. Recorder fails to run at all if I Run As Administrator. I get an exception "The DTD Path setting is missing or incorrect. Recorder is not installed properly and cannot start."

Everything works happily on the W2003 Server.

Any ideas?

Les.