We have a program that uses the office partner components for doing mail merges, running on a local pc it works fine, running under terminal server we get a 'No Such Interface Supported' message, unless you are logged in as the administrator.
I don't know Office partner, but I am running my D5 app with Crystal Reps. on a Citrix server. I'm also no expert with Terminal servers but here's what I've learnt. You have to ensure that all the users can see the relevant files,Dll's etc. to run the app as normal. I'm guessing that you need to give users Read access to the Office Partner dir/s. I had to give all the users read access to the System directory on the Term.Serv. as this is where Crystal had all it's files.
We have given all users full access to the folders, following a bit of playing around with the office partner source code it turns out that the error is produced by a call to CoCreateInstance, this is returning the result Interface Not Supported. As far as I can tell all of the registry entries for calls to setvalue have full access to all users, logically as there are around 4000 registry commands from this one api call I have not been able to check for sure that the users have read access to all the rest of the registry values, but think they do.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.